-
Task
-
Resolution: Done
-
Medium
This is a question about C++ container startup time.
Observation:
An empty CPP Container on an idle machine takes 3
whole seconds to start.
How to repeat this:
In CTA we are currently working with ACS-2020AUG.
- CDB = `/alma/ACS-2020AUG/acsdata/config/defaultCDB/`
- `acsStart`
- `acsStartContainer -b 0 --cpp --name foobarbazoo`
Please observe in the container logs how between:
[foobarbazoo-GL - maci::ContainerThreadHook::initThread] ContainerThreadHook initiailized
and
ContainerStatusMsg: Automatic component loading begins
during 3 seconds it simply is waiting.
2021-06-28T07:04:50.294 [foobarbazoo - maci::ContainerImpl::init] Logging into the Manager...
|
2021-06-28T07:04:50.310 [foobarbazoo - maci::ContainerImpl::init] Logged into the Manager.
|
ContainerStatusMsg: Manager access initialization ends
|
ContainerStatusMsg: Startup ends
|
2021-06-28T07:04:50.311 [foobarbazoo - ContainerImpl::run] Container running...
|
2021-06-28T07:04:50.311 [foobarbazoo-GL - maci::ContainerThreadHook::initThread] ContainerThreadHook initiailized
|
2021-06-28T07:04:50.311 [foobarbazoo-GL - maci::ContainerThreadHook::initThread] ContainerThreadHook initiailized
|
2021-06-28T07:04:50.311 [foobarbazoo-GL - maci::ContainerThreadHook::initThread] ContainerThreadHook initiailized
|
2021-06-28T07:04:50.311 [foobarbazoo-GL - maci::ContainerThreadHook::initThread] ContainerThreadHook initiailized
|
2021-06-28T07:04:50.311 [foobarbazoo-GL - maci::ContainerThreadHook::initThread] ContainerThreadHook initiailized
|
2021-06-28T07:04:50.311 [foobarbazoo-GL - maci::ContainerThreadHook::initThread] ContainerThreadHook initiailized
|
ContainerStatusMsg: Automatic component loading begins
|
2021-06-28T07:04:53.316 [foobarbazoo - maci::ContainerImpl::taggedmessage] Message from manager received. Type: 20. Tag: 1. Message: Startup statistics: 0 components queued to be activated.
|
2021-06-28T07:04:53.326 [foobarbazoo - maci::ContainerImpl::taggedmessage] Message from manager received. Type: 20. Tag: 2. Message: Startup statistics: 0 of 0 components activated.
|
ContainerStatusMsg: Automatic component loading ends
|
ContainerStatusMsg: Ready
|
The manager logs during this time look like this:
2021-06-28T07:04:50.145 INFO [Manager] Request for component 'curl:///CDB' issued.
|
2021-06-28T07:04:50.147 INFO [Manager] Component 'curl:///CDB' provided.
|
45032 INFO ServerIIOPConnection - Opened new server-side TCP/IP transport to 172.18.0.2:33809
|
2021-06-28T07:04:50.174 NOTICE [CDB] Curl 'MACI/Containers/foobarbazoo' does not exist.
|
45070 INFO ServerIIOPConnection - Closed server-side transport to 172.18.0.2:33809
|
45083 INFO ServerIIOPConnection - Opened new server-side TCP/IP transport to 172.18.0.2:39397
|
2021-06-28T07:04:50.203 INFO [Manager] Request for component 'curl:///CDB' issued.
|
2021-06-28T07:04:50.206 INFO [Manager] Component 'curl:///CDB' provided.
|
2021-06-28T07:04:50.286 INFO [Manager] Request for component 'curl:///NameService' issued.
|
2021-06-28T07:04:50.286 INFO [Manager] Component 'curl:///NameService' provided.
|
2021-06-28T07:04:50.289 INFO [Manager] Request for component 'curl:///Log' issued.
|
2021-06-28T07:04:50.292 INFO [Manager] Component 'curl:///Log' provided.
|
2021-06-28T07:04:50.294 INFO [Manager] Request for component 'curl:///NameService' issued.
|
2021-06-28T07:04:50.294 INFO [Manager] Component 'curl:///NameService' provided.
|
2021-06-28T07:04:50.298 FINER [alma.acs.logging] Changed processName='Manager' to 'Manager-ContainerProxy' and updated logger names.
|
2021-06-28T07:04:50.307 FINE [Manager] 'foobarbazoo' is logging in.
|
2021-06-28T07:04:50.310 INFO [Manager] Container 'foobarbazoo' logged in.
|
2021-06-28T07:04:50.310 FINE [Manager] Client with handle 'Handle (0x4a90001) = { type = CONTAINER, key = (0xa9), id = (0x1) }' has logged in.
|
2021-06-28T07:04:53.312 INFO [Manager] Container 'foobarbazoo' startup statistics: 0 components queued to be activated.
|
2021-06-28T07:04:53.323 INFO [Manager] Container 'foobarbazoo' startup statistics: 0 of 0 components activated.
|
To me this seems to be a 3sec timeout, where something is waiting for something and gives up after 3seconds. I would like to know:
- who is waiting for what here? Is there a service supposed to be up, which is not up in my case? So can I do something to remove this waiting period entirely?
- IF NOT: is this timeout configurable? Can I set it to 0.1sec?
Thanks for you help.