[
https://issues.apache.org/jira/browse/ASTERIXDB-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086052#comment-15086052
]
Yingyi Bu commented on ASTERIXDB-1251:
--------------------------------------
Based on the conversation with @mhubail, it is an error message issue.
Instead of failing with NPE, we just need a better error message that tells a
user how to get the instance start and "behave" like a new instance.
> NPE at NC startup after upgrade
> -------------------------------
>
> Key: ASTERIXDB-1251
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1251
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: Metadata
> 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)
