another question kinda related to the above, we ar...
# troubleshooting
l
another question kinda related to the above, we are currently running on gke, and our deep storage is configured with gcs, we have liveness and readiness probes configured in these machines, i think that the server when it starts it tries to pull the data available from gcs, however, i think this may take longer as more data gets ingested, how do you all manage this? we had 10min configure for all the data to get into the server but now we more data being in the machines it seems like we need even more wait time for the data to be ready in the machines, any suggestions?
m
Every restart should not require pull from deep store if you are using ebs
l
right
i got confused
so right now the issue is that our health/readiness check is not getting ready in those 10 min
and pod gets restarted
"message": "null:\n64370 segments [….] unavailable, errorCode: 305
is the error we see in the brokers
and those are all the segments available