Re: Ticket CASSANDRA-3578 - Multithreaded CommitLog

2011/12/8 Piotr Kołaczkowski : > Right, this would be the best option to have an ability to write into > multiple log files, put on multiple disks. I'm not sure if it is part of > that ticket, though. It's not. I don't think anyone needs more than 80MB/s or so of commitlog bandwidth for a while.

Re: Ticket CASSANDRA-3578 - Multithreaded CommitLog

Right, this would be the best option to have an ability to write into multiple log files, put on multiple disks. I'm not sure if it is part of that ticket, though. Maybe we should split it into two things: parallel serialization / CRC and parallel writes to multiple logfiles (as another ticke

Jenkins build is still unstable: Cassandra-Coverage #184

See

Jenkins build is still unstable: Cassandra-0.8-Coverage #155

See

Jenkins build became unstable: Cassandra-0.7-Coverage #95

See

Build failed in Jenkins: Cassandra-0.8 #412

See Changes: [jbellis] merge from 0.7 -- [...truncated 747 lines...] AUNEWS.txt AUbuild.xml AUNOTICE.txt A tools A tools/stress A tools/stress/src A

Build failed in Jenkins: Cassandra-0.7 #556

See Changes: [jbellis] excise mention of 2189 from CHANGES since it didn't actually get fixed -- [...truncated 1776 lines...] [junit] [junit] Test org.apache.cassandra.locator.DynamicEndpoi

Build failed in Jenkins: Cassandra #1245

See Changes: [xedin] merge from 1.0 -- [...truncated 2386 lines...] [junit] Testsuite: org.apache.cassandra.locator.TokenMetadataTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed:

Build failed in Jenkins: Cassandra-quick #166

See Changes: [xedin] merge from 1.0 -- [...truncated 1740 lines...] [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.845 sec [junit] [junit] Testsuite: org.apache.cassand

Re: Ticket CASSANDRA-3578 - Multithreaded CommitLog

Another option is to have multiple threads reading from the queue and writing to their own commit log files. If you have multiple commit log directories with each having its own task writing to it, you can keep the "only sequential writes" optimization. Multiple writers to one disk only makes

Build failed in Jenkins: Cassandra #1244

See Changes: [slebresne] merge from 1.0 -- [...truncated 2409 lines...] [junit] Testsuite: org.apache.cassandra.locator.TokenMetadataTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elap

Build failed in Jenkins: Cassandra-quick #165

See Changes: [slebresne] merge from 1.0 -- [...truncated 1729 lines...] [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.86 sec [junit] [junit] Testsuite: org.apache.cass

Build failed in Jenkins: Cassandra-0.8 #411

See Changes: [slebresne] Detect misuses of CounterColumnType patch by slebresne; reviewed by jbellis for CASSANDRA-3422 -- [...truncated 2005 lines...] [junit] Testsuite: org.apache.cassandra.lo

Build failed in Jenkins: Cassandra #1243

See Changes: [eevans] Update to support TimeUUIDType (CASSANDRA-3541) Patch by eevans; reviewed by Pavel Yaskevich for CASSANDRA-2268 [eevans] optional CQL query support Patch by eevans; reviewed by Pavel Yaskevich for CASSANDRA-2268 [eev

Ticket CASSANDRA-3578 - Multithreaded CommitLog

Hello everyone, As an interview task I've got to make CommitLog multithreaded. I'm new to Cassandra project and therefore, before I start modifying code, I have to make sure I understand what is going on there correctly. Feel free to correct anything I got wrong or partially wrong. 1. The Co

Build failed in Jenkins: Cassandra-quick #164

See Changes: [eevans] Update to support TimeUUIDType (CASSANDRA-3541) Patch by eevans; reviewed by Pavel Yaskevich for CASSANDRA-2268 [eevans] optional CQL query support Patch by eevans; reviewed by Pavel Yaskevich for CASSANDRA-2268

Re: Build failed in Jenkins: Cassandra-quick #162

Unfortunately Jenkins tries to run all the Cassandra branches at once and gets port conflicts like this. Maybe we should restrict Jenkins to either current-stable or to trunk. On Wed, Dec 7, 2011 at 10:21 AM, Ted Crossman wrote: > Hi all, > > I was just wondering if this mailing list only sees t

Build failed in Jenkins: Cassandra #1242

See Changes: [slebresne] merge from 1.0 [jbellis] update CHANGES -- [...truncated 2382 lines...] [junit] Testsuite: org.apache.cassandra.locator.TokenMetadataTest [junit] Tests run: 3, Failure

Build failed in Jenkins: Cassandra-quick #163

See Changes: [slebresne] merge from 1.0 -- [...truncated 1712 lines...] [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.837 sec [junit] [junit] Testsuite: org.apache.cas

Re: Build failed in Jenkins: Cassandra-quick #162

Hi all, I was just wondering if this mailing list only sees the failures, while successful builds are happening and the list is not being alerted to them? Seems kind of pointless to have the e-mail being sent if no one does anything about them :) Just curious, tedo On 12/7/11 7:57 AM, Ap

Build failed in Jenkins: Cassandra-quick #162

See Changes: [jbellis] update CHANGES -- [...truncated 1694 lines...] [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.833 sec [junit] [junit] Testsuite: org.apache.cassa