I can share a few quick thoughts (which I admit is rare, but I happen to have a few minutes and this hit the top of my stack):
* How do you envision this overflowing when you have hundreds of databases within a cluster, or maybe 64 nodes in a cluster. ** On a related note, drag and drop is cool, but level of difficulty involved in adding a shard from node-1 increases in direct proportion to the number of nodes there are. I think the “Add Database” button on a new server should be labeled “Add Shard” and should present the option of selecting what shards to add. The add button is also not present on the nodes that have shards already so it would be good to keep it around somehow. * Speaking then of shards… They don’t appear to be captured here. How does one know which shard-set each server has? Each database has a number of shards that all have multiple shard copies and it is not a requirement that all servers have all shards. None of that is really represented in these mockups. When looking at a shard, it would be good to know if it is 00000000-15555554 or aaaaaaa8-bffffffc, or even both. Knowing this and being able to use it to scale/move hotspots in a cluster is pretty important for operations, once databases hit a significant size. * I don’t think doc-count and deleted-count is useful information at the overview page and runs the risk of requiring a lot of requests to fulfill (see point 1 on hundreds of databases). * What does compact: false mean? That the database is not small? or that it’s not actively compacting? And if the latter, wouldn’t that be on a db-shard basis, not a whole server. * It would be nice if cluster usage graphing page would show http-stats as well. Would give people a snapshot indication of where their load is hot. </JamesM> On Mar 23, 2015, at 20:32, madhuka udantha <madhukaudan...@gmail.com> wrote: > Hi All, > > are there any ideas and feedback for above mockup UIs? > > Community feedback will be useful in here. :) > > On Sun, Mar 22, 2015 at 11:51 PM, madhuka udantha <madhukaudan...@gmail.com> > wrote: > >> Hi, >> >> Here are the mockup UIs for Visualizing the CouchDB Clusters. It is just >> the initial UIs. >> >> * Page 1-cluster.png* [ >> https://app.box.com/s/isjbfop69j2cmz0kg0qar7l5nmupjnfl >> >> This Page visualize nodes in the clusters with summary information for >> each node. (Name, Memory usage..etc..) with a nice web UI interface. It is >> interactive (drag and drop supporting over nodes) >> >> *Page 2-cluster-notification-tip.png [* >> https://app.box.com/s/euc5megmx5lwseqib4511309ocoypryb >> <https://app.box.com/s/euc5megmx5lwseqib4511309ocoypryb>] >> >> Top of each panel of the nodes it contains a notification icon if there is >> notification. >> eg: Memory/disk space availability, Error in node etc... >> Notification will have a simple drop down structure as it is showing. >> >> *Page 3-cluster-warning.png* [ >> https://app.box.com/s/f2ljwxvz2w01f8uepsj4zyarhwbpiz8b] >> >> Critical level alert is showen. (Alert level can be set in config and >> notification center) >> >> *Page 4-adding-new-node.png* [ >> https://app.box.com/s/noygbeyze792bh4t93iaoxywdciau057] >> >> By clicking "add new node" you can add new nodes for clusters. UI >> Consistency is maintained >> >> *Page 5-adding-new-node-by-drag-drop.png*[ >> https://app.box.com/s/gbfsbwb6zt1jdkijve72mnullplecpj7] >> >> User interface is supported for drag-drop of databases in nodes. >> (replication operation in the BE) >> >> *Page 6-selected-db-in-node.png*[ >> https://app.box.com/s/6ojrvpxuvmo9k18dlnf8i4nmibzdx5s9] >> Each node shows the databases in it. By Clicking on database you can see >> detailed view of a particular database. This allows users to understand >> memory/data/doc distribution over DBs in particular nodes. >> >> *Page 7-custer-mgt-center.png* [ >> https://app.box.com/s/t9s42g3gwvv6bocbdsxrgjimdrh2ty0z] >> Each node is shown with disk usage under icon and summary text of the node >> is also given. It is easy to identify the disk space - free >> availability. (In here we need some BE services help) >> >> >> *Page 8-custer-mgt-center-infor.png* [ >> https://app.box.com/s/vvo4v9ji79l8japo3nm9f4lfbjhdamkc] >> User can customize notifications for each nodes by level (warning, infor, >> etc..) >> >> *Page 9-charting-disk-usages.png*[ >> https://app.box.com/s/fk7eyoyrtg8d3b29xoo0mdho9rr8cmyz] >> Cluster usage of the system is shown as a bar chart and the attributes to >> be shown can be selected according to user's preferences. >> >> You ideas are welcome in here. >> Thanks >> >> On Sun, Mar 22, 2015 at 7:34 PM, madhuka udantha <madhukaudan...@gmail.com >>> wrote: >> >>> Hi All, >>> >>> As I'm drafting my proposal for GSoC 2015 I went through some of the >>> existing Cluster Management Systems with Visualization. I recognized some >>> of the features regarding to Cluster Management HTTP API. (Some times not >>> fully documented yet) >>> Such us partitioning, re-balance..etc. >>> I was unable to find them on CouchDB API Documentation(only at the >>> implemented level but not documented yet? ) but I was able to find some of >>> the features such as adding nodes to clusters through dev-mailing list. >>> Are some of these features regarding cluster management present on the >>> API. If so where can I find the relevant documentations/resources? Even >>> the source code is fine to me. >>> >>> >>> Since I was able to clearly identify those missing features can I start a >>> discussion on a thread on the best feature list for cluster management on >>> CouchDB to be added to it on a future release. >>> My current project could also include these features that are supported >>> by the API else I could help on including them. >>> >>> [1] http://guide.couchdb.org/draft/clustering.html >>> Thanks. >>> BR, >>> >>> On Sat, Mar 21, 2015 at 11:40 AM, madhuka udantha < >>> madhukaudan...@gmail.com> wrote: >>> >>>> >>>> >>>> On Sat, Mar 21, 2015 at 12:17 AM, Alexander Shorin <kxe...@gmail.com> >>>> wrote: >>>> >>>>> On Fri, Mar 20, 2015 at 9:28 PM, madhuka udantha >>>>> <madhukaudan...@gmail.com> wrote: >>>>>> I like to know what is *different of '_nodes' and 'node'*? >>>>>> >>>>>> http://localhost:15986/nodes -->{"db_name":"nodes","doc_count":3..} >>>>>> http://localhost:25986/nodes -->{"db_name":"nodes","doc_count":1..} >>>>>> http://localhost:35986/nodes >>>>> -->{"error":"not_found","reason":"no_db_file"} >>>>> >>>>> Where did you get these nodes? >>>>> >>>> By '~/test/1/couchdb $ dev/run -n 4' I can added 4 nodes. (default it is >>>> 3 nodes) >>>> >>>> Here is my console print, Yes now I have four node running. >>>> >>>> *max@max-VirtualBox ~/test/1/couchdb $ dev/run -n 4* >>>> *Setup environment... ok* >>>> *Ensure CouchDB is built... ok* >>>> *Prepare configuration files... ok* >>>> *Start node node1... ok* >>>> *Start node node2... ok* >>>> *Start node node3... ok* >>>> *Start node node4... ok* >>>> *Ensure all nodes are run... ok* >>>> *Join nodes into cluster... ok* >>>> *Developers cluster is set up at http://127.0.0.1:15984 >>>> <http://127.0.0.1:15984>. Time to hack!... * >>>> >>>> Each above nodes are running in localhost in port 15986, 25986, 35986 >>>> and 45986 >>>> >>>> It seems docs are mainly in 15986 (node1) shown by 'doc_count' value, >>>> is there any reason for that or is it happening randomly? >>>> >>>> >>>> >>>> >>>>> >>>>> -- >>>>> ,,,^..^,,, >>>>> >>>> >>>> >>>> >>>> -- >>>> Cheers, >>>> Madhuka Udantha >>>> http://madhukaudantha.blogspot.com >>>> >>> >>> >>> >>> -- >>> Cheers, >>> Madhuka Udantha >>> http://madhukaudantha.blogspot.com >>> >> >> >> >> -- >> Cheers, >> Madhuka Udantha >> http://madhukaudantha.blogspot.com >> > > > > -- > Cheers, > Madhuka Udantha > http://madhukaudantha.blogspot.com
