You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2020/03/27 17:00:12 UTC

[GitHub] [druid] jihoonson commented on issue #9184: New properties in `DruidCoordinatorConfig` to retain a flexible duration for stale pendingSegments

jihoonson commented on issue #9184: New properties in `DruidCoordinatorConfig` to retain a flexible duration for stale pendingSegments
URL: https://github.com/apache/druid/pull/9184#issuecomment-605113377
 
 
   Hi @zihengCat, sorry for the late review. Would you tell me more about the motivation of this PR? Currently, the stale pendingSegments are computed by `created time of most recent running task (or complete task if there is no running task) - P1D`. I thought this is safe because 1) when a task is already finished, it's safe to delete all pendingSegments created by that task and 2) when a task is running, its pendingSegments is never deleted by the coordinator. Is there a use case where a flexible retention period is required?

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org