[
https://issues.apache.org/jira/browse/FLINK-17611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17107244#comment-17107244
]
Igal Shilman edited comment on FLINK-17611 at 5/14/20, 12:11 PM:
-----------------------------------------------------------------
[~slinkydeveloper] having an endpoint in addition to uds would allow folks to
serve their statefun endpoint in a different location than "/".
I guess we can simplify here, and make it a requirement that working with a
unix domain socket, you must serve the statefun endpoint at "/", I'm okay with
that.
By the way, peeking at other projects that expose a unix domain socket (for
example Docker) the way to specify the path for a unix domain socket is using
the unix schema: "unix://....".
What do you folks think (cc: [~tzulitai]) about using the endpoint field and
deciding by the schema part of the endpoint.
For example:
{code:java}
function:
spec:
endpoint: unix://mnt/shared/worker.sock {code}
would mean that we are using the unix domain socket.
was (Author: igal):
[~slinkydeveloper] having an endpoint in addition to uds would allow folks to
serve their statefun endpoint in a different location than "/".
I guess we can simplify here, and make it a requirement that working with a
unix domain socket, you must serve the statefun endpoint at "/", I'm okay with
that.
By the way, peeking at other projects that expose a unix domain socket (for
example Docker) the way to specify the path for a unix domain socket is using
the unix schema: "unix://....".
What do you folks think (cc: [~tzulitai]) about using the endpoint field and
deciding by the schema part of the endpoint.
For example:
{code:java}
function:
spec:
endpoint: unix://mnt/shared/worker.sock {code}
would mean that we are using the unix domain socket?
> Support unix domain sockets for sidecar communication in Stateful Functions
> ---------------------------------------------------------------------------
>
> Key: FLINK-17611
> URL: https://issues.apache.org/jira/browse/FLINK-17611
> Project: Flink
> Issue Type: New Feature
> Components: Stateful Functions
> Reporter: Francesco Guardiani
> Assignee: Francesco Guardiani
> Priority: Major
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Hi all,
> I'm quite new to this project and I've started investigating its potential
> usage in Kubernetes.
> I've found in past that using Unix Domain Sockets across several containers
> in the same pod gives an interesting performance boost and drastically
> reduces the overhead of going through the network stack. Given that
> containers in a pod run in the same host, it's perfectly reasonable to let
> them communicate through unix domain sockets.
> If you're interested in such feature, I'm more than willing to help
> implementing that, given that I need a few pointers where to start from
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
