locationtech / locationtech/geomesa

add-attribute-index does not appear to launch its M/R job via yarn

Open
#5,504 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
1.5k
Forks
446
Avg merge
1d 8h
Merged PRs (30d)
31

Description

add-attribute-index does not appear to launch its M/R job via yarn

The add-attribute-index command in the geomesa commandline tool does start the map-reduce job (AttributeIndexJob), but appears to run the job locally rather than submitting it via Yarn. This is the case despite the fact that the environment is properly configured to submit jobs via Yarn.

To add an attribute index for a test set of ~130M records on tcloud, this took about 8 hours. In contrast, submitting the job manually via the yarn commandline tool did submit the job to the cluster via yarn, and ultimately took less time (~2 hours) to complete.


Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-1661

Key: GEOMESA-1661
Type: Bug
Priority: Major
Status: To Do
Resolution: Unresolved
Assignee: Matt Zimmerman
Reporter: Matt Zimmerman
Created: Thu, 2 Feb 2017 15:18:52 -0500
Updated: Thu, 2 Feb 2017 15:18:52 -0500

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the geomesa commandline tool's add-attribute-index command and trace how it launches AttributeIndexJob. Compare that path with the manual yarn command-line submission described in the issue. Done means the command submits the MapReduce job through YARN when the environment is configured for it, rather than running locally.

Written by the indexing model from the issue text.

Assessment

Tech stack
hadoop, scala
Domain
cli, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.