[jira] [Comment Edited] (FLINK-32716) Give 'Default'(or maybe 'None') option for 'scheduler-mode'
[ https://issues.apache.org/jira/browse/FLINK-32716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1723#comment-1723 ] Kwangin (Dennis) Jung edited comment on FLINK-32716 at 10/20/23 11:50 AM: -- [~paul8263] thanks for comment. > The issue ID in your commit message is incorrect -> Could you let me know how to fix it? I'm not sure what 'issue ID in commit message' is... was (Author: JIRAUSER301448): [~paul8263] > The issue ID in your commit message is incorrect -> Could you let me know how to fix it? I'm not sure what 'issue ID in commit message' is... > Give 'Default'(or maybe 'None') option for 'scheduler-mode' > --- > > Key: FLINK-32716 > URL: https://issues.apache.org/jira/browse/FLINK-32716 > Project: Flink > Issue Type: Improvement >Reporter: Kwangin (Dennis) Jung >Priority: Minor > > By setting-up scheduler-mode as 'REACTIVE', it scales-up/down by computing > status. > [https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#advanced-scheduling-options] > But currently it only allows 'REACTIVE', and when I want to de-activate with > such value as 'None', it causes exception. > (For now, it causes exception if I setup any other value instead of > 'REACTIVE') > > To make configuration bit more flexible, how about give 'None' (or 'Default') > as an option, to run in default mode? > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-32716) Give 'Default'(or maybe 'None') option for 'scheduler-mode'
[ https://issues.apache.org/jira/browse/FLINK-32716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1723#comment-1723 ] Kwangin (Dennis) Jung commented on FLINK-32716: --- [~paul8263] > The issue ID in your commit message is incorrect -> Could you let me know how to fix it? I'm not sure what 'issue ID in commit message' is... > Give 'Default'(or maybe 'None') option for 'scheduler-mode' > --- > > Key: FLINK-32716 > URL: https://issues.apache.org/jira/browse/FLINK-32716 > Project: Flink > Issue Type: Improvement >Reporter: Kwangin (Dennis) Jung >Priority: Minor > > By setting-up scheduler-mode as 'REACTIVE', it scales-up/down by computing > status. > [https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#advanced-scheduling-options] > But currently it only allows 'REACTIVE', and when I want to de-activate with > such value as 'None', it causes exception. > (For now, it causes exception if I setup any other value instead of > 'REACTIVE') > > To make configuration bit more flexible, how about give 'None' (or 'Default') > as an option, to run in default mode? > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-28758) FlinkKafkaConsumer fails to stop with savepoint
[
https://issues.apache.org/jira/browse/FLINK-28758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764503#comment-17764503
]
Kwangin (Dennis) Jung edited comment on FLINK-28758 at 9/13/23 6:33 AM:
[~dwysakowicz] [~markcho] [~pnowojski] thanks for suggestion.
I'm also facing same issue, and temporary suggestions above worked well on my
side.
(yet not sure whether savepoint keeps the data correctly...)
Is there a plan to apply this change?
was (Author: JIRAUSER301448):
[~dwysakowicz] [~markcho] [~pnowojski] thanks for suggestion.
I'm also facing same issue, and temporary suggestions above worked well on my
side.
Is there a plan to apply this change?
> FlinkKafkaConsumer fails to stop with savepoint
>
>
> Key: FLINK-28758
> URL: https://issues.apache.org/jira/browse/FLINK-28758
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
>Affects Versions: 1.15.0, 1.17.0, 1.16.1
> Environment: Flink version:1.15.0
> deploy mode :K8s applicaiton Mode. local mini cluster also have this
> problem.
> Kafka Connector : use Kafka SourceFunction . No new Api.
>Reporter: hjw
>Assignee: Mark Cho
>Priority: Critical
> Attachments: image-2022-10-13-19-47-56-635.png
>
>
> I post a stop with savepoint request to Flink Job throught rest api.
> A Error happened in Kafka connector close.
> The job will enter restarting .
> It is successful to use savepoint command alone.
> {code:java}
> 13:33:42.857 [Kafka Fetcher for Source: nlp-kafka-source -> nlp-clean
> (1/1)#0] DEBUG org.apache.kafka.clients.consumer.KafkaConsumer - [Consumer
> clientId=consumer-hjw-3, groupId=hjw] Kafka consumer has been closed
> 13:33:42.857 [Kafka Fetcher for Source: cpp-kafka-source -> cpp-clean
> (1/1)#0] INFO org.apache.kafka.common.utils.AppInfoParser - App info
> kafka.consumer for consumer-hjw-4 unregistered
> 13:33:42.857 [Kafka Fetcher for Source: cpp-kafka-source -> cpp-clean
> (1/1)#0] DEBUG org.apache.kafka.clients.consumer.KafkaConsumer - [Consumer
> clientId=consumer-hjw-4, groupId=hjw] Kafka consumer has been closed
> 13:33:42.860 [Source: nlp-kafka-source -> nlp-clean (1/1)#0] DEBUG
> org.apache.flink.streaming.runtime.tasks.StreamTask - Cleanup StreamTask
> (operators closed: false, cancelled: false)
> 13:33:42.860 [jobmanager-io-thread-4] INFO
> org.apache.flink.runtime.checkpoint.CheckpointCoordinator - Decline
> checkpoint 5 by task eeefcb27475446241861ad8db3f33144 of job
> d6fed247feab1c0bcc1b0dcc2cfb4736 at 79edfa88-ccc3-4140-b0e1-7ce8a7f8669f @
> 127.0.0.1 (dataPort=-1).
> org.apache.flink.util.SerializedThrowable: Task name with subtask : Source:
> nlp-kafka-source -> nlp-clean (1/1)#0 Failure reason: Task has failed.
> at
> org.apache.flink.runtime.taskmanager.Task.declineCheckpoint(Task.java:1388)
> at
> org.apache.flink.runtime.taskmanager.Task.lambda$triggerCheckpointBarrier$3(Task.java:1331)
> at
> java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:822)
> at
> java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:797)
> at
> java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
> at
> java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977)
> at
> org.apache.flink.streaming.runtime.tasks.SourceStreamTask$LegacySourceFunctionThread.run(SourceStreamTask.java:343)
> Caused by: org.apache.flink.util.SerializedThrowable:
> org.apache.flink.streaming.connectors.kafka.internals.Handover$ClosedException
> at
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:292)
> at
> java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:308)
> at
> java.util.concurrent.CompletableFuture.uniCompose(CompletableFuture.java:943)
> at
> java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:926)
> ... 3 common frames omitted
> Caused by: org.apache.flink.util.SerializedThrowable: null
> at
> org.apache.flink.streaming.connectors.kafka.internals.Handover.close(Handover.java:177)
> at
> org.apache.flink.streaming.connectors.kafka.internals.KafkaFetcher.cancel(KafkaFetcher.java:164)
> at
> org.apache.flink.streaming.connectors.kafka.FlinkKafkaConsumerBase.cancel(FlinkKafkaConsumerBase.java:945)
> at
> org.apache.flink.streaming.api.operators.StreamSource.stop(StreamSource.java:128)
> at
> org.apache.flink.streaming.runtime.tasks.SourceStreamTask.stopOperatorForStopWithSavepoint(SourceStreamTask.java:305)
> at
> org.apache.flink.streaming.runtime.tasks.SourceStreamTask.lambda$triggerStopWithSavepointAsync$1(SourceStreamTask.java:285)
> at
>
[jira] [Commented] (FLINK-28758) FlinkKafkaConsumer fails to stop with savepoint
[
https://issues.apache.org/jira/browse/FLINK-28758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764503#comment-17764503
]
Kwangin (Dennis) Jung commented on FLINK-28758:
---
[~dwysakowicz] [~markcho] [~pnowojski] thanks for suggestion.
I'm also facing same issue, and temporary suggestions above worked well on my
side.
Is there a plan to apply this change?
> FlinkKafkaConsumer fails to stop with savepoint
>
>
> Key: FLINK-28758
> URL: https://issues.apache.org/jira/browse/FLINK-28758
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
>Affects Versions: 1.15.0, 1.17.0, 1.16.1
> Environment: Flink version:1.15.0
> deploy mode :K8s applicaiton Mode. local mini cluster also have this
> problem.
> Kafka Connector : use Kafka SourceFunction . No new Api.
>Reporter: hjw
>Assignee: Mark Cho
>Priority: Critical
> Attachments: image-2022-10-13-19-47-56-635.png
>
>
> I post a stop with savepoint request to Flink Job throught rest api.
> A Error happened in Kafka connector close.
> The job will enter restarting .
> It is successful to use savepoint command alone.
> {code:java}
> 13:33:42.857 [Kafka Fetcher for Source: nlp-kafka-source -> nlp-clean
> (1/1)#0] DEBUG org.apache.kafka.clients.consumer.KafkaConsumer - [Consumer
> clientId=consumer-hjw-3, groupId=hjw] Kafka consumer has been closed
> 13:33:42.857 [Kafka Fetcher for Source: cpp-kafka-source -> cpp-clean
> (1/1)#0] INFO org.apache.kafka.common.utils.AppInfoParser - App info
> kafka.consumer for consumer-hjw-4 unregistered
> 13:33:42.857 [Kafka Fetcher for Source: cpp-kafka-source -> cpp-clean
> (1/1)#0] DEBUG org.apache.kafka.clients.consumer.KafkaConsumer - [Consumer
> clientId=consumer-hjw-4, groupId=hjw] Kafka consumer has been closed
> 13:33:42.860 [Source: nlp-kafka-source -> nlp-clean (1/1)#0] DEBUG
> org.apache.flink.streaming.runtime.tasks.StreamTask - Cleanup StreamTask
> (operators closed: false, cancelled: false)
> 13:33:42.860 [jobmanager-io-thread-4] INFO
> org.apache.flink.runtime.checkpoint.CheckpointCoordinator - Decline
> checkpoint 5 by task eeefcb27475446241861ad8db3f33144 of job
> d6fed247feab1c0bcc1b0dcc2cfb4736 at 79edfa88-ccc3-4140-b0e1-7ce8a7f8669f @
> 127.0.0.1 (dataPort=-1).
> org.apache.flink.util.SerializedThrowable: Task name with subtask : Source:
> nlp-kafka-source -> nlp-clean (1/1)#0 Failure reason: Task has failed.
> at
> org.apache.flink.runtime.taskmanager.Task.declineCheckpoint(Task.java:1388)
> at
> org.apache.flink.runtime.taskmanager.Task.lambda$triggerCheckpointBarrier$3(Task.java:1331)
> at
> java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:822)
> at
> java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:797)
> at
> java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
> at
> java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977)
> at
> org.apache.flink.streaming.runtime.tasks.SourceStreamTask$LegacySourceFunctionThread.run(SourceStreamTask.java:343)
> Caused by: org.apache.flink.util.SerializedThrowable:
> org.apache.flink.streaming.connectors.kafka.internals.Handover$ClosedException
> at
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:292)
> at
> java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:308)
> at
> java.util.concurrent.CompletableFuture.uniCompose(CompletableFuture.java:943)
> at
> java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:926)
> ... 3 common frames omitted
> Caused by: org.apache.flink.util.SerializedThrowable: null
> at
> org.apache.flink.streaming.connectors.kafka.internals.Handover.close(Handover.java:177)
> at
> org.apache.flink.streaming.connectors.kafka.internals.KafkaFetcher.cancel(KafkaFetcher.java:164)
> at
> org.apache.flink.streaming.connectors.kafka.FlinkKafkaConsumerBase.cancel(FlinkKafkaConsumerBase.java:945)
> at
> org.apache.flink.streaming.api.operators.StreamSource.stop(StreamSource.java:128)
> at
> org.apache.flink.streaming.runtime.tasks.SourceStreamTask.stopOperatorForStopWithSavepoint(SourceStreamTask.java:305)
> at
> org.apache.flink.streaming.runtime.tasks.SourceStreamTask.lambda$triggerStopWithSavepointAsync$1(SourceStreamTask.java:285)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTaskActionExecutor$SynchronizedStreamTaskActionExecutor.runThrowing(StreamTaskActionExecutor.java:93)
> at org.apache.flink.streaming.runtime.tasks.mailbox.Mail.run(Mail.java:90)
> at
> org.apache.flink.streaming.runtime.tasks.mailbox.MailboxProcessor.processMailsWhenDefaultActionUnavailable(MailboxProcessor.java:338)
> at
>
[jira] [Commented] (FLINK-32716) Give 'Default'(or maybe 'None') option for 'scheduler-mode'
[ https://issues.apache.org/jira/browse/FLINK-32716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756868#comment-17756868 ] Kwangin (Dennis) Jung commented on FLINK-32716: --- I've add following PR for this issue. [https://github.com/apache/flink/pull/23248] Could someone help review? > Give 'Default'(or maybe 'None') option for 'scheduler-mode' > --- > > Key: FLINK-32716 > URL: https://issues.apache.org/jira/browse/FLINK-32716 > Project: Flink > Issue Type: Improvement >Reporter: Kwangin (Dennis) Jung >Priority: Minor > > By setting-up scheduler-mode as 'REACTIVE', it scales-up/down by computing > status. > [https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#advanced-scheduling-options] > But currently it only allows 'REACTIVE', and when I want to de-activate with > such value as 'None', it causes exception. > (For now, it causes exception if I setup any other value instead of > 'REACTIVE') > > To make configuration bit more flexible, how about give 'None' (or 'Default') > as an option, to run in default mode? > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-32716) Give 'Default'(or maybe 'None') option for 'scheduler-mode'
[ https://issues.apache.org/jira/browse/FLINK-32716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kwangin (Dennis) Jung updated FLINK-32716: -- Summary: Give 'Default'(or maybe 'None') option for 'scheduler-mode' (was: Give 'None' option for 'scheduler-mode') > Give 'Default'(or maybe 'None') option for 'scheduler-mode' > --- > > Key: FLINK-32716 > URL: https://issues.apache.org/jira/browse/FLINK-32716 > Project: Flink > Issue Type: Improvement >Reporter: Kwangin (Dennis) Jung >Priority: Minor > > By setting-up scheduler-mode as 'REACTIVE', it scales-up/down by computing > status. > [https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#advanced-scheduling-options] > But currently it only allows 'REACTIVE', and when I want to de-activate with > such value as 'None', it causes exception. > (For now, it causes exception if I setup any other value instead of > 'REACTIVE') > > To make configuration bit more flexible, how about give 'None' (or 'Default') > as an option, to run in default mode? > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-32716) Give 'None' option for 'scheduler-mode'
[ https://issues.apache.org/jira/browse/FLINK-32716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750517#comment-17750517 ] Kwangin (Dennis) Jung edited comment on FLINK-32716 at 8/5/23 1:10 AM: --- [~paul8263] thanks for comment! I'm currently working on it. If it's okay please review the work when ready :) But seems I need to wait to be assigned... was (Author: JIRAUSER301448): [~paul8263] thanks for comment! I'm currently working on it. If it's okay please review the work when ready :) > Give 'None' option for 'scheduler-mode' > --- > > Key: FLINK-32716 > URL: https://issues.apache.org/jira/browse/FLINK-32716 > Project: Flink > Issue Type: Improvement >Reporter: Kwangin (Dennis) Jung >Priority: Minor > > By setting-up scheduler-mode as 'REACTIVE', it scales-up/down by computing > status. > [https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#advanced-scheduling-options] > But currently it only allows 'REACTIVE', and when I want to de-activate with > such value as 'None', it causes exception. > (For now, it causes exception if I setup any other value instead of > 'REACTIVE') > > To make configuration bit more flexible, how about give 'None' (or 'Default') > as an option, to run in default mode? > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-32716) Give 'None' option for 'scheduler-mode'
[ https://issues.apache.org/jira/browse/FLINK-32716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kwangin (Dennis) Jung updated FLINK-32716: -- Description: By setting-up scheduler-mode as 'REACTIVE', it scales-up/down by computing status. [https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#advanced-scheduling-options] But currently it only allows 'REACTIVE', and when I want to de-activate with such value as 'None', it causes exception. (For now, it causes exception if I setup any other value instead of 'REACTIVE') To make configuration bit more flexible, how about give 'None' (or 'Default') as an option, to run in default mode? was: By setting-up scheduler-mode as 'REACTIVE', it scales-up/down by computing status. To make configuration bit more flexible, how about give 'None' (or 'Default') as an option, to run in default mode? (For now, it causes exception if I setup any other value instead of 'REACTIVE') > Give 'None' option for 'scheduler-mode' > --- > > Key: FLINK-32716 > URL: https://issues.apache.org/jira/browse/FLINK-32716 > Project: Flink > Issue Type: Improvement >Reporter: Kwangin (Dennis) Jung >Priority: Minor > > By setting-up scheduler-mode as 'REACTIVE', it scales-up/down by computing > status. > [https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#advanced-scheduling-options] > But currently it only allows 'REACTIVE', and when I want to de-activate with > such value as 'None', it causes exception. > (For now, it causes exception if I setup any other value instead of > 'REACTIVE') > > To make configuration bit more flexible, how about give 'None' (or 'Default') > as an option, to run in default mode? > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-32716) Give 'None' option for 'scheduler-mode'
[ https://issues.apache.org/jira/browse/FLINK-32716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750517#comment-17750517 ] Kwangin (Dennis) Jung commented on FLINK-32716: --- [~paul8263] thanks for comment! I'm currently working on it. If it's okay please review the work when ready :) > Give 'None' option for 'scheduler-mode' > --- > > Key: FLINK-32716 > URL: https://issues.apache.org/jira/browse/FLINK-32716 > Project: Flink > Issue Type: Improvement >Reporter: Kwangin (Dennis) Jung >Priority: Minor > > By setting-up scheduler-mode as 'REACTIVE', it scales-up/down by computing > status. > To make configuration bit more flexible, how about give 'None' (or 'Default') > as an option, to run in default mode? > (For now, it causes exception if I setup any other value instead of > 'REACTIVE') > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-32717) Change of topic list from KafkaSource not works
[
https://issues.apache.org/jira/browse/FLINK-32717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750276#comment-17750276
]
Kwangin (Dennis) Jung edited comment on FLINK-32717 at 8/2/23 11:55 AM:
[~martijnvisser] got it. Thanks for following-up.
was (Author: JIRAUSER301448):
[~martijnvisser] thanks for following-up
> Change of topic list from KafkaSource not works
> ---
>
> Key: FLINK-32717
> URL: https://issues.apache.org/jira/browse/FLINK-32717
> Project: Flink
> Issue Type: Improvement
>Reporter: Kwangin (Dennis) Jung
>Priority: Minor
>
> I've setup 'KafkaSource' as following:
>
> {code:java}
> KafkaSource.builder().setTopics("A", "B")...{code}
>
> and later, removed 1 topic from list as following and restart application.
>
> {code:java}
> KafkaSource.builder().setTopics("B")...{code}
>
> But application still ingest data from topic 'A'.
> * Is this expected?
> * If it is, how can I stop ingesting data from removed topic?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-32717) Change of topic list from KafkaSource not works
[
https://issues.apache.org/jira/browse/FLINK-32717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750276#comment-17750276
]
Kwangin (Dennis) Jung commented on FLINK-32717:
---
[~martijnvisser] thanks for following-up
> Change of topic list from KafkaSource not works
> ---
>
> Key: FLINK-32717
> URL: https://issues.apache.org/jira/browse/FLINK-32717
> Project: Flink
> Issue Type: Improvement
>Reporter: Kwangin (Dennis) Jung
>Priority: Minor
>
> I've setup 'KafkaSource' as following:
>
> {code:java}
> KafkaSource.builder().setTopics("A", "B")...{code}
>
> and later, removed 1 topic from list as following and restart application.
>
> {code:java}
> KafkaSource.builder().setTopics("B")...{code}
>
> But application still ingest data from topic 'A'.
> * Is this expected?
> * If it is, how can I stop ingesting data from removed topic?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-32717) Change of topic list from KafkaSource not works
[
https://issues.apache.org/jira/browse/FLINK-32717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kwangin (Dennis) Jung updated FLINK-32717:
--
Summary: Change of topic list from KafkaSource not works (was: Change of
topic list from KafkaSource)
> Change of topic list from KafkaSource not works
> ---
>
> Key: FLINK-32717
> URL: https://issues.apache.org/jira/browse/FLINK-32717
> Project: Flink
> Issue Type: Improvement
>Reporter: Kwangin (Dennis) Jung
>Priority: Minor
>
> I've setup 'KafkaSource' as following:
>
> {code:java}
> KafkaSource.builder().setTopics("A", "B")...{code}
>
> and later, removed 1 topic from list as following and restart application.
>
> {code:java}
> KafkaSource.builder().setTopics("B")...{code}
>
> But application still ingest data from topic 'A'.
> * Is this expected?
> * If it is, how can I stop ingesting data from removed topic?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-32717) Change of topic list from KafkaSource
Kwangin (Dennis) Jung created FLINK-32717:
-
Summary: Change of topic list from KafkaSource
Key: FLINK-32717
URL: https://issues.apache.org/jira/browse/FLINK-32717
Project: Flink
Issue Type: Improvement
Reporter: Kwangin (Dennis) Jung
I've setup 'KafkaSource' as following:
{code:java}
KafkaSource.builder().setTopics("A", "B")...{code}
and later, removed 1 topic from list as following and restart application.
{code:java}
KafkaSource.builder().setTopics("B")...{code}
But application still ingest data from topic 'A'.
* Is this expected?
* If it is, how can I stop ingesting data from removed topic?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-32716) Give 'None' option for 'scheduler-mode'
Kwangin (Dennis) Jung created FLINK-32716: - Summary: Give 'None' option for 'scheduler-mode' Key: FLINK-32716 URL: https://issues.apache.org/jira/browse/FLINK-32716 Project: Flink Issue Type: Improvement Reporter: Kwangin (Dennis) Jung By setting-up scheduler-mode as 'REACTIVE', it scales-up/down by computing status. To make configuration bit more flexible, how about give 'None' (or 'Default') as an option, to run in default mode? (For now, it causes exception if I setup any other value instead of 'REACTIVE') -- This message was sent by Atlassian Jira (v8.20.10#820010)
