Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: rbd-mirror: compare positions using all fields #8172

Merged
merged 1 commit into from Mar 19, 2016

Conversation

trociny
Copy link
Contributor

@trociny trociny commented Mar 16, 2016

Comparing by only entry_tid may give false positives.

Signed-off-by: Mykola Golub mgolub@mirantis.com

Comparing by only entry_tid may give false positives.

Signed-off-by: Mykola Golub <mgolub@mirantis.com>
@dillaman
Copy link

@trociny One of the tasks I want to get to next week is properly recording ownership within the journal tags to support failover/failback. For simple tests, I think the tag_tids will always align between two clients -- but for more complicated tests, I would expect them to diverge. For example, a peer that attaches to a remote journal after many exclusive locks (i.e. tag allocations) would result in a high tag tid on the remote side aligning with a small tag_tid on the local side.

@trociny
Copy link
Contributor Author

trociny commented Mar 19, 2016

@dillaman I guess what you describe is possible when comparing positions in different journals. But here I am comparing positions for two clients in the same journal. Shouldn't they always match exactly (object_number, tag_tid, entry_tid) if the positions are equal? They both pointing to the same event in the journal.

@dillaman
Copy link

Within the same journal, the tags should match. In that case, lgtm.

dillaman pushed a commit that referenced this pull request Mar 19, 2016
test: rbd-mirror: compare positions using all fields

Reviewed-by: Jason Dillaman <dillaman@redhat.com>
@dillaman dillaman merged commit f65cc6f into ceph:master Mar 19, 2016
@trociny trociny deleted the fix-test-rbd-mirror-position branch March 21, 2016 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants