[SERVER-12086] Odd lockpinger warning, inactive for a very long time Created: 13/Dec/13  Updated: 21/Jan/14  Resolved: 21/Jan/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.5.4
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Tyler Brock Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 Description   

2013-12-13T11:38:32.792-0500 [LockPinger] warning: Lock pinger for addr: localhost:6003,localhost:6004,localhost:6005, proc: bigbrock.local:4000:1386801886:16807 was inactive for 18446744073709143362 ms



 Comments   
Comment by Tyler Brock [ 10/Jan/14 ]

Discussed with greg_10gen and moved to needs triage. Its just a messaging problem but it should be looked at.

Comment by Tyler Brock [ 31/Dec/13 ]

I just saw this message in logs and thought it was something we should look into since I had just started that mongod and the message says it was inactive for "18446744073709143362ms" which is impossible.

Generated at Thu Feb 08 03:27:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.