[jira] [Commented] (TUBEMQ-253) tube-consumer fetch-worker cpu used too high
[ https://issues.apache.org/jira/browse/TUBEMQ-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151698#comment-17151698 ] yupili commented on TUBEMQ-253: --- ok, no exception now! thanks > tube-consumer fetch-worker cpu used too high > > > Key: TUBEMQ-253 > URL: https://issues.apache.org/jira/browse/TUBEMQ-253 > Project: Apache TubeMQ > Issue Type: Bug > Components: Client >Reporter: yupili >Assignee: Guocheng Zhang >Priority: Major > Labels: pull-request-available > Attachments: screenshot-1.png > > Time Spent: 20m > Remaining Estimate: 0h > > java tube-client sdk 0.3.0 > start 4 fetch-worker which are all runnable status and cause cpu occupy 390+! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TUBEMQ-253) tube-consumer fetch-worker cpu used too high
[ https://issues.apache.org/jira/browse/TUBEMQ-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151350#comment-17151350 ] Guocheng Zhang commented on TUBEMQ-253: --- [~yupili], has the problem been resolved? If there is no problem, I will close this issue > tube-consumer fetch-worker cpu used too high > > > Key: TUBEMQ-253 > URL: https://issues.apache.org/jira/browse/TUBEMQ-253 > Project: Apache TubeMQ > Issue Type: Bug > Components: Client >Reporter: yupili >Assignee: Guocheng Zhang >Priority: Major > Labels: pull-request-available > Attachments: screenshot-1.png > > Time Spent: 20m > Remaining Estimate: 0h > > java tube-client sdk 0.3.0 > start 4 fetch-worker which are all runnable status and cause cpu occupy 390+! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TUBEMQ-253) tube-consumer fetch-worker cpu used too high
[ https://issues.apache.org/jira/browse/TUBEMQ-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17147177#comment-17147177 ] ASF subversion and git services commented on TUBEMQ-253: Commit cfbca3e84b6515873e105057aa69c3d2b43caec6 in incubator-tubemq's branch refs/heads/master from gosonzhang [ https://gitbox.apache.org/repos/asf?p=incubator-tubemq.git;h=cfbca3e ] [TUBEMQ-253] tube-consumer fetch-worker cpu used too high (#173) * [TUBEMQ-253] tube-consumer fetch-worker cpu used too high > tube-consumer fetch-worker cpu used too high > > > Key: TUBEMQ-253 > URL: https://issues.apache.org/jira/browse/TUBEMQ-253 > Project: Apache TubeMQ > Issue Type: Bug > Components: Client >Reporter: yupili >Assignee: Guocheng Zhang >Priority: Major > Labels: pull-request-available > Attachments: screenshot-1.png > > Time Spent: 10m > Remaining Estimate: 0h > > java tube-client sdk 0.3.0 > start 4 fetch-worker which are all runnable status and cause cpu occupy 390+! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TUBEMQ-253) tube-consumer fetch-worker cpu used too high
[ https://issues.apache.org/jira/browse/TUBEMQ-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17147178#comment-17147178 ] ASF subversion and git services commented on TUBEMQ-253: Commit cfbca3e84b6515873e105057aa69c3d2b43caec6 in incubator-tubemq's branch refs/heads/master from gosonzhang [ https://gitbox.apache.org/repos/asf?p=incubator-tubemq.git;h=cfbca3e ] [TUBEMQ-253] tube-consumer fetch-worker cpu used too high (#173) * [TUBEMQ-253] tube-consumer fetch-worker cpu used too high > tube-consumer fetch-worker cpu used too high > > > Key: TUBEMQ-253 > URL: https://issues.apache.org/jira/browse/TUBEMQ-253 > Project: Apache TubeMQ > Issue Type: Bug > Components: Client >Reporter: yupili >Assignee: Guocheng Zhang >Priority: Major > Labels: pull-request-available > Attachments: screenshot-1.png > > Time Spent: 10m > Remaining Estimate: 0h > > java tube-client sdk 0.3.0 > start 4 fetch-worker which are all runnable status and cause cpu occupy 390+! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TUBEMQ-253) tube-consumer fetch-worker cpu used too high
[ https://issues.apache.org/jira/browse/TUBEMQ-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17143825#comment-17143825 ] Guocheng Zhang commented on TUBEMQ-253: --- This problem should be introduced when the TUBEMQ-149 problem was modified: after the indexPartition object was changed from BlockingQueue to ConcurrentLinkedQueue, in the pushSelect method, after the previous take method was not provided, the interface was changed to the poll mode, which caused the problem. Some businesses use the pull mode, so the problem is not discovered in time: !screenshot-1.png! > tube-consumer fetch-worker cpu used too high > > > Key: TUBEMQ-253 > URL: https://issues.apache.org/jira/browse/TUBEMQ-253 > Project: Apache TubeMQ > Issue Type: Bug > Components: Client >Reporter: yupili >Assignee: Guocheng Zhang >Priority: Major > Labels: pull-request-available > Attachments: screenshot-1.png > > Time Spent: 10m > Remaining Estimate: 0h > > java tube-client sdk 0.3.0 > start 4 fetch-worker which are all runnable status and cause cpu occupy 390+! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TUBEMQ-253) tube-consumer fetch-worker cpu used too high
[ https://issues.apache.org/jira/browse/TUBEMQ-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17143615#comment-17143615 ] Guocheng Zhang commented on TUBEMQ-253: --- I get it, thanks! > tube-consumer fetch-worker cpu used too high > > > Key: TUBEMQ-253 > URL: https://issues.apache.org/jira/browse/TUBEMQ-253 > Project: Apache TubeMQ > Issue Type: Bug > Components: Client >Reporter: yupili >Priority: Major > > java tube-client sdk 3.8.6 > start 4 fetch-worker which are all runnable status and cause cpu occupy 390+! -- This message was sent by Atlassian Jira (v8.3.4#803005)
