Hi,
I'm trying to use tablesnap [1] for disaster recovery backups, and while my
uploads seem to be working fine, I can't figure out how to run the
associated tableslurp tool for restores. If I pass the full S3 path to the
individual table to tableslurp, it will restore that table, but if I try to
According to the docs [1], when replacing a Cassandra node, I should start
the replacement with cassandra.replace_address specified. Does that just
become part of the replacement node's startup configuration? Can I (or do I
have to) stop specifying it at some point? Does this affect subsequent node
On Tue, Sep 8, 2015 at 11:14 AM, sai krishnam raju potturi <
pskraj...@gmail.com> wrote:
> Once the new node is bootstrapped, you could remove replacement_address
> from the env.sh file
>
Thanks, but how do I know when bootstrapping is completed?
On Thu, Sep 17, 2015 at 7:46 PM, Marc Tamsky wrote:
> This seems like an apt time to quote [1]:
>
> > Remember that you get 1 point for making a backup and 10,000 points for
> restoring one.
>
> Restoring from backups is my goal.
>
> The commonly recommended tools (tablesnap, cassandra_snapshotte
Following up on this older question: as per the docs, one *should* still do
full repair periodically (the docs say weekly), right? And run incremental
more often to fill in?
Hello,
I've been having some strange issues with one of our test clusters
(4-day-old, 3-node, 2.1.10 cluster on AWS). I saw a number of messages like
the following:
[] 10 Nov 20:21:00.406 * pri=WARN t=MessagingService-Incoming-/
192.168.168.202 at=IncomingTcpConnection.run UnknownColumnFamil
Oh and for what it's worth, I've also looked through the logs for this
node, and the oldest error in the logs seems to be:
[] 06 Nov 22:10:53.260 * pri=ERROR t=Thrift:16
at=CustomTThreadPoolServer.run Error occurred during processing of message.
java.lang.RuntimeException: java.util.concurrent
On Tue, Nov 10, 2015 at 3:20 PM, Sebastian Estevez <
sebastian.este...@datastax.com> wrote:
> #1 The cause of this problem is a CREATE TABLE statement collision. Do not
> generate tables
> dynamically from multiple clients, even with IF NOT EXISTS. First thing you
> need to do is
> fix your code
On Wed, Nov 11, 2015 at 9:55 AM, Sebastian Estevez <
sebastian.este...@datastax.com> wrote:
> Stupid question, but how do I find the problem table? The error message
>> complains about a keyspace (by uuid); I haven't seen errors relating to a
>> specific table. I've poked around in the data direct
Any advice on how to proceed here? Sebastian seems to have guessed
correctly at the underlying issue, but I'm still not sure how to resolve
this given what I see in the data directory and the catalogs.
On Wed, Nov 11, 2015 at 12:15 PM, Maciek Sakrejda wrote:
> On Wed, Nov 11, 2015 at
On Fri, Nov 13, 2015 at 9:56 AM, Sebastian Estevez <
sebastian.este...@datastax.com> wrote:
> I think you're just missing the steps in *Bold*:
>
> Thanks, but I wasn't clear on what to do if the "new" directory does not
exist at all on some of the nodes (only the old). Can I just rename the
"old"
Just wanted to follow up and say thanks: I went through this process (as
per Robert's suggestion, with the node stopped and no refresh) on an
affected cluster and was able to resolve the issue.
I'm still confused, even after reading the blog post twice (and reading the
linked Intel post). I understand what you are doing conceptually, but I'm
having a hard time mapping that to actual planned release numbers.
> The 3.0.2 will only contain bugfixes, while 3.2 will introduce new
features.
W
Thanks, Josh and Paulo--that's much clearer.
Anuj, do you have a link to the versioning policy? The tick-tock versioning
blog post [1] says that EOL happens after two major versions come out, but
I can't find this stated more formally anywhere. I'm interested in how long
a given version will receive patches for security issues or critical dat
15 matches
Mail list logo
