[GitHub] [shardingsphere-elasticjob] TeslaCN commented on issue #2131: Curator event thread blocked by Quartz when frequently triggering one-off job

[GitBox]

TeslaCN commented on issue #2131:
URL: 
https://github.com/apache/shardingsphere-elasticjob/issues/2131#issuecomment-1279944704

   I found this was not caused by deadlock. Maybe infinity loop occurred in 
Quartz.
   
   There are many tasks were not consumed.
   <img width="1680" alt="image" 
src="https://user-images.githubusercontent.com/20503072/196031122-a5aa04a0-86e4-4c96-9d69-276b97c87b74.png";>
   
   The mod count in TreeSet instance was keep changing.
   
   <img width="1561" alt="image" 
src="https://user-images.githubusercontent.com/20503072/196031203-1a4ed5ee-4daf-4eeb-aedc-73b9aafbb501.png";>
   
   <img width="1552" alt="image" 
src="https://user-images.githubusercontent.com/20503072/196031208-726497fe-90c8-4ceb-b2b5-931a2f9f70c9.png";>
   
   <img width="1549" alt="image" 
src="https://user-images.githubusercontent.com/20503072/196031211-dbb060ec-c46c-40bb-a6bc-d2645fdec394.png";>
   
   The Quartz thread was keep consuming CPU.
   
   <img width="1680" alt="image" 
src="https://user-images.githubusercontent.com/20503072/196031247-69390606-81c6-4335-b2bf-e531abe40162.png";>
   
   


-- 
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: notifications-unsubscr...@shardingsphere.apache.org

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