You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2009/04/24 23:39:30 UTC

[jira] Created: (LUCENE-1611) Do not launch new merges if IndexWriter has hit OOME

Do not launch new merges if IndexWriter has hit OOME
----------------------------------------------------

                 Key: LUCENE-1611
                 URL: https://issues.apache.org/jira/browse/LUCENE-1611
             Project: Lucene - Java
          Issue Type: Bug
          Components: Index
    Affects Versions: 2.4.1
            Reporter: Michael McCandless
            Assignee: Michael McCandless
             Fix For: 2.9


if IndexWriter has hit OOME, it defends itself by refusing to commit changes to the index, including merges.  But this can lead to infinite merge attempts because we fail to prevent starting a merge.

Spinoff from http://www.nabble.com/semi-infinite-loop-during-merging-td23036156.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


[jira] Resolved: (LUCENE-1611) Do not launch new merges if IndexWriter has hit OOME

Posted by "Michael McCandless (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael McCandless resolved LUCENE-1611.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.4.2

Thanks Christiaan!

> Do not launch new merges if IndexWriter has hit OOME
> ----------------------------------------------------
>
>                 Key: LUCENE-1611
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1611
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.4.1
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 2.4.2, 2.9
>
>         Attachments: LUCENE-1611-241.patch, LUCENE-1611.patch, LUCENE-1611.patch
>
>
> if IndexWriter has hit OOME, it defends itself by refusing to commit changes to the index, including merges.  But this can lead to infinite merge attempts because we fail to prevent starting a merge.
> Spinoff from http://www.nabble.com/semi-infinite-loop-during-merging-td23036156.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


[jira] Updated: (LUCENE-1611) Do not launch new merges if IndexWriter has hit OOME

Posted by "Michael McCandless (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael McCandless updated LUCENE-1611:
---------------------------------------

    Attachment: LUCENE-1611.patch

New patch that fixes a few issues Christiaan found.  I think this is ready to commit... I'll wait a few hours.

> Do not launch new merges if IndexWriter has hit OOME
> ----------------------------------------------------
>
>                 Key: LUCENE-1611
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1611
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.4.1
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 2.9
>
>         Attachments: LUCENE-1611-241.patch, LUCENE-1611.patch, LUCENE-1611.patch
>
>
> if IndexWriter has hit OOME, it defends itself by refusing to commit changes to the index, including merges.  But this can lead to infinite merge attempts because we fail to prevent starting a merge.
> Spinoff from http://www.nabble.com/semi-infinite-loop-during-merging-td23036156.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


[jira] Updated: (LUCENE-1611) Do not launch new merges if IndexWriter has hit OOME

Posted by "Michael McCandless (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael McCandless updated LUCENE-1611:
---------------------------------------

    Attachment: LUCENE-1611.patch

Attached patch to prevent starting new merges after OOME, and to throw IllegalStateException in optimize, expungeDeletes if OOME is hit.  I plan to commit in a day or two.

> Do not launch new merges if IndexWriter has hit OOME
> ----------------------------------------------------
>
>                 Key: LUCENE-1611
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1611
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.4.1
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 2.9
>
>         Attachments: LUCENE-1611.patch
>
>
> if IndexWriter has hit OOME, it defends itself by refusing to commit changes to the index, including merges.  But this can lead to infinite merge attempts because we fail to prevent starting a merge.
> Spinoff from http://www.nabble.com/semi-infinite-loop-during-merging-td23036156.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


[jira] Updated: (LUCENE-1611) Do not launch new merges if IndexWriter has hit OOME

Posted by "Michael McCandless (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael McCandless updated LUCENE-1611:
---------------------------------------

    Attachment: LUCENE-1611-241.patch

Attached 2.4.1 patch.

> Do not launch new merges if IndexWriter has hit OOME
> ----------------------------------------------------
>
>                 Key: LUCENE-1611
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1611
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.4.1
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 2.9
>
>         Attachments: LUCENE-1611-241.patch, LUCENE-1611.patch
>
>
> if IndexWriter has hit OOME, it defends itself by refusing to commit changes to the index, including merges.  But this can lead to infinite merge attempts because we fail to prevent starting a merge.
> Spinoff from http://www.nabble.com/semi-infinite-loop-during-merging-td23036156.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org