Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 5 Oct 2012 22:28:04 +0000 (UTC)
From: "Keith Turner (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <283043845.3284.1349476084959.JavaMail.jiratomcat@arcas>
In-Reply-To: <597665784.1049.1349447042673.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (ACCUMULO-786) Look into walog space usage
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Keith Turner commented on ACCUMULO-786:
---------------------------------------

Looking at the commit just made, I think we should restructure the code to have mutation class in the server code.  The server side Mutation could extend the client side mutation and add setSystemTimestamp().   The client code should not have setSystemTimestamp().  Also there is no reason for thrift to transfer the system time stamp that the user should never set.

Should probably make the mutation members private instead of package private.  I see this was done for testing, but can this be accomplished with the public API?


> Look into walog space usage
> ---------------------------
>
>                 Key: ACCUMULO-786
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-786
>             Project: Accumulo
>          Issue Type: Task
>            Reporter: Keith Turner
>             Fix For: 1.5.0
>
>
> I was experimenting with write ahead log write performance and noticed that when I wrote 1G of data that the walog was 1.5G.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira