Skip to content

Conversation

@Jaskey
Copy link
Contributor

@Jaskey Jaskey commented Jun 7, 2017

@coveralls
Copy link

coveralls commented Jun 7, 2017

Coverage Status

Coverage increased (+0.08%) to 38.692% when pulling 7f60c72 on Jaskey:ROCKETMQ-204-heartbeat-issue-when-topicRouteInfo-becomes-nonexist into 0c5e53d on apache:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) to 38.692% when pulling 7f60c72 on Jaskey:ROCKETMQ-204-heartbeat-issue-when-topicRouteInfo-becomes-nonexist into 0c5e53d on apache:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.3%) to 38.894% when pulling 0baa2d4 on Jaskey:ROCKETMQ-204-heartbeat-issue-when-topicRouteInfo-becomes-nonexist into 0c5e53d on apache:master.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage increased (+0.3%) to 38.894% when pulling 0baa2d4 on Jaskey:ROCKETMQ-204-heartbeat-issue-when-topicRouteInfo-becomes-nonexist into 0c5e53d on apache:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.3%) to 38.894% when pulling 0baa2d4 on Jaskey:ROCKETMQ-204-heartbeat-issue-when-topicRouteInfo-becomes-nonexist into 0c5e53d on apache:master.

@Jaskey Jaskey changed the base branch from master to develop June 7, 2017 09:28
@Jaskey Jaskey changed the base branch from develop to master June 7, 2017 09:28
@Jaskey Jaskey changed the title [Rocketmq 204]-when all brokers is offline, client still attempts to send heartbeat [ROCKETMQ-204]-when all brokers is offline, client still attempts to send heartbeat Jun 7, 2017
}
} else {
Set<MessageQueue> prev = this.rebalanceImpl.getTopicSubscribeInfoTable().remove(topic);
log.info("instanceName={}, group={}, topicSubscribeInfoTable of topic {} is remove, {}, prev = {}", defaultMQPullConsumer.getInstanceName(), defaultMQPullConsumer.getConsumerGroup(), topic, prev);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is remove --> is removed

}
} else {
log.warn("updateTopicRouteInfoFromNameServer, getTopicRouteInfoFromNameServer return null, Topic: {}", topic);
log.warn("updateTopicRouteInfoFromNameServer, getTopicRouteInfoFromNameServer return null. Topic: {}", topic);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO, API(getTopicRouteInfoFromNameServer) will throw exception when not found topic route, so the logic will never enter 'else', am I right?

Copy link
Contributor Author

@Jaskey Jaskey Jun 9, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems you are right, this design is confusing , maybe we change the logic into returns null, Or I just catch the MQClientException for the same logic

I will suggest

  1. return null
  2. throw a prefine exception

which is closer to the presentative judgment .

@coveralls
Copy link

coveralls commented Jun 9, 2017

Coverage Status

Coverage decreased (-0.03%) to 38.579% when pulling aa59bbd on Jaskey:ROCKETMQ-204-heartbeat-issue-when-topicRouteInfo-becomes-nonexist into 0c5e53d on apache:master.

@Jaskey
Copy link
Contributor Author

Jaskey commented Jun 12, 2017

@vsair @lizhanhui please review the updated pr

@lizhanhui
Copy link
Contributor

@Jaskey I'll check it today.

@Jaskey
Copy link
Contributor Author

Jaskey commented Jun 28, 2017

@lizhanhui @vsair @zhouxinyu

any opinions?

@vongosling
Copy link
Member

@Jaskey I will close the pr, if you happened to the same question, please let me know.

@vongosling vongosling closed this Jul 14, 2018
pingww pushed a commit that referenced this pull request Aug 26, 2022
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

Successfully merging this pull request may close these issues.

5 participants