This message was deleted.
# troubleshooting
s
This message was deleted.
n
@Gian Merlino would you have any suggestions/advice here?
a
@NKorade, a couple of thoughts. Is the supervisor stuck reading non-existent offsets on select partitions? Yeah, currently the supervisor reset API clears everything from the metadata table pertaining to a supervisor. IMO, itโ€™d be nice to add support to reset metadata for a subset of partitions (would be less risky as well). In the mean time, I wonder if you can edit the metadata table for the supervisor in question? Definitely exercise caution while doing this especially if this is a production system ๐Ÿ™‚
n
Thanks @Abhishek Balaji Radhakrishnan Yes, the consumers stuck with negative offset lag were due to the non-existent offsets in the partitions. We looked into updating the offsets in the metadata table. However, it is stored there in encoded form (presumably, of a json). So it's bit involved and unsafe and we decided to not go that route. Thanks though.
a
@NKorade got it, please feel free to open a GitHub issue/proposal to extend the supervisor reset API to reset specific partitions. Seems like a common and useful functionality to have in Druid ๐Ÿ‘