You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ nomad status
ID Type Priority Status Submit Date
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa service 50 pending 08/30/17 19:14:47 JST
2. run nomad status ${LONG_JOBID} and gets following error
$ nomad status aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Error querying search with id: "Unexpected response code: 500 (alloc lookup failed: index error: Invalid UUID length. UUID have 36 characters; got 70)"
Additional info
After nomad status started using /v1/search endpoint, this issue was included. Previously nomad status used /v1/jobs/prefix with GET(client.query), and it was no problem. So, nomad job status <LONG_JOB_ID> could be a workaround for this issue.
More than 36 characters sounds crazy, but spark job automatically often assign such long job ID.
$ spark-submit --class org.apache.spark.examples.JavaSparkPi --master nomad --deploy-mode cluster --conf spark.executor.instances=4 --conf spark.nomad.sparkDistribution=https://s3.amazonaws.com/nomad-spark/spark-2.1.0-bin-nomad.tgz https://s3.amazonaws.com/nomad-spark/spark-examples_2.11-2.1.0-SNAPSHOT.jar 100
$ nomad status
ID Type Priority Status Submit Date
org.apache.spark.examples.JavaSparkPi-2017-08-30T07:51:04.567Z batch 40 pending 08/30/17 16:51:05 JST
$ nomad status org.apache.spark.examples.JavaSparkPi-2017-08-30T07:51:04.567Z
Error querying search with id: "Unexpected response code: 500 (alloc lookup failed: index error: Invalid UUID length. UUID have 36 characters; got 58)"
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Nomad version
Output from
nomad version
commit: aa9bb33
Operating system and Environment details
Issue
Reproduction steps
1. create job with ${LONG_JOBID} > 36.
(eg.)
2. run nomad status ${LONG_JOBID} and gets following error
Additional info
After
nomad status
started using/v1/search
endpoint, this issue was included. Previouslynomad status
used/v1/jobs/prefix
with GET(client.query
), and it was no problem. So,nomad job status <LONG_JOB_ID>
could be a workaround for this issue.More than 36 characters sounds crazy, but spark job automatically often assign such long job ID.
The text was updated successfully, but these errors were encountered: