-
Notifications
You must be signed in to change notification settings - Fork 559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No reservable CPU for Thread[affinity.jupiter-provider-processor #60
Comments
这个日志没问题, 不影响什么, 有几个线程无法绑定到cpu上, 核 不够 |
报了这个错后,客户端也死掉了 TimeoutException{status=SERVER_TIMEOUT}
at org.jupiter.rpc.consumer.future.DefaultInvokeFuture.setException(DefaultInvokeFuture.java:177)
at org.jupiter.rpc.consumer.future.DefaultInvokeFuture.doReceived(DefaultInvokeFuture.java:163)
at org.jupiter.rpc.consumer.future.DefaultInvokeFuture.fakeReceived(DefaultInvokeFuture.java:235)
at org.jupiter.rpc.consumer.future.DefaultInvokeFuture$TimeoutScanner.process(DefaultInvokeFuture.java:277)
at org.jupiter.rpc.consumer.future.DefaultInvokeFuture$TimeoutScanner.run(DefaultInvokeFuture.java:251)
at java.base/java.lang.Thread.run(Thread.java:844) |
奇怪了 你github是最新代码吗? 下刚下载最新代码试了下没问题呀 |
是不是因为我把 callerRuns 这行给去掉了导致的? |
net.openhft.affinity.LockInventory日志的出现的确是因为callerRuns 这行去掉导致, 去掉callerRuns这行会新起一个线程池, 然后尝试将线程绑定到cpu的每个核心上 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: