[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-827) Remove the Worker executor
Sanne Grinovero (JIRA)
noreply at atlassian.com
Thu Feb 9 09:55:12 EST 2012
[ https://hibernate.onjira.com/browse/HSEARCH-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45483#comment-45483 ]
Sanne Grinovero commented on HSEARCH-827:
-----------------------------------------
This executor and configuration to resize it is now actually useful; I'm closing this issue as outdated and we might actually think in sharing the executor across multiple backends and provide a higher default value, or use an auto-scaling value instead of a fixed size as order of update operations is now correctly enforced by another pool.
> Remove the Worker executor
> --------------------------
>
> Key: HSEARCH-827
> URL: https://hibernate.onjira.com/browse/HSEARCH-827
> Project: Hibernate Search
> Issue Type: Remove Feature
> Components: engine
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
>
> There's no need any more to keep this executor around, it's only adding up some complexity, and possibly messing with order of LuceneWorks being applied, when used in a non-default threadpool size (which is one, providing a bottleneck too).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list