Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Pavithra MahamaniPavithra Mahamani(Deactivated)Reporter
Neil HuangNeil HuangIs this a Regression?
UnknownTriage
UntriagedStory Points
1Priority
CriticalInstabug
Open Instabug
Details
Details
Assignee
Pavithra Mahamani
Pavithra Mahamani(Deactivated)Reporter
Neil Huang
Neil HuangIs this a Regression?
Unknown
Triage
Untriaged
Story Points
1
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created August 27, 2021 at 4:48 PM
Updated December 11, 2021 at 1:28 AM
Resolved August 31, 2021 at 2:14 PM
In a recent case from the field we've seen XDCR holding 70,000 sockets that do not have a process on the other side of the connection. When
lsof
is run, these sockets show up as follows:COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME ... goxdcr.bi 24440 cbadmin 5u sock 0,7 0t0 303953540 protocol: TCP goxdcr.bi 24440 cbadmin 6u sock 0,7 0t0 211821560 protocol: TCP goxdcr.bi 24440 cbadmin 10u sock 0,7 0t0 216966092 protocol: TCP ...
In this case the user had set the file descriptor limit to 70k and so at this point XDCR is unable to create new connections. This issue was previously tracked in https://couchbasecloud.atlassian.net/browse/MB-44182#icft=MB-44182 and believed to be fixed, but it seems that the core issue hasn't been completely fixed.