Probably question better suited for the dev@ list. But I afaik the answer
is there is no way to tell the difference, but probably safe to look at the
created time, HHs tend to be older.
Chris
On Wed, Aug 17, 2016 at 5:02 AM, Stone Fang wrote:
> Hi All,
>
> I want to differ hint
Hi All,
I want to differ hintedhandoff mutation and normal write mutation when i
receive a mutation.
how to get this in cassandra source code.have not found any attribute about
this in Mutation class.
or there is no way to get this.
thanks
stone
HintedHandoff on 1 node in my 12 node cluster
running 1.2.13. Somehow it’s holding a large amount of hints for tokens that
have never been part of the cluster. Pretty sure this is causing a bunch of
memory pressure somehow that’s causing the node to go down.
I’d like to find out if I can just
d you try to delete the hints via
> JMX in other nodes?
>
>
> On Mon, Jan 20, 2014 at 12:18 PM, Allan C wrote:
>
>> Hi ,
>>
>> I’m hitting a very odd issue with HintedHandoff on 1 node in my 12 node
>> cluster running 1.2.13. Somehow it’s holding a large amount
node or all. Did you try to delete the hints via JMX
in other nodes?
On Mon, Jan 20, 2014 at 12:18 PM, Allan C wrote:
Hi ,
I’m hitting a very odd issue with HintedHandoff on 1 node in my 12 node cluster
running 1.2.13. Somehow it’s holding a large amount of hints for tokens that
have never
Is this happening in one node or all. Did you try to delete the hints via
JMX in other nodes?
On Mon, Jan 20, 2014 at 12:18 PM, Allan C wrote:
> Hi ,
>
> I’m hitting a very odd issue with HintedHandoff on 1 node in my 12 node
> cluster running 1.2.13. Somehow it’s holding a lar
Hi ,
I’m hitting a very odd issue with HintedHandoff on 1 node in my 12 node cluster
running 1.2.13. Somehow it’s holding a large amount of hints for tokens that
have never been part of the cluster. Pretty sure this is causing a bunch of
memory pressure somehow that’s causing the node to go
first place might be a
>> spike in CF writes that must be replicated to a node in another data
>> center. The available bandwidth to that data center might not be able to
>> handle the data quickly enough, resulting in stored hints. The
>> HintedHandoff task that is
lating in the first place might be a
> spike in CF writes that must be replicated to a node in another data
> center. The available bandwidth to that data center might not be able to
> handle the data quickly enough, resulting in stored hints. The
> HintedHandoff task that is started i
not be able to
handle the data quickly enough, resulting in stored hints. The
HintedHandoff task that is started is targeting that remote node.
Thanks,
Tom
On Tue, Dec 3, 2013 at 2:22 PM, Rahul Menon wrote:
> Tom,
>
> Do you know why these hints are piling up? What is the size of the
Timed out replaying hints to {}; aborting ({} delivered
>>
>>
>>
>>
>>
>> OR
>>
>> Finished hinted handoff of {} rows to endpoint {}
>>
>>
>>
>> Thanks
>> Rahul
>>
>>
>> On Tue, Dec 3, 2013 at 2:36 PM, To
progress of a hinted handoff task?
>>
>> I found the following two mbeans providing some info:
>>
>> org.apache.cassandra.internal:type=HintedHandoff, which tells me that
>> there is 1 active task, and
>> org.apache.cassandra.db:type=HintedHandoffManager#countPen
providing some info:
>
> org.apache.cassandra.internal:type=HintedHandoff, which tells me that
> there is 1 active task, and
> org.apache.cassandra.db:type=HintedHandoffManager#countPendingHints(),
> which quite often gives a timeout when executed.
>
> Ideally, I would like
Hi,
Is there a way to monitor the progress of a hinted handoff task?
I found the following two mbeans providing some info:
org.apache.cassandra.internal:type=HintedHandoff, which tells me that there
is 1 active task, and
org.apache.cassandra.db:type=HintedHandoffManager#countPendingHints
11:18 PM, Tom van den Berge wrote:
> Hi,
>
> One one of my nodes, the (storage) load increased dramatically (doubled),
> within one or two hours. The hints column family was causing the growth. I
> noticed one HintedHandoff process that was started some two hours ago, but
> h
Hi,
One one of my nodes, the (storage) load increased dramatically (doubled),
within one or two hours. The hints column family was causing the growth. I
noticed one HintedHandoff process that was started some two hours ago, but
hadn't finished. Normally, these processes take only a few se
nd
@aaronmorton
http://www.thelastpickle.com
On 9/05/2013, at 4:38 PM, Kanwar Sangha wrote:
> Is this correct guys ?
>
> From: Kanwar Sangha [mailto:kan...@mavenir.com]
> Sent: 07 May 2013 14:07
> To: user@cassandra.apache.org
> Subject: HintedHandoff
>
> Hi -I had
Is this correct guys ?
From: Kanwar Sangha [mailto:kan...@mavenir.com]
Sent: 07 May 2013 14:07
To: user@cassandra.apache.org
Subject: HintedHandoff
Hi -I had a question on hinted-handoff. We have 2 DCs configured with overall
RF = 2 (DC1:1, DC2:1) and 4 nodes in each DC (total - 8 nodes
Hi -I had a question on hinted-handoff. We have 2 DCs configured with overall
RF = 2 (DC1:1, DC2:1) and 4 nodes in each DC (total - 8 nodes across 2 DCs)
Now we do a write with CL = ONE and Hinted Handoff enabled.
*If node 'X ' in DC1 which is a 'replica' node is down and a write
co
;
>>> @aaronmorton
>>> http://www.thelastpickle.com
>>>
>>> On 11/03/2013, at 2:13 PM, Robert Coli wrote:
>>>
>>>> On Mon, Mar 11, 2013 at 7:05 AM, Janne Jalkanen
>>>> wrote:
>>>>> I keep seeing these in my log
se in my log. Three-node cluster, one node is working
>>>> fine, but two other nodes have increased latencies and these in the error
>>>> logs (might of course be unrelated). No obvious GC pressure, no disk
>>>> errors that I can see. Ubuntu 12.04 on EC2, Java 7. R
EC2, Java 7. Repair is run regularly.
>>>
>>> My two questions: 1) should I worry, and 2) what might be going on, and 3)
>>> is there any way to get rid of these? Can I just blow my HintedHandoff
>>> table to smithereens?
>>
>> http://svn
e unrelated). No obvious GC pressure, no disk errors
>> that I can see. Ubuntu 12.04 on EC2, Java 7. Repair is run regularly.
>>
>> My two questions: 1) should I worry, and 2) what might be going on, and 3)
>> is there any way to get rid of these? Can I just blow my H
rs that I
> can see. Ubuntu 12.04 on EC2, Java 7. Repair is run regularly.
>
> My two questions: 1) should I worry, and 2) what might be going on, and 3) is
> there any way to get rid of these? Can I just blow my HintedHandoff table to
> smithereens?
http://svn.apache.org/repos/asf/
.
My two questions: 1) should I worry, and 2) what might be going on, and 3) is
there any way to get rid of these? Can I just blow my HintedHandoff table to
smithereens?
The only relevant issue I might see is CASSANDRA-5158, but it's not about HH.
Any more info I could dig?
Node A:
f the reads could ask for information that was inserted a while back.
>> In this scenario we are seeing this assertion error in HintedHandoff.
>> Is this a known issue?
>>
>> ERROR [HintedHandoff:3] 2011-12-05 15:42:04,324
>> AbstractCassandraDaemon.java (line 1
a test where we did a lot
> of inserts for 3 days. After that we started to run tests where some
> of the reads could ask for information that was inserted a while back.
> In this scenario we are seeing this assertion error in HintedHandoff.
> Is this a known issue?
>
> ERROR [Hin
from log output it seems that during hintedhandoff delivery compaction
is kicked too soon. There needs to be some delay for flusher to write
sstable.
INFO [GossipStage:1] 2011-11-14 13:16:03,933 Gossiper.java (line 745)
InetAddress /***.99.40 is now UP
INFO [HintedHandoff:1] 2011-11-14
? When a node is asked to store a hint it will log a
message with "Adding hint for" You should then see a message that includes
"applied. Sending response to"
- Number of nodes and RF ?
ReadRepair does not use HintedHandoff as part of it's processing.
Hope that helps.
Hi,
When I looking at "countPendingHints" in HintedHandoffManager via jmx,
I found that pending hints increases even when my cluster handles only
reads with quorum from clients.
The count decreases when I see it in long period (e.g., in an hour).
But it can increase in several thousands in short p
The last time this came up on the list Jonathan Ellis said (something
along the lines of) if your application can't tolerate stale data then
you should read with a consistency level of QUORUM.
It would be nice if there was some sort of middle ground for an
application that can tolerate slightly st
On 10/22/10 2:55 PM, Craig Ching wrote:
Even better, I'd love a way to not allow B to be available
until replication is complete, can I detect that somehow?
Proposed and rejected a while back :
https://issues.apache.org/jira/browse/CASSANDRA-768
=Rob
.ONE during the inserts, which, according to the HintedHandoff wiki
shouldn't be working in this case?). All columns are successfully
created. I then start node B and wait a bit. I start doing a get
(with CL.ONE) for every key I created in node A. They seem to be
trickling in to node B a
Yes, I think current HintedHandOff implementation in 0.6.x cannot support
large hints, it is a risk in a production system.
On Tue, Jun 29, 2010 at 12:31 AM, albert_e wrote:
> In 0.6.2, HH sending MUTATION message using the same OutboundTcpConnection
> with READ message. When HH trans
On 6/28/10 3:29 AM, Lu Ming wrote:
> Every one hour HintedHandOffManager will check hintedhandoff
> ColumnFamily then send out the big rowmutations to alive nodes,
> It fails again because of the TimeoutException, so the task will never
> finish and the big rowmutation is sending aga
he answer.
>
> Some bad buy keeps on writing many data day and night, then made a very
> big row mutation which size is about 140M.
> In this period I restarted some Cassandra nodes, and when the nodes is alive
> again, them got some hintedhandoff messages.
> HintedHandOffManager.
some Cassandra nodes, and when the nodes is alive
again, them got some hintedhandoff messages.
HintedHandOffManager.sendMessage() will send the rowmutations to these nodes,
but the rowmutation is too big to finish transferring in
8 seconds (defined in DatabaseDescriptor.getRpcTimeout()), and
37 matches
Mail list logo
