[jira] Created: (LUCENE-1160) MergeException from CMS threads should record the Directory

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (LUCENE-1160) MergeException from CMS threads should record the Directory

Markus Jelsma (Jira)
MergeException from CMS threads should record the Directory
-----------------------------------------------------------

                 Key: LUCENE-1160
                 URL: https://issues.apache.org/jira/browse/LUCENE-1160
             Project: Lucene - Java
          Issue Type: Improvement
          Components: Index
    Affects Versions: 2.3
            Reporter: Michael McCandless
            Assignee: Michael McCandless
            Priority: Minor
             Fix For: 2.4
         Attachments: LUCENE-1150.patch

When you hit an unhandled exception in ConcurrentMergeScheduler, it
throws a MergePolicy.MergeException, but there's no easy way to figure
out which index caused this (if you have more than one).

I plan to add the Directory to the MergeException.  I also made a few
other small changes to ConcurrentMergeScheduler:

  * Added handleMergeException method, which is called on exception,
    so that you can subclass ConcurrentMergeScheduler to do something
    when an exception occurs.

  * Added getMergeThread() method so you can override how the threads
    are created (eg, if you want to make them in a different thread
    group, use a pool, change priorities, etc.).

  * Added doMerge(...) to actually do this merge, so you can do
    something before starting and after finishing a merge.

  * Changed private -> protected on a few attrs

I plan to commit in a day or two.


--
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (LUCENE-1160) MergeException from CMS threads should record the Directory

Markus Jelsma (Jira)

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

Michael McCandless updated LUCENE-1160:
---------------------------------------

    Attachment: LUCENE-1150.patch

> MergeException from CMS threads should record the Directory
> -----------------------------------------------------------
>
>                 Key: LUCENE-1160
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1160
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>    Affects Versions: 2.3
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 2.4
>
>         Attachments: LUCENE-1150.patch
>
>
> When you hit an unhandled exception in ConcurrentMergeScheduler, it
> throws a MergePolicy.MergeException, but there's no easy way to figure
> out which index caused this (if you have more than one).
> I plan to add the Directory to the MergeException.  I also made a few
> other small changes to ConcurrentMergeScheduler:
>   * Added handleMergeException method, which is called on exception,
>     so that you can subclass ConcurrentMergeScheduler to do something
>     when an exception occurs.
>   * Added getMergeThread() method so you can override how the threads
>     are created (eg, if you want to make them in a different thread
>     group, use a pool, change priorities, etc.).
>   * Added doMerge(...) to actually do this merge, so you can do
>     something before starting and after finishing a merge.
>   * Changed private -> protected on a few attrs
> I plan to commit in a day or two.

--
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (LUCENE-1160) MergeException from CMS threads should record the Directory

Markus Jelsma (Jira)
In reply to this post by Markus Jelsma (Jira)

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

Michael McCandless updated LUCENE-1160:
---------------------------------------

    Attachment: LUCENE-1160.patch

> MergeException from CMS threads should record the Directory
> -----------------------------------------------------------
>
>                 Key: LUCENE-1160
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1160
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>    Affects Versions: 2.3
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 2.4
>
>         Attachments: LUCENE-1160.patch
>
>
> When you hit an unhandled exception in ConcurrentMergeScheduler, it
> throws a MergePolicy.MergeException, but there's no easy way to figure
> out which index caused this (if you have more than one).
> I plan to add the Directory to the MergeException.  I also made a few
> other small changes to ConcurrentMergeScheduler:
>   * Added handleMergeException method, which is called on exception,
>     so that you can subclass ConcurrentMergeScheduler to do something
>     when an exception occurs.
>   * Added getMergeThread() method so you can override how the threads
>     are created (eg, if you want to make them in a different thread
>     group, use a pool, change priorities, etc.).
>   * Added doMerge(...) to actually do this merge, so you can do
>     something before starting and after finishing a merge.
>   * Changed private -> protected on a few attrs
> I plan to commit in a day or two.

--
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (LUCENE-1160) MergeException from CMS threads should record the Directory

Markus Jelsma (Jira)
In reply to this post by Markus Jelsma (Jira)

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

Michael McCandless updated LUCENE-1160:
---------------------------------------

    Attachment:     (was: LUCENE-1150.patch)

> MergeException from CMS threads should record the Directory
> -----------------------------------------------------------
>
>                 Key: LUCENE-1160
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1160
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>    Affects Versions: 2.3
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 2.4
>
>         Attachments: LUCENE-1160.patch
>
>
> When you hit an unhandled exception in ConcurrentMergeScheduler, it
> throws a MergePolicy.MergeException, but there's no easy way to figure
> out which index caused this (if you have more than one).
> I plan to add the Directory to the MergeException.  I also made a few
> other small changes to ConcurrentMergeScheduler:
>   * Added handleMergeException method, which is called on exception,
>     so that you can subclass ConcurrentMergeScheduler to do something
>     when an exception occurs.
>   * Added getMergeThread() method so you can override how the threads
>     are created (eg, if you want to make them in a different thread
>     group, use a pool, change priorities, etc.).
>   * Added doMerge(...) to actually do this merge, so you can do
>     something before starting and after finishing a merge.
>   * Changed private -> protected on a few attrs
> I plan to commit in a day or two.

--
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (LUCENE-1160) MergeException from CMS threads should record the Directory

Markus Jelsma (Jira)
In reply to this post by Markus Jelsma (Jira)

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

Michael McCandless resolved LUCENE-1160.
----------------------------------------

    Resolution: Fixed

> MergeException from CMS threads should record the Directory
> -----------------------------------------------------------
>
>                 Key: LUCENE-1160
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1160
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>    Affects Versions: 2.3
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 2.4
>
>         Attachments: LUCENE-1160.patch
>
>
> When you hit an unhandled exception in ConcurrentMergeScheduler, it
> throws a MergePolicy.MergeException, but there's no easy way to figure
> out which index caused this (if you have more than one).
> I plan to add the Directory to the MergeException.  I also made a few
> other small changes to ConcurrentMergeScheduler:
>   * Added handleMergeException method, which is called on exception,
>     so that you can subclass ConcurrentMergeScheduler to do something
>     when an exception occurs.
>   * Added getMergeThread() method so you can override how the threads
>     are created (eg, if you want to make them in a different thread
>     group, use a pool, change priorities, etc.).
>   * Added doMerge(...) to actually do this merge, so you can do
>     something before starting and after finishing a merge.
>   * Changed private -> protected on a few attrs
> I plan to commit in a day or two.

--
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: [hidden email]
For additional commands, e-mail: [hidden email]