You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Commit Tag Bot (JIRA)" <ji...@apache.org> on 2013/03/22 17:39:22 UTC

[jira] [Commented] (SOLR-3749) Default syncLevel cannot be configured by solrconfig.xml for updateLog(transaction log)

    [ https://issues.apache.org/jira/browse/SOLR-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610829#comment-13610829 ] 

Commit Tag Bot commented on SOLR-3749:
--------------------------------------

[branch_4x commit] Mark Robert Miller
http://svn.apache.org/viewvc?view=revision&revision=1385151

SOLR-3749: Allow default UpdateLog syncLevel to be configured by solrconfig.xml.

                
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org