[
https://issues.apache.org/jira/browse/SOLR-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638031#comment-13638031
]
Shalin Shekhar Mangar commented on SOLR-4747:
---------------------------------------------
It sounds like you want DIH to close all connections per root entity as soon as
all rows have been processed. This way, when DIH goes to the next root entity,
connections for the previous entity's data sources would have been closed. If
so, the title of the issue should be changed because DIH does close connections
but not when you expect.
> DIH postgres connections are not closed
> ---------------------------------------
>
> Key: SOLR-4747
> URL: https://issues.apache.org/jira/browse/SOLR-4747
> Project: Solr
> Issue Type: Bug
> 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: [email protected]
For additional commands, e-mail: [email protected]
