Ok found a solution for this problem.
I deleted the system's keyspace directory and restarted COSS and it was
rebuilt.
rm -rf /var/lib/cassandra/data/system
A bit drastic but I'll test it also on a multi-node cluster.
On Thu, Aug 17, 2017 at 3:57 PM, Ioannis Zafiropoulos
Thanks Felipe and Erick,
Yes, your comment helped a lot, I was able to resolve that by:
ALTER KEYSPACE dse_system WITH replication = {'class': 'SimpleStrategy',
'replication_factor':'1'};
Another problem I had was with CentOS release 6.7 (Final)
I was getting glibc 2.14 not found.
Based on this
Ioannis,
As some people already said, there's one or two keyspaces that uses
EverywhereStrategy, dse_system is one of them, if I'm not wrong.
You must remember to change them to a community strategy or it will fail.
--
We use NetworkTopologyStrategy as the replication strategy.
The only DSE specific features we use (left untouched by default) are:
authenticator: com.datastax.bdp.cassandra.auth.DseAuthenticator
authorizer: com.datastax.bdp.cassandra.auth.DseAuthorizer
role_manager:
I agree with Jeff, it’s not necessary to launch a new cluster for this
operation.
> On Aug 15, 2017, at 7:39 PM, Jeff Jirsa wrote:
>
> Or just alter the key space replication strategy and remove the DSE specific
> strategies in favor of network topology strategy
>
>
> --
Or just alter the key space replication strategy and remove the DSE specific
strategies in favor of network topology strategy
--
Jeff Jirsa
> On Aug 15, 2017, at 7:26 PM, Erick Ramirez wrote:
>
> Ioannis, it's not a straightforward process to migrate from DSE to COSS.
Ioannis, it's not a straightforward process to migrate from DSE to COSS.
There are some parts of DSE which are not recognised by COSS, e.g.
EverywhereStrategy for replication only known to DSE.
You are better off standing up a new COSS 3.11 cluster and restore app
keyspaces to the new cluster.
Haven't done it for 5.1 but went smoothly for earlier versions. If you're
not using any of the additional features of DSE, it should be OK. Just
change any custom replication strategies before migrating and also make
sure your yaml options are compatible.
Hi all,
We have setup a new cluster DSE 5.1.2 (with Cassandra 3.11.0.1758) and we
want to migrate it to Apache Cassandra 3.11.0 without loosing schema or
data.
Anybody, has done it before?
Obviously we are going to test this, but it would be nice to hear if
somebody else has gone through with