[ 
https://issues.apache.org/jira/browse/FLINK-12992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-12992:
-----------------------------------
    Labels: auto-deprioritized-critical stale-major  (was: 
auto-deprioritized-critical)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Major but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this 
ticket is a Major, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> All host(s) tried for query failed (tried 
> com.datastax.driver.core.exceptions.TransportException: Error writing...)
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-12992
>                 URL: https://issues.apache.org/jira/browse/FLINK-12992
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Cassandra
>    Affects Versions: 1.7.2, 1.8.0
>         Environment: <dependency>
>  <groupId>org.apache.flink</groupId>
>  <artifactId>flink-connector-cassandra_2.11</artifactId>
>  <version>1.8.0</version>
> </dependency>
>            Reporter: yanxiaobin
>            Priority: Major
>              Labels: auto-deprioritized-critical, stale-major
>
> We are using flink streming application with cassandra connector providing 
> sinks that writes data into a [Apache 
> Cassandra|https://cassandra.apache.org/] database. 
> At first we found the following exceptions:All host(s) tried for query failed 
> (tried com.datastax.driver.core.exceptions.TransportException: Error 
> writing...). This exception will cause the streaming job to fail
>  
> And we have carefully checked that Cassandra service and network are all 
> normal. Finally, we refer to the source code of DataStax Java Driver that the 
> connector depends on. We found that the real exception caused the problem is 
> as follows:
> com.datastax.shaded.netty.handler.codec.EncoderException: 
> java.lang.IllegalAccessError: com/datastax/driver/core/Frame at 
> com.datastax.shaded.netty.handler.codec.MessageToMessageEncoder.write(MessageToMessageEncoder.java:107)
>  at 
> com.datastax.shaded.netty.channel.AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:643)
>  at 
> com.datastax.shaded.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:700)
>  at 
> com.datastax.shaded.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:636)
>  at 
> com.datastax.shaded.netty.handler.codec.MessageToMessageEncoder.write(MessageToMessageEncoder.java:112)
>  at 
> com.datastax.shaded.netty.channel.AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:643)
>  at 
> com.datastax.shaded.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:700)
>  at 
> com.datastax.shaded.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:636)
>  at 
> com.datastax.shaded.netty.handler.timeout.IdleStateHandler.write(IdleStateHandler.java:284)
>  at 
> com.datastax.shaded.netty.channel.AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:643)
>  at 
> com.datastax.shaded.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:700)
>  at 
> com.datastax.shaded.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:636)
>  at 
> com.datastax.shaded.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:622)
>  at 
> com.datastax.shaded.netty.channel.DefaultChannelPipeline.write(DefaultChannelPipeline.java:939)
>  at 
> com.datastax.shaded.netty.channel.AbstractChannel.write(AbstractChannel.java:234)
>  at com.datastax.driver.core.Connection$Flusher.run(Connection.java:872) at 
> com.datastax.shaded.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
>  at 
> com.datastax.shaded.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357) 
> at 
> com.datastax.shaded.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
>  at java.lang.Thread.run(Thread.java:748) Caused by: 
> java.lang.IllegalAccessError: com/datastax/driver/core/Frame at 
> com.datastax.shaded.netty.util.internal.__matchers__.com.datastax.driver.core.FrameMatcher.match(NoOpTypeParameterMatcher.java)
>  at 
> com.datastax.shaded.netty.handler.codec.MessageToMessageEncoder.acceptOutboundMessage(MessageToMessageEncoder.java:77)
>  at 
> com.datastax.shaded.netty.handler.codec.MessageToMessageEncoder.write(MessageToMessageEncoder.java:84)
>  
> Based on this exception, we found relevant information 
> [https://datastax-oss.atlassian.net/browse/JAVA-1337?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel]
>   
>  
> Because I found that the latest version of flink-cassandra-connector uses the 
> datastax Java driver old version 3.0.0.Perhaps we should upgrade the version 
> on which the connector depends to Java driver 3.3.0+ to avoid this problem.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to