I encountered this situation also once or twice but didn't succeed. I just
deleted the old hints and ran a repair 😂
Am 13.04.2017 10:35 schrieb "Roland Otta" :
> unfortunately it does not.
>
> i guess this is intended for resuming hinted handoff handling in case it
> hase been paused with the pau
unfortunately it does not.
i guess this is intended for resuming hinted handoff handling in case it hase
been paused with the pausehandoff before.
i have tested it (resuming .. pausing & resuming) but it has no effect on those
old hints
On Thu, 2017-04-13 at 10:27 +0200, benjamin roth wrote:
Th
There is a nodetool command to resume hints. Maybe that helps?
Am 13.04.2017 09:42 schrieb "Roland Otta" :
> oh ... the operation is deprecated according to the docs ...
>
>
> On Thu, 2017-04-13 at 07:40 +, Roland Otta wrote:
> > i figured out that there is an mbean
> > org.apache.cassandra.d
oh ... the operation is deprecated according to the docs ...
On Thu, 2017-04-13 at 07:40 +, Roland Otta wrote:
> i figured out that there is an mbean
> org.apache.cassandra.db.type=HintedHandoffManager with the operation
> scheduleHintDelivery
>
> i guess thats what i would need in that case
i figured out that there is an mbean
org.apache.cassandra.db.type=HintedHandoffManager with the operation
scheduleHintDelivery
i guess thats what i would need in that case. at least the docs let me
think so http://javadox.com/org.apache.cassandra/cassandra-all/3.0.0/or
g/apache/cassandra/db/Hinted
hi,
sometimes we have the problem that we have hinted handoffs (for example
because auf network problems between 2 DCs) that do not get processed
even if the connection problem between the dcs recovers. Some of the
files stay in the hints directory until we restart the node that
contains the hints
