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/01/20 18:52:09 UTC
[GitHub] [druid] suneet-s commented on issue #9221: Previous sequenceNumber
[344019] is no longer available for partition [0]
suneet-s commented on issue #9221: Previous sequenceNumber [344019] is no longer available for partition [0]
URL: https://github.com/apache/druid/issues/9221#issuecomment-576394119
@liujunhui I'd like to try and help with this issue, but I don't understand the problem. Can you describe when this exception happened,, what changed in your environment if anything. Was this a new supervisor job that just started running? Was this an already running job, that just started failing?
I've seen this happen for me when the ingestion spec has been failing for a while. I've resolved that by fixing the ingestion spec and resetting the supervisor as the error message suggests
----------------------------------------------------------------
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