Shaofeng,
OK, Thanks for your reply!

在 2015年10月10日 12:25, Shi, Shaofeng 写道:
This is by design; The GC step is not mandatory, its failure shouldn¹t
block prompting the new segment to ³ready²; In our case, some job¹s GC
step may take tens of minutes to finish, if moves it ahead of
³updateCubeInfoXXStep², it will delay the next build/merge job for tens of
minutes, which is not expected;

On 10/10/15, 12:03 PM, "Xiaoyu Wang" <[email protected]> wrote:

Hi all!
I think the "GarbageCollectionStep" should be before
"UpdateCubeInfoAfterBuildStep"
when "GarbageCollectionStep" throw exception,the segment status is
ready! but the job status is error.
Any other suggestions?
If not, I will create a jira and submit a patch!

Thanks!


Reply via email to