Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
1.8.1
-
Security Level: Public
-
None
Description
We are running 1.8.1-937 Coucbase server on 10 Linux nodes with about 200M items bucket.
About 1.5 month ago we've upgraded servers from 1.7 to 1.8 and started to see following error messages in the log:
killing myself due to unexpected upstream sender exit with reason: {{badmatch,
{error,
closed}},
[
]} ebucketmigrator_srv000 ns_1@172.19.4.41 03:52:33 - Thu Sep 20, 2012
In many cases this error comes from same node, but sometimes from different ones.
Since the upgrade we've experienced a failure of the node, which became unresponsive after spitting multiple errors of this kind. But in other cases (with single error appearing once a day or so), there seems to be no impact.
Google search gave me only following references for this error:
http://www.couchbase.com/issues/browse/MB-5171
http://www.couchbase.com/issues/browse/MB-5467
http://www.couchbase.com/issues/secure/ReleaseNote.jspa?projectId=10010&version=10295
It looks like according to the last reference, this error supposed to be fixed in 1.8.1 version.
I also can't find clear information as to whether this is a 'bad' error or not and how to fix and/or prevent it.