Locking Process failed with exception about newton HOT 5 CLOSED

Is there any context you could add about this?

The stack says that mongo client isn't in a suitable state yet, normally because its starting or stopping for some reason.

from newton.

I don't think mongo client is starting/stopping (99% sure) We've had previous stacktraces in past with same mongo stack even though it was a newton &/or underlying client app issue. I've asked Mark to gather a bit more info as to when this is happening

from newton.

Hi David, this is the same error as the one mentioned on Tuesday eve. I was hoping 0.0.14 would resolve it but it happened again. It seems to occur fairly randomly but afterwards I need to restart the service which appears to resolve it at least for a while. I'll add more info as soon as I have more.

from newton.

hmm, ok. So this is probably something client side rather than server side. Ie, in the Newton piece/ core-service rather than in the Photon server.

I'll do some experimentation. Do you have a log covering the period the error occurs from the client side (ie, core-service/ whatever)? I'm looking at things around the service. You can slack me that if you want to.

from newton.

In the latest master/ 0.11 snapshots MuonClusterAwareTrackingSubscriptionManager has changed quite a bit to address these kind of problems. Notably #51

That's marked as fixed in the latest snapshot, so it would be worth upgrading the services to the 0.0.11-SNAPSHOT and verify with that.

Note that this is in newton only, so would require the services to be updated, not the Photon server.

from newton.