asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Maxon <ima...@uci.edu>
Subject Re: Issue 933 in asterixdb: IllegalStateException in startRecovery
Date Thu, 13 Aug 2015 15:10:05 GMT
Huh, interesting that it actually happened. It seemed like it might be a
bug, but was really unlikely to happen, so I had the fix on the back
burner. I'll pick it back up, then

- Ian

On Thu, Aug 13, 2015 at 1:36 AM, Murtadha Hubail <hubailmor@gmail.com>
wrote:

> @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 :-)
>
> > On Aug 13, 2015, at 5:56 AM, asterixdb@googlecode.com wrote:
> >
> >
> > Comment #4 on issue 933 by buyingyi: IllegalStateException in
> startRecovery
> > https://code.google.com/p/asterixdb/issues/detail?id=933
> >
> > Got a similar issue -- my entire cluster is unusable now because one NC
> cannot start well:
> >
> > Aug 12, 2015 7:46:33 PM edu.uci.ics.hyracks.control.nc.NCDriver main
> > SEVERE: Setting uncaught exception handler
> edu.uci.ics.hyracks.api.lifecycle.LifeCycleComponentManager@c81739c
> > Aug 12, 2015 7:46:33 PM
> edu.uci.ics.hyracks.control.nc.NodeControllerService start
> > INFO: Starting NodeControllerService
> > Aug 12, 2015 7:46:33 PM
> edu.uci.ics.asterix.hyracks.bootstrap.NCApplicationEntryPoint start
> > INFO: Starting Asterix node controller: test_sensorium-27
> > java.lang.IllegalStateException: Failed to redo
> >       at
> edu.uci.ics.asterix.transaction.management.service.recovery.RecoveryManager.redo(RecoveryManager.java:738)
> >       at
> edu.uci.ics.asterix.transaction.management.service.recovery.RecoveryManager.startRecovery(RecoveryManager.java:318)
> >       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)
> > Caused by: java.lang.ArrayIndexOutOfBoundsException: 2
> >       at
> edu.uci.ics.hyracks.storage.am.common.tuples.TypeAwareTupleWriter.getFieldSlotsBytes(TypeAwareTupleWriter.java:122)
> >       at
> edu.uci.ics.hyracks.storage.am.common.tuples.TypeAwareTupleWriter.bytesRequired(TypeAwareTupleWriter.java:36)
> >       at
> edu.uci.ics.hyracks.storage.am.lsm.btree.tuples.LSMBTreeTupleWriter.bytesRequired(LSMBTreeTupleWriter.java:39)
> >       at
> edu.uci.ics.hyracks.storage.am.btree.frames.BTreeNSMInteriorFrame.getBytesRequriedToWriteTuple(BTreeNSMInteriorFrame.java:59)
> >       at
> edu.uci.ics.hyracks.storage.am.btree.impls.BTree.upsert(BTree.java:327)
> >       at
> edu.uci.ics.hyracks.storage.am.btree.impls.BTree.access$500(BTree.java:70)
> >       at
> edu.uci.ics.hyracks.storage.am.btree.impls.BTree$BTreeAccessor.upsertIfConditionElseInsert(BTree.java:897)
> >       at
> edu.uci.ics.hyracks.storage.am.btree.impls.BTree$BTreeAccessor.upsert(BTree.java:890)
> >       at
> edu.uci.ics.hyracks.storage.am.lsm.btree.impls.LSMBTree.modify(LSMBTree.java:365)
> >       at
> edu.uci.ics.hyracks.storage.am.lsm.common.impls.LSMHarness.modify(LSMHarness.java:331)
> >       at
> edu.uci.ics.hyracks.storage.am.lsm.common.impls.LSMHarness.forceModify(LSMHarness.java:314)
> >       at
> edu.uci.ics.hyracks.storage.am.lsm.common.impls.LSMTreeIndexAccessor.forceDelete(LSMTreeIndexAccessor.java:159)
> >       at
> edu.uci.ics.asterix.transaction.management.service.recovery.RecoveryManager.redo(RecoveryManager.java:733)
> >       ... 5 more
> >
> > --
> > You received this message because you were CC'd on the issue.
> > You may adjust your notification preferences at:
> > https://code.google.com/hosting/settings
> >
> > Reply to this email to add a comment or make updates.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message