cassandra pull request: Fix cassandra daemon management under debian/ubuntu
GitHub user lra opened a pull request: https://github.com/apache/cassandra/pull/21 Fix cassandra daemon management under debian/ubuntu This PR tries to fix 2 problems when installing the package on Ubuntu (and I think Debian) 1. `/var/run/cassandra` is missing and the pid file is not created on start, which renders the init script useless 2. the regexp used to check if cassandra is running does not match the launching command line (There is no "-user." in the launch command) You can merge this pull request into a Git repository by running: $ git pull https://github.com/lra/cassandra fix_debian_init_d Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cassandra/pull/21.patch
Re: cassandra pull request: Fix cassandra daemon management under debian/ubuntu
please add an apache jira ticket for this here: https://issues.apache.org/jira/browse/CASSANDRA On 09/24/2013 03:41 PM, lra wrote: GitHub user lra opened a pull request: https://github.com/apache/cassandra/pull/21 Fix cassandra daemon management under debian/ubuntu This PR tries to fix 2 problems when installing the package on Ubuntu (and I think Debian) 1. `/var/run/cassandra` is missing and the pid file is not created on start, which renders the init script useless 2. the regexp used to check if cassandra is running does not match the launching command line (There is no "-user." in the launch command) You can merge this pull request into a Git repository by running: $ git pull https://github.com/lra/cassandra fix_debian_init_d Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cassandra/pull/21.patch
2.1 / 3.0 roadmap
I'd like to focus 2.1 on technical debt as well as performance. I'm okay with not having big features to announce, other than custom types for CQL. If we focus on these, we should be able to hit a 2.1 release in January, with 3.0 back on a six month schedule for July. I note that we're still catching bugs introduced in 1.2.0; a short release focused on plumbing over features should give us a chance to catch up and release a 2.1.0 that can be more stable rather than less. We had a separate thread on performance tickets, summarized at [1]. I think these are the critical technical debts we need to pay off: - Counters (CASSANDRA-4775) - Repair overhead (CASSANDRA-5351 and possibly 3362) - Making CFIDs globally *and* temporally unique to prevent "re-using" data from an old incarnation in a drop/recreate cycle (CASSANDRA-5202) DataStax has engineers working on these, so I'm not asking for volunteers, but if there are other improvements that should be tier-1, I'd like to hear about those. (And volunteering would be great!) I don't yet have firm plans for 3.0, but I did want to float the idea early that we should kill CQL2 (CASSANDRA-5918). By July 2014 it will be 18 months after the introduction of CQL3 which is ample time to migrate. (Killing Thrift is still off the table indefinitely.) [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%2012310865%20AND%20labels%20%3D%20performance%20and%20status%3Dopen
