Hi ,
There is an issue in going with this approach since we have to make
cassandra server component depend on this glue component. Since glue
component must get activated before the Cassandra server component.
So we used following approach as a solution.
- Implement a switch in Cassandra serv
On Wed, Apr 4, 2012 at 2:01 PM, Afkham Azeez wrote:
> It looks like we will need a gluing component that will take control of
> managing this dependency between Andes & Cassandra. Instead of the 2
> components initializing themselves independently and loading configuration
> independently, this 3
It looks like we will need a gluing component that will take control of
managing this dependency between Andes & Cassandra. Instead of the 2
components initializing themselves independently and loading configuration
independently, this 3 component should read the conf files (may be a
separate, merg
On Wed, Apr 4, 2012 at 12:18 PM, Charith Wickramarachchi
wrote:
> There is one more problem even going with this
> property/configuration based approach.
>
> In Our case Cassandra server must be started before starting andes related
> features.
> So if we go with this approach In a Cluster enabled
There is one more problem even going with this
property/configuration based approach.
In Our case Cassandra server must be started before starting andes related
features.
So if we go with this approach In a Cluster enabled mode User will have to
1) Change the andes-config.xml in which he will ena
Hi,
basically its bundles that get activated. There is not feature concept in
runtime. Configuration based approach is the only way to handle this kind
of scenario. However configuration can be done using,
property/xml file
system property
Some other bundle configuring the target through configura
On Wed, Apr 4, 2012 at 9:12 AM, Charith Wickramarachchi wrote:
> Hi All ,
>
> For Message Broker We use Cassandra feature to startup a Cassandra server
> instance with the broker as it uses Cassandra as the underlying storage.
> This is fine when broker is running as a standalone broker.
> But Whe
Hi All ,
For Message Broker We use Cassandra feature to startup a Cassandra server
instance with the broker as it uses Cassandra as the underlying storage.
This is fine when broker is running as a standalone broker.
But When we enable clustering we need to disable this. Where using the MB
Configur
