I am using MongoDB Sharded Cluster architecture to store my datas safely and efficiently, but when I check my mongos (or mongoRouter) logs, on daily bases I have been getting this error on different times for each shards, config server and mongos regularly:
{“t”:{“$date”:“2022-02-28T15:59:45.511+03:00”},“s”:“I”, “c”:“CONNPOOL”, “id”:22572, “ctx”:“establishCursors cleanup”,“msg”:“Dropping all pooled connections”,“attr”:{“hostAndPort”:“server1:27019”,“error”:“ShutdownInProgress: Pool for server1:27019 has expired.”}}
{“t”:{“$date”:“2022-02-28T15:59:45.511+03:00”},“s”:“I”, “c”:“CONNPOOL”, “id”:22572, “ctx”:“establishCursors cleanup”,“msg”:“Dropping all pooled connections”,“attr”:{“hostAndPort”:“server2:27019”,“error”:“ShutdownInProgress: Pool for server2:27019 has expired.”}}
{“t”:{“$date”:“2022-02-28T15:59:45.511+03:00”},“s”:“I”, “c”:“CONNPOOL”, “id”:22572, “ctx”:“establishCursors cleanup”,“msg”:“Dropping all pooled connections”,“attr”:{“hostAndPort”:“server3:27019”,“error”:“ShutdownInProgress: Pool for server3:27019 has expired.”}}
{“t”:{“$date”:“2022-02-28T15:59:45.511+03:00”},“s”:“I”, “c”:“CONNPOOL”, “id”:22572, “ctx”:“establishCursors cleanup”,“msg”:“Dropping all pooled connections”,“attr”:{“hostAndPort”:“server1:27020”,“error”:“ShutdownInProgress: Pool for server1:27020 has expired.”}}
{“t”:{“$date”:“2022-02-28T15:59:45.511+03:00”},“s”:“I”, “c”:“CONNPOOL”, “id”:22572, “ctx”:“establishCursors cleanup”,“msg”:“Dropping all pooled connections”,“attr”:{“hostAndPort”:“server2:27020”,“error”:“ShutdownInProgress: Pool for server2:27020 has expired.”}}
{“t”:{“$date”:“2022-02-28T15:59:45.511+03:00”},“s”:“I”, “c”:“CONNPOOL”, “id”:22572, “ctx”:“establishCursors cleanup”,“msg”:“Dropping all pooled connections”,“attr”:{“hostAndPort”:“server3:27020”,“error”:“ShutdownInProgress: Pool for server3:27020 has expired.”}}
• Following figure shows my sharded cluster set-up (server1, server2 and server3 represent different servers)
Does anyone know what is the reason of getting this error and what to do for solving it?