From commits-return-205721-archive-asf-public=cust-asf.ponee.io@cassandra.apache.org Sat Jan 27 19:15:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 01CAF18065B for ; Sat, 27 Jan 2018 19:15:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E5547160C30; Sat, 27 Jan 2018 18:15:03 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 39327160C13 for ; Sat, 27 Jan 2018 19:15:03 +0100 (CET) Received: (qmail 40748 invoked by uid 500); 27 Jan 2018 18:15:02 -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 40737 invoked by uid 99); 27 Jan 2018 18:15:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Jan 2018 18:15:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B3250C028C for ; Sat, 27 Jan 2018 18:15:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id IeR-YXOP_7U9 for ; Sat, 27 Jan 2018 18:15:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D27A15F177 for ; Sat, 27 Jan 2018 18:15:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5851BE00A6 for ; Sat, 27 Jan 2018 18:15:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 14D8021301 for ; Sat, 27 Jan 2018 18:15:00 +0000 (UTC) Date: Sat, 27 Jan 2018 18:15:00 +0000 (UTC) From: "Jason Brown (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-14194) Chain commit log marker potential performance regression in batch commit mode 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-14194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342247#comment-16342247 ] Jason Brown commented on CASSANDRA-14194: ----------------------------------------- I've run the head of cassandra-3.11 (currently sha {{b8c12fba064fb0b6a3b6306b2670497434471920}}), and it completed in the same time that cassandra-3.0 did (no timeout). I ran trunk (sha {{6fc3699adb4f609f78a40888af9797bb205216b0}}), and it *did* timeout. I'm running 3.0 and 3.11 in circleci to see if they timeout. If not, then I think the regression is on trunk alone, and I'll focus my effort there. Obviously, if the source of the source looks like it'll affect earlier versions, i'll dig into that,as well. > Chain commit log marker potential performance regression in batch commit mode > ----------------------------------------------------------------------------- > > Key: CASSANDRA-14194 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14194 > Project: Cassandra > Issue Type: Bug > Components: Core, Testing > Reporter: Ariel Weisberg > Assignee: Jason Brown > Priority: Major > Attachments: jstack.txt > > > CASSANDRA-13987 modified how the commit log sync thread works. I noticed that cql3.ViewTest and ViewBuilderTaskTest have been timing out, but only in CircleCI. When I jstack in CircleCI what I see is that the commit log writer thread is parked and the threads trying to append to the commit log are blocked waiting on it. > I tested the commit before 13987 and it passed in CircleCI and then I tested with 13987 and it timed out. I suspect this may be a general performance regression and not just a CircleCI issue. > And this is with write barriers disabled (sync thread doesn't actually sync) so it wasn't blocked in the filesystem. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org For additional commands, e-mail: commits-help@cassandra.apache.org