[SERVER-1924] mongos reporting : [WriteBackListener] MessagingPort say send() errno:32 Created: 11/Oct/10  Updated: 17/Mar/11  Resolved: 11/Oct/10

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

Type: Bug Priority: Major - P3
Reporter: Alvin Richards (Inactive) Assignee: Kristina Chodorow (Inactive)
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 Description   

Problem:
during a rolling bounce of the members of a replset, the following was seen in the mongos logs

Sun Oct 10 22:05:40 [WriteBackListener] MessagingPort say send() errno:32 Broken pipe 10.121.14.5:27018
Sun Oct 10 22:05:40 [WriteBackListener] WriteBackListener exception : St9exception
Sun Oct 10 22:05:46 [WriteBackListener] MessagingPort say send() errno:32 Broken pipe 10.121.14.5:27018
Sun Oct 10 22:05:46 [WriteBackListener] WriteBackListener exception : St9exception

At this point the application could not read or write to the DB

Workaround:

  • bounce the mongos
  • bounce the apache server (running the PHP driver)

The bounce of the mongos did not solve the problem, the apache server had to be bounced as well. Possibly a connection pooling / persistent connection issue?

Business case:

  • User experience
    During a failover, the monogs/drivers should deal with this gracefully.


 Comments   
Comment by Eliot Horowitz (Inactive) [ 11/Oct/10 ]

those messages are harmless - and have nothing to do with user failures.
if bouncing the mongos didn't have an impact - than its not a connection pool issue on the mongos side.
could be something on the php side - but would need more info to even start reasoning

Generated at Thu Feb 08 02:58:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.