accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3002) Handle instance.volumes in upgrade
Date Fri, 19 Dec 2014 19:27:13 GMT


Keith Turner commented on ACCUMULO-3002:

I wish I had taken more notes about what the actual problem was, because I can not remember.
 I just ran two quick test on my workstation.  I started up 1.5.1, created a table, shut it
down, set two URIs in instance.volumes, and started 1.6.1.  For the two volumes I set, one
was the existing 1.5.1 dir and the other was a dir in hdfs that did not exist.  When I did
this, all server processes failed to start w/ a message like the following.  The URI in the
error message is the dir that did not exist.

2014-12-19 12:16:41,195 [zookeeper.ZooUtil] ERROR: unable obtain instance id at hdfs://nn1/accumulo2/instance_id
2014-12-19 12:16:41,196 [master.Master] ERROR: Unexpected exception, exiting
java.lang.RuntimeException: Accumulo not initialized, there is no instance id at hdfs://nn1/accumulo2/instance_id
	at org.apache.accumulo.core.zookeeper.ZooUtil.getInstanceIDFromHdfs(
	at org.apache.accumulo.server.client.HdfsZooInstance._getInstanceID(
	at org.apache.accumulo.server.client.HdfsZooInstance.getInstanceID(
	at org.apache.accumulo.server.conf.ServerConfigurationFactory.<init>(
	at org.apache.accumulo.server.conf.ServerConfiguration.<init>(
	at org.apache.accumulo.master.Master.main(
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
	at java.lang.reflect.Method.invoke(
	at org.apache.accumulo.start.Main$

After that I set instance.volumes to only the existing 1.5.1 dir and that worked ok.   

> Handle instance.volumes in upgrade
> ----------------------------------
>                 Key: ACCUMULO-3002
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.6.0
>            Reporter: Keith Turner
>            Priority: Blocker
>             Fix For: 1.6.2, 1.7.0
> A user configured instance.volumes before upgrading and ran into problems.  The 1.6.0
release notes mention not to do this.  However thats not really enough.  Need to fix this
issues or make the upgrade abort if instance.volumes is configured.

This message was sent by Atlassian JIRA

View raw message