[GitHub] [hadoop-ozone] avijayanhwx commented on pull request #1518: HDDS-4386: Each EndpointStateMachine uses its own thread pool to talk with SCM/Recon
avijayanhwx commented on pull request #1518: URL: https://github.com/apache/hadoop-ozone/pull/1518#issuecomment-716920861 > @GlenGeng Thanks for fixing this issue. > > Is there a JIRA created for the Recon slowness issue? > > Also, irrespective of whether there is a slow SCM or Recon, the DN should not submit a request to an endpoint if there is a pending request to that endpoint. Is that not true currently? Even if there are 2 threads in the same thread pool (1 for SCM and 1 for Recon), then a slow Recon should not affect SCM reports. Thanks for the explanation @GlenGeng. IMO, it is good to have Recon and SCM use different thread pools. 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: us...@infra.apache.org - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[GitHub] [hadoop-ozone] avijayanhwx commented on pull request #1518: HDDS-4386: Each EndpointStateMachine uses its own thread pool to talk with SCM/Recon
avijayanhwx commented on pull request #1518: URL: https://github.com/apache/hadoop-ozone/pull/1518#issuecomment-715582860 @GlenGeng Thanks for fixing this issue. Is there a JIRA created for the Recon slowness issue? Also, irrespective of whether there is a slow SCM or Recon, the DN should not submit a request to an endpoint if there is a pending request to that endpoint. Is that not true currently? Even if there are 2 threads in the same thread pool (1 for SCM and 1 for Recon), then a slow Recon should not affect SCM reports. 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: us...@infra.apache.org - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
