Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 23 Nov 2015 20:14:11 +0000 (UTC)
From: "Fahd Siddiqui (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12675151.1382482795000.164477.1448309651553@Atlassian.JIRA>
In-Reply-To: <JIRA.12675151.1382482795000@Atlassian.JIRA>
References: <JIRA.12675151.1382482795000@Atlassian.JIRA>
 <JIRA.12675151.1382482795710@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-6230) Write hints to flat files
 instead of the system.hints
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022736#comment-15022736 ] 

Fahd Siddiqui edited comment on CASSANDRA-6230 at 11/23/15 8:13 PM:
--------------------------------------------------------------------

Please entertain this question even though it may seem unnecessary. Is there some way to now know about the _oldest pending_ hint for a node? In system.hints, currently, this is trivial to know. 


was (Author: fahdsiddiqui):
Please entertain this question even though it may seem unnecessary. Is there some way to now know about the _oldest_ hint for a node? In system.hints, currently, this is trivial to know. 

> Write hints to flat files instead of the system.hints
> -----------------------------------------------------
>
>                 Key: CASSANDRA-6230
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6230
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Jonathan Ellis
>            Assignee: Aleksey Yeschenko
>             Fix For: 3.0 beta 1
>
>
> Writing to a file would have less overhead on both hint creation and replay.


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