I am using C*2.1 and DevCenter 1.3.1, it is not easy to upgrade C*2.1 to
C*2.2 since it running in production, but I will upgrade the DevCenter.
Thanks
Rock
On Aug 5, 2015, at 2:03 PM, Dan Jatnieks wrote:
Hi Rock,
I was not able to reproduce this problem using C* 2.2 and DevCenter 1.4.
What v
I'm passing this along from the DataStax Support folks.
This shouldn't affect new installs, since the install instruction will
pull the new expiry, but for users that already have a DSC/DSE Debian
repository configured, apt-get update/install will warn about the
expired key after 8/13.
curl
I agree with Jeff, those 2 solution should work well indeed to have
distinct cluster (data will be fixed in time, not synchronised).
It really depends on you but basically having hybride data storage
structures is not an issue at all in both cases as it is something that you
can set in the cassand
I forget to specify that you will obtain 2 DC instead of 2 cluster, the
main differences are that DCs are connected through gossip and keep synced
(make sure your clients are sticked to your main DC). Depending on what you
want to achieve you might want 2 clusters or 2 DC.
2015-08-06 22:31 GMT+02:
You can copy all of the sstables into any given data directory without issue
(keep them within the keyspace/table directories, but the mnt/mnt2/mnt3
location is irrelevant).
You can also stream them in via sstableloader if your ring topology has changed
(especially if tokens have moved)
From
Hi Gerard,
You should probably add a new datacenter following this procedure :
http://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_add_dc_to_cluster_t.html
You will just have to make sure to configure all the nodes of the new nodes
to use mnt + mnt2 instead of mnt + mnt2 + mnt3.
M
We do not use a tool exactly. We use spark to assert all of our data is in
tact, taking into account the changes that you have to make going from
rdbms to nosql.
On Thu, Aug 6, 2015 at 1:32 PM, Huang, Roger wrote:
> Surbhi
>
> Sorry I meant to send the CQL link
> http://docs.datastax.com/en/cql
Surbhi
Sorry I meant to send the CQL link
http://docs.datastax.com/en/cql/3.1/cql/cql_intro_c.html
Roger
From: Huang, Roger [mailto:rohu...@visa.com]
Sent: Thursday, August 06, 2015 11:39 AM
To: user@cassandra.apache.org
Subject: RE: Validation of Data after data migration from RDBMS to Cassandr
Hi,
I'm currently trying to duplicate a given keyspace on a new cluster to run
some analytics on it.
My source cluster has 3 disks and corresponding data directories (mnt,
mnt2, mnt3) but the machines in my target cluster only have 2 disks (mnt,
mnt2).
What should be the correct procedure to cop
Surbhi,
A general note, Cassandra tables are not normalized as in an RDBMS schema, so
it’s not straight migration.
Best practice is to design your queries and then design your Cassandra schema
to support those queries.
Patrick McFadin has a series on C* data modeling.
http://docs.datastax.com/en/
Hi,
We have to migrate the data from Oracle/mysql to Cassandra.
I wanted to understand, if we have any tool/utilitiy which can help in
validation the data after the data migration to Cassandra.
Thanks
Surbhi
You’re trying to force your view onto an established ecosystem. It’s not “wrong
only because its currently bootstrapping”, it’s not bootstrapping at all, you
told it not to bootstrap.
‘auto_bootstrap’ is the knob that tells cassandra whether or not you want to
stream data from other replicas w
It was suggested to me that I try running scrub on the other nodes in the
cluster, as the runtime exceptions I was seeing might be relevant to some
bad data. I am going to try that this morning and see how things go. Not
sure how long is long enough for nodetool scrub to run on a box though.
As fo
Hi Rob,
> Your asking the wrong nodes for data in the rebuild-a-new-DC case does not
> indicate a problem with the auto_bootstrap false + rebuild paradigm.
>
The node is "wrong" only because its currently bootstrapping. So imho
Cassandra should not serve any reads in such a case.
>
> What ma
Thank you Nick for the information.
--
Cyril SCETBON
> On Aug 5, 2015, at 15:35, Nick Bailey wrote:
>
> Cyril,
>
> That ticket should be fixed in the latest 5.2 series of OpsCenter. The fix
> did not make it into the 5.1 release series unfortunately.
>
> -Nick
>
> On Wed, Aug 5, 2015 at 3:4
15 matches
Mail list logo
