Re: CI's working, and repeatable !!

2024-04-28 Thread Josh McKenzie
A huge amount of work and time went into this and it's going to have a big impact on the project. I want to offer a heartfelt thanks to all involved for the focus and energy that went into this! As the author of the system David lovingly dubbed "JoshCI" (/sigh), I definitely want to see us all

CI's working, and repeatable !!

2024-04-28 Thread Mick Semb Wever
Good news. CI on 5.0 and trunk is working again, after an unexpected 6 weeks hiatus (and a string of general problems since last year). This includes pre-commit for 5.0 and trunk working again. More info… >From 5.0 we now have in-tree a Jenkinsfile that only relies on the in-tree scripts – it d

Re: [DISCUSS] Donating easy-cass-stress to the project

2024-04-28 Thread Mick Semb Wever
> > A separate subproject like dtest and the Java driver would maybe help > address concerns with introducing a gradle build system and Kotlin. > Nit, dtest is a separate repository, not a subproject. The Java driver is one repository to be in the Drivers subproject. Esoteric maybe, but ASF ter

Re: compaction trigger after every fix interval

2024-04-28 Thread manish khandelwal
Hi Prerna Compactions are triggered automatically based on the compaction strategy. Since you are seeing compactions triggered every 6 hours, the thing that can be happening is you have such a kind of traffic where you have lots of writes every 6 hours. PS: Please use the user mailing list (u.

compaction trigger after every fix interval

2024-04-28 Thread Prerna Jain
Hi team, I have a query, in our prod environment, there are multiple key spaces and tables. According to requirements, every table has different compaction strategies like level/time/size. Somehow, when I checked the compaction history, I noticed that compaction occurs every 6 hr for every table.