Hemika, I vote for now, let's have a plain table displaying nodes in the cluster with above properties, with coordinator highlighted. At the moment we do not have a lot of information to display via a drill down.
WDYT? Thanks On Tue, Jan 6, 2015 at 7:13 AM, Pamod Sylvester <[email protected]> wrote: > Hemika, you can have a separate section to display the cluster information > which will contain info regarding all the nodes in the cluster (info as in > ip, node id etc). There you could highlight the node which is the > coordinator. > > Further you could have sort of a drill down option where you could click > on the node an get more information regarding it, there you can display the > slot information. > > The above is one approach that I could think of. There might be more ways > of dealing with this. > > Thanks, > > > On Tuesday, January 6, 2015, Hemika Kodikara <[email protected]> wrote: > >> I was a bit stuck on the terminology there. But was able to figure it out >> with HasithH's help. :) >> >> So far from what I understood, following are the details that can be >> shown on this page and some of my suggestions. >> 1. Displaying the Node ID. >> 2. The IP and Port. >> 3. Showing the publishers and subscribers would be good as well. But the >> subscribers are already shown in another page. Instead, will it be useful >> if we show the number of publishers and subscribers ? >> 4. Displaying the coordinator node. What can be showing using the >> coordinator node ? >> >> Thanks, >> Hemika >> >> >> Hemika Kodikara >> Software Engineer >> WSO2 Inc. >> lean . enterprise . middleware >> http://wso2.com >> >> Mobile : +94777688882 >> >> On Tue, Dec 23, 2014 at 10:03 AM, Ramith Jayasinghe <[email protected]> >> wrote: >> >>> what are the stats that could be useful to display in coordinator node? >>> (that is if we are going to specifically display coordinator specific stats) >>> Information related to slot distribution etc... ( which will help us to >>> see how the deployment performs?) >>> >>> On Tue, Dec 23, 2014 at 8:09 AM, Sajini De Silva <[email protected]> >>> wrote: >>> >>>> Hi, >>>> >>>> Coordinator node will be critical since slot coordination is happening >>>> via the coordinator node. Therefore +1 for Pamod's idea. >>>> >>>> Thank you, >>>> Sajini. >>>> >>>> On Tue, Dec 23, 2014 at 1:13 AM, Pamod Sylvester <[email protected]> >>>> wrote: >>>> >>>>> Hi Hemika, >>>>> >>>>> Also will it make sense to display the coordinator node ? IMO this >>>>> will be useful. >>>>> >>>>> Thanks, >>>>> Pamod >>>>> >>>>> On Mon, Dec 22, 2014 at 10:48 PM, Hemika Kodikara <[email protected]> >>>>> wrote: >>>>> >>>>>> Thanks for the correction and feedback Asitha. >>>>>> >>>>>> Looping in Ramith and HasithaH. >>>>>> >>>>>> Hemika Kodikara >>>>>> Software Engineer >>>>>> WSO2 Inc. >>>>>> lean . enterprise . middleware >>>>>> http://wso2.com >>>>>> >>>>>> Mobile : +94777688882 >>>>>> >>>>>> On Mon, Dec 22, 2014 at 10:28 PM, Asitha Nanayakkara <[email protected] >>>>>> > wrote: >>>>>> >>>>>>> >>>>>>> On Mon, Dec 22, 2014 at 5:51 PM, Hemika Kodikara <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> The page mentioned in $subject provides several information related >>>>>>>> to nodes in a clustered deployment in MB 2.2.0 (See attachment). >>>>>>>> >>>>>>>> The page displays the cassandra details, zookeeper details and the >>>>>>>> node number. >>>>>>>> >>>>>>>> In MB 3.0.0, several change are done so that, >>>>>>>> 1. Zookeeper is not being used. >>>>>>>> 2. No such thing as Node number as node queues and global queues >>>>>>>> are not there anymore. >>>>>>>> >>>>>>> In 3.0.0 there is a node id for each node. And clustered/standalone >>>>>>> mode information need to be displayed >>>>>>> >>>>>>> 3. Supports other databases including other than cassandra. >>>>>>>> >>>>>>> +1 >>>>>>> >>>>>>>> >>>>>>>> Share your idea on $subject. >>>>>>>> >>>>>>> Something like number of subscribers and publishers handled by each >>>>>>> node. This will give an idea of load distribution in a cluster. >>>>>>> MQTT and AMQP ports used by the nodes >>>>>>> >>>>>>>> >>>>>>>> Regards, >>>>>>>> Hemika >>>>>>>> >>>>>>>> Hemika Kodikara >>>>>>>> Software Engineer >>>>>>>> WSO2 Inc. >>>>>>>> lean . enterprise . middleware >>>>>>>> http://wso2.com >>>>>>>> >>>>>>>> Mobile : +94777688882 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Dev mailing list >>>>>>>> [email protected] >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Asitha Nanayakkara* >>>>>>> Software Engineer >>>>>>> WSO2, Inc. http://wso2.com/ >>>>>>> Mob: + 94 77 85 30 682 >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> [email protected] >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Pamod Sylvester * >>>>> *Senior Software Engineer * >>>>> Integration Technologies Team, WSO2 Inc.; http://wso2.com >>>>> email: [email protected] cell: +94 77 7779495 >>>>> >>>> >>>> >>>> >>>> -- >>>> Sajini De SIlva >>>> Software Engineer; WSO2 Inc.; http://wso2.com , >>>> Email: [email protected] >>>> Blog: http://sajinid.blogspot.com/ >>>> Git hub profile: https://github.com/sajinidesilva >>>> >>>> Phone: +94 712797729 >>>> >>>> >>> >>> >>> -- >>> Ramith Jayasinghe >>> Technical Lead >>> WSO2 Inc., http://wso2.com >>> lean.enterprise.middleware >>> >>> E: [email protected] >>> P: +94 777542851 >>> >>> >> > > -- > *Pamod Sylvester * > *Senior Software Engineer * > Integration Technologies Team, WSO2 Inc.; http://wso2.com > email: [email protected] cell: +94 77 7779495 > > -- *Hasitha Abeykoon* Senior Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
