Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws: error: The step type spark_application is not supported. #7970

Closed
2 tasks
hongbo-miao opened this issue Jun 13, 2023 · 7 comments
Closed
2 tasks

aws: error: The step type spark_application is not supported. #7970

hongbo-miao opened this issue Jun 13, 2023 · 7 comments
Assignees
Labels
emr feature-request A feature should be added or improved. p3 This is a minor priority issue

Comments

@hongbo-miao
Copy link

hongbo-miao commented Jun 13, 2023

Describe the feature

I have an EMR cluster with step "Spark application" which created from EMR UI.

image

Now I am hoping to create it by CLI.

I got the command by clicking "View command for cloning cluster" button

image

It gives me command like

aws emr create-cluster \
    # ...
    --steps '[{"Name":"xxx","ActionOnFailure":"TERMINATE_CLUSTER","Jar":"command-runner.jar","Properties":"","Args":["spark-submit","--deploy-mode","cluster","s3://my-bucket/MySparkApp-assembly-1.0.jar"],"Type":"SPARK_APPLICATION"}]'

However, when I run this command, I got error

aws: error: The step type spark_application is not supported.

Based on CLI document, currently --steps only supports

"Type": "CUSTOM_JAR"|"STREAMING"|"HIVE"|"PIG"|"IMPALA"

It would be great to support SPARK_APPLICATION, thanks! 😃

Use Case

It would be convenient to use CLI to create EMR cluster with step "Spark application".

Proposed Solution

No response

Other Information

No response

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change

CLI version used

aws-cli/2.8.12 Python/3.9.11 Darwin/22.5.0 exe/x86_64 prompt/off

Environment details (OS name and version, etc.)

macOS

@hongbo-miao hongbo-miao added feature-request A feature should be added or improved. needs-triage This issue or PR still needs to be triaged. labels Jun 13, 2023
@RyanFitzSimmonsAK RyanFitzSimmonsAK self-assigned this Jun 13, 2023
@RyanFitzSimmonsAK RyanFitzSimmonsAK added emr p3 This is a minor priority issue investigating This issue is being investigated and/or work is in progress to resolve the issue. and removed needs-triage This issue or PR still needs to be triaged. labels Jun 13, 2023
@RyanFitzSimmonsAK
Copy link
Contributor

Hi @hongbo-miao, thanks for reaching out. In the developer guide for EMR, it looks like the examples use Type=Spark rather than SPARK_APPLICATION. Could you try formatting it similarly to the examples, and letting me know if that works? Thanks!

@RyanFitzSimmonsAK RyanFitzSimmonsAK added response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. and removed investigating This issue is being investigated and/or work is in progress to resolve the issue. labels Jun 13, 2023
@hongbo-miao
Copy link
Author

hongbo-miao commented Jun 13, 2023

Hi @RyanFitzSimmonsAK hmm the error is something else now

An error occurred (ValidationException) when calling the RunJobFlow operation: An instance group must have at least one instance.

Although this new error also should not exist as I exported, when I rerun, it should create same EMR cluster.

Back to this issue, I think SPARK works!

I guess just need

Feel free to use this ticket to track, or create other tickets and close this one. Thanks! 😃

@github-actions github-actions bot removed the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Jun 14, 2023
@RyanFitzSimmonsAK
Copy link
Contributor

RyanFitzSimmonsAK commented Jun 14, 2023

Back to this issue, I think SPARK works!

Glad to hear it. Did you change any other part of your command? And do you need help with the new error, or were you able to get this feature working?

@RyanFitzSimmonsAK RyanFitzSimmonsAK added the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Jun 14, 2023
@hongbo-miao
Copy link
Author

That is all changes I have. 😃
The new issue is a different one, I will create a new ticket later when I got time, thanks!

@github-actions github-actions bot removed the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Jun 14, 2023
@RyanFitzSimmonsAK
Copy link
Contributor

I'd like to make sure we get it working before I raise the issue with the service team about the button in the console. Let's follow up in this issue, and I'll bring everything up with them once we've figured out what all needs to be fixed.

@hongbo-miao
Copy link
Author

hongbo-miao commented Jun 14, 2023

Sounds good! I will provide more info regarding the new error. Hopefully this week!

@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
emr feature-request A feature should be added or improved. p3 This is a minor priority issue
Projects
None yet
Development

No branches or pull requests

2 participants