[
https://issues.apache.org/jira/browse/LUCENE-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273060#comment-16273060
]
ASF subversion and git services commented on LUCENE-8068:
---------------------------------------------------------
Commit 01d12777c4bcab7ae8085d5ed5e1b20a0e1a5526 in lucene-solr's branch
refs/heads/master from [~simonw]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=01d1277 ]
LUCENE-8068: Allow IndexWriter to write a single DWPT to disk
Adds a `flushNextBuffer` method to IndexWriter that allows the caller to
synchronously move the next pending or the biggest non-pending index buffer to
disk. This enables flushing selected buffer to disk without highjacking an
indexing thread. This is for instance useful if more than one IW (shards) must
be maintained in a single JVM / system.
> Allow IndexWriter to write a single DWPT to disk
> ------------------------------------------------
>
> Key: LUCENE-8068
> URL: https://issues.apache.org/jira/browse/LUCENE-8068
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Simon Willnauer
> Fix For: master (8.0), 7.2
>
> Attachments: LUCENE-8068.patch, LUCENE-8068.patch, LUCENE-8068.patch,
> LUCENE-8068.patch
>
>
> Today we IW can only flush a DWPT to disk if an external resource calls
> flush() or refreshes a NRT reader or if a DWPT is selected as flush pending.
> Yet, the latter has the problem that it always ties up an indexing thread and
> if flush / NRT refresh is called a whole bunch of indexing threads is tied
> up. If IW could offer a simple `flushNextBuffer()` method that synchronously
> flushes the next pending or biggest active buffer to disk memory could be
> controlled in a more fine granular fashion from outside of the IW. This is
> for instance useful if more than one IW (shards) must be maintained in a
> single JVM / system.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
