[
https://issues.apache.org/jira/browse/LUCENE-9297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved LUCENE-9297.
------------------------------------
Resolution: Invalid
Please raise questions like this on the user's list, we try to reserve JIRAs
for known bugs/enhancements rather than usage questions.
See:
[http://lucene.apache.org/solr/community.html#mailing-lists-irc,] there are
links to both Lucene and Solr user's lists.
A _lot_ more people will see your question on that list and may be able to help
more quickly.
If it's determined that this really is a code issue or enhancement to Lucene or
Solr and not a configuration/usage problem, we can raise a new JIRA or reopen
this one.
> 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: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
