[
https://issues.apache.org/jira/browse/LUCENE-9297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kaihe updated LUCENE-9297:
--------------------------
Summary: partly updating strategy (was: Index has about 600+
columns，average size of doc is relatively big, Lucene firstly obtain the
original doc from disk and then merge the old and the updating coulmns to a new
one,finally flush to disk.The dsik io usage rate of our 150+ nodes always reach
)
> partly updating strategy
> ------------------------
>
> Key: LUCENE-9297
> URL: https://issues.apache.org/jira/browse/LUCENE-9297
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: kaihe
> Priority: Major
>
> Index has about 600+ columns，average size of doc is relatively big, Lucene
> firstly obtain the original doc from disk and then merge the old and the
> updating coulmns to a new one,finally flush to disk.
> The dsik io usage rate of our 150+ nodes always reach nearly 99% while partly
> updating requests call frequently.
> I want to optimize the partly updating strategy, only partly columns instead
> of all are obtained and merge into a new one while partly updating request
> calls,in purpose of cuting down disk io usage rate.
> is there any suggestions?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
