[
https://issues.apache.org/jira/browse/SOLR-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638928#comment-13638928
]
Remko Kuipers commented on SOLR-4747:
-------------------------------------
I had assumed the connections would be closed automatically, especially as I'm
using readOnly on the root entities, after the entities using them were done.
But you are right, if there is a way to instruct the DIH to commit the
transaction and close the commits directly after the entity is finished that
would solve the issue. I'll update the title accordingly.
> 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]
