[
http://jira.amdatu.org/jira/browse/AMDATUCASSANDRA-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivo Ladage - van Doorn resolved AMDATUCASSANDRA-150.
----------------------------------------------------
Resolution: Fixed
By marking the package dependencies with cassandra server optional, all seems
to work fine. Executed a small test with a remote cassandra server (running on
Amdatu) and an Amdatu stack with only the cassandra client. This seems to work
just fine.
You do get nasty stacktraces in the dashboard though if the remote server is
offline, the client should be able to deal with this situation properly.
> Support running Cassandra Daemon separately from Cassandra PM
> -------------------------------------------------------------
>
> Key: AMDATUCASSANDRA-150
> URL: http://jira.amdatu.org/jira/browse/AMDATUCASSANDRA-150
> Project: Amdatu Cassandra
> Issue Type: Task
> Components: Cassandra daemon
> Reporter: Ivo Ladage - van Doorn
> Assignee: Ivo Ladage - van Doorn
> Priority: Critical
> Labels: blueconic
> Fix For: 0.2.3
>
>
> In theory it should be possible to run two Amdatu stacks; one with the
> cassandra daemon installed and one with the persistence manager. They already
> communicate over Thrift, so that should work. However, we should test this
> setup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://jira.amdatu.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
