You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2018/05/10 15:08:00 UTC
[jira] [Commented] (IGNITE-8354) Ignite Continuosly refreshes
Cassandra Session when there is an Exception in execute method of
CassandraSessionImpl
[ https://issues.apache.org/jira/browse/IGNITE-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470520#comment-16470520 ]
Alexey Kuznetsov commented on IGNITE-8354:
------------------------------------------
[~irudyak] I reviewed PR.
Only minor issues found from my side.
Other than that - looks good for me.
> Ignite Continuosly refreshes Cassandra Session when there is an Exception in execute method of CassandraSessionImpl
> --------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-8354
> URL: https://issues.apache.org/jira/browse/IGNITE-8354
> Project: Ignite
> Issue Type: Bug
> Components: cassandra
> Reporter: Yashasvi Kotamraju
> Assignee: Igor Rudyak
> Priority: Major
>
> *In CassandraSessionImpl.java*
> When handlePreparedStatementClusterError method is called during Exception, the session is refreshed.There might be many preparedstatements created with old session(since a session object can be shared between different batches). So when we execute the preparedstatements created with old session on a new session created , we get the the Exception "com.datastax.driver.core.exceptions.InvalidQueryException You may have used a PreparedStatement that was created with another Cluster instance". Which would again call handlePreparedStatementClusterError and refresh session again and this happens continuously. We have observed continuous cassandra session refresh warnings when this scenario occurred.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)