Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 8 Feb 2016 16:51:39 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12934880.1454007068000.329595.1454950299878@Atlassian.JIRA>
In-Reply-To: <JIRA.12934880.1454007068000@Atlassian.JIRA>
References: <JIRA.12934880.1454007068000@Atlassian.JIRA>
 <JIRA.12934880.1454007068371@arcas>
Subject: [jira] [Updated] (CASSANDRA-11090) Hinted Handoff loop
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-11090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-11090:
------------------------------------------
    Priority: Minor  (was: Major)

> Hinted Handoff loop
> -------------------
>
>                 Key: CASSANDRA-11090
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11090
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Blake Eggleston
>            Assignee: Aleksey Yeschenko
>            Priority: Minor
>             Fix For: 3.0.x, 3.x
>
>
> After the hints executor finishes sending hints, another hints file is created for the same host, which is then processed on the next go around. This continues indefinitely. The new hint files are empty, so there shouldn't be any network traffic. However, there's still unnecessary hint activity, and the hint crc file isn't deleted in the 3.0 branch after hints are dispatched (but is in trunk), so any hint activity will trigger ~8640 files being created per day until the node is restarted. Restarting the node fixes the problem, after the existing hint files are processed. 
> This can be duplicated on cassandra-3.0 to trunk with this script: https://gist.github.com/bdeggleston/13fbb9e70c0c0bd277c7


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)