[jira] [Commented] (BEAM-10192) Duplicate PubSub subscriptions with python direct runner in Jupyter/Colab environment

2022-06-04 Thread Danny McCormick (Jira)


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

Danny McCormick commented on BEAM-10192:


This issue has been migrated to https://github.com/apache/beam/issues/20250

> Duplicate PubSub subscriptions with python direct runner in Jupyter/Colab 
> environment
> -
>
> Key: BEAM-10192
> URL: https://issues.apache.org/jira/browse/BEAM-10192
> Project: Beam
>  Issue Type: Bug
>  Components: io-py-gcp
>Affects Versions: 2.22.0
> Environment: Ubuntu 18 (Colab notebook), Python SDK
>Reporter: Harrison
>Priority: P3
>
> When running a streaming pipeline on Colab with direct runner, ReadFromPubSub 
> can retain old subscriptions and cause message duplication. For example, 
> manually killing a cell that is running a streaming pubsub pipeline does not 
> delete the pubsub subscription. If the cell is rerun, the ReadFromPubSub 
> component will actually be subscribed twice which results in duplicate 
> messages.
> Manually deleting old subscriptions (e.g. via the GCP dashboard) temporarily 
> fixes the problem.
> This Colab notebook: 
> [https://gist.github.com/hgarrereyn/64ce87cbbcbe9c34ccdd13eafe49e3fb] 
> contains a runnable example of the bug.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Commented] (BEAM-10192) Duplicate PubSub subscriptions with python direct runner in Jupyter/Colab environment

2020-08-18 Thread Beam JIRA Bot (Jira)


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

Beam JIRA Bot commented on BEAM-10192:
--

This issue was marked "stale-P2" and has not received a public comment in 14 
days. It is now automatically moved to P3. If you are still affected by it, you 
can comment and move it back to P2.

> Duplicate PubSub subscriptions with python direct runner in Jupyter/Colab 
> environment
> -
>
> Key: BEAM-10192
> URL: https://issues.apache.org/jira/browse/BEAM-10192
> Project: Beam
>  Issue Type: Bug
>  Components: io-py-gcp
>Affects Versions: 2.22.0
> Environment: Ubuntu 18 (Colab notebook), Python SDK
>Reporter: Harrison
>Priority: P3
>
> When running a streaming pipeline on Colab with direct runner, ReadFromPubSub 
> can retain old subscriptions and cause message duplication. For example, 
> manually killing a cell that is running a streaming pubsub pipeline does not 
> delete the pubsub subscription. If the cell is rerun, the ReadFromPubSub 
> component will actually be subscribed twice which results in duplicate 
> messages.
> Manually deleting old subscriptions (e.g. via the GCP dashboard) temporarily 
> fixes the problem.
> This Colab notebook: 
> [https://gist.github.com/hgarrereyn/64ce87cbbcbe9c34ccdd13eafe49e3fb] 
> contains a runnable example of the bug.



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


[jira] [Commented] (BEAM-10192) Duplicate PubSub subscriptions with python direct runner in Jupyter/Colab environment

2020-08-04 Thread Beam JIRA Bot (Jira)


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

Beam JIRA Bot commented on BEAM-10192:
--

This issue is P2 but has been unassigned without any comment for 60 days so it 
has been labeled "stale-P2". If this issue is still affecting you, we care! 
Please comment and remove the label. Otherwise, in 14 days the issue will be 
moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed 
explanation of what these priorities mean.


> Duplicate PubSub subscriptions with python direct runner in Jupyter/Colab 
> environment
> -
>
> Key: BEAM-10192
> URL: https://issues.apache.org/jira/browse/BEAM-10192
> Project: Beam
>  Issue Type: Bug
>  Components: io-py-gcp
>Affects Versions: 2.22.0
> Environment: Ubuntu 18 (Colab notebook), Python SDK
>Reporter: Harrison
>Priority: P2
>  Labels: stale-P2
>
> When running a streaming pipeline on Colab with direct runner, ReadFromPubSub 
> can retain old subscriptions and cause message duplication. For example, 
> manually killing a cell that is running a streaming pubsub pipeline does not 
> delete the pubsub subscription. If the cell is rerun, the ReadFromPubSub 
> component will actually be subscribed twice which results in duplicate 
> messages.
> Manually deleting old subscriptions (e.g. via the GCP dashboard) temporarily 
> fixes the problem.
> This Colab notebook: 
> [https://gist.github.com/hgarrereyn/64ce87cbbcbe9c34ccdd13eafe49e3fb] 
> contains a runnable example of the bug.



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


[jira] [Commented] (BEAM-10192) Duplicate PubSub subscriptions with python direct runner in Jupyter/Colab environment

2020-06-04 Thread Harrison (Jira)


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

Harrison commented on BEAM-10192:
-

This may be related to BEAM-2988 

> Duplicate PubSub subscriptions with python direct runner in Jupyter/Colab 
> environment
> -
>
> Key: BEAM-10192
> URL: https://issues.apache.org/jira/browse/BEAM-10192
> Project: Beam
>  Issue Type: Bug
>  Components: io-py-gcp
>Affects Versions: 2.22.0
> Environment: Ubuntu 18 (Colab notebook), Python SDK
>Reporter: Harrison
>Priority: P2
>
> When running a streaming pipeline on Colab with direct runner, ReadFromPubSub 
> can retain old subscriptions and cause message duplication. For example, 
> manually killing a cell that is running a streaming pubsub pipeline does not 
> delete the pubsub subscription. If the cell is rerun, the ReadFromPubSub 
> component will actually be subscribed twice which results in duplicate 
> messages.
> Manually deleting old subscriptions (e.g. via the GCP dashboard) temporarily 
> fixes the problem.
> This Colab notebook: 
> [https://gist.github.com/hgarrereyn/64ce87cbbcbe9c34ccdd13eafe49e3fb] 
> contains a runnable example of the bug.



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