You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "tianhui (Jira)" <ji...@apache.org> on 2020/08/05 09:50:00 UTC

[jira] [Commented] (KYLIN-4683) Fail to consume kafka when partition number get larger

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

tianhui commented on KYLIN-4683:
--------------------------------

Looks like Kylin is not supportting kafka subscribe, because it's seeking kafka using null offset when there is CPPosition set. I think maybe Kylin can seek all new partitions from beginning.

 

> Fail to consume kafka when partition number get larger
> ------------------------------------------------------
>
>                 Key: KYLIN-4683
>                 URL: https://issues.apache.org/jira/browse/KYLIN-4683
>             Project: Kylin
>          Issue Type: Bug
>    Affects Versions: v3.0.2
>            Reporter: tianhui
>            Priority: Major
>         Attachments: image-2020-08-05-17-20-37-270.png
>
>
> I run a testing streaming cube with kafka. At first, the topic has 3 partitions, and the cube running smoothly. But after I alter kafka topic to 7 partitions, all receivers stop consuming. !image-2020-08-05-17-20-37-270.png!



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