[
https://issues.apache.org/jira/browse/SOLR-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-3749.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.0
Committed - thanks Raintung Li!
> Default syncLevel cannot be configured by solrconfig.xml for
> updateLog(transaction log)
> ---------------------------------------------------------------------------------------
>
> Key: SOLR-3749
> URL: https://issues.apache.org/jira/browse/SOLR-3749
> Project: Solr
> Issue Type: Improvement
> Components: update
> Affects Versions: 4.0
> Environment: Solr cloud
> Reporter: Raintung Li
> Assignee: Mark Miller
> Labels: log, syncLevel,, transaction, updateLog
> Fix For: 4.0, 5.0
>
> Attachments: configpatch, patch.txt
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> In solr 4.0 environment, transaction log had been defined in three level,
> none/flush/fsync. The updateLog hard code the default sync level is
> SyncLevel.FLUSH.
> If user want to use the other levels, have to rewrite the RunUpdateProcess,
> to set the level.
> At best, user can set it in the solrconfig.xml, that it is easy to control
> and use.
> BTW, transaction log is very important for solr cloud, at best, invoke the
> sync to make sure kernel memory submit into the disk to avoid some corner
> case that maybe damage transaction log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
