[
https://issues.apache.org/jira/browse/SOLR-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931168#action_12931168
]
Fuad Efendi commented on SOLR-2233:
-----------------------------------
*Performance Tuning*
I have extremely sophisticated SQL; root entity runs 10-15 subqueries, and I am
unable to use {{CachedSqlEntityProcessor}}. That's why I am looking into
multithreading.
Unfortunately, with existing approach connection will be closed after each use.
And for most databases _creating a connection (authentication, resource
allocation) is extremely expensive_.
The best approach is to use container resource (JNDI, connection pooling), but
I'll try to find what else can be improved.
> DataImportHandler - JdbcDataSource is not thread safe
> -----------------------------------------------------
>
> Key: SOLR-2233
> URL: https://issues.apache.org/jira/browse/SOLR-2233
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.5
> Reporter: Fuad Efendi
> Attachments: FE-patch.txt
>
>
> Whenever Thread A spends more than 10 seconds on a Connection (by retrieving
> records in a batch), Thread B will close connection.
> Related exceptions happen when we use "threads=" attribute for entity;
> usually exception stack contains message "connection already closed"
> It shouldn't happen with some JNDI data source, where Connection.close()
> simply returns Connection to a pool of available connections, but we might
> get different errors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
