[ https://issues.apache.org/jira/browse/AMQ-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-5846. ----------------------------- Resolution: Not A Problem Given the configuration this appears to be a non-issue, failover and network reconnection logic going to kick in here and cause a spike which can be controlled by configuring delay and backoff on the failover bits. > High cpu usage if using masterslave discovery in network brokers > ---------------------------------------------------------------- > > Key: AMQ-5846 > URL: https://issues.apache.org/jira/browse/AMQ-5846 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.11.1 > Reporter: duff qiu > > I setup a network brokers with 2 nodes (A, and B) > In the config, the A and B use masterslave discovery. > If I start A first, and then start B, I found that the cpu usaging in the > machine running A is very high (~100). But The B doens't like that because B > can connect to A at the first time. > I try to use the static:failover way, then the problem is the same > (static:failover:()?randomize=false&maxReconnectAttempts=0) > But I try to remove the "maxReconnectAttempts=0' or set the value more than > 10 , the issue disapeared. > I think there are some issues on the network transfer impl how to handle the > maxReconnectAttempts -- This message was sent by Atlassian JIRA (v6.3.4#6332)