Log file Viewer

[08:02:11] <finalspy> 2019-03-23T07:59:13.000+0000 W REPL [ftdc] Rollback ID is not initialized yet.

[08:02:11] <finalspy> 2019-03-23T07:59:13.871+0000 I - [initandlisten] Index Build: 630200/3065056 20%

[08:02:11] <finalspy> 2019-03-23T07:59:14.000+0000 W REPL [ftdc] Rollback ID is not initialized yet.

[08:02:13] <finalspy> Hi, during the add of a new replica, I keep getting this kind of logs (and never saw them during other replicas add), so i'm curious to know of this is normal or if something went wrong meanin I'd better remoeve it, clean it and restart :

[08:06:46] <finalspy> On other replica members I also see this :

[08:06:53] <finalspy> 2019-03-23T08:04:21.077+0000 I ASIO [NetworkInterfaceASIO-Replication-0] Connecting to repl3:37003

[08:06:53] <finalspy> 2019-03-23T08:04:21.077+0000 I ASIO [NetworkInterfaceASIO-Replication-0] Failed to connect to repl3:37003 - HostUnreachable: Connection refused

[08:06:53] <finalspy> 2019-03-23T08:04:21.077+0000 I ASIO [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to repl3:37003 due to failed operation on a connection

[08:06:55] <finalspy> 2019-03-23T08:04:21.077+0000 I REPL_HB [replexec-287] Error in heartbeat (requestId: 1373227) to repl3:37003, response status: HostUnreachable: Connection refused

[08:07:13] <finalspy> Any ideas / suggestions ?

[08:20:23] <finalspy> Answer to myself ... really sounds like a defect, the rs.status() on the primary shows this (partial extract) this :

[08:20:29] <finalspy> "health" : 0,

[08:20:29] <finalspy> "state" : 8,

[08:20:29] <finalspy> "stateStr" : "(not reachable/healthy)",

[08:20:31] <finalspy> "uptime" : 0,

[08:20:33] <finalspy> "optimeDate" : ISODate("1970-01-01T00:00:00Z"),

[08:20:35] <finalspy> "optimeDurableDate" : ISODate("1970-01-01T00:00:00Z"),

[08:20:37] <finalspy> "lastHeartbeatRecv" : ISODate("1970-01-01T00:00:00Z"),

[08:20:39] <finalspy> "pingMs" : NumberLong(0),

[08:20:41] <finalspy> "lastHeartbeatMessage" : "Connection refused",

[08:20:43] <finalspy> "configVersion" : -1

[15:59:26] <ahmad-n> Hello all. New to MongoDB and finding this issue to be unintuitive: successfully migrated 27m records to MongoDB Atlas. Using MongoDB Compass, trying to create a index for a "id" Number attribute (not to be confused with "_id"), however I'm getting the error message: "WiredTigerIndex::insert: key too large to index". The thing is, I am indexing "id" which is a Number.

[16:00:03] <ahmad-n> The error message is complaining about a different attribute, a String, which intuitively I do not understand why MongoDB would touch during the indexing operation.