Cool, good to know. Do you know this is still true for 3.11.1?
> Am 03.02.2018 um 08:19 schrieb Oleksandr Shulgin
> :
>
> On 3 Feb 2018 02:42, "Kyrylo Lebediev" wrote:
> Thanks, Oleksandr,
> In my case I'll need to replace all nodes in
On 3 Feb 2018 02:42, "Kyrylo Lebediev" wrote:
Thanks, Oleksandr,
In my case I'll need to replace all nodes in the cluster (one-by-one), so
streaming will introduce perceptible overhead.
My question is not about data movement/copy itself, but more about all this
token
Thanks, Oleksandr,
In my case I'll need to replace all nodes in the cluster (one-by-one), so
streaming will introduce perceptible overhead.
My question is not about data movement/copy itself, but more about all this
token magic.
Okay, let's say we stopped old node, moved data to new node.
Once
Java 9 is a significantly larger issue, see CASSANDRA-9608.
> On Feb 2, 2018, at 8:49 AM, Kant Kodali wrote:
>
> When you say latest Java runtime you mean does it work with Java 9 as well?
>
> On Fri, Feb 2, 2018 at 5:02 AM, Sam Tunnicliffe
When you say latest Java runtime you mean does it work with Java 9 as well?
On Fri, Feb 2, 2018 at 5:02 AM, Sam Tunnicliffe wrote:
> I've actually just committed the fix for this to the 3.11 and trunk
> branches, so if you desperately need a compatible build you can make build
On Fri, Feb 2, 2018 at 3:15 PM, Kyrylo Lebediev
wrote:
> Hello All!
>
> I've got a pretty standard task - to replace a running C* node [version
> 2.1.15, vnodes=256, Ec2Snitch] (IP address will change after replacement,
> have no control over it).
>
> There are 2 ways
Hello All!
I've got a pretty standard task - to replace a running C* node [version 2.1.15,
vnodes=256, Ec2Snitch] (IP address will change after replacement, have no
control over it).
There are 2 ways stated in C* documentation how this can be done:
1) Add a new node, than 'nodetool
I've actually just committed the fix for this to the 3.11 and trunk
branches, so if you desperately need a compatible build you can make build
from those branches.
As I mentioned on the JIRA, I expect we'll move to a release vote very
soon, so hopefully should have a 3.11.2 release with this fix
you can try to checkout https://github.com/beobal/cassandra/tree/14173-3.11
and compile yourself a compatible version (unreleased), in case you are bound
to
the latest java runtime for any reason.
Marcus Haarmann
Von: "Kant Kodali"
An: "user"
Wouldn’t that still try to read the index on the disk? So you would just
potentially have all keys on the memory and on the disk and reading would first
happen in memory and then on the disk and only after that you would read the
sstable.
So you wouldn’t gain much, right?
Hannu
> On 2 Feb
10 matches
Mail list logo