GitHub user aledsage opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/81
cassandra v2 support
Adds support for Cassandra v2, and for Cassandra
Note I'm having problems with `JAVA_HOME` which really should be addressed
before merging.
In `CassandraDatacenterLiveTest.testDatacenterWithVnodesVersion2` (running
on CentOS on EC2), I had to add `.configure("shell.env",
MutableMap.of("JAVA_HOME", "/etc/alternatives/java_sdk_1.7.0"))`. The VM had
Java 1.6 installed already; brooklyn then installed `java-1.7.0-openjdk-devel`.
At that point, `which java` reported 1.7. However, running Cassandra (with the
remote `ssh` commands) still picked up 1.6 until I explicitly set `JAVA_HOME`.
This could perhaps be an issue with `~/.profile` etc not being sourced for the
`ssh` commands.
@ahgittin @grkvlt any opinions on how to portably/reliably upgrade to Java
1.7 such that Cassandra picks it up?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aledsage/incubator-brooklyn
feature/cassandra-v2-support
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/81.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #81
----
commit 85d1ac083957279a0ad2e68b0e07364f20266a55
Author: Aled Sage <[email protected]>
Date: 2014-07-16T14:39:42Z
Support for cassandra v2 and vnodes
- adds USE_VNODES config for v1.2 and v2
- adds numTokensPerNode config
- adds checkForAndInstllJava7or8
- make AstyanaxSupport more robust for testing
commit 6ea80b3d5895061f00868cb20164590ba09ef7ea
Author: Aled Sage <[email protected]>
Date: 2014-07-18T13:46:11Z
Adds JmxHelper.terminate()
- important for entity stop(), if a connect attempt is taking a very
long time to timeout and there are other jobs backing up.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
