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

Posted to notifications@asterixdb.apache.org by "Michael J. Carey (Jira)" <ji...@apache.org> on 2019/10/09 14:02:00 UTC

[jira] [Commented] (ASTERIXDB-2654) Potential LSM failure related to max file size

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

Michael J. Carey commented on ASTERIXDB-2654:
---------------------------------------------

PS - Please include Mike Blow and Murtadah as reviewers when done.  (And I'm happy to brainstorm about this if need be, but I doubt the need will be. :-))

> Potential LSM failure related to max file size
> ----------------------------------------------
>
>                 Key: ASTERIXDB-2654
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2654
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: *DB - AsterixDB, IDX - Indexes, STO - Storage
>    Affects Versions: 0.9.5
>            Reporter: Michael J. Carey
>            Assignee: Chen Luo
>            Priority: Critical
>             Fix For: 0.9.5
>
>
> The new "unlimited" merge policy (aka concurrent) needs to gracefully handle the condition where the system has components that can no longer be merged due to OS file size limits!!!  (Pointed out by M. Blow just now.)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)