You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2013/06/12 19:31:20 UTC

[jira] [Created] (AMBARI-2365) Use lock or concurrent hash map to store response and responseId for heartbeat

Sumit Mohanty created AMBARI-2365:
-------------------------------------

             Summary: Use lock or concurrent hash map to store response and responseId for heartbeat
                 Key: AMBARI-2365
                 URL: https://issues.apache.org/jira/browse/AMBARI-2365
             Project: Ambari
          Issue Type: Bug
          Components: controller
    Affects Versions: 1.2.5
            Reporter: Sumit Mohanty
            Assignee: Sumit Mohanty
             Fix For: 1.2.5


{code}
private Map<String, Long> hostResponseIds = new HashMap<String, Long>();
  private Map<String, HeartBeatResponse> hostResponses = new HashMap<String, HeartBeatResponse>();
{code}

Noticed spurious re-registrations because the responseId from agent was not recognized by the server. It seems to be due to lack of synchronization around the above fields considering multiple threads may modify the map.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira