You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Md Mehrab Alam (Jira)" <ji...@apache.org> on 2022/01/24 14:03:00 UTC

[jira] [Created] (FLINK-25787) Adding endpoint support in Pubsub Source / Sink

Md Mehrab Alam created FLINK-25787:
--------------------------------------

             Summary: Adding endpoint support in Pubsub Source / Sink
                 Key: FLINK-25787
                 URL: https://issues.apache.org/jira/browse/FLINK-25787
             Project: Flink
          Issue Type: Improvement
            Reporter: Md Mehrab Alam


From Google Pubsub blog ([https://medium.com/google-cloud/google-cloud-pub-sub-reliability-user-guide-part-1-publishing-12577b9069fd])

 
{noformat}
Multi-regional or “global” outages affect only the regions where you have running publishers. If you have an application publishing from regions A, B and C and regions A and B go down, the application in region C is unaffected. At the same time, traffic from applications in A and B is not load-balanced out to C or another region. This is because Pub/Sub deliberately keeps traffic within the region to prevent cascading failures. An exception to this is traffic from outside of the GCP network connecting to Pub/Sub’s global service endpoint{noformat}
 

 

Example:

If Google Pubsub in region "us-central1" down then the application running in same region with global endpoint ({{{}pubsub.googleapis.com{}}}.) will not be able to connect to Google pubsub. But if we use regional endpoint to connect to Google pubsub in another region (say: us-east1) will work.

 

So we should expose option to set regional endpoint in Source/Sink.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)