You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2014/06/20 15:05:24 UTC
[jira] [Created] (AMBARI-6219) Performance Issues When Parsing
structured_output From Agents
Jonathan Hurley created AMBARI-6219:
---------------------------------------
Summary: Performance Issues When Parsing structured_output From Agents
Key: AMBARI-6219
URL: https://issues.apache.org/jira/browse/AMBARI-6219
Project: Ambari
Issue Type: Bug
Affects Versions: 1.6.1
Environment: CentOS 6.4
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Blocker
Fix For: 1.6.1
TaskResourceProvider.parseStructuredOutput(...) uses Jackson to parse the structured_out of agent responses. In general, we should move to Gson and away from Jackson globally.
However, because of the ambiguous nature of the responses, there is no first-class object mapping for responses like java_home_check and host_resolution_check. Gson, in turn, will convert integers to float when there is no contract for it to map with. Jackson, although slower, will try to determine if the numbers are integers or floats first.
There are two solutions; either provide mappings for the various responses in structured_out so that Gson can correctly deserialize the JSON, or determine why Jackson is so slow.
--
This message was sent by Atlassian JIRA
(v6.2#6252)