You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@asterixdb.apache.org by as...@googlecode.com on 2015/08/12 02:59:39 UTC
Issue 933 in asterixdb: IllegalStateException in startRecovery
Status: Accepted
Owner: buyingyi@gmail.com
CC: kiss...@gmail.com
Labels: Type-Defect Priority-Critical
New issue 933 by buyingyi@gmail.com: IllegalStateException in startRecovery
https://code.google.com/p/asterixdb/issues/detail?id=933
$ cat /scratch/yingyib/data/asterix_log8/test4_sensorium-33.log
Aug 11, 2015 5:48:50 PM edu.uci.ics.hyracks.control.nc.NCDriver main
SEVERE: Setting uncaught exception handler
edu.uci.ics.hyracks.api.lifecycle.LifeCycleComponentManager@17da89a0
Aug 11, 2015 5:48:50 PM
edu.uci.ics.hyracks.control.nc.NodeControllerService start
INFO: Starting NodeControllerService
Aug 11, 2015 5:48:50 PM
edu.uci.ics.asterix.hyracks.bootstrap.NCApplicationEntryPoint start
INFO: Starting Asterix node controller: test4_sensorium-33
java.lang.IllegalStateException
at
edu.uci.ics.asterix.transaction.management.service.logging.LogReader.next(LogReader.java:78)
at
edu.uci.ics.asterix.transaction.management.service.recovery.RecoveryManager.startRecovery(RecoveryManager.java:222)
at
edu.uci.ics.asterix.hyracks.bootstrap.NCApplicationEntryPoint.start(NCApplicationEntryPoint.java:118)
at
edu.uci.ics.hyracks.control.nc.NodeControllerService.startApplication(NodeControllerService.java:318)
at
edu.uci.ics.hyracks.control.nc.NodeControllerService.start(NodeControllerService.java:255)
at edu.uci.ics.hyracks.control.nc.NCDriver.main(NCDriver.java:44)
With this exception in one NC, my instance can never be usable....
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Re: Issue 933 in asterixdb: IllegalStateException in startRecovery
Posted by as...@googlecode.com.
Comment #8 on issue 933 by buyingyi@gmail.com: IllegalStateException in
startRecovery
https://code.google.com/p/asterixdb/issues/detail?id=933
That's great! Thanks!
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Re: Issue 933 in asterixdb: IllegalStateException in startRecovery
Posted by as...@googlecode.com.
Comment #7 on issue 933 by hubail...@gmail.com: IllegalStateException in
startRecovery
https://code.google.com/p/asterixdb/issues/detail?id=933
Yes, Ian’s fix is going to do that. When a corrupted log is encountered,
the rest of the logs will be skipped but the node will continue starting up.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Re: Issue 933 in asterixdb: IllegalStateException in startRecovery
Posted by as...@googlecode.com.
Comment #6 on issue 933 by buyingyi@gmail.com: IllegalStateException in
startRecovery
https://code.google.com/p/asterixdb/issues/detail?id=933
Thanks, Murtadha!
IMO, even without replication, a bit data loss in one dataset sounds MUCH
better than losing the entire cluster...
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Re: Issue 933 in asterixdb: IllegalStateException in startRecovery
Posted by as...@googlecode.com.
Comment #5 on issue 933 by hubail...@gmail.com: IllegalStateException in
startRecovery
https://code.google.com/p/asterixdb/issues/detail?id=933
@Yingyi,
Both of these issues are related to corrupted log records.
The problem was reported in issue902:
https://code.google.com/p/asterixdb/issues/detail?id=902&q=logs&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary%20ETA%20Severity
<https://code.google.com/p/asterixdb/issues/detail?id=902&q=logs&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary%20ETA%20Severity>
Ian has already started a fix for this.
P.S. for the unusable cluster issue, looks like we need data replication
support to overcome the problem :-)
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings