This sounds like you will have about 500 million rows in your database after 6 months. To my mind, this is at the level of inconvenient for a conventional database, but hardly impossible.
HBase will definitely hold this much data. It would probably help you to do some slightly clever tricks to use wider tables. The openTSDB project [1] is an excellent example of how this can be done with metric data. [1] http://opentsdb.net/ On Wed, Sep 14, 2011 at 6:08 AM, stable29 <[email protected]> wrote: > Currently I am using RDBMS in my project. My project basically monitor > servers. It has to collect the information from all the servers ( no. of > servers could be very huge) every 5 minutes and store it in the database. > storing all the servers information ( around 10000 rows will be inserted > with logical comparison) within 5 minutes itself is challenging for RDBMS > database. we have to maintain around 6 months data in the database. > So,that’s why the data amount becomes very huge. This is the primary > requirement of our project and if it works good then this could be used > widely. Basically I like to know if at all the Hbase could enhance the > writing and reading time of the database and could be used to scale the > database in great respect. > > -- > View this message in context: > http://apache-hbase.679495.n3.nabble.com/Should-I-use-HBASE-tp3335385p3335385.html > Sent from the HBase - Developer mailing list archive at Nabble.com.
