You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2022/10/27 23:19:32 UTC
[GitHub] [accumulo] keith-turner opened a new issue, #3053: ThreadPool logging is a large percentage of tserver logs
keith-turner opened a new issue, #3053:
URL: https://github.com/apache/accumulo/issues/3053
While running bulk RW test against 2.1.0-SNAPSHOT I was looking in the tserver logs and noticed a lot of messages related to thread pools. I did some simple analysis and found 61% of lines i the logs were related to ThreadPools. This makes me wonder if those messages should be adjusted from debug to trace.
```
accumulo-2.1.0-SNAPSHOT/logs$ cp tserver1_dev-uk.log copy.log
accumulo-2.1.0-SNAPSHOT/logs$ wc copy.log
2345141 33482620 423666089 copy.log
accumulo-2.1.0-SNAPSHOT/logs$ grep ThreadPools copy.log | wc
1434601 21997471 246272425
accumulo-2.1.0-SNAPSHOT/logs$ grep ThreadPools copy.log | tail
2022-10-27T23:11:47,271 [threads.ThreadPools] DEBUG: Creating ThreadPoolExecutor for BinMutations with 1 core threads and 1 max threads 180000 MILLISECONDS timeout
2022-10-27T23:11:47,294 [threads.ThreadPools] DEBUG: Creating ScheduledThreadPoolExecutor for GeneralExecutor with 1 threads
2022-10-27T23:11:47,295 [threads.ThreadPools] DEBUG: Creating ThreadPoolExecutor for org.apache.accumulo.core.clientImpl.TabletServerBatchWriter$MutationWriter with 3 core threads and 3 max threads 180000 MILLISECONDS timeout
2022-10-27T23:11:47,295 [threads.ThreadPools] DEBUG: Creating ThreadPoolExecutor for BinMutations with 1 core threads and 1 max threads 180000 MILLISECONDS timeout
2022-10-27T23:11:47,305 [threads.ThreadPools] DEBUG: Creating ScheduledThreadPoolExecutor for GeneralExecutor with 1 threads
2022-10-27T23:11:47,306 [threads.ThreadPools] DEBUG: Creating ThreadPoolExecutor for org.apache.accumulo.core.clientImpl.TabletServerBatchWriter$MutationWriter with 3 core threads and 3 max threads 180000 MILLISECONDS timeout
2022-10-27T23:11:47,306 [threads.ThreadPools] DEBUG: Creating ThreadPoolExecutor for BinMutations with 1 core threads and 1 max threads 180000 MILLISECONDS timeout
2022-10-27T23:11:47,317 [threads.ThreadPools] DEBUG: Creating ScheduledThreadPoolExecutor for GeneralExecutor with 1 threads
2022-10-27T23:11:47,317 [threads.ThreadPools] DEBUG: Creating ThreadPoolExecutor for org.apache.accumulo.core.clientImpl.TabletServerBatchWriter$MutationWriter with 3 core threads and 3 max threads 180000 MILLISECONDS timeout
2022-10-27T23:11:47,317 [threads.ThreadPools] DEBUG: Creating ThreadPoolExecutor for BinMutations with 1 core threads and 1 max threads 180000 MILLISECONDS timeout
```
--
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-unsubscribe@accumulo.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [accumulo] EdColeman commented on issue #3053: ThreadPool logging is a large percentage of tserver logs
Posted by GitBox <gi...@apache.org>.
EdColeman commented on issue #3053:
URL: https://github.com/apache/accumulo/issues/3053#issuecomment-1294870236
I agree that the thread pool creation is noisy and does not seem to add much user value and we should look at bumping the log level down to trace. However, for development - is this pointing to places where there may inefficiencies where we creating thread pools where we could be reusing one that already exists - could be a separate issue to investigate.
(this is also true for the manager log)
--
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-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [accumulo] EdColeman commented on issue #3053: ThreadPool logging is a large percentage of tserver logs
Posted by GitBox <gi...@apache.org>.
EdColeman commented on issue #3053:
URL: https://github.com/apache/accumulo/issues/3053#issuecomment-1298904564
resolved with #3061
--
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-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [accumulo] EdColeman closed issue #3053: ThreadPool logging is a large percentage of tserver logs
Posted by GitBox <gi...@apache.org>.
EdColeman closed issue #3053: ThreadPool logging is a large percentage of tserver logs
URL: https://github.com/apache/accumulo/issues/3053
--
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-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org