-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Affects Version/s: 1.15.0
-
Component/s: None
-
Java Drivers
-
None
-
None
-
None
-
None
-
None
-
None
Currently, the MongoDB Kafka connector outputs at least some errors with the INFO level, which is disconcerting, since there are more appropriate levels, notably ERROR (and maybe some WARN cases).
For the sake of illustrating it, here is one instance of suck a problem:
| Message | Exception in monitor thread while connecting to server <***> |
|---|---|
| Error type | com.mongodb.MongoSocketOpenException |
| Logger | org.mongodb.driver.cluster |
| Level | INFO |
| Stack trace | "com.mongodb.MongoSocketOpenException: Exception opening socket\n\tat com.mongodb.internal.connection.SocketStream.open(SocketStream.java:70)\n\tat com.mongodb.internal.connection.InternalStreamConnection.open(InternalStreamConnection.java:180)\n\tat com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.lookupServerDescription(DefaultServerMonitor.java:193)\n\tat com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:157)\n\tat java.base/java.lang.Thread.run(Unknown Source)\nCaused by: java.net.ConnectException: Connection refused\n\tat java.base/sun.nio.ch.Net.pollConnect(Native Method)\n\tat java.base/sun.nio.ch.Net.pollConnectNow(Unknown Source)\n\tat java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(Unknown Source)\n\tat java.base/sun.nio.ch.NioSocketImpl.connect(Unknown Source)\n\tat java.base/java.net.SocksSocketImpl.connect(Unknown Source)\n\tat java.base/java.net.Socket.connect(Unknown Source)\n\tat com.mongodb.internal.connection.SocketStreamHelper.initialize(SocketStreamHelper.java:107)\n\tat com.mongodb.internal.connection.SocketStream.initializeSocket(SocketStream.java:79)\n\tat com.mongodb.internal.connection.SocketStream.open(SocketStream.java:65)\n\t... 4 more\n" |