Debian compatibility

[netflix]

Debian compatibility

[sorenvind]

Ok, here's an update on my progress. I reverted back to Cassandra 1.0.10 to be able to run get_seeds/get_token and get a correct response. Also, I found that Cassandra would bind to 127.0.0.1, so to let it bind to the local ip, I've removed 127.0.0.1 from /etc/hosts. This seems to work.

By applying the fix to JSVC by codyaray, I am now in a situation where get_token returns the same token value as nodetool. However, nodetool only reports the local machine I'm running it on - it seems that it can't see the other hosts. I'm running with hosts only in eu-west-1a and have set priam.zones.available accordingly. I am able to connect to the other hosts (I have a security group with everything allowed by now). I'm a little stuck here, do you have any suggestions to what I might be missing?

Thanks!
Søren

[sorenvind]

Ok, after yet another couple of days I FINALLY got things working!

Here's a few notes for you:

• I decided to expand to using two zones (eu-west-1a, eu-west-1b) to make sure that the single-zone deployment wasn't causing the issue. On doing so, Priam exploded because I included a space between the zones in the priam.zones.available property. Reading that property should probably be made a little more robust (e.g. trimming spaces). Sadly, this did not remove my problem.
• I finally discovered that the wrong cassandra.yaml was read. It turns out that on Debian the classpath ordering was such that the cassandra.yaml added in commit faa2ce7f7f352c50caa0be372ba9c485d349d837 was read before /etc/cassandra/conf/cassandra.yaml. The quickest fix is to change the classpath definition in /etc/init.d/cassandra so the configuration file folder is before the lib file. Suggestion: Remove the default cassandra.yaml in Priam (or at least rename it to something non-clashing).

I'll submit a suggested fix for these problems later.

[aryanet]

sorenvind: about your issue with maven not being able to find jvnet stuff, I found it this is an issue with maven 2.2.1's http driver not being able to follow symlinks for moved package in central. I upgraded to maven3 and use this command instead and it fetched all the dependencies just fine:

mvn3 -Dmaven.wagon.provider.http=httpclient clean compile jar:jar war:war

[sorenvind]

Aryanet: Thank!

Status here: Things seem to be running fine. I'll close the issue and can confirm that it's possible but somewhat difficult to get things rolling on Debian in the current state.