Details
-
Bug
-
Resolution: Won't Fix
-
Major
-
None
-
7.1.0
-
None
-
Untriaged
-
1
-
Unknown
Description
On my mac I do the following
- cluster_run a node running the top of repo for madhatter as of today
- create cluster with kv, query, index
- cluster_run a node running the top of master (aka Neo) which includes this ns_server fix http://review.couchbase.org/c/ns_server/+/161619
- rebalance to get the second node into the cluster
- from the UI pointing to the MH node load the travel-sample bucket
- go to the UI buckets page and notice the items increases extremely slowing
On the MH node the memcached.log file shows these
2021-09-15T15:16:54.848765-07:00 WARNING (travel-sample) Invalid streaming connection
|
2021-09-15T15:17:00.849110-07:00 WARNING (travel-sample) Invalid streaming connection
|
2021-09-15T15:17:01.850002-07:00 WARNING (travel-sample) Invalid streaming connection
|
On the master/Neo node the memcached.log file shows
2021-09-15T15:18:38.098154-07:00 WARNING 63: User [<ud>unknown</ud>] not found. Mechanism:[PLAIN], UUID:[e33f20e4-709a-4e2f-3db4-052c054a95a6]
|
2021-09-15T15:18:43.099409-07:00 INFO 87: HELO [{"a":"gocbcore/v7.1.14 gocb/v1.4.2","i":"466659448836a767/c10f91b7f2450e48"}] XATTR, XERROR, Select bucket, Snappy, Tracing [ {"ip":"127.0.0.1","port":61735} - {"ip":"127.0.0.1","port":12002} (not authenticated) ]
|
2021-09-15T15:18:43.099409-07:00 INFO 63: HELO [{"a":"gocbcore/v7.1.14 gocb/v1.4.2","i":"c77d93d5f261fb1f/2cd98d2ff3fb558d"}] XATTR, XERROR, Select bucket, Snappy, Tracing [ {"ip":"127.0.0.1","port":61734} - {"ip":"127.0.0.1","port":12002} (not authenticated) ]
|
2021-09-15T15:18:43.099989-07:00 WARNING 63: User [<ud>unknown</ud>] not found. Mechanism:[PLAIN], UUID:[24ef9562-d349-4a95-119f-dc83fe4d2a1e]
|
2021-09-15T15:18:43.099996-07:00 WARNING 87: User [<ud>unknown</ud>] not found. Mechanism:[PLAIN], UUID:[456d8acc-1306-4f9b-a846-c0dc8082543b]
|
Note that cbdocloader is using the bucket-name/sasl-password authentication as it is running on the MH node. The bucket-name/sasl-password is deprecated in 7.0 but technically should work while the cluster is operating at pre-7.0 compatibility mode.
Attachments
Issue Links
- relates to
-
-
- Closed
-