[jira] [Commented] (LUCENE-6579) Unexpected merge exceptions should be tragic to IndexWriter
[ https://issues.apache.org/jira/browse/LUCENE-6579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14626121#comment-14626121 ] ASF subversion and git services commented on LUCENE-6579: - Commit 1690887 from [~mikemccand] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1690887 ] LUCENE-6579: exceptions during merging are now tragic Unexpected merge exceptions should be tragic to IndexWriter --- Key: LUCENE-6579 URL: https://issues.apache.org/jira/browse/LUCENE-6579 Project: Lucene - Core Issue Type: Bug Reporter: Michael McCandless Assignee: Michael McCandless Fix For: 5.3, Trunk Attachments: LUCENE-6579.patch Today our behavior is weird: we will fail the merge (which is running in a background thread if you are using the default CMS), pause for 1.0 seconds, and then the next chance we get, kick off the merge again. I think this is a poor default, e.g. on disk full we will just keep trying and filling up disk again, wasting IO/CPU. I think IW should declare this a tragedy instead? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-6579) Unexpected merge exceptions should be tragic to IndexWriter
[ https://issues.apache.org/jira/browse/LUCENE-6579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14626116#comment-14626116 ] ASF subversion and git services commented on LUCENE-6579: - Commit 1690886 from [~mikemccand] in branch 'dev/trunk' [ https://svn.apache.org/r1690886 ] LUCENE-6579: exceptions during merging are now tragic Unexpected merge exceptions should be tragic to IndexWriter --- Key: LUCENE-6579 URL: https://issues.apache.org/jira/browse/LUCENE-6579 Project: Lucene - Core Issue Type: Bug Reporter: Michael McCandless Assignee: Michael McCandless Fix For: 5.3, Trunk Attachments: LUCENE-6579.patch Today our behavior is weird: we will fail the merge (which is running in a background thread if you are using the default CMS), pause for 1.0 seconds, and then the next chance we get, kick off the merge again. I think this is a poor default, e.g. on disk full we will just keep trying and filling up disk again, wasting IO/CPU. I think IW should declare this a tragedy instead? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-6579) Unexpected merge exceptions should be tragic to IndexWriter
[ https://issues.apache.org/jira/browse/LUCENE-6579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14626307#comment-14626307 ] ASF subversion and git services commented on LUCENE-6579: - Commit 1690918 from [~mikemccand] in branch 'dev/trunk' [ https://svn.apache.org/r1690918 ] LUCENE-6579: fix this test case to cope with tragedy Unexpected merge exceptions should be tragic to IndexWriter --- Key: LUCENE-6579 URL: https://issues.apache.org/jira/browse/LUCENE-6579 Project: Lucene - Core Issue Type: Bug Reporter: Michael McCandless Assignee: Michael McCandless Fix For: 5.3, Trunk Attachments: LUCENE-6579.patch Today our behavior is weird: we will fail the merge (which is running in a background thread if you are using the default CMS), pause for 1.0 seconds, and then the next chance we get, kick off the merge again. I think this is a poor default, e.g. on disk full we will just keep trying and filling up disk again, wasting IO/CPU. I think IW should declare this a tragedy instead? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-6579) Unexpected merge exceptions should be tragic to IndexWriter
[ https://issues.apache.org/jira/browse/LUCENE-6579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14626308#comment-14626308 ] ASF subversion and git services commented on LUCENE-6579: - Commit 1690919 from [~mikemccand] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1690919 ] LUCENE-6579: fix this test case to cope with tragedy Unexpected merge exceptions should be tragic to IndexWriter --- Key: LUCENE-6579 URL: https://issues.apache.org/jira/browse/LUCENE-6579 Project: Lucene - Core Issue Type: Bug Reporter: Michael McCandless Assignee: Michael McCandless Fix For: 5.3, Trunk Attachments: LUCENE-6579.patch Today our behavior is weird: we will fail the merge (which is running in a background thread if you are using the default CMS), pause for 1.0 seconds, and then the next chance we get, kick off the merge again. I think this is a poor default, e.g. on disk full we will just keep trying and filling up disk again, wasting IO/CPU. I think IW should declare this a tragedy instead? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-6579) Unexpected merge exceptions should be tragic to IndexWriter
[ https://issues.apache.org/jira/browse/LUCENE-6579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14590014#comment-14590014 ] Robert Muir commented on LUCENE-6579: - +1 Unexpected merge exceptions should be tragic to IndexWriter --- Key: LUCENE-6579 URL: https://issues.apache.org/jira/browse/LUCENE-6579 Project: Lucene - Core Issue Type: Bug Reporter: Michael McCandless Assignee: Michael McCandless Fix For: 5.3, Trunk Today our behavior is weird: we will fail the merge (which is running in a background thread if you are using the default CMS), pause for 1.0 seconds, and then the next chance we get, kick off the merge again. I think this is a poor default, e.g. on disk full we will just keep trying and filling up disk again, wasting IO/CPU. I think IW should declare this a tragedy instead? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
