Seeing similar errors on another system (0.7.4). Maybe something bogus with
the hint columnfamilies.
Terje
On Mon, Mar 28, 2011 at 7:15 PM, Shotaro Kamio wrote:
> I see. Then, I'll remove the HintsColumnFamily.
>
> Because our cluster has a lot of data, running repair takes much time
> (more th
I see. Then, I'll remove the HintsColumnFamily.
Because our cluster has a lot of data, running repair takes much time
(more than a day). And it's a kind of pain. It often causes disk full,
creates many sstables and degrades read performance.
If it's easy to fix the hint, it could be less painful s
Why would you try to repair hints?
If you run repair on the non-system data then you don't need the hint
data and can remove it.
On Sun, Mar 27, 2011 at 12:17 AM, Shotaro Kamio wrote:
> Hi,
>
> Our cluster uses cassandra 0.7.4 (upgraded from 0.7.3) with
> replication = 3. I found that error occu
Hi Aaron,
I saw the discussion and I already tried to repair. But it doesn't
work since it's HintsColumnFamily. it's not replicated to other nodes.
Any suggestions are welcome.
Thanks,
Shotaro
On Sun, Mar 27, 2011 at 2:25 PM, aaron morton wrote:
> Similar case
> here http://www.mail-archive.
Similar case here
http://www.mail-archive.com/user@cassandra.apache.org/msg11358.html
Suggestion was to run repair if scrub raises an error.
Aaron
On 27 Mar 2011, at 16:17, Shotaro Kamio wrote:
> Hi,
>
> Our cluster uses cassandra 0.7.4 (upgraded from 0.7.3) with
> replication = 3. I found t
Hi,
Our cluster uses cassandra 0.7.4 (upgraded from 0.7.3) with
replication = 3. I found that error occurs on one node during hinted
handoff with following error (log #1 below).
When I tried out "scrub system HintsColumnFamily", I saw an ERROR in
log (log #2 below).
Do you think these errors are c
