You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Yingyi Bu (JIRA)" <ji...@apache.org> on 2016/01/06 19:38:39 UTC

[jira] [Created] (ASTERIXDB-1251) NPE at NC startup after upgrade

Yingyi Bu created ASTERIXDB-1251:
------------------------------------

             Summary: NPE at NC startup after upgrade
                 Key: ASTERIXDB-1251
                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1251
             Project: Apache AsterixDB
          Issue Type: Bug
            Reporter: Yingyi Bu
            Assignee: Murtadha Hubail


I upgraded my instance to latest master but got this exception:

{noformat}
java.lang.NullPointerException
        at org.apache.asterix.metadata.bootstrap.MetadataBootstrap.enlistMetadataDataset(MetadataBootstrap.java:412)
        at org.apache.asterix.metadata.bootstrap.MetadataBootstrap.startUniverse(MetadataBootstrap.java:199)
        at org.apache.asterix.hyracks.bootstrap.NCApplicationEntryPoint.notifyStartupComplete(NCApplicationEntryPoint.java:235)
        at org.apache.hyracks.control.nc.NodeControllerService.start(NodeControllerService.java:311)
        at org.apache.hyracks.control.nc.NCDriver.main(NCDriver.java:48)
{noformat}

It seems related to the recent global resource id changes.  
But failing the instance forever seems not the right answer for that case. To me, the bottomline is that the instance can at least start (with warnings in the log saying which datasets are lost) though the old data could lose, so that a user doesn't need to reinstall a new instance.





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