Re: compaction trigger after every fix interval
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...@cassandra.apache.org) for posting such queries. Regards Manish On Sun, Apr 28, 2024 at 2:26 PM Prerna Jain wrote: > 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. > We did not trigger any job manual and neither did I find any configuration. > Can you please help me find out the root cause of this case. > > I appreciate any help you can provide. > > Regards > Prerna Jain >
Re: Regarding CASSANDRA-14227
Hi Benjamin, thanks for your response. And Berenguer Blasi you are the shining light for us. Regards Manish On Tue, Feb 21, 2023 at 3:04 PM Berenguer Blasi wrote: > I'm actively working on it :-) > On 21/2/23 9:56, Benjamin Lerer wrote: > > Hi Manish, > It is unfortunately not an easy bug to fix as it has some significant > impact at different levels of the code base. > The plan is to have the fix as part of 5.0 which should be released later > this year. > > Le mar. 21 févr. 2023 à 09:48, manish khandelwal < > manishkhandelwa...@gmail.com> a écrit : > >> Hi Team >> >> We are hit by this bug as we approach the deadline as we reach close to >> 2038 as we can see some of our projects breaching the deadline fixed. >> I can see some progress made in this bug by Berenguer Blasi in last few >> months. I do understand that review timings and development can not be >> predicted but it would be helpful in planning and updating our projects >> with some tentative dates/release when this bug can be targeted. >> >> I would appreciate any indication from community on this. >> >> Regards >> Manish >> >
Regarding CASSANDRA-14227
Hi Team We are hit by this bug as we approach the deadline as we reach close to 2038 as we can see some of our projects breaching the deadline fixed. I can see some progress made in this bug by Berenguer Blasi in last few months. I do understand that review timings and development can not be predicted but it would be helpful in planning and updating our projects with some tentative dates/release when this bug can be targeted. I would appreciate any indication from community on this. Regards Manish
JIRA account creation request
Hi I would like to get my JIRA account created as I would like to contribute. Here are my details email address : manishkhandelwa...@gmail.com If any other information is needed please let me know. Regards Manish
Re: Unsubscribe
.Please email dev-unsubscr...@cassandra.apache.org for unsubscrbing. Regards Manish On Wed, Jul 20, 2022, 06:14 @Nandan@ wrote: > Unsubscribe me plzz >
CASSANDRA-16465
While studying open bugs for upgrading to 3.11.11, I found this bug ( https://issues.apache.org/jira/browse/CASSANDRA-16465) which causes increased read latency. I would like to know that is this bug occurs with some specific workloads or it is generic issue with all workloads. Is there any workaround available to circumvent this issue? Not seen much activity around this issue. Regards Manish
Re: Regarding JIRA Cassandra-14227
Thanks Michael for updating the severity and complexity of this JIRA ticket. With time ticking lots of use cases might start failing, unable to meet TTL criteria for them. Regards Manish On Fri, Jun 12, 2020 at 8:41 PM Michael Shuler wrote: > I updated the severity and complexity of this ticket. It is not a > trivial fix, but I agree that as time goes on, this is becoming higher > priority to focus some effort on it. > > (fyi, I'm not volunteering, is way beyond my means :) ) > > Kind regards, > Michael > > On 6/10/20 11:55 PM, manish khandelwal wrote: > > Hi Team > > > > We are not able to insert data with large TTLs (expiration time beyond > > 2038-01-19T03:14:06+00:00). > > > > Even though https://jira.apache.org/jira/browse/CASSANDRA-14092 > prevented a > > workaround to avoid data loss, the permanent fix is still pending. I can > > see that the JIRA: https://jira.apache.org/jira/browse/CASSANDRA-14227 > which > > was open for permanent fix is still in unassigned state. I think it’s a > > high priority issue as the timestamp limit is continuously reducing as we > > approach 2038. > > > > > > Are there any plans to prioritize this JIRA ticket : > > https://jira.apache.org/jira/browse/CASSANDRA-14227 > > > > > > Regards > > > > Manish > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
Regarding JIRA Cassandra-14227
Hi Team We are not able to insert data with large TTLs (expiration time beyond 2038-01-19T03:14:06+00:00). Even though https://jira.apache.org/jira/browse/CASSANDRA-14092 prevented a workaround to avoid data loss, the permanent fix is still pending. I can see that the JIRA: https://jira.apache.org/jira/browse/CASSANDRA-14227 which was open for permanent fix is still in unassigned state. I think it’s a high priority issue as the timestamp limit is continuously reducing as we approach 2038. Are there any plans to prioritize this JIRA ticket : https://jira.apache.org/jira/browse/CASSANDRA-14227 Regards Manish
Regarding CASSANDRA-14227
Hi Team We are not able to insert data with large TTLs (expiration time beyond 2038-01-19T03:14:06+00:00). Even though https://jira.apache.org/jira/browse/CASSANDRA-14092 prevented a workaround to avoid data loss, the permanent fix is still pending. I can see that the JIRA: https://jira.apache.org/jira/browse/CASSANDRA-14227 which was open for permanent fix is still in unassigned state. I think it’s a high priority issue as the timestamp limit is continuously reducing as we approach 2038. Are there any plans to prioritize and fix the ticket? Regards Manish
