On Wed, Jan 25, 2017 at 9:55 PM, Sam Overton wrote:
> Hello cassandra-dev,
>
> I would like to continue the momentum on improving Cassandra's tracing,
> following Mick's excellent work on pluggable tracing and Zipkin support.
>
> There are a couple of areas we can improve that would make tracing a
We are just getting started with 3.0.10. Will let you know.
On Wed, Jan 25, 2017 at 12:00 PM, Nate McCall wrote:
> There was CASSANDRA-12269 fixed in 3.10 recently as well.
>
> On Wed, Jan 25, 2017 at 11:47 AM, Dikang Gu wrote:
> > We still see perf regression with the otc_coalescing_strategy d
Hello cassandra-dev,
I would like to continue the momentum on improving Cassandra's tracing,
following Mick's excellent work on pluggable tracing and Zipkin support.
There are a couple of areas we can improve that would make tracing an even
more
useful tool for cluster operators to diagnose ongoi
There was CASSANDRA-12269 fixed in 3.10 recently as well.
On Wed, Jan 25, 2017 at 11:47 AM, Dikang Gu wrote:
> We still see perf regression with the otc_coalescing_strategy disabled, and
> on 3.0.10 branches as well. We can share our stress test results here.
>
> @Sankalp, are you guys seeing any
We still see perf regression with the otc_coalescing_strategy disabled, and
on 3.0.10 branches as well. We can share our stress test results here.
@Sankalp, are you guys seeing any throughput regressions on 3.0.10 branch?
Thanks.
On Thu, Jan 19, 2017 at 2:33 PM, Jeremiah D Jordan <
jeremiah.jor.
