Hi, I built and ran developer-perview 2.0 as explained previously and here are the steps of it [1].
I have 2 Questions to ask. Q1) I also went through the REST API and I like to know weather we can add nodes into clusters from the REST API (else only in config.)? Q2) When I am running the fauxton (http://localhost:8000/#/_all_dbs), I see the list of DBs but when I click one of them and move to ' http://localhost:8000/#/database/test8000/_all_docs' it gives an error in web UI with RED text saying 'bad request'. Some pages it shows 'Databases is not exit' Here i am sharing my screen shoots. Is it the way it work? I think the reason for above Q2. is round-robin nature of Loadbalancer. Am I correct? I went one step on this issue (Q2) to find the root then I noticed (I am using *haproxy.cfg*) it is acting in round robbing manner, So 1st request hit for node 1, then second one hit for node2, as My test_db was in node1, not in node2 that's why it says "database is not exist'. It is correct as request was treated by node2[3] and not from the node1[4]. After 2 request sent, it shows fine as it hit again by round-robin Is it normal? or am I missing anything here? [1] http://madhukaudantha.blogspot.com/2015/03/couchdb-fauxton-introduction.html [2] https://app.box.com/s/vunvxxfepzdle33b70710b6omj2rjo2y [3] https://app.box.com/s/h3izlnadghnj6zfsgww93kernqn9x2gy [4] https://app.box.com/s/pdsnvle5x1oihubfryojkixj82uz2qe2 On Thu, Mar 19, 2015 at 11:45 AM, madhuka udantha <[email protected]> wrote: > Hi. All > > > > I'm Udantha. I'm a MSc. Student at University of Moratuwa. This particular > project looks interesting to me. Since I have previous experiences on > visualization(web portals / dashboards [1]), javascript [2], html5, REST > etc. > > > > Under guidance of Alexander Shorin, Robert Kowalski and Sebastian > Rothbucher, I have started the initial phase. Building > (/developer-preview/2.0/) from source and pointing out few small bugs in > build process. Going through the REST api[3] and following few > tutorials[4]. If there are any material or ideas that can help for > $subject, please let me know. > > > Here is the list of features that I gain over the period of time (this can > be change). Your ideas and view will be grateful in here. > > > > - Visualize the Couch DB Clusters with nodes (icons, grouping) > - Memory usage on each node in the cluster. > - Charting and graph representation of memory usage over the nodes > - Notification center > - Where it will give notification for user when he/she reaches memory > limits > - Notification over documents/ document count > - Summary of each node (name of the Databases, recent DB updates on > each) > - List databases cluster/node > - Drag and Drop supporting for DB over the nodes * > - Basic operation for node/DB can be done with interactive user > interface* > - Retrieving stats/actives* > > > Your ideas are welcome in here. > > > > [1] https://github.com/wso2/product-ues/ > > [2] https://github.com/wso2/jaggery > > [3] http://couchdb.readthedocs.org/en/1.6.1/api/server/common.html > > [4] https://github.com/ryanflorence/react-training/tree/gh-pages/lessons > > > Thanks, > -- > Madhuka Udantha > http://madhukaudantha.blogspot.com > -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com
