On 2017-07-27 21:36 (-0700), Mitch Gitman wrote:
> Now, the particular symptom to which that response refers is not what I was
> seeing, but the response got me thinking that perhaps the failures I was
> getting were on account of attempting to run "nodetool repair
> --partitioner-range" simult
Thanks Jeff
On Jul 30, 2017 11:22 PM, "Jeff Jirsa" wrote:
> start_native_transport: false
>
>
> --
> Jeff Jirsa
>
>
> > On Jul 30, 2017, at 7:14 PM, Pranay akula
> wrote:
> >
> > Hi,
> >
> > It is possible to disable binary in configuration when re-starting
> cassandra service, instead of disab
start_native_transport: false
--
Jeff Jirsa
> On Jul 30, 2017, at 7:14 PM, Pranay akula wrote:
>
> Hi,
>
> It is possible to disable binary in configuration when re-starting cassandra
> service, instead of disabling it using nodetool once the node is up.
>
>
>
> Thanks
> Pranay.
--
Hi,
It is possible to disable binary in configuration when re-starting
cassandra service, instead of disabling it using nodetool once the node is
up.
Thanks
Pranay.
You need check the node that failed validation to find the relevant error.
The IP should be in the logs of the node you started repair on.
You shouldn't run multiple repairs on the same table from multiple nodes
unless you really know what you're doing and not using vnodes. The failure
you are lik
