vishesh92 opened a new issue, #8011:
URL: https://github.com/apache/cloudstack/issues/8011
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Improvement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Agent, ServerResource
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
All versions
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
N/A
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
N/A
##### SUMMARY
<!-- Explain the problem/feature briefly -->
The value for
[wait](https://github.com/apache/cloudstack/blob/main/api/src/main/java/com/cloud/agent/api/Command.java#L39)
set in Command is not honored by agents (SSVM, host agent, etc.) while
processing the request. These requests can also pile up if the same request is
sent multiple times because of retries by user or the management server itself.
This can potentially cause issues on SSVM and agents while executing long tasks
leading to high wait times for commands to get executed on host agents, ssvm,
etc.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
1. Add a sleep in a ssvm command for 60 seconds and a log line before and
after the sleep to check number of executions for that command.
2. Send 100 requests in parallel which will execute the above ssvm command
with cmd.setWait(5).
3. Check logs on ssvm to check the actual number of requests received.
Note: The above example is for a Command for which executeInSequence is
false.
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
If the request on management server times out in 5 seconds, the processing
of command on SSVM should stop after 5 seconds as well.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
The number of requests received on the SSVM would be executing these
requests in batches of 10 requests or so. The requests would still get
processed even if the server itself has timed out and no longer waiting for the
answer. You will the log for both before sleep and after sleep.
--
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]
