Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
5.5.0
-
None
-
Untriaged
-
Unknown
Description
Hi Sreekanth Sivasankaran, from the cbcollect-info attached to https://issues.couchbase.com/browse/MB-29770, looks like there's lots of attempts to try to cleanup an FTS index for a bucket that's no longer there...
ns_server.fts.log 2018-05-20T02:22:59.078-07:00 [INFO] main: meh.OnFeedError, srcType: couchbase, err: could not connect to any serverURL: []string{"http://127.0.0.1:8091"}
|
ns_server.fts.log 2018-05-20T02:22:59.078-07:00 [INFO] main: meh.OnFeedError, srcType: couchbase, err: No bucket named default
|
ns_server.fts.log 2018-05-20T02:22:59.084-07:00 [INFO] main: meh.OnFeedError, VerifyBucketNotExists, srcType: couchbase, gone: true, err: No bucket named default
|
ns_server.fts.log 2018-05-20T02:22:59.084-07:00 [INFO] main: meh.OnFeedError, DeleteAllIndexFromSource, srcType: couchbase, bucketName: default, bucketUUID:
|
ns_server.fts.log 2018-05-20T02:22:59.086-07:00 [INFO] main: meh.OnFeedError, VerifyBucketNotExists, srcType: couchbase, gone: true, err: No bucket named default
|
ns_server.fts.log 2018-05-20T02:22:59.086-07:00 [INFO] main: meh.OnFeedError, DeleteAllIndexFromSource, srcType: couchbase, bucketName: default, bucketUUID:
|
But, as you can see from the logs, that attempt seems to fail and keep on repeating in a loop. Please take a dig into this? thx, steve