sureshanaparti opened a new pull request, #13028:
URL: https://github.com/apache/cloudstack/pull/13028

   ### Description
   
   This PR improves the Indirect agent connection handling, has the following 
improvements.
   
   - Enhances the Host connecting logic to avoid connecting storm (where Agent 
opens multiple sockets against Management Server).
   - Implements HostConnectProcess task where Host upon connection checks 
whether lock is available, traces Host connecting progress, status and timeout.
   - Introduces AgentConnectStatusCommand, where Host checks whether lock for 
the Host is available (i.e. "previous" connect process is finished).
   - Implementes logic to check whether Management Server has lock against Host 
(exposed MySQL DB lock presence via API)
   - Removes synchronization on Host disconnect process, double-disconnect 
logic in clustered Management Server environment, added early removal from ping 
map (in case of combination ping timeout delay + synchronized disconnect 
process the Agent Manager submits more disconnect requests)
   - Introduces parameterized connection and status check timeouts
   - Implements backoff algorithm abstraction - can be used either constant 
backoff timeout or exponential with jitter to wait between connection Host 
attempts to Management Server
   - Implements ServerAttache to be used on the Agent side of communication 
(similar to Attache on Management Server side)
   - Enhances/Adds logs significantly to Host Agent and Agent Manager logic to 
trace Host connecting and disconnecting process, including ids, names, context 
UUIDs and timings (how much time took overall initialization/deinitialization)
   - Adds logs to communication between Management Servers (PDU requests)
   - Adds DB indexes to improve search performance, uses IDEMPOTENT_ADD_INDEX 
for safer DB schema updates
   
   
   <!--- Describe your changes in DETAIL - And how has behaviour functionally 
changed. -->
   
   <!-- For new features, provide link to FS, dev ML discussion etc. -->
   <!-- In case of bug fix, the expected and actual behaviours, steps to 
reproduce. -->
   
   <!-- When "Fixes: #<id>" is specified, the issue/PR will automatically be 
closed when this PR gets merged -->
   <!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" -->
   <!-- Fixes: # -->
   
   <!--- 
******************************************************************************* 
-->
   <!--- NOTE: AUTOMATION USES THE DESCRIPTIONS TO SET LABELS AND PRODUCE 
DOCUMENTATION. -->
   <!--- PLEASE PUT AN 'X' in only **ONE** box -->
   <!--- 
******************************************************************************* 
-->
   
   ### Types of changes
   
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [x] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   - [ ] Build/CI
   - [ ] Test (unit or integration test code)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Feature/Enhancement Scale
   
   - [x] Major
   - [ ] Minor
   
   #### Bug Severity
   
   - [ ] BLOCKER
   - [ ] Critical
   - [ ] Major
   - [ ] Minor
   - [ ] Trivial
   
   ### Screenshots (if appropriate):
   
   ### How Has This Been Tested?
   
   <!-- Please describe in detail how you tested your changes. -->
   <!-- Include details of your testing environment, and the tests you ran to 
-->
   
   #### How did you try to break this feature and the system with this change?
   
   <!-- see how your change affects other areas of the code, etc. -->
   
   <!-- Please read the 
[CONTRIBUTING](https://github.com/apache/cloudstack/blob/main/CONTRIBUTING.md) 
document -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to