http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/MB-6423 Couchbase Server Use case:- <br/> 1) Users upgrade to 20 from 181 <br/> 2) They decide to separate out partition for indexes. Currently there is no way to configure just index_path without wiping out data_path or reconfiguring the cluster. <br/> &nbsp;Currently, issuing the data_path command will wipe out the database files. <br/> <br/> <br/> <br/> One can configure the data path <br/> curl -d path=/var/tmp/test <a href="http://localhost:8091/nodes/self/controller/settings">http://localhost:8091/nodes/self/controller/settings</a> <br/> <br/> This does not seem to work... <br/> curl -d index_path=/data2 <a href="http://localhost:8091/nodes/self/controller/settings">http://localhost:8091/nodes/self/controller/settings</a> <br/> 1639 MB-6423

Allow users to set index_path post upgrade to 2.0

Bug Major Closed Fixed Public Aliaksey Artamonau Karan Kumar system-test Sat, 25 Aug 2012 16:27:53 -0500 Wed, 9 Jan 2013 23:13:18 -0600 Mon, 8 Oct 2012 14:40:11 -0500 2.0-beta 2.0 ns_server 0 2 I guess right now, we would need separate rest api to configure just indexes. <br/> Not a bug, but a feature i guess. <br/> <br/> Following seems to work fine. <br/> curl -d &quot;path=/data&amp;index_path=/indexes&quot; <a href="http://localhost:8091/nodes/self/controller/settings">http://localhost:8091/nodes/self/controller/settings</a> yes for our testing we want to try and put each index on a seperate disk. not sure if there is an api that allows us to do so We don&#39;t plan to have such API. You can manually replace files with symlinks. Another option is raid 0 From capacity planning point of view, <br/> <br/> if customer upgrade to 20 and later plan to create views, <br/> <br/> by default, views would get created on the same partition as the database files. <br/> <br/> There is no separate rest_api to setup path for just indexes. I see _no point at all_ having _separate_ API for setting up just index path. <br/> <br/> We _do_ have API to setup separate index path. <br/> <br/> The only thing we dont have is api to set up per-index path. <br/> And my performance recommendation would be: <br/> <br/> instead of have disk spindle per index, just raid 0 all spindles you have. That should be as good as or even better than spindle per index. <br/> Sure. I can create a separate ticket to test out raid 0 and see if it provides better performance. Will try to convey this in a better way:- <br/> <br/> I can configure the data_path as following <br/> curl -d path=/data <a href="http://localhost:8091/nodes/self/controller/settings">http://localhost:8091/nodes/self/controller/settings</a> <br/> <br/> BUT, I cant configure the index_path as following (not per index, but for all indexes) <br/> curl -d index_path=/var/tmp/test <a href="http://localhost:8091/nodes/self/controller/settings">http://localhost:8091/nodes/self/controller/settings</a> <br/> <br/> <br/> curl -vvv -d &quot;index_path=/data&quot; <a href="http://Administrator:">http://Administrator:</a><a href='mailto:password@localhost'>password@localhost</a>:8091/nodes/self/controller/settings <br/> * About to connect() to localhost port 8091 (#0) <br/> * Trying ::1... Connection refused <br/> * Trying 127.0.0.1... connected <br/> * Connected to localhost (127.0.0.1) port 8091 (#0) <br/> * Server auth using Basic with user &#39;Administrator&#39; <br/> &gt; POST /nodes/self/controller/settings HTTP/1.1 <br/> &gt; Authorization: Basic QWRtaW5pc3RyYXRvcjpwYXNzd29yZA== <br/> &gt; User-Agent: curl/7.19.7 (x86_64-unknown-linux-gnu) libcurl/7.19.7 NSS/3.12.7.0 zlib/1.2.3 libidn/1.18 libssh2/1.2.2 <br/> &gt; Host: localhost:8091 <br/> &gt; Accept: */* <br/> &gt; Content-Length: 16 <br/> &gt; Content-Type: application/x-www-form-urlencoded <br/> &gt; <br/> &lt; HTTP/1.1 400 Bad Request <br/> &lt; Server: Couchbase Server 2.0.0-1695-rel-enterprise <br/> &lt; Pragma: no-cache <br/> &lt; Date: Fri, 07 Sep 2012 19:10:36 GMT <br/> &lt; Content-Type: application/json <br/> &lt; Content-Length: 47 <br/> &lt; Cache-Control: no-cache <br/> &lt; <br/> * Connection #0 to host localhost left intact <br/> * Closing connection #0 <br/> [&quot;The database or index path cannot be empty.&quot;] <br/> <br/> <br/> <br/> The only way for me to configure index_path is by specfying both index_path and data_path <br/> as following:- <br/> curl -d &quot;path=/data&amp;index_path=/indexes&quot; <a href="http://localhost:8091/nodes/self/controller/settings">http://localhost:8091/nodes/self/controller/settings</a> <br/> <br/> The above command nukes the bucket and looses deletes all the data. <br/> <br/> Well here, I am not trying to point out a performance issue. I am trying to point out a functional bug. <br/> <br/> I will take this offline with Alk Karan, <br/> Any updates ? <br/> <br/> do you need to discuss this with Dipti ? Looks like simply implementing new API or extending old in some way is the way to go here. <a href="http://review.membase.org/#/c/21425/">http://review.membase.org/#/c/21425/</a> build 1820 <br/> <br/> verification steps: <br/> 1. 1 node with default bucket and 1 item in it <br/> 2. create 1 view <br/> 3. change index path <br/> curl --user Administrator:password -d index_path=/tmp/bbbbb/ <a href="http://localhost:8091/nodes/self/controller/settings">http://localhost:8091/nodes/self/controller/settings</a> <br/> observation: view works after indexing, data index location was changed <br/> 4. change index path in second time <br/> curl --user Administrator:password -d index_path=/tmp/aaaa/ <a href="http://localhost:8091/nodes/self/controller/settings">http://localhost:8091/nodes/self/controller/settings</a> <br/> observation: view works after indexing, data index location was changed on new <br/> 5. change data path <br/> curl --user Administrator:password -d path=/tmp/data_folder/ <a href="http://localhost:8091/nodes/self/controller/settings">http://localhost:8091/nodes/self/controller/settings</a> <br/> <br/> result: view is left on UI for some time but with error on request {&quot;error&quot;:&quot;not_found&quot;,&quot;reason&quot;:&quot;Design document _design/dev_a not found&quot;} <br/> after a couple minutes ddoc/view is deleted from ui ( browser cash was expired) Andrei so ? <br/> <br/> BTW changing data path after the fact is a bad idea. We don&#39;t necessarily handle it well. In RN: This enables users to change the disk location of an index without destroying <br/> persisted data. You can now set index_path and it will delete an existing index only <br/> and create a new disk location for use. Date of First Response Sat, 25 Aug 2012 18:53:37 -0500 Rank 4172 Time In Status