Sorry to intrude in this thread, but my intention is to get a clarity on
read_repair_chance.
Our reads doesn't need near real time data, so all our reads use CL.ONE. In
this case, how read repair happens in the replicas? what should be the
ideal value of read_repair_chance in this case?
how often
, 2012 at 12:01 AM, santi kumar wrote:
>
>> While running the nodetool repair , we are running into
>> FileNotFoundException with too many open files error. We increased the
>> ulimit value to 32768, and still we have seen this issue.
>>
>> THe number of files
While running the nodetool repair , we are running into
FileNotFoundException with too many open files error. We increased the
ulimit value to 32768, and still we have seen this issue.
THe number of files in the data directory is around 29500+.
If we further increase the limit of ulimt, would it
It makes sense. rpc_address is interface to listen. Try to set up public
> IP to broadcast_address.
>
> Andrey
>
>
> On Wed, Dec 12, 2012 at 9:33 AM, santi kumar wrote:
>
>> When I configured rpc_address with public IP, cassandra is not starting
>> up. It's t
s the registered RPC addresses for the
> nodes. Trying setting the rpc_address to the public IP.
>
> Cheers
>
> -
> Aaron Morton
> Freelance Cassandra Developer
> New Zealand
>
> @aaronmorton
> http://www.thelastpickle.com
>
> On 11/12/2012,
We have a 4 node cluster in us-east region in two different AZ's. Clients
connect to this cluster from our datacenter which is not on AWS.
Hector clients are initialized with public DNS names, then listern_address
is with private ip and rpc_address is with 0.0.0.0.
Having issues with Node Auto Di
