t;>> >
>>> > Each release would be allowed to make breaking changes but only for
>>> features that have already been deprecated for one major release cycle.
>>> >
>>> > This is a process change so as per our governance:
>>> https://cwiki.apache.org/confluence/display/CASSANDRA/Cassandra+Project+Governance,
>>> it'll require a super majority of 50% of the roll called PMC in favor.
>>> Current roll call is 21 so we need 11 pmc members to participate, 8 of
>>> which are in favor of the change.
>>> >
>>> > I'll plan to leave the vote open until we hit enough participation to
>>> pass or fail it up to probably a couple weeks.
>>>
>>>
>>>
--
Dmitry Konstantinov
t.
>>>>> >
>>>>> > -Jeremiah
>>>>> >
>>>>> > On Mar 5, 2025 at 12:15:23 PM, Benedict Elliott Smith <
>>>>> bened...@apache.org> wrote:
>>>>> >>
>>>>> >> That depends on all of you lovely people :D
>
project's CI resources !
>>>
>>> This is a big deal for the project, adding both stability and improved
>>> throughput of CI for the community.
>>> https://github.com/apache/cassandra-builds/blob/trunk/ASF-jenkins-agents.md
>>>
>>>
>>> A very big thank you to NetApp, and to all our contributors employed
>>> there to help make this happen.
>>>
>>
--
Dmitry Konstantinov
x27;t really compatibility, and I don't
>> have any real investment in DropWizard. I don't know if there's any real
>> value in putting in effort to maintain compatibility, but I'm just one
>> sample, so I won't make a strong statement here.
>> >
>>
status quo.
>
> It's hard to know the full extent of what you're planning and the impact,
> so I'll save any opinions till I know more about the plan.
>
> Thanks for bringing this up!
> Jon
>
> [1]
> https://planetcassandra.org/leaf/apache-cassandra-
nsibilities.html if you're
> interested in learning more about the rights and responsibilities of PMC
> members.
>
> Please join us in welcoming Ekaterina Dimitrova to her new role in our
> project!
>
> Paulo, on behalf of the Apache Cassandra PMC
>
--
Dmitry Konstantinov
regarding this suggestion?
--
Dmitry Konstantinov
pe you will
> join me in thanking them all for their contributions.
>
> Alex has also kindly produced some initial overview documentation for
> developers, that can be found here:
> https://github.com/apache/cassandra/blob/cep-15-accord/doc/modules/cassandra/pages/developing/accord/index.adoc.
> This will be expanded as time permits.
>
> Does anyone have any questions or concerns?
>
>
>
--
Dmitry Konstantinov
between exposing what people actually are
> likely to need to modify vs having a super intimidating config file. It's
> already nearly 2000 lines. Personally I'd rather see some
> auto-documentation or something that's in the docs
> <https://cassandra.apache.org/
; > announce that he has accepted.
> >
> > Please join us in welcoming Bernardo Botella to his new role and
> > responsibility in our project community.
> >
> > Stefan Miklosovic
> >
> > On behalf of the Apache Cassandra PMC
>
--
Dmitry Konstantinov
Guerrero wrote:
> Congrats to both of you!
>
> On 2025/02/20 17:47:05 Štefan Miklošovič wrote:
> > The Project Management Committee (PMC) for Apache Cassandra
> > has invited Maxwell Guo and Dmitry Konstantinov to become committers and
> we
> > are pleased
> >
a member of the community for 10 years and is one of the
> most active committers on the project.
>
> Please join us in welcoming Caleb to his new role!
>
> Jon
> On behalf of the Cassandra PMC
>
>
>
--
Dmitry Konstantinov
t be
>> attractive for scholars who are trying to find a problem to solve with a
>> lot of theory behind it while it is also practical. I do not know what
>> plans Bernardo has with this as it is his brain-child. I just stumbled upon
>> this topic and I am trying to drive it to som
I do not think that we are going to solve NP-completeness of SAT here :D
>> so I just want to make sure that we are on the same page when it comes to
>> this and all we will ever support is just a simple AND (that is complicated
>> enough to verify if it is satisfiable already).
>>
>> What do you think about this? Is this all OK for you?
>>
>> Regards
>>
>> (1) https://en.wikipedia.org/wiki/Boolean_satisfiability_problem
>>
>
--
Dmitry Konstantinov
;>>
>>>> Kind Regards,
>>>> Brandon
>>>>
>>>> On Fri, Feb 14, 2025 at 8:32 AM Benedict Elliott Smith
>>>> wrote:
>>>> >
>>>> > The PMC is happy to announce that Jeremiah Jordan has joined its
>>>> membership.
>>>> >
>>>> > Jeremiah has been a member of this community for almost 15 years. I
>>>> hope you will join me in welcoming him to the committee.
>>>>
>>>
>>>
--
Dmitry Konstantinov
t;>> see
>>>>>>> on EBS (100micros vs 1-3ms), and you can do hundreds of thousands of
>>>>>>> IOPS
>>>>>>> vs a max of 16K.
>>>>>>> >
>>>>>>> > Related to this, Branimir wrote CASSANDRA-20092 [3], which
>>>>>>> significantly improves compaction by avoiding reading the partition
>>>>>>> index.
>>>>>>> CASSANDRA-20092 has been merged to trunk already [4].
>>>>>>> >
>>>>>>> > I think we should merge both of these patches into 5.0, as the
>>>>>>> perf improvement should allow teams to increase density of EBS backed C*
>>>>>>> clusters by 2-5x, driving cost way down. There's a lot of teams
>>>>>>> running C*
>>>>>>> on EBS now. I'm currently working with one that's bottlenecked on maxed
>>>>>>> out EBS GP3 storage. I propose we merge both, because without
>>>>>>> CASSANDRA-20092, we won't get the performance improvements in
>>>>>>> CASSANDRA-15452 with BTI, only BIG format. I've tested BTI in other
>>>>>>> situations and found it to be far more performant than BIG.
>>>>>>> >
>>>>>>> > If we were looking at a small win, I wouldn't care much, but since
>>>>>>> these patches, combined with UCS, allows more teams to run C* on EBS at
>>>>>>> >
>>>>>>> 10TB / node, I think it's worth doing now.
>>>>>>> >
>>>>>>> > Thanks in advance,
>>>>>>> > Jon
>>>>>>> >
>>>>>>> > [1] https://issues.apache.org/jira/browse/CASSANDRA-15452
>>>>>>> > [2]
>>>>>>> https://aws.amazon.com/blogs/database/best-practices-for-running-apache-cassandra-with-amazon-ebs/
>>>>>>> > [3] https://issues.apache.org/jira/browse/CASSANDRA-20092
>>>>>>> > [4]
>>>>>>> https://github.com/apache/cassandra/commit/3078aea1cfc70092a185bab8ac5dc8a35627330f
>>>>>>> >
>>>>>>>
>>>>>>
>>
--
Dmitry Konstantinov
+1 (nb)
On Tue, 4 Feb 2025 at 22:00, Abe Ratnofsky wrote:
> +1 (nb)
>
--
Dmitry Konstantinov
commit link are updated)
Regards,
Dmitry
On Wed, 29 Jan 2025 at 16:32, Brandon Williams wrote:
> On Wed, Jan 29, 2025 at 10:26 AM Dmitry Konstantinov
> wrote:
> > I want to draw it explicitly (as a diagram or as a table) and share to
> check my understanding, then after a discuss
t; https://lists.apache.org/thread/g4mvx41jdvn700719po0nxhz7n1ftpnc
>
> Kind Regards,
> Brandon
>
--
Dmitry Konstantinov
c table and document what each is for and what is the decision
> about adding that property to yaml or not.
>
> On Fri, Jan 24, 2025 at 4:31 PM Dmitry Konstantinov
> wrote:
>
>> A very primitive implementation of the 1st idea below:
>>
>> String configUrl =
>&
https://issues.apache.org/jira/browse/CASSANDRA-20249
On Fri, 24 Jan 2025 at 15:40, Dmitry Konstantinov
wrote:
> Maybe I missed some patterns but it looks like a pretty good estimation, I
> did like 10 random checks manually to verify :-)
> I will try to make an ant target with a simi
gt; On Fri, Jan 24, 2025 at 4:31 PM Dmitry Konstantinov
> wrote:
>
>> A very primitive implementation of the 1st idea below:
>>
>> String configUrl =
>> "file:///Users/dmitry/IdeaProjects/cassandra-trunk/conf/cassandra.yaml";
>> Field[] allFields = Config.
config
>>>> enable_user_defined_functions, then there should be a respective JVM flag
>>>> -Dcassandra.enable_user_defined_functions, and vice versa.
>>>>
>>>
>>> Yeah, good idea.
>>>
>>>
>>>>
>>>> On Fri, Jan 24, 2025 at 9:16 AM Štefan Miklošovič <
>>>> smikloso...@apache.org> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> from time to time I see configuration properties in Config.java and
>>>>> they are clearly not in cassandra.yaml. Not every property in Config is in
>>>>> cassandra.yaml. I would like to know if there is some specific reason
>>>>> behind that.
>>>>>
>>>>> Question related to that is if we could not have a build-time check
>>>>> that all properties in Config have to be in cassandra.yaml and fail the
>>>>> build if a property in Config does not have its counterpart in yaml.
>>>>>
>>>>> There are dozens of properties in Config and I have a strong suspicion
>>>>> that we missed to publish some to yaml so users do not even know such a
>>>>> property exists and as of now we do not even know which they are.
>>>>>
>>>>
--
Dmitry Konstantinov
n cassandra.yaml and fail the build if
>> a property in Config does not have its counterpart in yaml.
>>
>> There are dozens of properties in Config and I have a strong suspicion
>> that we missed to publish some to yaml so users do not even know such a
>> property exists and as of now we do not even know which they are.
>>
>
--
Dmitry Konstantinov
months), there is no overhead for branches/merges.
On Thu, 23 Jan 2025 at 14:31, Štefan Miklošovič
wrote:
>
>
> On Thu, Jan 23, 2025 at 3:20 PM Dmitry Konstantinov
> wrote:
>
>> Hi Stefan,
>>
>> Thank you a lot for the detailed feedback! Few comments:
>>
&g
things not visible behind the
> scenes and doing releases is a job in itself.
>
> So if we ask for more frequent releases, it is a good question to ask who
> would be actually releasing that.
>
> On Wed, Jan 22, 2025 at 12:17 PM Dmitry Konstantinov
> wrote:
>
>> Hi
n West wrote:
>>
>>> The PMC's members are pleased to announce that Patrick McFadin has accepted
>>> an invitation to become a PMC member.
>>>
>>> Thanks a lot, Patrick, for everything you have done for the project all
>>> these years.
>>>
>>> Congratulations and welcome!!
>>>
>>> The Apache Cassandra PMC
>>>
>>
--
Dmitry Konstantinov
er.
>> Also, there will be exceptions: patches that are too large, invasive,
>> risky, or complicated to backport. For these, we rely on the contributor
>> and reviewer’s judgment and the mailing list. So, I’m proposing an
>> allowance to backport to active branches, not a requirement to merge them.
>>
>> I’m curious to hear your thoughts.
>> Jordan
>>
>>
--
Dmitry Konstantinov
acking enabled, the immediate benefits of
>>> this CEP are:
>>> * reduced replication lag with a continuous background reconciliation
>>> process
>>> * eliminate the disk load caused by repair merkle tree calculation
>>> * eliminate repair overstreaming
>>> * reduce disk load of reads on cluster to close to 1/CL
>>> * fix longstanding mutation atomicity issues caused by read repair and
>>> short read protection
>>>
>>> Additionally, although it's outside the scope of this CEP, mutation
>>> tracking would enable:
>>> * completion of witness replicas / transient replication, making the
>>> feature usable for all workloads
>>> * lightweight witness only datacenters
>>>
>>> The CEP is linked here:
>>> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-45%3A+Mutation+Tracking,
>>> but please keep the discussion on the dev list.
>>>
>>> Thanks!
>>>
>>> Blake Eggleston
>>>
>>
>>
--
Dmitry Konstantinov
45%3A+Mutation+Tracking,
> but please keep the discussion on the dev list.
>
> Thanks!
>
> Blake Eggleston
>
--
Dmitry Konstantinov
Thank you, Brandon!
I have moved the page to
https://cwiki.apache.org/confluence/display/CASSANDRA/SSTable%27s+partition+cardinality+implementation
On Fri, 3 Jan 2025 at 14:45, Brandon Williams wrote:
> I've granted access to the account "Dmitry Konstantinov (netudima)"
ve that page to a more
> appropriate part of the Apache wiki as soon as you can.
>
> Thanks!
> BKP
>
> On 2025/01/03 13:55:49 Dmitry Konstantinov wrote:
> > I have summarized information from this mail thread to
> >
> https://cwiki.apache.org/confluence/display/COC/SST
gt;>>>>
>>>>> If we are to replace the library, we should at the very least do
>>>>> proper due diligence by reviewing the new library’s implementation(s)
>>>>> ourselves. We cannot simply assume the new library behaves well for our
&g
>> was, how many tables there are etc. On an idle system thats meaningless, if
>> there were 5gb/s allocations of reads/writes happening at the time thats
>> huge.
>>
>> On Thu, Jan 2, 2025 at 8:42 AM Štefan Miklošovič
>> wrote:
>>
>>> Interesting,
Hi,
Can somebody help with reviewing of
https://issues.apache.org/jira/browse/CASSANDRA-20132.
When tombstones are expired they become almost invisible from a monitoring
point view: you do not see them in metrics and tracing except a latency
impact. I have observed such cases in production when co
unds. I think it is worth trying to do something with this. Would be
>> great if you were part of this effort!
>>
>> On Thu, Jan 2, 2025 at 3:38 PM Dmitry Konstantinov
>> wrote:
>>
>>> I have seen this place in async profiler memory allocation profile on
>
Hello All,
Some time ago I have submitted a patch what makes UDT codec tolerant to
extra unknown fields at the tail of UDT to support live schema upgrades:
https://issues.apache.org/jira/browse/CASSJAVA-4
Could someone help with reviewing it?
Thank you for your time!
--
Dmitry Konstantinov
Hello All,
I recently submitted a patch what addresses a bug in idealCLWriteLatency
metric calculation: https://issues.apache.org/jira/browse/CASSANDRA-19651
Could someone help with reviewing it?
Thank you for your time!
--
Dmitry
idea was to migrate
fully to the Cassandra networking_cache as a Netty allocator?
Thank you,
Dmitry
--
Dmitry Konstantinov
--
Dmitry Konstantinov
40 matches
Mail list logo
