[AMBARI-25912] Performance improvement when server handle agent heartbeat and registration

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.0
• Fix Version/s: 2.9.0
• Assignee: Jialiang Cai
• Reporter: Jialiang Cai
• Created: 24/Mar/23 03:03
• Updated: 21/Aug/23 03:14
• Resolved: 21/Aug/23 03:14

Description

The AgentRegisteringQueueChecker is an interceptor used during the long connection between the agent and server, mainly for requesting congestion control. It internally uses AgentsRegistrationQueue to store the sessionID of connections.

The sessionID is added to the AgentsRegistrationQueue when the ambari agent registers to the server or sends a heartbeat.

When the long connection between the agent and server is disconnected, or when the server completes the heartbeat request, the sessionID is removed from the AgentsRegistrationQueue.

When the queue is full, the server returns "not allowed" to the agent.

AgentsRegistrationQueue uses ArrayBlockingQueue, which uses the same lock for both writing and consuming, making it easy to negatively impact performance when dealing with large clusters. Therefore, we are switching to using LinkedBlockingQueue in order to improve performance.

Issue Links

• links to: GitHub PR#3672