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

fix replication bandwidth unit conversion #4922

Merged
merged 2 commits into from
May 9, 2024

Conversation

kanagarajkm
Copy link
Contributor

Community Contribution License

All community contributions in this pull request are licensed to the project maintainers
under the terms of the Apache 2 license.
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

the user input will be in bytes, need not convert it again to bytes.

Motivation and Context

To avoid any confusion while setting the replication bandwidth.

How to test this PR?

./mc replicate update ALIAS/BUCKET --id site-repl-769b7d7a-b0df-4d66-abf1-68516ddb53d4 --bandwidth 1G --remote-bucket REMOTE_ALIAS/BUCKET

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Optimization (provides speedup with no functional changes)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • Fixes a regression (If yes, please add commit-id or PR # here)
  • Unit tests added/updated
  • Internal documentation updated
  • Create a documentation update request here

the user input will be in bytes, need not convert it again to bytes.
Copy link
Member

@vadmeste vadmeste left a comment

Choose a reason for hiding this comment

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

LGTM

@poornas
Copy link
Contributor

poornas commented May 8, 2024

@kanagarajkm , the bandwidth is converted here to bytes because the server is accepting in bytes/sec

@kanagarajkm
Copy link
Contributor Author

@poornas https://pkg.go.dev/github.com/dustin/go-humanize#ParseBytes is already returning the value in bytes, it need not be converted again

@poornas
Copy link
Contributor

poornas commented May 8, 2024

@poornas https://pkg.go.dev/github.com/dustin/go-humanize#ParseBytes is already returning the value in bytes, it need not be converted again

@kanagarajkm , the bandwidth setting is supposed to be set in bits/sec - whereas the humanize package does not support conversion of bits. Therefore the parse followed by /8 to convert to bytes.

What we can do instead is, take bandwidth only in bytes (flags need to be updated in replicate add/update), then your change will be ok

@harshavardhana harshavardhana self-requested a review May 9, 2024 08:41
@kanagarajkm
Copy link
Contributor Author

What we can do instead is, take bandwidth only in bytes (flags need to be updated in replicate add/update), then your change will be ok

@poornas I have updated the flag usage.

Also removed the bits conversion from mc replicate status and mc admin replicate info. PTAL

@harshavardhana
Copy link
Member

Bytes are actually OK; that is how we communicate anyway. Its not much to talk about things in bits anyway.

@harshavardhana harshavardhana merged commit 45ae315 into minio:master May 9, 2024
7 checks passed
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.

None yet

5 participants