Description of problem: Today, enable_vol.sh prepends the volume name to the fs.glusterfs.volumes property of core-site.xml. This causes the just-enabled volume to become the default volume used for all unqualified URIs. bin/set_glusterdfs_uri.sh supports both prepending and appending a volume to this property value, so a new option should be added to enable_vol so the user can decide if the new;y enabled volume should be used as the default or not. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
added --make-default to enable_vol.sh. When specified this causes the target volume to become the default volume. The default behavior is that the target volume will not be the default volume,
*** Bug 1151207 has been marked as a duplicate of this bug. ***
Tested and verified on several clusters also with different scenarios and multiple Volumes. # rpm -q rhs-hadoop-install rhs-hadoop-install-2_28-1.el6rhs.noarch > VERIFIED
Jeff, Could you please provide the doc text in the Doc Text field for this bug?
Jeff, Could you please review the edited doc text for technical accuracy and sign-off?
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2014-1275.html
(In reply to Divya from comment #7) > Jeff, > > Could you please review the edited doc text for technical accuracy and > sign-off? done