Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 012581182E for ; Mon, 11 Aug 2014 21:54:14 +0000 (UTC) Received: (qmail 57501 invoked by uid 500); 11 Aug 2014 21:54:13 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 57466 invoked by uid 500); 11 Aug 2014 21:54:13 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 57450 invoked by uid 99); 11 Aug 2014 21:54:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Aug 2014 21:54:13 +0000 Date: Mon, 11 Aug 2014 21:54:13 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-7735) Remove ref-counting of netty buffers 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/CASSANDRA-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-7735: -------------------------------------- Reviewer: Benedict (was: Aleksey Yeschenko) Aleksey's review plate is pretty full, putting this on Benedict's. > Remove ref-counting of netty buffers > ------------------------------------ > > Key: CASSANDRA-7735 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7735 > Project: Cassandra > Issue Type: Bug > Components: Core > Reporter: Benedict > Assignee: T Jake Luciani > Priority: Critical > Labels: correctness, performance > Fix For: 2.1.0 > > Attachments: 7735.txt > > > This has turned out to be more bug prone than we'd hoped, and it no longer seems to be a justified risk factor, since the performance gains were generally quite modest. When there's some time we can reengineer the API to make it safer to produce more obviously correct usage, but in the meantime I propose rolling back this change before general availability of 2.1 -- This message was sent by Atlassian JIRA (v6.2#6252)