[GitHub] sisyphsu edited a comment on issue #363: when consumer start，the order of “pullMessage” and “rebalance notify brokers” is not strongly controlled，lead to CODE25

[GitBox <gi...@apache.org>]

sisyphsu edited a comment on issue #363: when consumer start，the order of “pullMessage” and “rebalance notify brokers” is not strongly controlled，lead to CODE25
URL: https://github.com/apache/rocketmq/issues/363#issuecomment-422305056
 
 
   **It's wired.**
   When I changed the logger of `RocketmqClient` to `slf4j`, and changed the `level` to `WARN`, 
   like `<logger name="RocketmqClient" level="WARN"/>`, Everything became chaos.
   If the `level` is `INFO`, everything will be OK.
   
   I don't know why, but I guess the issue may be concurrent problem.
   When `INFO` log was disabled, possibly some thread run faster, likely 1ms, which make this happen:
   ```
   if (subscriptionData.getSubVersion() < requestHeader.getSubVersion()) {
       log.warn("The broker's subscription is not latest, group: {} {}", requestHeader.getConsumerGroup(),
                       subscriptionData.getSubString());
       response.setCode(ResponseCode.SUBSCRIPTION_NOT_LATEST);
       response.setRemark("the consumer's subscription not latest");
       return response;
   }
   ``` 
   
   **RocketMQ version: 4.3.1**
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services