[ https://issues.apache.org/jira/browse/KUDU-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917942#comment-16917942 ]
Todd Lipcon commented on KUDU-2932: ----------------------------------- bq. kudu doesn't support data locality What do you mean by that? I think it _does_ support data locality (Impala/Spark tasks are put on the same machine as the kudu tserver, usually). bq. I think it's useful to support unix domain socket for computing engine(impala/spark) and storage engine(kudu) mixed deployment scenarios. We actually did some work on this many years ago, and also tried using shared memory. The domain socket seemed to have a small improvement, but shared memory didn't seem to be worth the benefit. You can find some of the really old patches on gerrit: https://gerrit.cloudera.org/#/c/957/ > Unix domain socket could speed up data transmission > --------------------------------------------------- > > Key: KUDU-2932 > URL: https://issues.apache.org/jira/browse/KUDU-2932 > Project: Kudu > Issue Type: New Feature > Reporter: HeLifu > Priority: Major > > Right now, kudu doesn't support data locality. So, I think it's useful to > support unix domain socket for computing engine(impala/spark) and storage > engine(kudu) mixed deployment scenarios. -- This message was sent by Atlassian Jira (v8.3.2#803003)