You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@asterixdb.apache.org by "Till (JIRA)" <ji...@apache.org> on 2016/11/07 19:07:58 UTC

[jira] [Resolved] (ASTERIXDB-1732) Sporadic deadlock in LogManager

     [ https://issues.apache.org/jira/browse/ASTERIXDB-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till resolved ASTERIXDB-1732.
-----------------------------
    Resolution: Fixed

https://github.com/apache/asterixdb/commit/d292151eb4f0983705e60dee5d43cea8d33d486e

> Sporadic deadlock in LogManager
> -------------------------------
>
>                 Key: ASTERIXDB-1732
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1732
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: AsterixDB, Transactions
>            Reporter: Till
>            Assignee: Abdullah Alamoudi
>            Priority: Critical
>              Labels: sporadic-error
>
> The LogBuffer has a race condition if the log buffer capacity is exceeded. If this happens, we can lose log pages for large records. In that case the log is corrupted and it leads to a deadlock when the LogManager switches to a new log file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)