Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Strange inter-region replicaton for my PubSub instance

Hi,

I have a GAE app in the US, so I set up my PubSub in the US as well. I was charged for inter-region PubSub replication from the US to Australia. I don't have any app running in Australia.

The only thing I can think of is that I am in Australia, and I have a local tool to test the PubSub subscription. But in my test tool, I did not specify which PubSub region it should use, I only need to provide the project ID. So, I wonder how the client could connect to the Australia region and trigger the PubSub replication. Also, can I set my PubSub client to connect to the US region?

Thanks

Solved Solved
0 1 404
1 ACCEPTED SOLUTION

A 1:1 support seems to be a much more suitable platform since this issue is specific to your project. A support dedicated to your issue can tap Billing support as well regarding your question with inter-region replication charges. 

As to your question with PubSub client connecting to another, I have found in this documentation pub/sub's load balancing mechanism:


Publishers in multiple regions may publish messages to a single topic with low latency. Any individual message is stored in a single region. However, a topic may have messages stored in many regions. When a subscriber client requests messages published to this topic, it connects to the nearest server which aggregates data from all messages published to the topic for delivery to the client.

 

 

View solution in original post

1 REPLY 1

A 1:1 support seems to be a much more suitable platform since this issue is specific to your project. A support dedicated to your issue can tap Billing support as well regarding your question with inter-region replication charges. 

As to your question with PubSub client connecting to another, I have found in this documentation pub/sub's load balancing mechanism:


Publishers in multiple regions may publish messages to a single topic with low latency. Any individual message is stored in a single region. However, a topic may have messages stored in many regions. When a subscriber client requests messages published to this topic, it connects to the nearest server which aggregates data from all messages published to the topic for delivery to the client.