Bug P2
Status Update
Comments
sa...@google.com <sa...@google.com> #2
Apologies, I intended to create a feature request not a bug. I will create a feature request instead.
sa...@google.com <sa...@google.com> #3
Hello,
This issue report has been forwarded to the Cloud Dataproc Product team so that they may investigate it, but there is no ETA for a resolution today. Future updates regarding this issue will be provided here.
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
As part of network egress traffic analysis, customer has observed that there are connections and data transfer happening between different dataproc
cluster nodes which we are not expecting.
What you expected to happen:
Identify why Egress Nov 21st and on Nov 22nd are suddenly increased
Steps to reproduce:
These dataproc clusters are NOT configured to communicate with each other in any way.
Based on my skimming if the sheet, it looks like that traffic is always between a secondary worker of one cluster and a primary worker of another cluster.
The secondary can be either the source or the dest. Here is an example from the "nov23"
Other information (workarounds you have tried, documentation consulted, etc):
This public issue tracker was created for customer visibility