asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yingyi Bu (JIRA)" <>
Subject [jira] [Commented] (ASTERIXDB-1251) NPE at NC startup after upgrade
Date Wed, 06 Jan 2016 18:52:39 GMT


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:
>             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(
>         at org.apache.asterix.metadata.bootstrap.MetadataBootstrap.startUniverse(
>         at org.apache.asterix.hyracks.bootstrap.NCApplicationEntryPoint.notifyStartupComplete(
>         at
>         at
> {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

View raw message