[jira] [Created] (DRILL-6064) NPE in Drill startup if Drill ZK znode removed

["Paul Rogers (JIRA)" <ji...@apache.org>]

Paul Rogers created DRILL-6064:
----------------------------------

             Summary: NPE in Drill startup if Drill ZK znode removed
                 Key: DRILL-6064
                 URL: https://issues.apache.org/jira/browse/DRILL-6064
             Project: Apache Drill
          Issue Type: Bug
    Affects Versions: 1.12.0
            Reporter: Paul Rogers


Was working on an example storage plugin. Messed up the dfs storage plugin config. So, deleted the Drill ZK root:

{noformat}
> ./zkCli.sh
[zk: localhost:2181(CONNECTED) 3] rmr /drill
{noformat}

Attempted to restart the Drillbit:

{noformat}
> cd $DRILL_HOME/bin
> ./drillbit.sh start
{noformat}

Drill failed to start. Entry in {{drillbit.out}}:

{noformat}
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0
Exception in thread "main" java.lang.NullPointerException
	at org.apache.drill.exec.coord.zk.ZKClusterCoordinator.update(ZKClusterCoordinator.java:218)
	at org.apache.drill.exec.server.Drillbit.close(Drillbit.java:228)
	at org.apache.drill.exec.server.Drillbit.start(Drillbit.java:401)
	at org.apache.drill.exec.server.Drillbit.start(Drillbit.java:372)
	at org.apache.drill.exec.server.Drillbit.main(Drillbit.java:368)
{noformat}

Content of line 218:

{code}
        endpoint = h.endpoint.toBuilder().setState(state).build();
{code}

Despite this error, the Drill process started running:

{noformat}
ps -a
29217 ttys003    0:17.27 /Library/Java/JavaVirtualMachines/jdk1.8.0_102.jdk/Contents/Home/bin/java -Xms4G -Xmx4G -XX:MaxDirectMemo
{noformat}

But, the Drill ZK entries were not properly created:

{noformat}
> ./zkCli.sh
[zk: localhost:2181(CONNECTED) 1] ls /drill
[running, sys.storage_plugins, drillbits1]
[zk: localhost:2181(CONNECTED) 2] ls /drill/running
[]
[zk: localhost:2181(CONNECTED) 3] ls /drill/drillbits1
[]
{noformat}

As a user, I'm stuck. (As a developer, I'll have to debug to determine how to fix the problem.)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)