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: make sure to use uniform drive count calculation #10208

Merged
merged 1 commit into from
Aug 5, 2020

Commits on Aug 5, 2020

  1. fix: make sure to use uniform drive count calculation

    It is possible in situations when server was deployed
    in asymmetric configuration in the past such as
    
    ```
    minio server ~/fs{1...4}/disk{1...5}
    ```
    
    Results in setDriveCount of 10 in older releases
    but with fairly recent releases we have moved to
    having server affinity which means that a set drive
    count ascertained from above config will be now '4'
    
    While the object layer make sure that we honor
    `format.json` the storageClass configuration however
    was by mistake was using the global value obtained
    by heuristics. Which leads to prematurely using
    lower parity without being requested by the an
    administrator.
    
    This PR fixes this behavior.
    harshavardhana committed Aug 5, 2020
    Configuration menu
    Copy the full SHA
    9fc2500 View commit details
    Browse the repository at this point in the history