apache / apache/druid

Task can't be stopped if import task failed

Open
#8,574 2 comments 2 reactions 0 assignees View on GitHub
Area - Batch Ingestion Bug
Dominant language
Java
Stars
14.1k
Forks
3.8k
Avg merge
2d 58m
Merged PRs (30d)
233

Description

Please provide a detailed title (e.g. "Broker crashes when using TopN query with Bound filter" instead of just "Broker crashes").

### Affected Version

druid-0.15.0

### Description

The druid-0.15.0 can not stop offline imort task in kerberos environment. If there is no data,and
task will failed and it will gracefully stop task which launch new task to connect yarn ,but kerberos authorize failed like:
2019-09-05T15:07:16,972 WARN [pool-43-thread-2] org.apache.hadoop.ipc.Client - Exception encountered while connecting to the server : javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]
2019-09-05T15:07:46,990 WARN [pool-43-thread-2] org.apache.hadoop.ipc.Client - Exception encountered while connecting to the server : javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]
2019-09-05T15:08:17,005 WARN [pool-43-thread-2] org.apache.hadoop.ipc.Client - Exception encountered while connecting to the server : javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]
....

Contributor guide

Open the contributing guide

Research direction

The report concerns stopping an offline import task after failure while connecting to YARN in a Kerberos environment; no source files, tests, or entry points are named. Start by tracing the failed-task shutdown path and its Hadoop connection handling, then verify that a failed import can stop gracefully when Kerberos credentials are unavailable.

Written by the indexing model from the issue text.

Assessment

Tech stack
hadoop, java
Domain
backend, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.