Skip to content
This repository was archived by the owner on Jun 20, 2024. It is now read-only.

Conversation

@bboreham
Copy link
Contributor

Fixes #2275

In the case that we do receive a ring very soon, the consequence of this change is that the requestor doesn't hear back so retries within 5 seconds.

I also moved the debug message so we still see it on requests that are ignored.

@bboreham bboreham added this to the 1.5.2 milestone May 10, 2016
@brb brb self-assigned this May 10, 2016
start_suite "Claiming addresses"

weave_on $HOST1 launch-router --ipalloc-range $UNIVERSE
weave_on $HOST1 launch-router --ipalloc-range $UNIVERSE $HOST2

This comment was marked as abuse.

This comment was marked as abuse.

@brb
Copy link
Contributor

brb commented May 10, 2016

EDITED.

Have you considered calling alloc.tryPendingOps() after establishing the ring? It could make re-try to happen sooner.

Ignore it.

@brb brb assigned bboreham and unassigned brb May 10, 2016
@brb
Copy link
Contributor

brb commented May 10, 2016

LGTM.

@brb brb merged commit 6326944 into 1.5 May 10, 2016
@bboreham bboreham deleted the issues/2275-request-order branch November 9, 2016 17:20
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants