Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

All spark-submit are routed to the same yarn queue

avatar
Reader

Hi,

we are using HDP 2.6.5 and are facing an issue for some days now.
Yesterday we realized that when we issue a spark-submit command, it is sent to the same yarn queue even if we specify --queue param.

Had anybody ever come to that issue?

Spark version is 2.3.0.

Regards

3 REPLIES 3

avatar
Master Collaborator

HI @Samie 

 

Please attach the spark application and event logs to check the queue name. The easiest way to check the spark application is by running spark pi example.

 

spark-submit \
  --class org.apache.spark.examples.SparkPi \
  --queue <queue_name> \
  --master yarn \
  --deploy-mode cluster \
  --num-executors 1 \
  --driver-memory 512m \
  --executor-memory 512m \
  --executor-cores 1 \
  /usr/hdp/current/spark2-client/examples/jars/spark-examples_*.jar 10

 

Spark on YARN only:
--queue QUEUE_NAME The YARN queue to submit to (Default: "default").

 

avatar
Master Collaborator

Hi @Samie 

Is there any update on your testing?

avatar
Community Manager

@Samie, Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  



Regards,

Vidya Sargur,
Community Manager


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Learn more about the Cloudera Community: