Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 2 Jul 2015 19:15:04 +0000 (UTC)
From: "Yuki Morishita (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12840603.1435254884000.88300.1435864504704@Atlassian.JIRA>
In-Reply-To: <JIRA.12840603.1435254884000@Atlassian.JIRA>
References: <JIRA.12840603.1435254884000@Atlassian.JIRA>
 <JIRA.12840603.1435254884590@arcas>
Subject: [jira] [Commented] (CASSANDRA-9654) Failure to open sstable after
 upgrade to trunk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-9654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612398#comment-14612398 ] 

Yuki Morishita commented on CASSANDRA-9654:
-------------------------------------------

I think this is the same as CASSANDRA-9687.
Now that was committed to trunk, but I couldn't run upgrade test due to the following error:

{code}
======================================================================
ERROR: upgrade_test (upgrade_through_versions_test.TestUpgradeThroughVersions)
----------------------------------------------------------------------
Traceback (most recent call last):
  File /home/yuki/Developments/riptano/cassandra-dtest/upgrade_through_versions_test.py, line 189, in upgrade_test
    self.upgrade_scenario()
  File /home/yuki/Developments/riptano/cassandra-dtest/upgrade_through_versions_test.py, line 244, in upgrade_scenario
    self.upgrade_to_version(tag)
  File /home/yuki/Developments/riptano/cassandra-dtest/upgrade_through_versions_test.py, line 303, in upgrade_to_version
    node.nodetool('upgradesstables -a')
  File build/bdist.linux-x86_64/egg/ccmlib/node.py, line 595, in nodetool
    raise NodetoolError( .join(args), exit_status, stdout, stderr)
NodetoolError: Nodetool command '/home/yuki/.ccm/repository/git_cassandra-2.1/bin/nodetool -h localhost -p 7100 upgradesstables -a' failed; exit status: 1; stdout: Error occurred during initialization of VM
agent library failed to init: instrument
; stderr: Error opening zip file or JAR manifest missing : /home/yuki/.ccm/repository/git_cassandra-2.1/lib/jamm-0.2.5.jar
{code}

[~philipthompson]
Can you verify this issue can be duplicate of CASSANDRA-9687?

> Failure to open sstable after upgrade to trunk
> ----------------------------------------------
>
>                 Key: CASSANDRA-9654
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9654
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Philip Thompson
>            Assignee: Branimir Lambov
>             Fix For: 3.x
>
>         Attachments: node1.log, node2.log, node3.log, sstables.tar.gz
>
>
> After upgrading a 3 node cluster on the path 1.2.19 -> 2.0.16 -> 2.1-head -> 2.2-head -> trunk
> {code}
> ERROR [SSTableBatchOpen:1] 2015-06-25 17:16:55,424 SSTableReader.java:435 - Cannot open /tmp/dtest-Ibi6zm/test/node1/data/upgrade/cf/la-7-big; partitioner org.apache.cassandra.dht.LocalPartitioner does not match system partitioner org.apache.cassandra.dht.Murmur3Partitioner.  Note that the default partitioner starting with Cassandra 1.2 is Murmur3Partitioner, so you will need to edit that to match your old partitioner if upgrading.
> ERROR [SSTableBatchOpen:2] 2015-06-25 17:16:55,425 SSTableReader.java:435 - Cannot open /tmp/dtest-Ibi6zm/test/node1/data/upgrade/cf/la-10-big; partitioner org.apache.cassandra.dht.LocalPartitioner does not match system partitioner org.apache.cassandra.dht.Murmur3Partitioner.  Note that the default partitioner starting with Cassandra 1.2 is Murmur3Partitioner, so you will need to edit that to match your old partitioner if upgrading.
> {code}
> Node logs are attached.
> To reproduce, you'll need to run the upgrade dtest as follows:
> {{nosetests -sv upgrade_through_versions_test.py:TestUpgradeThroughVersions.upgrade_test}}. I don't have CI results for this yet, nor will I soon. To run this, you'll need both JDK7 and JDK8 installed, for compilation reasons. Set the env vars JAVA7_HOME and JAVA8_HOME, respectively. I'll work on finding an sstable that represent the issue.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)