Description of problem: At any given point of time, users can only perform operations on only one gluster volume. To use the other volume, the ring files have to be recreated. Version-Release number of selected component (if applicable): Master How reproducible: Always Steps to Reproduce: 1. Try to do operations on two different accounts at the same time. 2. Operations on one the account's will fail. Actual results: Operations on one the account's will fail. Expected results: Operations on both the account should complete successfully. Additional info:
Per Feb-13 bug triage meeting, targeting for 2.1.0.
CHANGE: http://review.gluster.org/4485 (object-storage: Restoring multi volume support in UFO.) merged in master by Vijay Bellur (vbellur)
Fixed in upstream.
This only partially corrects the problem. When this patch is applied against 3.4 Alpha 1, and against 3.3.1-11, everything works fine with just one volume. With a second volume, all works well when just referencing the first volume, but when referencing the second volume, the container-server requests are against the wrong volume. Here's a snippet of output from my storage1.log file: Mar 18 22:01:03 r3master account-server 127.0.0.1 - - [18/Mar/2013:22:01:03 +0000] "HEAD /test/0/AUTH_test" 204 - "txe0a73e5b77fa4d6497c20b5377427388" "-" "-" 0.0114 "" Mar 18 22:01:03 r3master account-server 127.0.0.1 - - [18/Mar/2013:22:01:03 +0000] "PUT /test/0/AUTH_test/test.txt" 201 - "txe0a73e5b77fa4d6497c20b5377427388" "-" "-" 0.0036 "" Mar 18 22:01:03 r3master container-server 127.0.0.1 - - [18/Mar/2013:22:01:03 +0000] "PUT /admin/0/AUTH_test/test.txt" 202 - "txe0a73e5b77fa4d6497c20b5377427388" "-" "-" 0.0147 As you can see, the container-server PUT is trying to access the admin volume, instead of the test volume.
Was this entered for RHS2.0 with or without PDQ patches?