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 2017/07/27 16:40:00 UTC

[jira] [Commented] (ASTERIXDB-1995) Write transactions hang when storage devices become full

    [ https://issues.apache.org/jira/browse/ASTERIXDB-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103454#comment-16103454 ] 

ASF subversion and git services commented on ASTERIXDB-1995:
------------------------------------------------------------

Commit 0d0a113f40014384bcf54b68235581286c9b2c2b in asterixdb's branch refs/heads/master from [~mhubail]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=0d0a113 ]

[ASTERIXDB-1995][STO] Abort write txn when index cannot be flushed

- user model changes: no
- storage format changes: no
- interface changes: no

Details:
- Fix LSM memory component state transition on flush/merge failure
- When index cannot be flushed, abort waiting threads
- Prevent NPE in MateralizerTaskState when file creation fails
- Check parent dirs creation for index metadata file

Change-Id: I28592c30c788f4a6f44db8b47a84bc77f6b3f8f3
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1896
Sonar-Qube: Jenkins <je...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
BAD: Jenkins <je...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: abdullah alamoudi <ba...@gmail.com>


> Write transactions hang when storage devices become full
> --------------------------------------------------------
>
>                 Key: ASTERIXDB-1995
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1995
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: STO - Storage
>            Reporter: Murtadha Hubail
>            Assignee: Murtadha Hubail
>
> Write transactions hang when storage devices become full. This is because memory components cannot be flushed and jobs wait forever to be notified that a memory component is available. The proposed solution is to abort the waiting/incoming jobs with a disk is full exception.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)