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 0F6F875A3 for ; Wed, 9 Nov 2011 12:53:21 +0000 (UTC) Received: (qmail 29843 invoked by uid 500); 9 Nov 2011 12:53:20 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 29817 invoked by uid 500); 9 Nov 2011 12:53:20 -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 29804 invoked by uid 99); 9 Nov 2011 12:53:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Nov 2011 12:53:20 +0000 X-ASF-Spam-Status: No, hits=-2001.2 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Nov 2011 12:53:19 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 986F244267 for ; Wed, 9 Nov 2011 12:52:59 +0000 (UTC) Date: Wed, 9 Nov 2011 12:52:59 +0000 (UTC) From: "Brandon Williams (Commented) (JIRA)" To: commits@cassandra.apache.org Message-ID: <98283404.14137.1320843179626.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1510324170.7567.1320693411652.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (CASSANDRA-3466) Hinted handoff not working after rolling upgrade from 0.8.7 to 1.0.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-3466?page=3Dcom.atlas= sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D= 13147007#comment-13147007 ]=20 Brandon Williams commented on CASSANDRA-3466: --------------------------------------------- I haven't been able to reproduce the assertion errors, but I did find what = is preventing hint delivery in some cases: {noformat} if (hintStore.getSSTables().isEmpty()) return; // nothing to do, don't confuse users by logging a no-o= p handoff {noformat} If you're testing with a small enough amount of hints that the hints table = never flushes, we never deliver the hints in the current memtable. =20 > Hinted handoff not working after rolling upgrade from 0.8.7 to 1.0.2 > -------------------------------------------------------------------- > > Key: CASSANDRA-3466 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3466 > Project: Cassandra > Issue Type: Bug > Affects Versions: 1.0.0 > Reporter: Jonas Borgstr=C3=B6m > Assignee: Brandon Williams > Labels: hintedhandoff > Fix For: 1.0.3 > > > While testing rolling upgrades from 0.8.7 to 1.0.2 on a test cluster I've= noticed that hinted hand-off didn't always work properly. Hints generated = on an upgraded node does not seem to be delivered to other newly upgraded n= odes once they rejoin the ring. They only way I've found to get a node to d= eliver its hints is to restart it. > Here's some steps to reproduce this issue: > 1. Install cassandra 0.8.7 on node1 and node2 using default settings. > 2. Create keyspace foo with {replication_factor: 2}. Create column family= bar > 3. Shutdown node2=20 > 4. Insert data into bar and verify that HintsColumnFamily on node2 contai= ns hints > 5. Start node2 and verify that hinted handoff is performed and HintsColum= nFamily becomes empty again. > 6. Upgrade and restart node1 > 7. Shutdown node2=20 > 8. Insert data into bar and verify that HintsColumnFamily on node2 contai= ns hints > 9. Upgrade and start node2 > 10. Notice that hinted handoff is *not* performed when "node2" comes back= . (Only if node1 is restarted) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp= a For more information on JIRA, see: http://www.atlassian.com/software/jira