Let's increase the connections to ~2000 and check... You may have one analyzer, but 3 nodes are accessing the mysql db concurrently using 3 jdbc pools.
I have run 5 analyzers and with 20 gadgets on a single node and there hasn't been too many connections... so the above distributed mode should be the reason for this... On Thu, Jul 12, 2012 at 12:17 PM, Manisha Gayathri <[email protected]> wrote: > > > On Thu, Jul 12, 2012 at 11:23 AM, Tharindu Mathew <[email protected]>wrote: > >> How many gadgets and analyzers do you have? > > > 2 Gadgets in the dashboard. > 1 Analyzer script (running in 1 analyzer node) which runs a simple hive > query that reads the Cassandra db and write data to MySQL. > >> >> >> On Thu, Jul 12, 2012 at 11:18 AM, Manisha Gayathri <[email protected]>wrote: >> >>> Hi Tharindu, >>> >>> Increased the number of max connections to 300. (Default was set to 151) >>> With that also, the error occurred, 4 minutes after the gadget got >>> populated. >>> Any recommended # that I should try with? >>> >>> Tnx >>> Rgds >>> Manisha >>> >>> >>> On Wed, Jul 11, 2012 at 9:37 PM, Tharindu Mathew <[email protected]>wrote: >>> >>>> Hi Manisha, >>>> >>>> As the error states, this probably is an issue on your number of mysql >>>> connections. >>>> >>>> Can you increase the number and update the findings? >>>> >>>> >>>> On Wed, Jul 11, 2012 at 9:28 PM, Manisha Gayathri <[email protected]>wrote: >>>> >>>>> Hi all, >>>>> >>>>> Tested BAM2 with a clustered distributed set up. The test was carried >>>>> out with the following configurations. >>>>> >>>>> - 1 ESB Server for data publishing (WSO2 ESB- 4.0.2 with >>>>> backported data publishers) >>>>> - 1 AS Server for data publishing (WSO2 AS-4.1.2 with backported >>>>> data publishers) >>>>> - 3 remote Hadoop nodes >>>>> - 3 remote Cassandra nodes >>>>> - 1 Analyzer node >>>>> - 1 Collector node >>>>> - 1 Dashboard node >>>>> - MySQL database >>>>> >>>>> The end-to-end work flow was executed correctly within the above set >>>>> up. >>>>> Will further enhance the deployment to cluster Analyzer, Collector and >>>>> Dashboard nodes and report the progress. >>>>> >>>>> A draft deployment guide for this distributed cluster can be found in >>>>> [1]. >>>>> >>>>> Note that during the deployment, I came across an issue with Database >>>>> connections and I have updated the issue [2]. >>>>> >>>>> [1]. >>>>> https://docs.google.com/a/wso2.com/document/d/1a_J7apt_lqJNCnuJUVwMD_JxBgV3MIUnnpQxfwmaoqU/edit# >>>>> [2]. https://wso2.org/jira/browse/BAM-522 >>>>> >>>>> PS: Thanks BAM Team for the help in setting this up. >>>>> >>>>> -- >>>>> ~Regards >>>>> *Manisha Eleperuma* >>>>> Software Engineer >>>>> WSO2, Inc.: http://wso2.com >>>>> lean.enterprise.middleware >>>>> >>>>> * >>>>> * >>>>> * >>>>> * >>>>> >>>>> >>>> >>>> >>>> -- >>>> Regards, >>>> >>>> Tharindu >>>> >>>> blog: http://mackiemathew.com/ >>>> M: +94777759908 >>>> >>>> >>> >>> >>> -- >>> ~Regards >>> *Manisha Eleperuma* >>> Software Engineer >>> WSO2, Inc.: http://wso2.com >>> lean.enterprise.middleware >>> >>> * >>> * >>> * >>> * >>> >>> >> >> >> -- >> Regards, >> >> Tharindu >> >> blog: http://mackiemathew.com/ >> M: +94777759908 >> >> > > > -- > ~Regards > *Manisha Eleperuma* > Software Engineer > WSO2, Inc.: http://wso2.com > lean.enterprise.middleware > > * > * > > -- Regards, Tharindu blog: http://mackiemathew.com/ M: +94777759908
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
