You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pinot.apache.org by GitBox <gi...@apache.org> on 2022/07/13 15:59:42 UTC

[GitHub] [pinot] mcvsubbu commented on pull request #9043: Task generator debug api

mcvsubbu commented on PR #9043:
URL: https://github.com/apache/pinot/pull/9043#issuecomment-1183402833

   In general, use alerts and logs to debug problems. If you really want to persist problem state over time, the approach I prefer is to sprinkle code all over pinot (similar to metrics) that emit some events to a stream underneath. This stream can be fielded by Pinot into a pinot table, and used to debug the pinot cluster via queries: "How many minion jobs failed last week vs previous week?", "Which table has the most errors loading a segment?" etc.
   
   @npawar, @kishoreg  and I have discussed before about introducing new znodes for new features (let alone debugging), and came to the conclusion that it is hard to clean up things afterwards. 
   
   Anyways, since we are concluding to go with keeping stuff in memory and using APIs to debug, I suggest you put out an issue and add some interface definitions there (or a doc if you choose). 
   
   Please close thsis PR and begin a new one


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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