Why --max-instances 1?

[nick-youngblut]

I'm curious why you used --max-instances 1 for gcloud run deploy.

Was that necessary to deal with the GCR http 400 errors?

[randy3k]

It was needed because Shiny is a stateful application and GCR didn't route the traffic of the same user to the same container.
Having just 1 container makes sure that all traffic are routed to the same place.

This is no longer needed since GCR introduced session affinity. https://cloud.google.com/run/docs/configuring/session-affinity

Additionally, I believe that GCR now supports websocket, you probably do not need to use the customized shiny config.

[randy3k]

Judging from your message in the other thread, sounds like that the webdocket patch is still needed.

[nick-youngblut]

Thanks @randy3k for the info!

This is no longer needed since GCR introduced session affinity.

My problems persisted after adding the webdocket patch. Adding --max-instances 1 fixed the issue.

[randy3k]

Thanks @randy3k for the info!

This is no longer needed since GCR introduced session affinity.

My problems persisted after adding the webdocket patch. Adding --max-instances 1 fixed the issue.

you will need to enable session affinity.