JiriOndrusek
commented
3 years ago @ppalaga It seems, like the container didn't start correctly.
Here is my local log
2021-05-25 11:20:07,097 INFO [org.tes.DockerClientFactory] (pool-4-thread-1) ✔︎ Docker environment should have more than 2GB free disk space
2021-05-25 11:20:07,107 INFO [🐳 .0]] (pool-4-thread-1) Creating container for image: mongo:4.0
2021-05-25 11:20:07,459 INFO [🐳 .0]] (pool-4-thread-1) Starting container with ID: 4dcfebda5b25af00058f8dfe7045644521dd6e575d85afff0fbb44abe5f86287
2021-05-25 11:20:07,979 INFO [🐳 .0]] (pool-4-thread-1) Container mongo:4.0 is starting: 4dcfebda5b25af00058f8dfe7045644521dd6e575d85afff0fbb44abe5f86287
2021-05-25 11:20:09,195 INFO [🐳 .0]] (pool-4-thread-1) Container mongo:4.0 started in PT2.097561S
2021-05-25 11:20:09,972 INFO [org.mon.dri.cluster] (pool-4-thread-1) Cluster created with settings {hosts=[localhost:49154], mode=SINGLE, requiredClusterType=UNKNOWN, serverSelectionTimeout='30000 ms'}
2021-05-25 11:20:10,015 INFO [org.mon.dri.cluster] (pool-4-thread-1) Cluster description not yet available. Waiting for 30000 ms before timing out
2021-05-25 11:20:10,035 INFO [org.mon.dri.connection] (cluster-rtt-ClusterId{value='60acc14961fda01911b47ca5', description='null'}-localhost:49154) Opened connection [connectionId{localValue:2, serverValue:6}] to localhost:49154
2021-05-25 11:20:10,035 INFO [org.mon.dri.connection] (cluster-ClusterId{value='60acc14961fda01911b47ca5', description='null'}-localhost:49154) Opened connection [connectionId{localValue:1, serverValue:5}] to localhost:49154
2021-05-25 11:20:10,044 INFO [org.mon.dri.cluster] (cluster-ClusterId{value='60acc14961fda01911b47ca5', description='null'}-localhost:49154) Monitor thread successfully connected to server with description ServerDescription{address=localhost:49154, type=REPLICA_SET_PRIMARY, state=CONNECTED, ok=true, minWireVersion=0, maxWireVersion=7, maxDocumentSize=16777216, logicalSessionTimeoutMinutes=30, roundTripTimeNanos=21143267, setName='my-mongo-set', canonicalAddress=mongodb_private:27017, hosts=[mongodb_private:27017], passives=[], arbiters=[], primary='mongodb_private:27017', tagSet=TagSet{[]}, electionId=7fffffff0000000000000001, setVersion=1, topologyVersion=null, lastWriteDate=Tue May 25 11:20:09 CEST 2021, lastUpdateTimeNanos=8563393016415}As you can see, there are messages about started container right after line ✔︎ Docker environment should have more than 2GB free disk space. But in the log with an error, there is an error right instead. The only explanation is that container configuration can make this container to intermittently fail. (which surprises me, because almost the same configuration is used for debezium-mongodb test. I'll try to investigate it.
ppalaga
I have seen this once on the CI and once locally (1 in ~6 attempts). I guess there is a race in how we read and write to the results collection. Maybe synchronizing on the list could help.