Hi, if you want to stick to MySQL I see two options:
1) You could try to batch your writes. The DbWriterBolt would buffer some writes (e.g.) thousand and write them in batch mode. This is usually much faster. However your database is not always up to date. 2) You could try to shrad you database and have several DbWriter bolts, each writing to its own data base. You should then use a fieldsGrouping to ensure the data always end up in the right data base. Cheers, klaus On Wed, Feb 26, 2014 at 2:38 PM, masoom alam <[email protected]> wrote: > Dear All, > > Have any body worked on the configurations/optimizations needed generally > for using STORM with MYSQL. Our scenario stores data in MYSQL tables, but > as the data rate increases MYSQL starts responding very slow (in some cases > connection refused error), resulting in DBWriterBolt to slowdown. All the > Topology is bottleneck by this issue. We cannot increase the traffic at > source beyond a certain level, the reason we noted is that sink (MYSQL) or > the bolt adjacent to sink is performing slow. > > Any suggestion on how should we proceed will be highly appreciated. > > Thanks. > > >
