locationtech / locationtech/geomesa
Distributed HBase ingest fails when using Keberos
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Distributed HBase ingest fails when using Keberos
This may just be a kerberos configuration issue, or may require some additional code to pass around the tickets correctly.
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2604
Key: GEOMESA-2604
Type: Bug
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Fri, 19 Apr 2019 09:04:50 -0400
Updated: Tue, 14 Apr 2020 15:48:35 -0400
Comments:
557058:48912df4-0004-4f90-9915-db26684ec006 (Tue, 14 Apr 2020 15:35:15 -0400):
Emilio Lahr-Vivaz did any of our looking at HBase turn up anything relative to this?
Also, should we prioritize this?
557058:da7f6dfa-f0a1-468b-aec5-2cb61273feb5 (Tue, 14 Apr 2020 15:48:35 -0400):
I don't think we've found anything relevant to this. I don't think it's necessarily a priority right now, but might be good to have in our back pocket so we could go ahead and figure it out if we have time.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing distributed HBase ingest with Kerberos enabled and checking the Kerberos configuration and ticket handling. Determine whether the failure is configuration-related or requires code to pass tickets correctly. Done means distributed ingest succeeds under Kerberos authentication.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100