Skip to content
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

Closed
hank-whu opened this issue Mar 22, 2018 · 5 comments
Closed

No reservable CPU for Thread[affinity.jupiter-provider-processor #60

hank-whu opened this issue Mar 22, 2018 · 5 comments

Comments

@hank-whu
Copy link

hank-whu commented Mar 22, 2018

17:22:39.286 [affinity.jupiter-provider-processor #1] WARN  net.openhft.affinity.LockInventory - Unable to acquire lock on CPU 6 for thread Thread[affinity.jupiter-provider-processor #1,5,main], trying to find another CPU
17:22:39.297 [affinity.jupiter-provider-processor #2] WARN  net.openhft.affinity.LockInventory - Unable to acquire lock on CPU 5 for thread Thread[affinity.jupiter-provider-processor #2,5,main], trying to find another CPU
17:22:39.299 [affinity.jupiter-provider-processor #3] WARN  net.openhft.affinity.LockInventory - Unable to acquire lock on CPU 4 for thread Thread[affinity.jupiter-provider-processor #3,5,main], trying to find another CPU
17:22:39.301 [affinity.jupiter-provider-processor #5] WARN  net.openhft.affinity.LockInventory - Unable to acquire lock on CPU 3 for thread Thread[affinity.jupiter-provider-processor #5,5,main], trying to find another CPU
17:22:39.311 [affinity.jupiter-provider-processor #4] WARN  net.openhft.affinity.LockInventory - Unable to acquire lock on CPU 2 for thread Thread[affinity.jupiter-provider-processor #4,5,main], trying to find another CPU
17:22:39.323 [affinity.jupiter-provider-processor #7] WARN  net.openhft.affinity.LockInventory - Unable to acquire lock on CPU 1 for thread Thread[affinity.jupiter-provider-processor #7,5,main], trying to find another CPU
17:22:39.326 [affinity.jupiter-provider-processor #7] WARN  net.openhft.affinity.LockInventory - No reservable CPU for Thread[affinity.jupiter-provider-processor #7,5,main]
17:22:39.328 [affinity.jupiter-provider-processor #6] WARN  net.openhft.affinity.LockInventory - Unable to acquire lock on CPU 1 for thread Thread[affinity.jupiter-provider-processor #6,5,main], trying to find another CPU
17:22:39.330 [affinity.jupiter-provider-processor #6] WARN  net.openhft.affinity.LockInventory - No reservable CPU for Thread[affinity.jupiter-provider-processor #6,5,main]
@fengjiachun
Copy link
Owner

这个日志没问题, 不影响什么, 有几个线程无法绑定到cpu上, 核 不够

@hank-whu
Copy link
Author

报了这个错后,客户端也死掉了

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)

@fengjiachun
Copy link
Owner

奇怪了 你github是最新代码吗? 下刚下载最新代码试了下没问题呀

@hank-whu
Copy link
Author

是不是因为我把 callerRuns 这行给去掉了导致的?

@fengjiachun
Copy link
Owner

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants