> How will you recommend doing schema level health checks (consistency) for
> Cassandra within the cluster?
describe cluster in the cli can be used to see how many schema versions there
are.
The similar functionality is included in most other clients.
Cheers
-
Aaron Morton
F
On Wed, Mar 21, 2012 at 4:45 AM, aaron morton wrote:
> no, describe cluster is a feature of the CLI.
>
>
How will you recommend doing schema level health checks (consistency) for
Cassandra within the cluster?
cheers,
Shoaib
no, describe cluster is a feature of the CLI.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 20/03/2012, at 11:24 AM, Shoaib Mir wrote:
> On Tue, Mar 20, 2012 at 4:18 AM, aaron morton wrote:
> There is a server side check to ensure that
That's correct. If you run describe cluster normally you'll see something
like:
Cluster Information:
Snitch: org.apache.cassandra.locator.SimpleSnitch
Partitioner: org.apache.cassandra.dht.RandomPartitioner
Schema versions:
3a0f6a80-7140-11e1--511aec3785ff: [IP_OF_NODE, IP_OF
On Tue, Mar 20, 2012 at 4:18 AM, aaron morton wrote:
> There is a server side check to ensure that all available nodes share the
> same schema version.
>
>
Is that checked using "describe cluster" ??
cheers,
Shoaib
There is a server side check to ensure that all available nodes share the same
schema version.
The migration will proceed though if any of the nodes are unavailable.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 17/03/2012, at 11:07 AM,
Hi guys,
While creating schema on our cluster today I didn't get any errors even
when some of the hosts in the cluster were unreachable (not the ones in the
same data centre but in another region). cli kept on showing all nodes
agreeing where all nodes were agreeing.
Now after this when I did "de
