You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/03/21 20:53:00 UTC
[jira] [Commented] (ASTERIXDB-1708) Rollback failure at scale
[ https://issues.apache.org/jira/browse/ASTERIXDB-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16408568#comment-16408568 ]
ASF subversion and git services commented on ASTERIXDB-1708:
------------------------------------------------------------
Commit e6587f628a72f10594e676ec375c1cf26e73ec53 in asterixdb's branch refs/heads/release-0.9.4-pre-rc from [~imaxon]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=e6587f6 ]
[ASTERIXDB-1708][TX] Prevent log deletion during scan
Right now there is a potential for a soft checkpoint to delete a
log file that is about to be read as part of a transaction rollback.
This patch stops the soft checkpoint from proceeding if a rollback
is about to take place and vice-versa.
Change-Id: Icff1a520af24c8fac8e5836cdbf46425b78b1260
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2508
Sonar-Qube: Jenkins <je...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <je...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Murtadha Hubail <mh...@apache.org>
> Rollback failure at scale
> -------------------------
>
> Key: ASTERIXDB-1708
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1708
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Ian Maxon
> Assignee: Ian Maxon
> Priority: Major
>
> Seems that transaction rollback can fail at certain points. This happened with the same file ID on a cluster of 5 nodes which is an interesting coincidence.
> org.apache.asterix.common.exceptions.ACIDException: java.io.IOException: Log file with id(37) was not found. Requested LSN: 80892085216
> at org.apache.asterix.transaction.management.service.logging.LogReader.getLogFile(LogReader.java:293)
> at org.apache.asterix.transaction.management.service.logging.LogReader.initializeScan(LogReader.java:76)
> at org.apache.asterix.transaction.management.service.recovery.RecoveryManager.rollbackTransaction(RecoveryManager.java:734)
> at org.apache.asterix.transaction.management.service.transaction.TransactionManager.abortTransaction(TransactionManager.java:64)
> at org.apache.asterix.transaction.management.service.transaction.TransactionManager.completedTransaction(TransactionManager.java:130)
> at org.apache.asterix.runtime.job.listener.JobEventListenerFactory$1.jobletFinish(JobEventListenerFactory.java:58)
> at org.apache.hyracks.control.nc.Joblet.performCleanup(Joblet.java:318)
> at org.apache.hyracks.control.nc.Joblet.cleanup(Joblet.java:310)
> at org.apache.hyracks.control.nc.work.CleanupJobletWork.run(CleanupJobletWork.java:67)
> at org.apache.hyracks.control.common.work.WorkQueue$WorkerThread.run(WorkQueue.java:127)
> Caused by: java.io.IOException: Log file with id(37) was not found. Requested LSN: 80892085216
> at org.apache.asterix.transaction.management.service.logging.LogManager.getLogFile(LogManager.java:544)
> at org.apache.asterix.transaction.management.service.logging.LogReader.getLogFile(LogReader.java:290)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)