Windows service startup is noticeably slower for fluent-package.
I'm talking about the time to reach the Running state. In other words, the time to finish StartServiceCtrlDispatcher.
For td-agent, it takes about 5 seconds, but for fluent-package it can take more than 20 seconds.
Windows service needs to finish StartServiceCtrlDispatcher in 30 seconds by default.
So, this problem can cause timeout errors.
EventID 7000
The testservice service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
EventID 7009
A timeout was reached (30000 milliseconds) while waiting for the testservice service to connect.
Reproduce
If you try to start the service several times, it will often take 10 to 20 seconds.
Abst
Details
Windows service startup is noticeably slower for fluent-package. I'm talking about the time to reach the
Running
state. In other words, the time to finish StartServiceCtrlDispatcher. For td-agent, it takes about 5 seconds, but for fluent-package it can take more than 20 seconds.Windows service needs to finish StartServiceCtrlDispatcher in 30 seconds by default. So, this problem can cause timeout errors.
EventID 7000
EventID 7009
Reproduce
If you try to start the service several times, it will often take 10 to 20 seconds.
I confirm this problem in the following:
Interestingly, this problem does not occur in t2.small EC2 instance type. I think it occurs in environments with multiple CPUs.