You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "SiyaoIsHiding (via GitHub)" <gi...@apache.org> on 2026/06/04 00:28:51 UTC
Re: [PR] NODEJS-681: ControlConnection Concurrent Read and Write on .host and .connection [cassandra-nodejs-driver]
SiyaoIsHiding commented on PR #462:
URL: https://github.com/apache/cassandra-nodejs-driver/pull/462#issuecomment-4617856321
Confirming above is correct.
The question is whether `refreshKeyspacesInternal` is enough to cover any EVENTs potentially lost.
There are 3 kinds of EVENTs
1. TOPOLOGY_CHANGE, handled by `refreshHosts`
2. STATUS_CHANGE, a host UP or DOWN, is handled by `host.js`'s reconnection schedule, independent from `ControlConnection`
3. SCHEMA_CHANGE
3a. `refreshKeyspacesInternal` redo `SELECT * FROM system_schema.keyspaces`
3b. It also removes the cache for udt, table, function, aggregate, and views. They will be lazy-loaded when used for the first time.
So I think `refreshKeyspacesInternal` is enough.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org