FrankChen021 opened a new issue #10508:
URL: https://github.com/apache/druid/issues/10508


   
   ### Affected Version
   
   It's been verified on 0.16 and 0.19, and I think 0.17 and 0.18 are also 
affected.
   
   ### Description
   
   Steps to reproduce this problem:
   1. start a realtime ingestion task for one data source
   2. issue a kill task for the same data source through menu item "Delete 
unused segments" on the web-console UI
   
   The kill task is created successfully but its status is always WAITING even 
after the ingestion task for current segment completes and a new ingestion task 
starts for another new segment.
   
   
![image](https://user-images.githubusercontent.com/6525742/95814578-48cd7780-0d4d-11eb-892c-a93f99c561df.png)
   
   From the image above, we can see:
   1.  ingestion task started at 02:55
   2. kill task started at 02:26
   3. an hour(segment granularity) later, ingestion task finished at about 
03:55, and a new task started at 03:55
   
   There's no chance for the kill task to be scheduled, and its status is 
always WAITING.
   
   ### Analysis
   
   When launching a kill-task from web console, a kill-task request with 
`interval` ranging from year 1000 to year 3000 is sent to druid backend 
service. While there's a running ingestion task which holds time chunk lock, 
this kill request couldn't obtain the time chunk lock because the given 
interval is too large.
   
   To solve this, I think there're two ways to solve it as follows, both of 
which requires some modifications on web console
   
   1. do it as the way 'Mark as unused segment by interval' does, ask for a 
given interval from user instead of using year 3000 as the end interval
   or 
   2. set `forceTimeChunkLock` of `context` parameter to `false` in the kill 
task request


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to