简体   繁体   English

在 Kafka 连接器中获取 Ignite 异常

[英]Getting Ignite Exception in Kafka Connector

I am running 3 servers and 1 client topology.我正在运行 3 个服务器和 1 个客户端拓扑。

1 of the servers node is being run by kafka connector process. 1 个服务器节点由 kafka 连接器进程运行。

client is not able to send any message to that kafka connector ignite node.客户端无法向该 kafka 连接器点燃节点发送任何消息。

this is the exception这是例外

SEVERE: Failed to read message [msg=GridIoMessage [plc=0, topic=null, topicOrd=-1, ordered=false, timeout=0, skipOnTimeout=false, msg=null], buf=java.nio.DirectByteBuffer[pos=4 lim=251 cap=32768], reader=DirectMessageReader [state=DirectMessageState [pos=0, stack=[StateItem [stream=DirectByteBufferStreamImplV2 [baseOff=140323292482432, arrOff=-1, tmpArrOff=0, valReadBytes=0, tmpArrBytes=0, msgTypeDone=false, msg=null, mapIt=null, it=null, arrPos=-1, keyDone=false, readSize=-1, readItems=0, prim=0, primShift=0, uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0], state=0], null, null, null, null, null, null, null, null, null]], protoVer=3, lastRead=false], ses=GridSelectorNioSessionImpl [worker=DirectNioClientWorker [super=AbstractNioClientWorker [idx=3, bytesRcvd=251, bytesSent=0, bytesRcvd0=251, bytesSent0=0, select=true, super=GridWorker [name=grid-nio-worker-tcp-comm-3, igniteInstanceName=null, finished=false, heartbeatTs=1604581761046, hashCode=1782557810, interrupted=false, runner=grid-nio-worker-tcp-comm-3-#139]]], writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768], readBuf=java.nio.DirectByteBuffer[pos=4 lim=251 cap=32768], inRecovery=GridNioRecoveryDescriptor [acked=9, resendCnt=0, rcvCnt=7, sentCnt=9, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode [id=3f63a8d7-8964-4a4b-89c1-124d8eaba14a, consistentId=3f63a8d7-8964-4a4b-89c1-124d8eaba14a, addrs=ArrayList [127.0.0.1, 172.20.50.222], sockAddrs=HashSet [/127.0.0.1:0, /172.20.50.222:0], discPort=0, order=4, intOrder=4, lastExchangeTime=1604581749120, loc=false, ver=8.7.10#20191227-sha1:c481441d, isClient=true], connected=false, connectCnt=1, queueLimit=4096, reserveCnt=2, pairedConnections=false], outRecovery=GridNioRecoveryDescriptor [acked=9, resendCnt=0, rcvCnt=7, sentCnt=9, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode [id=3f63a8d7-8964-4a4b-89c1-124d8eaba14a, consistentId=3f63a8d7-8964-4a4b-89c1-124d8eaba14a, addrs=ArrayList [127.0.0.1, 172.20.50.222], sockAddrs=HashSet [/127.0.0.1:0, /172.20.50.222:0], discPort=0, order=4, intOrder=4, lastExchangeTime=1604581749120, loc=false, ver=8.7.10#20191227-sha1:c481441d, isClient=true], connected=false, connectCnt=1, queueLimit=4096, reserveCnt=2, pairedConnections=false], outboundMessagesQueueSizeMetric=o.a.i.i.processors.metric.impl.AtomicLongMetric@69a257d1, super=GridNioSessionImpl [locAddr=/172.20.52.38:54412, rmtAddr=/172.20.50.222:47100, createTime=1604581761046, closeTime=0, bytesSent=0, bytesRcvd=251, bytesSent0=0, bytesRcvd0=251, sndSchedTime=1604581761046, lastSndTime=1604581761046, lastRcvTime=1604581761046, readsPaused=false, filterChain=FilterChain[filters=[GridNioTracerFilter [tracer=GridProcessorAdapter []], GridNioCodecFilter [parser=o.a.i.i.util.nio.GridDirectParser@1766eecd, directMode=true], GridConnectionBytesVerifyFilter], accepted=false, markedForClose=false]]]
class org.apache.ignite.IgniteException: Invalid message type: -33
    at org.apache.ignite.internal.managers.communication.GridIoMessageFactory.create(GridIoMessageFactory.java:1106)
    at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$5.create(TcpCommunicationSpi.java:2407)
    at org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1175)
    at org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:335)
    at org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:270)
    at org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:89)
    at org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:112)
    at org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:108)
    at org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:87)
    at org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:108)
    at org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3681)
    at org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:174)
    at org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1360)
    at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2472)
    at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2239)
    at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1880)
    at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
    at java.lang.Thread.run(Thread.java:748)```

Direct type -33 is GridH2QueryRequest .直接类型 -33 是GridH2QueryRequest

Are you sure that your Kafka connector node has ignite-indexing in its classpath?您确定您的 Kafka 连接器节点在其类路径中具有ignite-indexing吗? Try adding it explicitly.尝试明确添加它。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 kafka 点燃水槽连接器 - kafka ignite sink connector Kafka Ignite Sink Connector - Ignite 的配置文件 - Kafka Ignite Sink Connector - Configuration file for Ignite Ignite Source Kafka Connector 是否提供数据的主题分区? - Does Ignite Source Kafka Connector provide topic partitioning of data? Kafka Connect:获取连接器配置 - Kafka Connect: Getting connector configuration 使用 kafka 连接器推送到 elasticsearch 时出现非法参数异常 - illegal_argument_exception while using kafka connector to push to elasticsearch 运行 Kafka Connect S3 Source Connector 的 ClassNotFound 异常 - ClassNotFound exception running Kafka Connect S3 Source Connector Kafka Connect JDBC连接器-由于发生不可恢复的异常而退出WorkerSinkTask - Kafka Connect JDBC Connector - Exiting WorkerSinkTask due to unrecoverable exception kafka-connect:连接器接收器cassandra的分布式配置出错 - kafka-connect : Getting error in distributed configuration for connector sink cassandra 无法通过雪花 kafka 连接器将数据插入雪花数据库,但是连接器正在启动 - Not able to get the data insert into snowflake database, through snowflake kafka connector, however connector is getting started Apache Ignite 与 Apache Kafka - Apache Ignite vs Apache Kafka
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM