Skip to content

mon: fix osd failure info in mon#6278

Merged
liewegas merged 2 commits intoceph:masterfrom
XinzeChi:wip-failinfo-mon
Nov 25, 2015
Merged

mon: fix osd failure info in mon#6278
liewegas merged 2 commits intoceph:masterfrom
XinzeChi:wip-failinfo-mon

Conversation

@XinzeChi
Copy link
Contributor

when the network adapter of node A run into error, osd in this node
would tell mon other osd's heartbeat is timeout also. So when rebind
fail after retry 3 times, the osd should cancel in-flight failure report
send to mon before.

Signed-off-by: Xinze Chi xinze@xsky.com

@loic-bot
Copy link

@ghost ghost added bug-fix core labels Oct 16, 2015
Copy link
Member

Choose a reason for hiding this comment

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

If I'm reading this correct it means a failure report cancellation should not be ignored, even if the osd is down. That makes sense, but can you break that into a separate commit please?

@liewegas
Copy link
Member

The report cancellation part looks good to me too. Can you rebase on current master and break it into 2 patches please? Thanks!

@liewegas liewegas self-assigned this Nov 20, 2015
@XinzeChi
Copy link
Contributor Author

@liewegas , I fix the PR based on your comment. Thanks.

@loic-bot
Copy link

when the network adapter of node A run into error, osd in this node
would tell mon other osd's heartbeat is timeout also. So when rebind
fail after retry 3 times, the osd should cancel in-flight failure report
send to mon before.

Signed-off-by: Xinze Chi <xinze@xsky.com>
do not ignore a failure report cancellation form osd even if it is
down.

Signed-off-by: Xinze Chi <xinze@xsky.com>
@loic-bot
Copy link

@loic-bot
Copy link

liewegas added a commit that referenced this pull request Nov 25, 2015
osd: cancel failure reports if we fail to rebind network

Reviewed-by: Sage Weil <sage@redhat.com>
@liewegas liewegas merged commit d9705f4 into ceph:master Nov 25, 2015
@dzafman dzafman mentioned this pull request May 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants