lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Connie Yau <>
Subject RE: Changing Thread management to Tasks
Date Thu, 07 Apr 2016 19:30:40 GMT
Hi Oren,

Thanks for letting me know about this! When you say "default merge scheduler", do you mean
ConcurrentMergeScheduler? Would you be able to tell me about a scenario where the default
merge scheduler would leak exceptions? Also, are there a set of unit tests that test this?


-----Original Message-----
From: Oren Eini (Ayende Rahien) [] 
Sent: Monday, April 4, 2016 10:58 PM
Cc: Daniel Plaisted <>
Subject: Re: Changing Thread management to Tasks

Please note, one of the things that we had to do with this is to make sure that this doesn't
leak exceptions.
The default merge scheduler is known to leak exceptions to the thread, killing the process.
Need to be sure to handle this

*Hibernating Rhinos Ltd  *

Oren Eini* l CEO l *Mobile: + 972-52-548-6969

Office: +972-4-622-7811 *l *Fax: +972-153-4-622-7811

On Tue, Apr 5, 2016 at 1:15 AM, Connie Yau <> wrote:

> Hi,
> I've been working on trying to move 
> f988bf86f141af91ab2d7cd011db47%7c1&sdata=lcp54tq4j93yifdy8sWFmDNS2OiYZ
> MGl5EDtRcJJ%2bzU%3d to .NET Core and one of the issues I am having is migrating ConcurrentMergeScheduler
and Threads.  I want to replace the ConcurrentMergeScheduler with the default TaskScheduler
and Threads with Tasks. However, I noticed that there is a lot of logic to alter merges based
on the priority of their threads, etc.
> *         What is the reason we manage priority threads?
> o   If the default TaskScheduler is not sufficient, there is a
> QueuedTaskScheduler<
> Id%3d44488%26pathId%3d462437453&
> %7c574774f60d874dcc43da08d35d174289%7c72f988bf86f141af91ab2d7cd011db47
> %7c1&sdata=%2bqPmfU%2fxQ0hSPSpBWKMJYTkBCkkkOMh1PQ1j7kjwlDA%3d>
> that manages priority
> Thanks,
> Connie
View raw message