Skip to content

Conversation

@thejcfactor
Copy link
Contributor

Motivation

An HTTP workload can potentially use an invalid node index to access a node in the config in scenarios to where a node in the cluster has been failed over.

Changes

  • Upon updating the config w/in the HTTP Session manager, reset the next node index if its current value is greater than or equal to the number of nodes in the new config
  • Update analytics tool to only populate error context if the analytics operation has an error

Motivation
==========
An HTTP workload can potentially use an invalid node index to access a node in the config in scenarios to where a node in the cluster has been failed over.

Changes
=======
* Upon updating the config w/in the HTTP Session manager, reset the next node index if its current value is greater than or equal to the number of nodes in the new config
* Update analytics tool to only populate error context if the analytics operation has an error
@thejcfactor thejcfactor requested a review from avsej August 27, 2025 21:51
@thejcfactor thejcfactor merged commit 37cfa6d into couchbase:main Aug 28, 2025
24 of 27 checks passed
@thejcfactor thejcfactor deleted the CXXCBC-715 branch August 28, 2025 22:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants