On Tue, Jun 9, 2015 at 1:48 AM, ZeroUno wrote:
> As far as I read from the docs, bootstrapping happens when adding a new
> node to the cluster, but in my situation the nodes already exist, I'm only
> adding data back into them.
>
If you don't have the contents of the system keyspace, there is a
Il 08/06/15 20:11, Robert Coli ha scritto:
On Mon, Jun 8, 2015 at 6:58 AM, ZeroUno mailto:zerozerouno...@gmail.com>> wrote:
So... if I stop the two nodes on the first DC, restore their
sstables' files, and then restart the nodes, nothing else needs to
be done on the first DC?
Be ca
On Mon, Jun 8, 2015 at 6:58 AM, ZeroUno wrote:
> So you mean that "refresh" needs to be used if the cluster is running, but
> if I stopped cassandra while copying the sstables then refresh is useless?
> So the error "No new SSTables were found" during my refresh attempt is due
> to the fact that
Il 05/06/15 22:40, Robert Coli ha scritto:
On Fri, Jun 5, 2015 at 7:53 AM, Sebastian Estevez
mailto:sebastian.este...@datastax.com>>
wrote:
Since you only restored one dc's sstables, you should be able to
rebuild them on the second DC.
Refresh means pick up new SSTables that have b
On Fri, Jun 5, 2015 at 7:53 AM, Sebastian Estevez <
sebastian.este...@datastax.com> wrote:
> Since you only restored one dc's sstables, you should be able to rebuild
> them on the second DC.
>
> Refresh means pick up new SSTables that have been directly added to the
> data directory.
>
> Rebuild m
Since you only restored one dc's sstables, you should be able to rebuild
them on the second DC.
Refresh means pick up new SSTables that have been directly added to the
data directory.
Rebuild means stream data from other replicas to re create SSTables from
scratch.
On Jun 5, 2015 6:40 AM, "ZeroUn
Il 04/06/15 19:50, Robert Coli ha scritto:
http://www.pythian.com/blog/bulk-loading-options-for-cassandra/
Thank you Rob, but actually it doesn't matter to me which method is
used, I can use both nodetool refresh or sstableloader, as long as they
work! ;-)
My problem here is that it looks
Il 04/06/15 17:17, Sebastian Estevez ha scritto:
If you have all the sstables for each node and no token range changes,
you can just move the sstables to their spot in the data directory
(rsync or w/e) and bring up your nodes. If you're already up you can use
nodetool refresh to load the sstable
On Thu, Jun 4, 2015 at 5:39 AM, ZeroUno wrote:
> while defining backup and restore procedures for a Cassandra cluster I'm
> trying to use sstableloader for restoring a snapshot from a backup, but I'm
> not sure I fully understand the documentation on how it should be used.
>
http://www.pythian.c
You don't need sstable loader if your topology hasn't changed and you have
all your sstables backed up for each node. SStableloader actually streams
data to all the nodes in a ring (this is what OpsCenter backup restore
does). So you can actually restore to a larger or smaller cluster or a
cluster
Hi,
while defining backup and restore procedures for a Cassandra cluster I'm
trying to use sstableloader for restoring a snapshot from a backup, but
I'm not sure I fully understand the documentation on how it should be used.
Looking at the examples in the doc at
http://docs.datastax.com/en/ca
11 matches
Mail list logo
