Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Sujay GadSujay GadReporter
Abhishek JindalAbhishek JindalIs this a Regression?
UnknownTriage
UntriagedOperating System
Centos 64-bitStory Points
1Priority
CriticalInstabug
Open Instabug
Details
Details
Assignee
Sujay Gad
Sujay GadReporter
Abhishek Jindal
Abhishek JindalIs this a Regression?
Unknown
Triage
Untriaged
Operating System
Centos 64-bit
Story Points
1
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created April 4, 2022 at 12:11 PM
Updated April 12, 2022 at 10:08 AM
Resolved April 7, 2022 at 2:04 PM
STEPS
Cluster consists of 2 nodes (kv + eventing, index + query) running on 6.6.5 - 10080.
Create 4 eventing handlers - bucket_op, timers, curl and n1ql.
Deploy all 4 handlers, load data into source bucket and verify mutations are processed or not.
Disable auto failover, enable n2n encryption and enforce tls.
Pause - resume all 4 handlers.
Load data into source bucket and verify mutations are processed or not.
Perform online upgrade using swap rebalance of the cluster to 7.1.0 - 2017.
Load docs into source bucket and verify mutations are processed or not.
OBSERVATION
Few bucket operations fail with the following error.
Eventing Stats
On 172.23.106.74
ns_server.eventing.log