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
rg/jira/browse/CASSANDRA-4445
--
Sam Overton
Acunu | http://www.acunu.com | @acunu
comfortable committing 4121, 4122, 4125, 4127, 4123 as a group.
> From what I've seen, review should proceed fairly quickly, so
> hopefully floating the earlier ones a bit longer won't add much pain.
Agreed, that makes sense.
--
Sam Overton
Acunu | http://www.acunu.com | @acunu
suites but we will also be writing new tests in
addition.
I look forward to your questions and comments!
--
Sam Overton
Acunu | http://www.acunu.com | @acunu
There is now a parent ticket for this issue in JIRA:
https://issues.apache.org/jira/browse/CASSANDRA-4119
Comments and contributions are still welcome!
Cheers,
Sam
On 16 March 2012 23:38, Sam Overton wrote:
> Hello cassandra-dev,
>
> This is a long email. It concerns a significant
sale replacing the entire distribution logic in
Cassandra with CRUSH. I'm not sure if that's exactly what your design
is suggesting?
--
Sam Overton
Acunu | http://www.acunu.com | @acunu
On 20 March 2012 13:37, Eric Evans wrote:
> On Tue, Mar 20, 2012 at 6:40 AM, Sam Overton wrote:
>> On 20 March 2012 04:35, Vijay wrote:
>>> May be, what i mean is little more simple than that... We can consider
>>> every node having a multiple conservative ranges and
described previously is then fairly trivial. The only
additional change needed is to assign the tokens in some other way
which does not restrict the ranges to being contiguous.
--
Sam Overton
Acunu | http://www.acunu.com | @acunu
> For OPP the problem of load balancing is more profound. Now you need
> vnodes per keyspace because you can not expect each keyspace to have
> the same distribution. With three keyspaces you are not unsure as to
> which was is causing the hotness. I think OPP should just go away.
That's a good po
tokens into hot ranges. It makes sense that this would not be a
manual process, but there would certainly be more control than just
increasing or decreasing the number of tokens assigned to a node.
--
Sam Overton
Acunu | http://www.acunu.com | @acunu
ith more than two
replicas increases with declustering [Xin et al. 2004]"
("declustering" meaning increasing DF towards N)
Regards,
--
Sam Overton
Acunu | http://www.acunu.com | @acunu
is is how we anticipate support for heterogeneity in
cluster hardware.
Sam
--
Sam Overton
Acunu | http://www.acunu.com | @acunu
orward to your
input, ideas and recommendations.
Best Regards,
Sam Overton
[1] Staggering repair: https://issues.apache.org/jira/browse/CASSANDRA-3721
[2] Project Voldemort, Design: http://project-voldemort.com/design.php
[3] Dynamo:
http://www.allthingsdistributed.com/files/amazon-dynamo-sos
13 matches
Mail list logo
