You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (JIRA)" <ji...@apache.org> on 2019/01/23 17:12:00 UTC
[jira] [Commented] (KUDU-2666) kudu spark intergration taskRead
Locality Level is RACK_LOCAL
[ https://issues.apache.org/jira/browse/KUDU-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750240#comment-16750240 ]
Grant Henke commented on KUDU-2666:
-----------------------------------
I looked at recent spark runs I have done and have seen NODE_LOCAL tasks.
Are you sure that your spark executor nodes are the same as your kudu nodes in your cluster?
Adjusting the `spark.locality.wait` configurations could also help improve locality: http://spark.apache.org/docs/latest/configuration.html#scheduling
> kudu spark intergration taskRead Locality Level is RACK_LOCAL
> -------------------------------------------------------------
>
> Key: KUDU-2666
> URL: https://issues.apache.org/jira/browse/KUDU-2666
> Project: Kudu
> Issue Type: Improvement
> Components: spark
> Affects Versions: 1.8.0
> Reporter: wkhapy123
> Priority: Major
> Attachments: 1.png, 2.png
>
>
> spark version 2.3.0
> MyKuduCluster is 3 node
> each tablet 3 replicas.
> when I use sparkcontext read kudu table, task Locality Level is RACK_LOCAL。
> How could it be Node_LOCAL?
> query like this
> spark.sqlContext.sql(s"select * from tablea where event_day>=1546185600 and tenant_id=1 and channel_id='15850513729' limit 1 ").collect
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)