Enforce best practices to save yourself and your organization from system debt
brought on by bad practices compounded by bad practices because some people are
beyond reproach. See bad practices as they are and correct them.
TLDR;
I still stick with my initial recommendations. What you are
Thank you Kurt
> On Mar 14, 2018, at 5:57 PM, kurt greaves wrote:
>
> At least set GCGS == max_hint_window_in_ms that way you don't effectively
> disable hints for the table while your compaction is running. Might be
> preferable to use nodetool garbagecollect if you
At least set GCGS == max_hint_window_in_ms that way you don't effectively
disable hints for the table while your compaction is running. Might be
preferable to use nodetool garbagecollect if you don't have enough disk
space for a major compaction. Also worth noting you should do a splitting
major
Can’t advise that without knowing the risk to your app if there’s data
resurrected
If there’s no risk, then sure - set gcgs to 0 and force / major compact if you
have the room
--
Jeff Jirsa
> On Mar 14, 2018, at 11:47 AM, Madhu-Nosql wrote:
>
> Jeff,
>
> Thank
Jeff,
Thank you i got this- how about Dropping the existing Tombstones right now
can setting gc_grace time to zero per Table level would be good or what
would you suggest?
On Wed, Mar 14, 2018 at 1:41 PM, Jeff Jirsa wrote:
> What version of Cassandra?
>
>
What version of Cassandra?
https://issues.apache.org/jira/browse/CASSANDRA-7304 sort of addresses this
in 2.2+
On Wed, Mar 14, 2018 at 11:32 AM, Madhu-Nosql wrote:
> Rahul,
>
> Tomstone caused is on the Application driver side so even though they are
> not using some
Rahul,
Tomstone caused is on the Application driver side so even though they are
not using some of the Columns in their logic
waht they did is that they mentioned in driver logic that means if you are
updateting one Column so the rest of the Columns so the driver automatically
pick some nulls,
Then don’t write nulls. That’s the root of the issue. Sometimes they surface
from prepared statements. Othertimes they come because of default null values
in objects.
--
Rahul Singh
rahul.si...@anant.us
Anant Corporation
On Mar 13, 2018, 2:18 PM -0400, Madhu-Nosql ,
We assume that's becoz of nulls
On Tue, Mar 13, 2018 at 12:58 PM, Rahul Singh
wrote:
> Are you writing nulls or does the data cycle that way?
>
> --
> Rahul Singh
> rahul.si...@anant.us
>
> Anant Corporation
>
> On Mar 13, 2018, 11:48 AM -0400, Madhu-Nosql
Are you writing nulls or does the data cycle that way?
--
Rahul Singh
rahul.si...@anant.us
Anant Corporation
On Mar 13, 2018, 11:48 AM -0400, Madhu-Nosql , wrote:
> Rahul,
>
> Nodetool scrub is good for rescue, what if its happening all the time?
>
> > On Tue, Mar 13, 2018
Rahul,
Nodetool scrub is good for rescue, what if its happening all the time?
On Tue, Mar 13, 2018 at 10:37 AM, Rahul Singh
wrote:
> Do you anticipate this happening all the time or are you just trying to
> rescue?
>
> Nodetool scrub can be useful too.
>
>
> --
>
Do you anticipate this happening all the time or are you just trying to rescue?
Nodetool scrub can be useful too.
--
Rahul Singh
rahul.si...@anant.us
Anant Corporation
On Mar 13, 2018, 11:29 AM -0400, Madhu-Nosql , wrote:
> I got few ways to Drop Tombstones- Chos
12 matches
Mail list logo