Distributed masterless architecture

Hi everyone, I am an undergrad student and working on a simple distributed database for learning purposes. I was wondering if you guys can give me tips about designing and coding distributed no master nodes. For instance what classes should I be looking for in source code? I am so sorry if

Re: CASSANDRA-9143

Agreed, I’d rather discuss the details on JIRA. It might be nice to send another email describing whatever conclusion we come to, after we have everything hashed out. > On Aug 24, 2016, at 4:09 PM, Paulo Motta wrote: > > Thanks for sharing this! I added some

Re: CASSANDRA-9143

Thanks for sharing this! I added some comments/suggestions on the ticket for those interested. On a side note, it's still not clear if we should do the discussion here on the dev-list or just call attention for a particular issue/ticket and then continue discussion on JIRA, but I find the latter

CASSANDRA-9143

Hi everyone, I just posted a proposed solution to some issues with incremental repair in CASSANDRA-9143. The solution involves non-trivial changes to the way incremental repair works, so I’m giving it a shout out on the dev list in the spirit of increasing the flow of information here.

Failing tests 2016-08-24 [cassandra-3.9]

=== testall: All passed! === dtest: 2 failures scrub_test.TestScrubIndexes.test_standalone_scrub CASSANDRA-12337. I've root-caused this; the failure is cosmetic but user-facing, so I plan on

Failing tests 2016-08-23 [cassandra-3.9]

=== testall: All passed! === dtest: 1 failure materialized_views_test.TestMaterializedViews .add_dc_after_mv_network_replication_test CASSANDRA-12140. Known issue, still needs to be solved.

3.8/3.9 releases/branch freeze, current merge order

TL;DR: cassandra-3.8 branch is dead; cassandra-3.9 is frozen, unless you are committing the fix for #12140 or #12528. For everything else go cassandra-3.0 -> trunk. There has been some confusion regarding the current branch merge order that I’d like to clarify. As you’ve seen from Joel’s last

Re: 3.8/3.9 releases/branch freeze, current merge order

Correction: s/12528/11195/g. I’m an idiot who cannot copy-paste. Also, cassandra-3.8 branch was removed from the repo, to further minimise confusion. --  AY On 24 August 2016 at 16:25:21, Aleksey Yeschenko (alek...@apache.org) wrote: TL;DR: cassandra-3.8 branch is dead; cassandra-3.9 is

Re: Distributed masterless architecture

You can read this blog post, there are a handful of interesting links: http://the-paper-trail.org/blog/distributed-systems-theory-for-the-distributed-systems-engineer/ On Wed, Aug 24, 2016 at 1:45 PM, Salih Gedik wrote: > Hi everyone, > I am an undergrad student and working on a

Re: 3.8/3.9 releases/branch freeze, current merge order

No. Removing a dead branch is just mindless admin work. As for 3.8/3.9 plans, look up the previous quite lengthy vote discussion on 3.8, on dev. --  AY On 24 August 2016 at 20:23:04, Mark Thomas (ma...@apache.org) wrote: On 24/08/2016 16:44, Aleksey Yeschenko wrote: > Also,

Re: 3.8/3.9 releases/branch freeze, current merge order

On 24/08/2016 20:26, Aleksey Yeschenko wrote: > No. Removing a dead branch is just mindless admin work. > > As for 3.8/3.9 plans, look up the previous quite lengthy vote discussion on > 3.8, on dev. Thanks. Found it. Just need to go back a little further in the archive. Mark > > -- > AY >

Re: 3.8/3.9 releases/branch freeze, current merge order

No worries. It was a somewhat.. messy thread. And it’s taken us a while to get the tests to this level, so it’s somewhat far away in time in the past. --  AY On 24 August 2016 at 20:43:39, Mark Thomas (ma...@apache.org) wrote: On 24/08/2016 20:26, Aleksey Yeschenko wrote: > No. Removing a

Re: 3.8/3.9 releases/branch freeze, current merge order

On 24/08/2016 16:44, Aleksey Yeschenko wrote: > Also, cassandra-3.8 branch was removed from the repo, to further minimise > confusion. That is the sort of thing I'd expect to see discussed on the dev list first. Where is that discussion? Mark

Re: 3.8/3.9 releases/branch freeze, current merge order

It's basically just removing a tag, nothing more. Completely trivial. --- On 2016-08-24 15:22, Mark Thomas wrote: On 24/08/2016 16:44, Aleksey Yeschenko wrote: Also, cassandra-3.8 branch was removed from the repo, to further minimise confusion. That is the sort of thing I'd expect to

Re: Distributed masterless architecture

Thanks for the resources! On 24.08.2016 21:27, DuyHai Doan wrote: You can read this blog post, there are a handful of interesting links: http://the-paper-trail.org/blog/distributed-systems-theory-for-the-distributed-systems-engineer/ On Wed, Aug 24, 2016 at 1:45 PM, Salih Gedik