On Wed, Dec 18, 2013 at 7:31 PM, Robert Coli wrote:
> On Wed, Dec 18, 2013 at 2:44 AM, Sylvain Lebresne wrote:
>
>> As Janne said, you could still have hint being written by other nodes if
>> the one storage node is dead, but you can use the system
>> property cassandra.maxHintTTL to 0 to disable
Probably yes, if you also disabled any sort of failovers from the token-aware
client…
(Talking about this makes you realize how many failsafes Cassandra has. And
still you can lose data… :-P)
/Janne
On 18 Dec 2013, at 20:31, Robert Coli wrote:
> On Wed, Dec 18, 2013 at 2:44 AM, Sylvain Lebr
On Wed, Dec 18, 2013 at 2:44 AM, Sylvain Lebresne wrote:
> As Janne said, you could still have hint being written by other nodes if
> the one storage node is dead, but you can use the system
> property cassandra.maxHintTTL to 0 to disable hints.
>
If one uses a Token Aware client with RF=1, that
> -Original Message-
> From: Sylvain Lebresne [mailto:sylv...@datastax.com]
> Sent: 18 December 2013 12:46
> Google up NetworkTopologyStrategy. This is what you want to use and it's
> not configured in cassandra.yaml but when you create the keyspace.
>
> Basically, you define your topology
Google up NetworkTopologyStrategy. This is what you want to use and it's
not configured in cassandra.yaml but when you create the keyspace.
Basically, you define your topology in cassandra-topology.yaml (where you
basically manually set which node is in which DC, which you can really just
see as a
> -Original Message-
> From: Sylvain Lebresne [mailto:sylv...@datastax.com]
> Sent: 18 December 2013 10:45
>
> You seem to be well aware that you're not looking at using Cassandra for
> what it is designed for (which obviously imply you'll need to expect under-
> optimal behavior), so I'm
You seem to be well aware that you're not looking at using Cassandra for
what it is designed for (which obviously imply you'll need to expect
under-optimal behavior), so I'm not going to insist on it.
As to how you could achieve that, a relatively simple solution (that do not
require writing your
> -Original Message-
> From: Janne Jalkanen [mailto:janne.jalka...@ecyrd.com]
>
> Essentially you want to turn off all the features which make Cassandra a
> robust product ;-).
Oh, I don't want to, but sadly those are the requirements that I have to work
with.
Again, the context is usin
This may be hard because the coordinator could store hinted handoff (HH) data
on disk. You could turn HH off and have RF=1 to keep data on a single instance,
but you would be likely to lose data if you had any problems with your
instances… Also you would need to tweak the memtable flushing so t
