In evaluating 3.x, we found that hints are unable to be replayed between
2.x and 3.x nodes. This introduces a risk during the upgrade path for some
of our write-heavy clusters - nodes will accumulate upwards of 1TB of hints
if a node goes/remains down for <1hr.
Any suggestions to mitigate this
lid>
wrote:
> Hi Andrew,
>
> Do you mind sharing the backport patch? We're very interested in that,
> 20-30% improvement sounds great to us.
>
> Thanks,
> Jay
>
> On 7/27/17 11:52 PM, Andrew Whang wrote:
> > Yes, seeing latency improvement after backporting 9
after you backported 9472 to 3.0?
>
> --
> Jeff Jirsa
>
>
> > On Jul 27, 2017, at 10:33 PM, Andrew Whang <andrewgwh...@gmail.com>
> wrote:
> >
> > Jay,
> >
> > We see ~20% write latency improvement on 3.0.13 in a write-heavy
> workload,
> >
mance gain from reintroducing off-heap memtables for
> 3.0.x? When we were on 2.2.x we saw big improvements from enabling
> off-heap memtables.
>
> Thanks,
> Jay
>
> On 7/27/17 9:37 PM, Andrew Whang wrote:
> > I'm wondering if anyone has been able to patch CASSANDRA-9472 to 3.0,
I'm wondering if anyone has been able to patch CASSANDRA-9472 to 3.0,
without breaking unit tests. The patch was introduced in 3.4, but 3.0.x
contains unit tests and code from later 3.x releases, which makes debugging
unit test failures difficult - i.e. SSTableCorruptionDetectionTest, which
was
Hi,
I'm seeing perf regressions (using cassandra-stress) between 2.2.5 and
3.11. I understand these versions are quite far apart, but just wondering
if there are stress results publicly available that compare 2.x to 3.x?
Thanks.
