Discussion:
Mongo secondary instance is hanging on startup
(too old to reply)
i***@meniscus.co.uk
2018-12-03 13:36:38 UTC
Permalink
We have a replica set which was all working fine and then over the weekend
we ran out of disk space on the primary.

On adding extra disk space both machines, both servers were restarted.

Since we did this the secondary service is always in the starting state and
this is the last error in the log file:

2018-12-03T12:37:53.544+0000 I FTDC [initandlisten] Initializing
full-time diagnostic data capture with directory
'D:/MongoData/DB/diagnostic.data'
2018-12-03T12:37:53.551+0000 I REPL [initandlisten] Rollback ID is 2
2018-12-03T12:37:53.552+0000 I REPL [initandlisten] Starting recovery
oplog application at the appliedThrough: { ts: Timestamp(1543588255, 92),
t: 29 }
2018-12-03T12:37:53.552+0000 I REPL [initandlisten] Replaying stored
operations from { : Timestamp(1543588255, 92) } (exclusive) to { :
Timestamp(1543588257, 181) } (inclusive).

I am unable to connect to Mongo from a command prompt and it remains in
this state.

Any ideas why it does not get into a running state?
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/575fac07-97a2-43bc-9db8-f41f1ba1db6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
i***@meniscus.co.uk
2018-12-03 14:54:44 UTC
Permalink
Please note that I am using Mongo 3.6.8
Post by i***@meniscus.co.uk
We have a replica set which was all working fine and then over the weekend
we ran out of disk space on the primary.
On adding extra disk space both machines, both servers were restarted.
Since we did this the secondary service is always in the starting state
2018-12-03T12:37:53.544+0000 I FTDC [initandlisten] Initializing
full-time diagnostic data capture with directory
'D:/MongoData/DB/diagnostic.data'
2018-12-03T12:37:53.551+0000 I REPL [initandlisten] Rollback ID is 2
2018-12-03T12:37:53.552+0000 I REPL [initandlisten] Starting recovery
oplog application at the appliedThrough: { ts: Timestamp(1543588255, 92),
t: 29 }
2018-12-03T12:37:53.552+0000 I REPL [initandlisten] Replaying stored
Timestamp(1543588257, 181) } (inclusive).
I am unable to connect to Mongo from a command prompt and it remains in
this state.
Any ideas why it does not get into a running state?
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/a6a5a3e0-5548-4d89-9413-b4c5b8614a3f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
'Kevin Adistambha' via mongodb-user
2018-12-05 01:29:38 UTC
Permalink
Hi,

From the logs, it appears that the node is undergoing a rollback. There are
many reasons why this can happen, but typically rollbacks are undesirable.
See Rollbacks During Replica Set Failover
<https://docs.mongodb.com/manual/core/replica-set-rollbacks/> for more
details.

If this is a busy replica set, it is possible that the rollback simply
takes a long time to finish. If there is no error in the logs, I don’t see
a reason to suspect it is not proceeding. You might be able to open another
terminal window and check whether the disk is busy, CPU is being used, or
similar signs that there is a process happening in the server. Could you
confirm whether it is no longer in this state or otherwise?

Best regards,
Kevin
​
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/854b8054-69c1-47cd-a446-3e6692399390%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Continue reading on narkive:
Loading...