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

stripe cleanup: Remove the option from create and add-brick cmds #1812

Merged
merged 4 commits into from
Jan 5, 2021

Conversation

Sheetalpamecha
Copy link
Member

This patch aims to remove the code for stripe option instead
of keeping a default values of stripe/stripe-count variables and
setting and getting dict options and similar redundant operations.
Also removing tests for stripe volumes that have been already
marked bad.

Updates: #1000
Change-Id: Ic2b3cabd671f0c8dc0521384b164c3078f7ca7c6
Signed-off-by: Sheetal Pamecha spamecha@redhat.com

@Sheetalpamecha
Copy link
Member Author

/run regression

@@ -5841,8 +5833,6 @@ glusterd_get_state(rpcsvc_request_t *req, dict_t *dict)

fprintf(fp, "Volume%d.snap_count: %" PRIu64 "\n", count,
volinfo->snap_count);
fprintf(fp, "Volume%d.stripe_count: %d\n", count,
volinfo->stripe_count);
Copy link
Member

Choose a reason for hiding this comment

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

this removal may result in checksum mismatch during update... can you check if we need to write it regardless.

@mohit84 please confirm.

Copy link
Member

@amarts amarts left a comment

Choose a reason for hiding this comment

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

LGTM.

@Sheetalpamecha
Copy link
Member Author

/run regression

1 similar comment
@Sheetalpamecha
Copy link
Member Author

/run regression

amarts
amarts previously approved these changes Dec 4, 2020
@Sheetalpamecha
Copy link
Member Author

Hi @mohit84, Review approval please if you don't see any other issue with this patch.
As discussed in gchat, Should we move on with constant value for stripe as it will never change and serve the purpose for just comparison?

@mohit84
Copy link
Contributor

mohit84 commented Dec 7, 2020

Hi @mohit84, Review approval please if you don't see any other issue with this patch.
As discussed in gchat, Should we move on with constant value for stripe as it will never change and serve the purpose for just comparison?

Yes sheetal please do it

@Sheetalpamecha
Copy link
Member Author

/run regression

@Sheetalpamecha
Copy link
Member Author

/recheck smoke

This patch aims to remove the code for stripe option instead
of keeping a default values of stripe/stripe-count variables and
setting and getting dict options and similar redundant operations.
Also removing tests for stripe volumes that have been already
marked bad.

Updates: gluster#1000
Change-Id: Ic2b3cabd671f0c8dc0521384b164c3078f7ca7c6
Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>
tests/000-flaky/basic_changelog_changelog-snapshot.t
was failing due to 0 return value

Change-Id: I8ea0443669c63768760526db5aa1f205978e1dbb
Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>
Change-Id: I49f3da4f106c55f9da20d0b0a299275a19daf4ba
Change-Id: I83bae85d10c8c5b3c66f56c9f8de1ec81d0bbc95
@Sheetalpamecha
Copy link
Member Author

/run regression

@Sheetalpamecha
Copy link
Member Author

@mohit84 and @amarts please review the patch. Required changes have been done after last discussion.

@mohit84 mohit84 merged commit 1d74669 into gluster:devel Jan 5, 2021
Shwetha-Acharya added a commit to Shwetha-Acharya/glusterfs that referenced this pull request May 10, 2022
…mds (gluster#1812)"

This reverts commit 1d74669.

Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>
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.

None yet

3 participants