RE: Region hot spotting
We are not fetching single row back. Hashing really helped, the data is now almost equally split between the servers. Thanks a lot. -Ajay -Original Message- From: Michael Segel [mailto:michael_se...@hotmail.com] Sent: Thursday, November 22, 2012 2:52 AM To: user@hbase.apache.org Subject: Re: Region hot spotting Salting is not a good idea and I don't know why people suggest it. Case in point you want to fetch a single row/record back. Because the salt is arbitrary, you will need to send N number of get()s one for each salt value. Doing a simple one way hash of the data, even appending the data, would be a better idea. Note that if you are worried about key length, you can do the hash and take the first N bytes and then append the row to it. It should give you enough of a spread of hash values that you don't have to worry about hotspots. HTH -Mike On Nov 21, 2012, at 2:44 AM, ramkrishna vasudevan wrote: > Hi > This link is pretty much useful. But still there too it says if you dont > pre split you need to wait for the salting to help you from hotspotting > till the region gets splitted. > > Mohammad just pointing this to say the usefulness of presplitting > definitely your's is a good pointer to Ajay. :) > > Regards > Ram > > On Wed, Nov 21, 2012 at 1:59 PM, Mohammad Tariq wrote: > >> Hello Ajay, >> >> You can use 'salting' if you don't want to presplit your table. You might >> this link useful : >> >> http://blog.sematext.com/2012/04/09/hbasewd-avoid-regionserver-hotspotting-d espite-writing-records-with-sequential-keys/ >> >> HTH >> >> Regards, >>Mohammad Tariq >> >> >> >> On Wed, Nov 21, 2012 at 1:49 PM, ramkrishna vasudevan < >> ramkrishna.s.vasude...@gmail.com> wrote: >> >>> Hotspotting is bound to happen until the region starts splitting and gets >>> assigned to diff region servers. >>> >>> Regards >>> Ram >>> >>> On Wed, Nov 21, 2012 at 12:49 PM, Ajay Bhosle >>> wrote: >>> >>>> Hi, >>>> >>>> >>>> >>>> I am inserting some data in hbase which is getting hot spotted in a >>>> particular server. The format of the row key is (0 or >>>> 1)|[timestamp]_[sequence]. Basically I want to add log information to >>>> hbase >>>> and search the records based on range of dates. >>>> >>>> >>>> >>>> Can someone suggest any configuration changes or any ideas on how the >> row >>>> key should be design. I do not want to specify the splits while >> creating >>>> table. >>>> >>>> >>>> >>>> Thanks >>>> >>>> Ajay >>>> >>>> >>>> >>>> >>>> The information contained in this electronic message (email) and any >>>> attachments to this email are intended for the exclusive use of the >>>> addressee(s) and access to this email by any one else is unauthorised. >>> The >>>> email may contain proprietary, confidential or privileged information >> or >>>> information relating to Reliance Group. If you are not the intended >>>> recipient, please notify the sender by telephone, fax, or return email >>> and >>>> delete this communication and any attachments thereto, immediately from >>>> your computer. Any dissemination, distribution, or copying of this >>>> communication and the attachments thereto (in whole or part), in any >>>> manner, is strictly prohibited and actionable at law. The recipient >>>> acknowledges that emails are susceptible to alteration and their >>> integrity >>>> can not be guaranteed and that Company does not guarantee that any >> e-mail >>>> is virus-free and accept no liability for any damage caused by any >> virus >>>> transmitted by this email. >>>> >>> >> The information contained in this electronic message (email) and any attachments to this email are intended for the exclusive use of the addressee(s) and access to this email by any one else is unauthorised. The email may contain proprietary, confidential or privileged information or information relating to Reliance Group. If you are not the intended recipient, please notify the sender by telephone, fax, or return email and delete this communication and any attachments thereto, immediately from your computer. Any dissemination, distribution, or copying of this communication and the attachments thereto (in whole or part), in any manner, is strictly prohibited and actionable at law. The recipient acknowledges that emails are susceptible to alteration and their integrity can not be guaranteed and that Company does not guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.
Re: Region hot spotting
Good point Mike. Regards, Mohammad Tariq On Thu, Nov 22, 2012 at 2:51 AM, Michael Segel wrote: > Salting is not a good idea and I don't know why people suggest it. > > Case in point you want to fetch a single row/record back. Because the > salt is arbitrary, you will need to send N number of get()s one for each > salt value. > Doing a simple one way hash of the data, even appending the data, would be > a better idea. Note that if you are worried about key length, you can do > the hash and take the first N bytes and then append the row to it. It > should give you enough of a spread of hash values that you don't have to > worry about hotspots. > > HTH > > -Mike > > On Nov 21, 2012, at 2:44 AM, ramkrishna vasudevan < > ramkrishna.s.vasude...@gmail.com> wrote: > > > Hi > > This link is pretty much useful. But still there too it says if you dont > > pre split you need to wait for the salting to help you from hotspotting > > till the region gets splitted. > > > > Mohammad just pointing this to say the usefulness of presplitting > > definitely your's is a good pointer to Ajay. :) > > > > Regards > > Ram > > > > On Wed, Nov 21, 2012 at 1:59 PM, Mohammad Tariq > wrote: > > > >> Hello Ajay, > >> > >> You can use 'salting' if you don't want to presplit your table. You > might > >> this link useful : > >> > >> > http://blog.sematext.com/2012/04/09/hbasewd-avoid-regionserver-hotspotting-despite-writing-records-with-sequential-keys/ > >> > >> HTH > >> > >> Regards, > >>Mohammad Tariq > >> > >> > >> > >> On Wed, Nov 21, 2012 at 1:49 PM, ramkrishna vasudevan < > >> ramkrishna.s.vasude...@gmail.com> wrote: > >> > >>> Hotspotting is bound to happen until the region starts splitting and > gets > >>> assigned to diff region servers. > >>> > >>> Regards > >>> Ram > >>> > >>> On Wed, Nov 21, 2012 at 12:49 PM, Ajay Bhosle > >>> wrote: > >>> > Hi, > > > > I am inserting some data in hbase which is getting hot spotted in a > particular server. The format of the row key is (0 or > 1)|[timestamp]_[sequence]. Basically I want to add log information to > hbase > and search the records based on range of dates. > > > > Can someone suggest any configuration changes or any ideas on how the > >> row > key should be design. I do not want to specify the splits while > >> creating > table. > > > > Thanks > > Ajay > > > > > The information contained in this electronic message (email) and any > attachments to this email are intended for the exclusive use of the > addressee(s) and access to this email by any one else is unauthorised. > >>> The > email may contain proprietary, confidential or privileged information > >> or > information relating to Reliance Group. If you are not the intended > recipient, please notify the sender by telephone, fax, or return email > >>> and > delete this communication and any attachments thereto, immediately > from > your computer. Any dissemination, distribution, or copying of this > communication and the attachments thereto (in whole or part), in any > manner, is strictly prohibited and actionable at law. The recipient > acknowledges that emails are susceptible to alteration and their > >>> integrity > can not be guaranteed and that Company does not guarantee that any > >> e-mail > is virus-free and accept no liability for any damage caused by any > >> virus > transmitted by this email. > > >>> > >> > >
Re: Region hot spotting
Salting is not a good idea and I don't know why people suggest it. Case in point you want to fetch a single row/record back. Because the salt is arbitrary, you will need to send N number of get()s one for each salt value. Doing a simple one way hash of the data, even appending the data, would be a better idea. Note that if you are worried about key length, you can do the hash and take the first N bytes and then append the row to it. It should give you enough of a spread of hash values that you don't have to worry about hotspots. HTH -Mike On Nov 21, 2012, at 2:44 AM, ramkrishna vasudevan wrote: > Hi > This link is pretty much useful. But still there too it says if you dont > pre split you need to wait for the salting to help you from hotspotting > till the region gets splitted. > > Mohammad just pointing this to say the usefulness of presplitting > definitely your's is a good pointer to Ajay. :) > > Regards > Ram > > On Wed, Nov 21, 2012 at 1:59 PM, Mohammad Tariq wrote: > >> Hello Ajay, >> >> You can use 'salting' if you don't want to presplit your table. You might >> this link useful : >> >> http://blog.sematext.com/2012/04/09/hbasewd-avoid-regionserver-hotspotting-despite-writing-records-with-sequential-keys/ >> >> HTH >> >> Regards, >>Mohammad Tariq >> >> >> >> On Wed, Nov 21, 2012 at 1:49 PM, ramkrishna vasudevan < >> ramkrishna.s.vasude...@gmail.com> wrote: >> >>> Hotspotting is bound to happen until the region starts splitting and gets >>> assigned to diff region servers. >>> >>> Regards >>> Ram >>> >>> On Wed, Nov 21, 2012 at 12:49 PM, Ajay Bhosle >>> wrote: >>> Hi, I am inserting some data in hbase which is getting hot spotted in a particular server. The format of the row key is (0 or 1)|[timestamp]_[sequence]. Basically I want to add log information to hbase and search the records based on range of dates. Can someone suggest any configuration changes or any ideas on how the >> row key should be design. I do not want to specify the splits while >> creating table. Thanks Ajay The information contained in this electronic message (email) and any attachments to this email are intended for the exclusive use of the addressee(s) and access to this email by any one else is unauthorised. >>> The email may contain proprietary, confidential or privileged information >> or information relating to Reliance Group. If you are not the intended recipient, please notify the sender by telephone, fax, or return email >>> and delete this communication and any attachments thereto, immediately from your computer. Any dissemination, distribution, or copying of this communication and the attachments thereto (in whole or part), in any manner, is strictly prohibited and actionable at law. The recipient acknowledges that emails are susceptible to alteration and their >>> integrity can not be guaranteed and that Company does not guarantee that any >> e-mail is virus-free and accept no liability for any damage caused by any >> virus transmitted by this email. >>> >>
Re: Region hot spotting
Hi there- If he's using monotonically increasing keys the pre splits won't help because the same region is going to get all the writes. http://hbase.apache.org/book.html#rowkey.design On 11/21/12 12:33 PM, "Suraj Varma" wrote: >Ajay: >Why would you not want to specify splits while creating table? If your >0-10 prefix is at random ... why not pre-split with that? > >Without presplitting, as Ram says, you cannot avoid region hotspotting >until table starts automatic splits. >--S > >On Wed, Nov 21, 2012 at 3:46 AM, Ajay Bhosle > wrote: >> Thanks for your comments, >> >> I am already prefixing the timestamp with integer in range of 1..10, >>also >> the hbase.hregion.max.filesize is defined as 256 MB. Still it is hot >> spotting. >> >> Thanks >> Ajay >> >> -Original Message- >> From: ramkrishna vasudevan [mailto:ramkrishna.s.vasude...@gmail.com] >> Sent: Wednesday, November 21, 2012 2:14 PM >> To: user@hbase.apache.org >> Subject: Re: Region hot spotting >> >> Hi >> This link is pretty much useful. But still there too it says if you >>dont >> pre split you need to wait for the salting to help you from hotspotting >> till the region gets splitted. >> >> Mohammad just pointing this to say the usefulness of presplitting >> definitely your's is a good pointer to Ajay. :) >> >> Regards >> Ram >> >> On Wed, Nov 21, 2012 at 1:59 PM, Mohammad Tariq >>wrote: >> >>> Hello Ajay, >>> >>> You can use 'salting' if you don't want to presplit your table. You >>>might >>> this link useful : >>> >>> >> >>http://blog.sematext.com/2012/04/09/hbasewd-avoid-regionserver-hotspottin >>g-d >> espite-writing-records-with-sequential-keys/ >>> >>> HTH >>> >>> Regards, >>> Mohammad Tariq >>> >>> >>> >>> On Wed, Nov 21, 2012 at 1:49 PM, ramkrishna vasudevan < >>> ramkrishna.s.vasude...@gmail.com> wrote: >>> >>> > Hotspotting is bound to happen until the region starts splitting and >> gets >>> > assigned to diff region servers. >>> > >>> > Regards >>> > Ram >>> > >>> > On Wed, Nov 21, 2012 at 12:49 PM, Ajay Bhosle >>> > wrote: >>> > >>> > > Hi, >>> > > >>> > > >>> > > >>> > > I am inserting some data in hbase which is getting hot spotted in a >>> > > particular server. The format of the row key is (0 or >>> > > 1)|[timestamp]_[sequence]. Basically I want to add log >>>information to >>> > > hbase >>> > > and search the records based on range of dates. >>> > > >>> > > >>> > > >>> > > Can someone suggest any configuration changes or any ideas on how >>>the >>> row >>> > > key should be design. I do not want to specify the splits while >>> creating >>> > > table. >>> > > >>> > > >>> > > >>> > > Thanks >>> > > >>> > > Ajay >>> > > >>> > > >>> > > >>> > > >>> > > The information contained in this electronic message (email) and >>>any >>> > > attachments to this email are intended for the exclusive use of the >>> > > addressee(s) and access to this email by any one else is >>>unauthorised. >>> > The >>> > > email may contain proprietary, confidential or privileged >>>information >>> or >>> > > information relating to Reliance Group. If you are not the intended >>> > > recipient, please notify the sender by telephone, fax, or return >>>email >>> > and >>> > > delete this communication and any attachments thereto, immediately >> from >>> > > your computer. Any dissemination, distribution, or copying of this >>> > > communication and the attachments thereto (in whole or part), in >>>any >>> > > manner, is strictly prohibited and actionable at law. The recipient >>> > > acknowledges that emails are susceptible to alteration and their >>> > integrity >>> > > can not be guaranteed and that Company does not guarantee that any >>> e-mail >>> > > is virus-free and accept no liability for any damage caused by any >>> virus >>> > > transmitted by this email. >>> > > >>> > >>> >> >> >> >> >> The information contained in this electronic message (email) and any >>attachments to this email are intended for the exclusive use of the >>addressee(s) and access to this email by any one else is unauthorised. >>The email may contain proprietary, confidential or privileged >>information or information relating to Reliance Group. If you are not >>the intended recipient, please notify the sender by telephone, fax, or >>return email and delete this communication and any attachments thereto, >>immediately from your computer. Any dissemination, distribution, or >>copying of this communication and the attachments thereto (in whole or >>part), in any manner, is strictly prohibited and actionable at law. The >>recipient acknowledges that emails are susceptible to alteration and >>their integrity can not be guaranteed and that Company does not >>guarantee that any e-mail is virus-free and accept no liability for any >>damage caused by any virus transmitted by this email. >
Re: Region hot spotting
Hello again, Just a small query. Is your data getting streamed continuously or are you making use of bulk load. In case of latter, I don't find any harm in creating pre-splitted tables. Regards, Mohammad Tariq On Wed, Nov 21, 2012 at 2:14 PM, ramkrishna vasudevan < ramkrishna.s.vasude...@gmail.com> wrote: > Hi > This link is pretty much useful. But still there too it says if you dont > pre split you need to wait for the salting to help you from hotspotting > till the region gets splitted. > > Mohammad just pointing this to say the usefulness of presplitting > definitely your's is a good pointer to Ajay. :) > > Regards > Ram > > On Wed, Nov 21, 2012 at 1:59 PM, Mohammad Tariq > wrote: > > > Hello Ajay, > > > > You can use 'salting' if you don't want to presplit your table. You > might > > this link useful : > > > > > http://blog.sematext.com/2012/04/09/hbasewd-avoid-regionserver-hotspotting-despite-writing-records-with-sequential-keys/ > > > > HTH > > > > Regards, > > Mohammad Tariq > > > > > > > > On Wed, Nov 21, 2012 at 1:49 PM, ramkrishna vasudevan < > > ramkrishna.s.vasude...@gmail.com> wrote: > > > > > Hotspotting is bound to happen until the region starts splitting and > gets > > > assigned to diff region servers. > > > > > > Regards > > > Ram > > > > > > On Wed, Nov 21, 2012 at 12:49 PM, Ajay Bhosle > > > wrote: > > > > > > > Hi, > > > > > > > > > > > > > > > > I am inserting some data in hbase which is getting hot spotted in a > > > > particular server. The format of the row key is (0 or > > > > 1)|[timestamp]_[sequence]. Basically I want to add log information > to > > > > hbase > > > > and search the records based on range of dates. > > > > > > > > > > > > > > > > Can someone suggest any configuration changes or any ideas on how the > > row > > > > key should be design. I do not want to specify the splits while > > creating > > > > table. > > > > > > > > > > > > > > > > Thanks > > > > > > > > Ajay > > > > > > > > > > > > > > > > > > > > The information contained in this electronic message (email) and any > > > > attachments to this email are intended for the exclusive use of the > > > > addressee(s) and access to this email by any one else is > unauthorised. > > > The > > > > email may contain proprietary, confidential or privileged information > > or > > > > information relating to Reliance Group. If you are not the intended > > > > recipient, please notify the sender by telephone, fax, or return > email > > > and > > > > delete this communication and any attachments thereto, immediately > from > > > > your computer. Any dissemination, distribution, or copying of this > > > > communication and the attachments thereto (in whole or part), in any > > > > manner, is strictly prohibited and actionable at law. The recipient > > > > acknowledges that emails are susceptible to alteration and their > > > integrity > > > > can not be guaranteed and that Company does not guarantee that any > > e-mail > > > > is virus-free and accept no liability for any damage caused by any > > virus > > > > transmitted by this email. > > > > > > > > > >
Re: Region hot spotting
Ajay: Why would you not want to specify splits while creating table? If your 0-10 prefix is at random ... why not pre-split with that? Without presplitting, as Ram says, you cannot avoid region hotspotting until table starts automatic splits. --S On Wed, Nov 21, 2012 at 3:46 AM, Ajay Bhosle wrote: > Thanks for your comments, > > I am already prefixing the timestamp with integer in range of 1..10, also > the hbase.hregion.max.filesize is defined as 256 MB. Still it is hot > spotting. > > Thanks > Ajay > > -Original Message- > From: ramkrishna vasudevan [mailto:ramkrishna.s.vasude...@gmail.com] > Sent: Wednesday, November 21, 2012 2:14 PM > To: user@hbase.apache.org > Subject: Re: Region hot spotting > > Hi > This link is pretty much useful. But still there too it says if you dont > pre split you need to wait for the salting to help you from hotspotting > till the region gets splitted. > > Mohammad just pointing this to say the usefulness of presplitting > definitely your's is a good pointer to Ajay. :) > > Regards > Ram > > On Wed, Nov 21, 2012 at 1:59 PM, Mohammad Tariq wrote: > >> Hello Ajay, >> >> You can use 'salting' if you don't want to presplit your table. You might >> this link useful : >> >> > http://blog.sematext.com/2012/04/09/hbasewd-avoid-regionserver-hotspotting-d > espite-writing-records-with-sequential-keys/ >> >> HTH >> >> Regards, >> Mohammad Tariq >> >> >> >> On Wed, Nov 21, 2012 at 1:49 PM, ramkrishna vasudevan < >> ramkrishna.s.vasude...@gmail.com> wrote: >> >> > Hotspotting is bound to happen until the region starts splitting and > gets >> > assigned to diff region servers. >> > >> > Regards >> > Ram >> > >> > On Wed, Nov 21, 2012 at 12:49 PM, Ajay Bhosle >> > wrote: >> > >> > > Hi, >> > > >> > > >> > > >> > > I am inserting some data in hbase which is getting hot spotted in a >> > > particular server. The format of the row key is (0 or >> > > 1)|[timestamp]_[sequence]. Basically I want to add log information to >> > > hbase >> > > and search the records based on range of dates. >> > > >> > > >> > > >> > > Can someone suggest any configuration changes or any ideas on how the >> row >> > > key should be design. I do not want to specify the splits while >> creating >> > > table. >> > > >> > > >> > > >> > > Thanks >> > > >> > > Ajay >> > > >> > > >> > > >> > > >> > > The information contained in this electronic message (email) and any >> > > attachments to this email are intended for the exclusive use of the >> > > addressee(s) and access to this email by any one else is unauthorised. >> > The >> > > email may contain proprietary, confidential or privileged information >> or >> > > information relating to Reliance Group. If you are not the intended >> > > recipient, please notify the sender by telephone, fax, or return email >> > and >> > > delete this communication and any attachments thereto, immediately > from >> > > your computer. Any dissemination, distribution, or copying of this >> > > communication and the attachments thereto (in whole or part), in any >> > > manner, is strictly prohibited and actionable at law. The recipient >> > > acknowledges that emails are susceptible to alteration and their >> > integrity >> > > can not be guaranteed and that Company does not guarantee that any >> e-mail >> > > is virus-free and accept no liability for any damage caused by any >> virus >> > > transmitted by this email. >> > > >> > >> > > > > > The information contained in this electronic message (email) and any > attachments to this email are intended for the exclusive use of the > addressee(s) and access to this email by any one else is unauthorised. The > email may contain proprietary, confidential or privileged information or > information relating to Reliance Group. If you are not the intended > recipient, please notify the sender by telephone, fax, or return email and > delete this communication and any attachments thereto, immediately from your > computer. Any dissemination, distribution, or copying of this communication > and the attachments thereto (in whole or part), in any manner, is strictly > prohibited and actionable at law. The recipient acknowledges that emails are > susceptible to alteration and their integrity can not be guaranteed and that > Company does not guarantee that any e-mail is virus-free and accept no > liability for any damage caused by any virus transmitted by this email.
RE: Region hot spotting
Thanks for your comments, I am already prefixing the timestamp with integer in range of 1..10, also the hbase.hregion.max.filesize is defined as 256 MB. Still it is hot spotting. Thanks Ajay -Original Message- From: ramkrishna vasudevan [mailto:ramkrishna.s.vasude...@gmail.com] Sent: Wednesday, November 21, 2012 2:14 PM To: user@hbase.apache.org Subject: Re: Region hot spotting Hi This link is pretty much useful. But still there too it says if you dont pre split you need to wait for the salting to help you from hotspotting till the region gets splitted. Mohammad just pointing this to say the usefulness of presplitting definitely your's is a good pointer to Ajay. :) Regards Ram On Wed, Nov 21, 2012 at 1:59 PM, Mohammad Tariq wrote: > Hello Ajay, > > You can use 'salting' if you don't want to presplit your table. You might > this link useful : > > http://blog.sematext.com/2012/04/09/hbasewd-avoid-regionserver-hotspotting-d espite-writing-records-with-sequential-keys/ > > HTH > > Regards, > Mohammad Tariq > > > > On Wed, Nov 21, 2012 at 1:49 PM, ramkrishna vasudevan < > ramkrishna.s.vasude...@gmail.com> wrote: > > > Hotspotting is bound to happen until the region starts splitting and gets > > assigned to diff region servers. > > > > Regards > > Ram > > > > On Wed, Nov 21, 2012 at 12:49 PM, Ajay Bhosle > > wrote: > > > > > Hi, > > > > > > > > > > > > I am inserting some data in hbase which is getting hot spotted in a > > > particular server. The format of the row key is (0 or > > > 1)|[timestamp]_[sequence]. Basically I want to add log information to > > > hbase > > > and search the records based on range of dates. > > > > > > > > > > > > Can someone suggest any configuration changes or any ideas on how the > row > > > key should be design. I do not want to specify the splits while > creating > > > table. > > > > > > > > > > > > Thanks > > > > > > Ajay > > > > > > > > > > > > > > > The information contained in this electronic message (email) and any > > > attachments to this email are intended for the exclusive use of the > > > addressee(s) and access to this email by any one else is unauthorised. > > The > > > email may contain proprietary, confidential or privileged information > or > > > information relating to Reliance Group. If you are not the intended > > > recipient, please notify the sender by telephone, fax, or return email > > and > > > delete this communication and any attachments thereto, immediately from > > > your computer. Any dissemination, distribution, or copying of this > > > communication and the attachments thereto (in whole or part), in any > > > manner, is strictly prohibited and actionable at law. The recipient > > > acknowledges that emails are susceptible to alteration and their > > integrity > > > can not be guaranteed and that Company does not guarantee that any > e-mail > > > is virus-free and accept no liability for any damage caused by any > virus > > > transmitted by this email. > > > > > > The information contained in this electronic message (email) and any attachments to this email are intended for the exclusive use of the addressee(s) and access to this email by any one else is unauthorised. The email may contain proprietary, confidential or privileged information or information relating to Reliance Group. If you are not the intended recipient, please notify the sender by telephone, fax, or return email and delete this communication and any attachments thereto, immediately from your computer. Any dissemination, distribution, or copying of this communication and the attachments thereto (in whole or part), in any manner, is strictly prohibited and actionable at law. The recipient acknowledges that emails are susceptible to alteration and their integrity can not be guaranteed and that Company does not guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.
Re: Region hot spotting
Hi This link is pretty much useful. But still there too it says if you dont pre split you need to wait for the salting to help you from hotspotting till the region gets splitted. Mohammad just pointing this to say the usefulness of presplitting definitely your's is a good pointer to Ajay. :) Regards Ram On Wed, Nov 21, 2012 at 1:59 PM, Mohammad Tariq wrote: > Hello Ajay, > > You can use 'salting' if you don't want to presplit your table. You might > this link useful : > > http://blog.sematext.com/2012/04/09/hbasewd-avoid-regionserver-hotspotting-despite-writing-records-with-sequential-keys/ > > HTH > > Regards, > Mohammad Tariq > > > > On Wed, Nov 21, 2012 at 1:49 PM, ramkrishna vasudevan < > ramkrishna.s.vasude...@gmail.com> wrote: > > > Hotspotting is bound to happen until the region starts splitting and gets > > assigned to diff region servers. > > > > Regards > > Ram > > > > On Wed, Nov 21, 2012 at 12:49 PM, Ajay Bhosle > > wrote: > > > > > Hi, > > > > > > > > > > > > I am inserting some data in hbase which is getting hot spotted in a > > > particular server. The format of the row key is (0 or > > > 1)|[timestamp]_[sequence]. Basically I want to add log information to > > > hbase > > > and search the records based on range of dates. > > > > > > > > > > > > Can someone suggest any configuration changes or any ideas on how the > row > > > key should be design. I do not want to specify the splits while > creating > > > table. > > > > > > > > > > > > Thanks > > > > > > Ajay > > > > > > > > > > > > > > > The information contained in this electronic message (email) and any > > > attachments to this email are intended for the exclusive use of the > > > addressee(s) and access to this email by any one else is unauthorised. > > The > > > email may contain proprietary, confidential or privileged information > or > > > information relating to Reliance Group. If you are not the intended > > > recipient, please notify the sender by telephone, fax, or return email > > and > > > delete this communication and any attachments thereto, immediately from > > > your computer. Any dissemination, distribution, or copying of this > > > communication and the attachments thereto (in whole or part), in any > > > manner, is strictly prohibited and actionable at law. The recipient > > > acknowledges that emails are susceptible to alteration and their > > integrity > > > can not be guaranteed and that Company does not guarantee that any > e-mail > > > is virus-free and accept no liability for any damage caused by any > virus > > > transmitted by this email. > > > > > >
Re: Region hot spotting
Hello Ajay, You can use 'salting' if you don't want to presplit your table. You might this link useful : http://blog.sematext.com/2012/04/09/hbasewd-avoid-regionserver-hotspotting-despite-writing-records-with-sequential-keys/ HTH Regards, Mohammad Tariq On Wed, Nov 21, 2012 at 1:49 PM, ramkrishna vasudevan < ramkrishna.s.vasude...@gmail.com> wrote: > Hotspotting is bound to happen until the region starts splitting and gets > assigned to diff region servers. > > Regards > Ram > > On Wed, Nov 21, 2012 at 12:49 PM, Ajay Bhosle > wrote: > > > Hi, > > > > > > > > I am inserting some data in hbase which is getting hot spotted in a > > particular server. The format of the row key is (0 or > > 1)|[timestamp]_[sequence]. Basically I want to add log information to > > hbase > > and search the records based on range of dates. > > > > > > > > Can someone suggest any configuration changes or any ideas on how the row > > key should be design. I do not want to specify the splits while creating > > table. > > > > > > > > Thanks > > > > Ajay > > > > > > > > > > The information contained in this electronic message (email) and any > > attachments to this email are intended for the exclusive use of the > > addressee(s) and access to this email by any one else is unauthorised. > The > > email may contain proprietary, confidential or privileged information or > > information relating to Reliance Group. If you are not the intended > > recipient, please notify the sender by telephone, fax, or return email > and > > delete this communication and any attachments thereto, immediately from > > your computer. Any dissemination, distribution, or copying of this > > communication and the attachments thereto (in whole or part), in any > > manner, is strictly prohibited and actionable at law. The recipient > > acknowledges that emails are susceptible to alteration and their > integrity > > can not be guaranteed and that Company does not guarantee that any e-mail > > is virus-free and accept no liability for any damage caused by any virus > > transmitted by this email. > > >
Re: Region hot spotting
Hotspotting is bound to happen until the region starts splitting and gets assigned to diff region servers. Regards Ram On Wed, Nov 21, 2012 at 12:49 PM, Ajay Bhosle wrote: > Hi, > > > > I am inserting some data in hbase which is getting hot spotted in a > particular server. The format of the row key is (0 or > 1)|[timestamp]_[sequence]. Basically I want to add log information to > hbase > and search the records based on range of dates. > > > > Can someone suggest any configuration changes or any ideas on how the row > key should be design. I do not want to specify the splits while creating > table. > > > > Thanks > > Ajay > > > > > The information contained in this electronic message (email) and any > attachments to this email are intended for the exclusive use of the > addressee(s) and access to this email by any one else is unauthorised. The > email may contain proprietary, confidential or privileged information or > information relating to Reliance Group. If you are not the intended > recipient, please notify the sender by telephone, fax, or return email and > delete this communication and any attachments thereto, immediately from > your computer. Any dissemination, distribution, or copying of this > communication and the attachments thereto (in whole or part), in any > manner, is strictly prohibited and actionable at law. The recipient > acknowledges that emails are susceptible to alteration and their integrity > can not be guaranteed and that Company does not guarantee that any e-mail > is virus-free and accept no liability for any damage caused by any virus > transmitted by this email. >
Region hot spotting
Hi, I am inserting some data in hbase which is getting hot spotted in a particular server. The format of the row key is (0 or 1)|[timestamp]_[sequence]. Basically I want to add log information to hbase and search the records based on range of dates. Can someone suggest any configuration changes or any ideas on how the row key should be design. I do not want to specify the splits while creating table. Thanks Ajay The information contained in this electronic message (email) and any attachments to this email are intended for the exclusive use of the addressee(s) and access to this email by any one else is unauthorised. The email may contain proprietary, confidential or privileged information or information relating to Reliance Group. If you are not the intended recipient, please notify the sender by telephone, fax, or return email and delete this communication and any attachments thereto, immediately from your computer. Any dissemination, distribution, or copying of this communication and the attachments thereto (in whole or part), in any manner, is strictly prohibited and actionable at law. The recipient acknowledges that emails are susceptible to alteration and their integrity can not be guaranteed and that Company does not guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.
