-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
Repl 2018-10-22, Repl 2018-11-05, Repl 2018-11-19, Service Arch 2018-12-03, Service Arch 2018-12-17, Service Arch 2018-12-31, Service Arch 2019-01-14, Service Arch 2019-01-28, Service Arch 2019-02-11, Service Arch 2019-02-25
-
None
-
0
-
None
-
None
-
None
-
None
-
None
-
None
If you happen to have a node in your config that is down, the system log on all the other nodes each fill with 12 log messages every half second (24 messages per second). This seems excessive.
Example of all the messages logged in 3 ms:
2018-10-01T13:45:16.770-0400 I ASIO [Replication] Connecting to localhost:27019 2018-10-01T13:45:16.770-0400 I ASIO [Replication] Failed to connect to localhost:27019 - HostUnreachable: Error connecting to localhost:27019 (127.0.0.1:27019) :: caused by :: Connection refused 2018-10-01T13:45:16.770-0400 I ASIO [Replication] Dropping all pooled connections to localhost:27019 due to HostUnreachable: Error connecting to localhost:27019 (127.0.0.1:27019) :: caused by :: Connection refused 2018-10-01T13:45:16.770-0400 I REPL_HB [replexec-3] Error in heartbeat (requestId: 225) to localhost:27019, response status: HostUnreachable: Error connecting to localhost:27019 (127.0.0.1:27019) :: caused by :: Connection refused 2018-10-01T13:45:16.771-0400 I ASIO [Replication] Connecting to localhost:27019 2018-10-01T13:45:16.771-0400 I ASIO [Replication] Failed to connect to localhost:27019 - HostUnreachable: Error connecting to localhost:27019 (127.0.0.1:27019) :: caused by :: Connection refused 2018-10-01T13:45:16.771-0400 I ASIO [Replication] Dropping all pooled connections to localhost:27019 due to HostUnreachable: Error connecting to localhost:27019 (127.0.0.1:27019) :: caused by :: Connection refused 2018-10-01T13:45:16.771-0400 I REPL_HB [replexec-3] Error in heartbeat (requestId: 226) to localhost:27019, response status: HostUnreachable: Error connecting to localhost:27019 (127.0.0.1:27019) :: caused by :: Connection refused 2018-10-01T13:45:16.771-0400 I ASIO [Replication] Connecting to localhost:27019 2018-10-01T13:45:16.771-0400 I ASIO [Replication] Failed to connect to localhost:27019 - HostUnreachable: Error connecting to localhost:27019 (127.0.0.1:27019) :: caused by :: Connection refused 2018-10-01T13:45:16.771-0400 I ASIO [Replication] Dropping all pooled connections to localhost:27019 due to HostUnreachable: Error connecting to localhost:27019 (127.0.0.1:27019) :: caused by :: Connection refused 2018-10-01T13:45:16.772-0400 I REPL_HB [replexec-3] Error in heartbeat (requestId: 227) to localhost:27019, response status: HostUnreachable: Error connecting to localhost:27019 (127.0.0.1:27019) :: caused by :: Connection refused
I wonder if the volume of ASIO messages could be reduced in this situation.