Even if it is a network error it would be good to detect it.
If you can run a small repair with those log settings I'll can take a look at
the logs if you want. Cannot promise anything but another set of eyes may help.
Ping me off list if you want to send me the logs.
Cheers
---
I had ran into the same problem before:
http://comments.gmane.org/gmane.comp.db.cassandra.user/25334
I have not fond any solutions yet.
Bill
On Mon, Jul 16, 2012 at 11:10 AM, Bart Swedrowski wrote:
>
>
> On 16 July 2012 11:25, aaron morton wrote:
>
>> In the before time someone had problems
On 16 July 2012 11:25, aaron morton wrote:
> In the before time someone had problems with a switch/router that was
> dropping persistent but idle connections. Doubt this applies, and it would
> probably result in an error, just throwing it out there.
>
Yes, been through them few times. There's
> Now, pretty much every single scenario points towards connectivity
> problem, however we also have few PostgreSQL replication streams
In the before time someone had problems with a switch/router that was dropping
persistent but idle connections. Doubt this applies, and it would probably
result
Hello everyone,
I'm facing quite weird problem with Cassandra since we've added
secondary DC to our cluster and have totally ran out of ideas; this
email is a call for help/advice!
History looks like:
- we used to have 4 nodes in a single DC
- running Cassandra 0.8.7
- RF:3
- around 50GB of data
