Project

General

Profile

Bug #9848

Wrong agent startup time reported in logs

Added by Andrei Plugaru over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#1 Updated by Andrei Plugaru over 1 year ago

At the moment, the calculation for the agent's startup time is slightly incorrect. In AppServerLauncher.launchFirstAgents, some futures are created for each agent, however, each one of them is handled sequentially in handleLaunchResult. To be noted that in this method the logging with the startup time happens. The problem occurs in the situation when one agent takes longer to start, but the next ones start fast. Currently, as the startup time is calculated in handleLaunchResult, all the agents whose futures were processed after that laggy one, will report longer startup time than it was in reality.

A solution for that would be to do the logging right after the agent was started or failed. I think this can be done in the task for the future created in getLaunchWorkerFutures.

#3 Updated by Constantin Asofiei over 1 year ago

Please include in this task also stress-testing the appserver agent startup, i.e. launch 50-100 agents and see if they all start in a reasonable time.

Also available in: Atom PDF