-
Notifications
You must be signed in to change notification settings - Fork 553
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
Option to enable disable ILM expiry for site replication #4698
Option to enable disable ILM expiry for site replication #4698
Conversation
36d2ba1
to
0df318e
Compare
replicate-ilm-expiry
to mc admin replication add
a36701f
to
95b5435
Compare
cdeb151
to
5ee893f
Compare
you should provide the option to enable ilm expiry replication later as well? |
Ah ok, makes sense. Will add option for the same. |
8c92d6f
to
be3553c
Compare
Done @poornas |
validations are broken - on update of enable|disable of the new flag, it expects endpoint also to be passed
|
I am able to enable|disable ILM expiry replication below
It does not mandate to pass Regarding |
be3553c
to
62aa11c
Compare
Updated and now ILM expiry replication details are shown as below
and added option
|
62aa11c
to
3bdc1d6
Compare
94a8e9d
to
bc4efea
Compare
bc4efea
to
0348585
Compare
0348585
to
eafbf36
Compare
eb128bf
to
6c94adc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Added options `replicate-ilm-expiry` and `disable-ilm-expiry-replication` for `mc admin replicate add` and `mc admin replicate update` commands respectively. Signed-off-by: Shubhendu Ram Tripathi <shubhendu@minio.io>
Signed-off-by: Shubhendu Ram Tripathi <shubhendu@minio.io>
Signed-off-by: Shubhendu Ram Tripathi <shubhendu@minio.io>
Signed-off-by: Shubhendu Ram Tripathi <shubhendu@minio.io>
Signed-off-by: Shubhendu Ram Tripathi <shubhendu@minio.io>
Signed-off-by: Shubhendu Ram Tripathi <shubhendu@minio.io>
Signed-off-by: Shubhendu Ram Tripathi <shubhendu@minio.io>
Signed-off-by: Shubhendu Ram Tripathi <shubhendu@minio.io>
Don't pass `--deployment-id` while using `--disable-ilm-expiry-replication` or `--enable-ilm-expiry-replication` with `mc admin replicate update` Signed-off-by: Shubhendu Ram Tripathi <shubhendu@minio.io>
Signed-off-by: Shubhendu Ram Tripathi <shubhendu@minio.io>
It would be calculated at server side Signed-off-by: Shubhendu Ram Tripathi <shubhendu@minio.io>
Signed-off-by: Shubhendu Ram Tripathi <shubhendu@minio.io>
f4921bd
to
f550126
Compare
Community Contribution License
All community contributions in this pull request are licensed to the project maintainers
under the terms of the [Apache 2 license] (https://www.apache.org/licenses/LICENSE-2.0).
By creating this pull request I represent that I have the right to license the
contributions to the project maintainers under the Apache 2 license.
Description
Added options
replicate-ilm-expiry
anddisable-ilm-expiry-replication
formc admin replicate add
andmc admin replicate update
commands respectively.Motivation and Context
How to test this PR?
Follow below detailed steps for verifying the different scenarios
Step-1: Create three MinIO sites sat
m1
,m2
andm3
Step-2: Setup site replication between the first two sites now
mc admin replicate add m1 m2 --replicate-ilm-expiry
Step-3: Create a bucket for first site (
test-bucket
)mc mb m1/test-bucket
Step-4: Setup warm tier to
m3
for sitem1
Step-5: Check details of the replication
Step-6: Add ILM rules to the first site's bucket
test-bucket
Step-7: Check ILM rules list for sites
Step-8: Check replication status details as below
Step-9: Check the replication of removal of expiry rules across sites
The replication of removal of expiry rule would take few seconds to reflect in site2 as it happens as part of a sync process
Repeat this process keeping second site up and down both. The replication of removed expiry rules should happen as part of sync when second site comes up.
Step-10: Check removal of all ILM rules from first site and all expiry rules should get replicated (removed) from second site as well
again this replication of expiry rules removal would take few secs for site2 (as runs as part of sync)
Step-11: Test editing of expiry rules details and their replication
Step-12: Check disabling and re-enabling of replication of ilm expiry across site replicated sites
Step-13: Verify healing of enabled/disabled ILM expiry to sites which were offline while changes done
Bring down one of the remote sites and update the ILM expiry flag for the up site
Bring back the remote site and wait for few secs and then check the replication info for the site
Update same rule on both site separately with different values. The values should not be healed even after few mins (as it needs ILM expiry to be enabled for all sites for heal to happen)
Re-enable ILM expiry for the site we disabled earlier and wait for few secs. Rules should be healed and latest one should win to update to all sites
Needs corresponding changes from
minio
,console
,minio-go
andmadmin-go
Types of changes
Checklist:
commit-id
orPR #
here)