Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 37ADC172F2 for ; Sun, 5 Apr 2015 05:01:35 +0000 (UTC) Received: (qmail 37727 invoked by uid 500); 5 Apr 2015 05:01:35 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 37465 invoked by uid 500); 5 Apr 2015 05:01:34 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 37130 invoked by uid 99); 5 Apr 2015 05:01:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Apr 2015 05:01:34 +0000 Date: Sun, 5 Apr 2015 05:01:34 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-3174) Avoid mutation copy on remote replica MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated ACCUMULO-3174: --------------------------------- Fix Version/s: (was: 1.7.0) > Avoid mutation copy on remote replica > ------------------------------------- > > Key: ACCUMULO-3174 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3174 > Project: Accumulo > Issue Type: Improvement > Components: replication > Reporter: Josh Elser > > To ensure that all replicas see mutations applied in the same order as the source, we need to preserve the timestamp on the received mutations to replicate (either user-assigned or server-assigned). > The way that ServerMutation implements the server-assigned timestamp is done so as to not modify the serialized bytes (for efficiencies sake). The problem arises when the ServerMutation is cast back to a "regular" Mutation, the timestamp that the system assigned, which was tracked outside of the serialized bytes, is lost and a new server-assigned timestamp is used. > The naive way to circumvent this is to copy the ServerMutation into a new Mutation, checking for a system-assigned timestamp and set that on the updates for each Mutation. This has a big downside as the amount of required heap nearly doubled (assuming that the mutations are the majority of memory used). -- This message was sent by Atlassian JIRA (v6.3.4#6332)