You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use presto-gateway as proxy front of the Presto cluster. Presto-gateway stores query_id and next_url in the memory.
If presto-gateway is down, the mapping relationship between query_id and next_url is lost. Although presto can get mapping relationship by using mysql, it is too slow.
We deploy presto-gateway on the k8s, it is common for presto-gateway instances to restart. So we stores mapping relationship in the Redis. Presto-gateway becomes stateless service.
There are some advantages
Horizontal expansion
Upgrade presto-gateway transparent to users
Tolerate N-1 instance failures
I think this feature can make Presto-gateway highly available. Now I want to contribute this feature to the presto-gateway.
The text was updated successfully, but these errors were encountered:
hi, we are running presto-gateway on k8s and it is stateless. have you run into any issues?
I used the http protocol before, and now I use presto-gateway which is the https protocol. In Java 1.8 some versions jdbc-client can encounter timeout or get request blocked.
We use presto-gateway as proxy front of the Presto cluster. Presto-gateway stores
query_id
andnext_url
in the memory.If presto-gateway is down, the mapping relationship between query_id and next_url is lost. Although presto can get mapping relationship by using mysql, it is too slow.
We deploy presto-gateway on the k8s, it is common for presto-gateway instances to restart. So we stores mapping relationship in the Redis. Presto-gateway becomes stateless service.
There are some advantages
I think this feature can make Presto-gateway highly available. Now I want to contribute this feature to the presto-gateway.
The text was updated successfully, but these errors were encountered: