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 05D1FE18C for ; Fri, 11 Jan 2013 09:36:22 +0000 (UTC) Received: (qmail 56772 invoked by uid 500); 11 Jan 2013 09:36:21 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 56406 invoked by uid 500); 11 Jan 2013 09:36:21 -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 56336 invoked by uid 99); 11 Jan 2013 09:36:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jan 2013 09:36:20 +0000 Date: Fri, 11 Jan 2013 09:36:12 +0000 (UTC) From: "Marcus Eriksson (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CASSANDRA-5148) Add option to disable tcp_nodelay MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Marcus Eriksson created CASSANDRA-5148: ------------------------------------------ Summary: Add option to disable tcp_nodelay Key: CASSANDRA-5148 URL: https://issues.apache.org/jira/browse/CASSANDRA-5148 Project: Cassandra Issue Type: Bug Reporter: Marcus Eriksson Assignee: Marcus Eriksson Priority: Minor Attachments: 0001-Add-option-to-disable-TCP_NODELAY-for-inter-dc-commu.patch Add option to disable TCP_NODELAY for cross-dc communication. Reason is we are seeing huge amounts of packets being sent over our poor firewalls. For us, disabling this for inter-dc communication increases average packet size from ~400 bytes to ~1300 bytes. -- 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