You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Ian Maxon (JIRA)" <ji...@apache.org> on 2016/10/27 20:35:58 UTC
[jira] [Assigned] (ASTERIXDB-1710) Recovery redo fails whenever
deadlock-free locking protocol invoked
[ https://issues.apache.org/jira/browse/ASTERIXDB-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Maxon reassigned ASTERIXDB-1710:
------------------------------------
Assignee: Ian Maxon
> Recovery redo fails whenever deadlock-free locking protocol invoked
> -------------------------------------------------------------------
>
> Key: ASTERIXDB-1710
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1710
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Ian Maxon
> Assignee: Ian Maxon
>
> The WAIT log isn't handled in the switch/case for the redo phase. It should get through analysis fine. The stack will be something like this:
> org.apache.asterix.common.exceptions.ACIDException: Unsupported LogType: 6
> at org.apache.asterix.transaction.management.service.recovery.RecoveryManager.startRecoveryRedoPhase(RecoveryManager.java:412)
> at org.apache.asterix.transaction.management.service.recovery.RecoveryManager.replayPartitionsLogs(RecoveryManager.java:202)
> at org.apache.asterix.transaction.management.service.recovery.RecoveryManager.startRecovery(RecoveryManager.java:194)
> at org.apache.asterix.hyracks.bootstrap.NCApplicationEntryPoint.start(NCApplicationEntryPoint.java:151)
> at org.apache.hyracks.control.nc.NodeControllerService.startApplication(NodeControllerService.java:342)
> at org.apache.hyracks.control.nc.NodeControllerService.start(NodeControllerService.java:271)
> at org.apache.hyracks.control.nc.NCDriver.main(NCDriver.java:48)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)