You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Remko Kuipers (JIRA)" <ji...@apache.org> on 2013/04/23 12:23:16 UTC
[jira] [Updated] (SOLR-4747) DIH close database connection directly
after entity is completed
[ https://issues.apache.org/jira/browse/SOLR-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Remko Kuipers updated SOLR-4747:
--------------------------------
Issue Type: New Feature (was: Bug)
Summary: DIH close database connection directly after entity is completed (was: DIH postgres connections are not closed)
> DIH close database connection directly after entity is completed
> ----------------------------------------------------------------
>
> Key: SOLR-4747
> URL: https://issues.apache.org/jira/browse/SOLR-4747
> Project: Solr
> Issue Type: New Feature
> Components: contrib - DataImportHandler
> Affects Versions: 4.2
> Environment: Solr on CentOs 6.4 within jboss, debian 7.0 postgres server
> Reporter: Remko Kuipers
>
> I use DIH to create an index for a number of postgres databases. These databases all contain an identical schema/table setup. The config looks like <entity rootEntity="false"><entity/><entity/></entity> repeated for each datasource. The readonly flag is set to true on the subentity objects. For each database solr creates three connections. These connections remain active as "idle in transaction" until the indexer is finished. As the number of databases times three exceeds my max_connections setting in postgres the indexer inevitably fails halfway through with a no more connections available error.
--
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