Changelog #19, the overview blog for August is open for 72-hr community
review. Permissions are set for comment only for amends and issues:
https://docs.google.com/document/d/1I5_6pUTWpfKfX16cc-eDS9AjMhe0kPimOpKgFAiS8c4/edit?usp=sharing
Thanks,
--
Chris Thornett
Senior Content Strategist,
Hi,
We are running a production Cassandra version (3.0.14) with 256 tokens
v-node configuration. Occasionally, we see that different nodes show
different ownership for the same key. Only a node restart corrects;
otherwise, it continues to behave in a split-brain.
Say, for example,
*NodeA*
Git and jira , nothing specific
On Fri, 2 Sep 2022 at 12:51, Derek Chen-Becker
wrote:
> I think it's fine to state it explicitly rather than making it an
> assumption. Are we tracking any usage of internals in the codebase
> currently?
>
> Cheers,
>
> Derek
>
> On Fri, Sep 2, 2022 at 6:30 AM
I think it's fine to state it explicitly rather than making it an
assumption. Are we tracking any usage of internals in the codebase
currently?
Cheers,
Derek
On Fri, Sep 2, 2022 at 6:30 AM Ekaterina Dimitrova
wrote:
>
>
> “ A quick heads up to the dev list with the jira would be sufficient
+1 to matching SQL. If we look at our population of users that are going to run
into this, my intuition is that more of them will be familiar with SQL
semantics than counters, so there's the angle where "the more consistent
option" here is to follow SQL convention.
On Wed, Aug 31, 2022, at
+1 on removing JDK8 support from trunk.
On Wed, Aug 31, 2022, at 12:07 PM, David Capwell wrote:
> +1 to remove from trunk
>
>> On Aug 30, 2022, at 7:54 PM, Caleb Rackliffe
>> wrote:
>>
>> +1 on removing 8 for trunk
>>
>> On Tue, Aug 30, 2022 at 2:42 PM Jon Haddad
>> wrote:
>>> +1 to
“ A quick heads up to the dev list with the jira would be sufficient for
anybody interested in discussing it further to comment on the jira.”
Agreed, I did’t mean voting but more or less we have the lazy consensus or
sharing concerns. Discussing them on a ticket should be enough but it needs
to
Unmesh, LWTs today repair themselves periodically already, and do not rely on a
later proposer.
Also, the CMS will naturally use a single partition key for each log it needs
to maintain, else they would not be linearised.
> On 2 Sep 2022, at 05:01, Unmesh Joshi wrote:
>
>
>> I think
