Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
3.4.10
-
None
-
Enterprise Edition 7.6.0 build 1898
-
0
Description
Description
if collection on which range scan calls are hitting gets deleted , subsequent range scan calls should fail saying resource not found or something along the line, instead of getting timed out
Steps:
create a 6 node cluster
+----------------+---------+----------+
|
| Nodes | Zone | Services |
|
+----------------+---------+----------+
|
| 172.23.104.107 | Group 1 | kv |
|
| 172.23.104.234 | None | kv |
|
| 172.23.104.235 | None | kv |
|
| 172.23.104.236 | None | n1ql |
|
| 172.23.105.123 | None | index |
|
| 172.23.104.97 | None | index |
|
+----------------+---------+----------+
|
create 2 buckets with some dataload
| Bucket | Type / Storage | Replicas |
|
+----------+------------------------+----------+
|
| bucket-0 | couchbase / couchstore | 3 |
|
| default | couchbase / magma | 1 |
|
+----------+------------------------+----------+
|
start continuous range scan on
bucket default scope1 , collection-7
|
delete the above collection while continuous range scan calls keeps on hitting cluster in parallel
Timestamp
the mentioned collection is deleted around the timestamp
2023-12-06 02:28:00
|
Observation
all subsequent calls post deletion times out