A static collection is probably atypical, and again, would encourage you to
open a JIRA.
This seems like a case we should be able to find in a simulator.
On Tue, Dec 12, 2023 at 2:05 PM Sebastian Marsching
wrote:
> I assume these are column names of a non-system table.
>
> This is correct. It
> I assume these are column names of a non-system table.
>
This is correct. It is one of our application tables. The table has the
following schema:
CREATE TABLE pv_archive.channels (
channel_name text,
decimation_level int,
bucket_start_time bigint,
channel_data_id uuid static,
I don't recognise those names:
* channel_data_id
* control_system_type
* server_id
* decimation_levels
I assume these are column names of a non-system table.
From the stack trace, this looks like an error from a node which was
running 4.1.3, and this node was not the coordinator for this
> If an upgrade involves changing the schema, I think backwards compatibility
> would be out of the question?
That’s a good point.
I just noticed that during the upgrade, the output of “nodetool
describecluster” showed a schema version disagreement, where the nodes running
3.11.14 were on
If an upgrade involves changing the schema, I think backwards
compatibility would be out of the question?
On Tue, Dec 12, 2023 at 10:36 AM Jeff Jirsa wrote:
> This deserves a JIRA
>
>
>
> On Tue, Dec 12, 2023 at 8:30 AM Sebastian Marsching <
> sebast...@marsching.com> wrote:
>
>> Hi,
>>
>>
The Cassandra team is pleased to announce the release of Cassandra Java
Driver version 4.18.0
The Source release and Binary convenience artifacts are available here:
https://dist.apache.org/repos/dist/release/cassandra/cassandra-java-driver/4.18.0/
The Maven artifacts can be found at:
This deserves a JIRA
On Tue, Dec 12, 2023 at 8:30 AM Sebastian Marsching
wrote:
> Hi,
>
> while upgrading our production cluster from C* 3.11.14 to 4.1.3, we
> experienced the issue that some SELECT queries failed due to supposedly no
> replica being available. The system logs on the C* nodes
Hi,
while upgrading our production cluster from C* 3.11.14 to 4.1.3, we experienced
the issue that some SELECT queries failed due to supposedly no replica being
available. The system logs on the C* nodes where full of messages like the
following one:
ERROR [ReadStage-1] 2023-12-11
