Say there are 1 vs three vs five vs 8 parts of a column key.
Will range slicing slow down the more parts there are? Will compactions be
impacted?
Hello Voytek,
In my opinion, It would be better for you to continue using
GossipingPropertyFileSnitch in AWS as well. I would do it to avoid
surprises. I've set up datacenters in AWS using GossipingPropertyFileSnitch
with zero problems.
Jean Carlo
"The best way to predict the future is to
With DataStax bulkloader you can only export from a Cassandra table but not
import into Cassandra (only load into DSE cluster).
And +1 on the confusing name of batches ... yes it’s for writes but not for
loading data.
Amanda
> On Aug 5, 2019, at 8:14 AM, Durity, Sean R
> wrote:
>
>
Hi Cyril,
it will depend on the load balancing policy that is used in the client code.
If you're only accessing DC1, with the node being rebuilt living in DC2,
then you need your clients to be using the DCAwareRoundRobinPolicy to
restrict connections to DC1 and avoid all kind of queries hitting
We have clients in all our DCs.
Rebuild has always been much faster for us than repairs. It operates as
bootstrap by streaming data from only one source replica for each token range
(need to do a cleanup if run multiple times). Repair is a different operation
and is not supposed to be run on
Can you elaborate on that ? We use GPFS without cassandra-topology.properties.
—
Cyril Scetbon
> On Aug 5, 2019, at 11:23 PM, Jeff Jirsa wrote:
>
> some snitch trickery (setting the badness for the rebuilding host) via jmx
cassandra-loader is also useful because you don't need to create sstables.
https://github.com/brianmhess/cassandra-loader
Hiro
On Tue, Aug 6, 2019 at 12:15 AM Durity, Sean R
wrote:
>
> DataStax has a very fast bulk load tool - dsebulk. Not sure if it is
> available for open source or not. In
