ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8354) Ignite Continuosly refreshes Cassandra Session when there is an Exception in execute method of CassandraSessionImpl
Date Sat, 28 Apr 2018 23:21:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457836#comment-16457836
] 

ASF GitHub Bot commented on IGNITE-8354:
----------------------------------------

GitHub user irudyak opened a pull request:

    https://github.com/apache/ignite/pull/3940

    IGNITE-8354 Ignite Continuosly refreshes Cassandra Session when there is an Exception
in execute method of CassandraSessionImpl

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/irudyak/ignite ignite-8354

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/3940.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3940
    
----
commit 2def238b89e155b163f5c61d3f84ff195dbe390c
Author: Igor Rudyak <igor.rudyak@...>
Date:   2018-04-28T23:19:25Z

    IGNITE-8354

----


> 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)

Mime
View raw message