You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2013/06/05 12:47:19 UTC

[jira] [Created] (STANBOL-1092) Improve UpdateHandler configuration of the SolrYard and enable commitWithin by default

Rupert Westenthaler created STANBOL-1092:
--------------------------------------------

             Summary: Improve UpdateHandler configuration of the SolrYard and enable commitWithin by default
                 Key: STANBOL-1092
                 URL: https://issues.apache.org/jira/browse/STANBOL-1092
             Project: Stanbol
          Issue Type: Improvement
          Components: Entityhub
            Reporter: Rupert Westenthaler
            Assignee: Rupert Westenthaler


Right now the default configuration of the SolrYard is

* commitWithin is deactivated - meaning that every change does trigger a commit
* Auto commit is deactivated
* Transaction Log is enabled
* Soft Commit is deactivated

This has several potential issues

* The default configuration is very slow for updates (e.g. loading Entities to a ManagedSite)
* If commitWithin is enabled there will be no commits what will cause the Transaction Log to grow up to the size of the index


With this issue the default configuration will be changed like follows:

* commitWithin will be enabled by default(change in the DEFAULT value for the configuration property). The (default) duration will be kept by 10sec
* (hard) auto commit will be set to 20sec. This ensures that data are written to disc at least every 20sec
* soft auto commit will be set to 1sec. This means that an added/updated Entity will be available to seaches latest 1sec after adding it
* transaction log will be deactivated. Users that do need real time search will need to configure this manually. Please also not the Solr Documentation for how to configure this feature properly (e.g. it is recommended to have the transaction log on a different disc as the index)


--
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