[
https://issues.apache.org/jira/browse/FLINK-17611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17107270#comment-17107270
]
Francesco Guardiani edited comment on FLINK-17611 at 5/14/20, 1:05 PM:
-----------------------------------------------------------------------
Opened the PR here: https://github.com/apache/flink-statefun/pull/110
]I've implemented a solution that uses both endpoint and uds field, to specify
both path and socket file, let me know your thoughts about that
was (Author: slinkydeveloper):
Opened the PR here: [https://github.com/apache/flink-statefun/pull/110
]I've implemented a solution that uses both endpoint and uds field, to specify
both path and socket file, let me know your thoughts about that
> 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
> Labels: pull-request-available
> 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)
