Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Wed, 3 Feb 2016 15:42:39 +0000 (UTC)
From: "Robert Metzger (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12936372.1454513798000.289374.1454514159947@Atlassian.JIRA>
In-Reply-To: <JIRA.12936372.1454513798000@Atlassian.JIRA>
References: <JIRA.12936372.1454513798000@Atlassian.JIRA>
 <JIRA.12936372.1454513798032@arcas>
Subject: [jira] [Commented] (FLINK-3326) Kafka Consumer doesn't retrieve
 messages after killing flink job which was using the same topic
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Metzger commented on FLINK-3326:
---------------------------------------

Did the first job use checkpointing?
Do you use the same "group.id" for all jobs?

> Kafka Consumer doesn't retrieve messages after killing flink job which was using the same topic
> -----------------------------------------------------------------------------------------------
>
>                 Key: FLINK-3326
>                 URL: https://issues.apache.org/jira/browse/FLINK-3326
>             Project: Flink
>          Issue Type: Bug
>          Components: flink-contrib
>    Affects Versions: 0.10.1
>         Environment: Java
>            Reporter: Farouk Salem
>            Priority: Blocker
>              Labels: flink, kafka
>
> If there is a streaming job which retrieving data from a Kafka topic (from the smallest offest) and this job is killed manually, starting another job (or the same job) after the killed job will not be able to consume data from the same topic starting from smallest offset.
> I tried this behavior more than 10 times and each time, it failed


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)