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.

Sign up for GitHub

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

Jump to bottom

Fix arbiter doc #163

Merged
merged 1 commit into from
Apr 2, 2018
Merged

Fix arbiter doc #163

merged 1 commit into from
Apr 2, 2018

Conversation

NITEMAN
Copy link
Contributor

@NITEMAN NITEMAN commented Apr 2, 2018

Pull Request (PR) description

Current README statement about arbiter is wrong, if you follow instructions the result is

Notice: /Stage[main]/Gluster/Gluster::Volume[g0]/Exec[gluster create volume g0]/returns: For arbiter configuration, replica count must be 3 and arbiter count must be 1. The 3rd brick of the replica will be the arbiter
Notice: /Stage[main]/Gluster/Gluster::Volume[g0]/Exec[gluster create volume g0]/returns: 
Notice: /Stage[main]/Gluster/Gluster::Volume[g0]/Exec[gluster create volume g0]/returns: Usage:
Notice: /Stage[main]/Gluster/Gluster::Volume[g0]/Exec[gluster create volume g0]/returns: volume create <NEW-VOLNAME> [stripe <COUNT>] [replica <COUNT> [arbiter <COUNT>]] [disperse [<COUNT>]] [disperse-data <COUNT>] [redundancy <COUNT>] [transport <tcp|rdma|tcp,rdma>] <NEW-BRICK>?<vg_name>... [force]

@juniorsysadmin juniorsysadmin added the docs Improvements or additions to documentation label Apr 2, 2018
@juniorsysadmin juniorsysadmin merged commit 234dc97 into voxpupuli:master Apr 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
docs Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@NITEMAN @juniorsysadmin