lizhimins opened a new issue, #142: URL: https://github.com/apache/rocketmq-flink/issues/142
Two defects in the gRPC module that both end in a job which stays RUNNING, checkpoints normally, logs nothing and reads zero records. **LITE mode never subscribes a sub lite topic** The builder binds the main topic and nothing else: there is no `subscribeLite` call anywhere in the module and no option to name the sub topics, so the SDK's lite topic set stays empty and the broker delivers no message. Three separate runs read zero rows. A native client comparison isolates it: with the same LITE topic and the same data, `bindTopic` alone receives 0 messages (`liteTopicSet=[]`), while `bindTopic` plus two `subscribeLite` calls receives 144. There is also no way to tell a missing subscription from an idle topic, and the Table path cannot work in LITE mode at all: it strips the receipt handle, so nothing can ever ack and every message is redelivered forever once its invisible duration expires. **A consumer the server rejected is retried forever** A consumer group the server registered as LITE cannot be used by a SIMPLE mode source; the proxy answers `ILLEGAL_CONSUMER_GROUP` on every request. The receive workers catch every `ClientException` and retry forever, so the job stays RUNNING, reads no record and reports nothing through the job's exception history. An unchecked failure from the SDK kills the worker thread outright with the same result. Consumer creation also catches `ClientException` only, while the SDK reports a rejected client as an unchecked exception wrapped by its Guava service. That escapes uncaught and leaves the reader marked as started with no consumer, so a later split assignment silently does nothing. A lite subscription rejected after the consumer is built leaks its channels and threads. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
