Filed https://issues.apache.org/jira/browse/HBASE-7805
Test case attached
It occurs only if the table has a region observer coprocessor.
James
On 02/09/2013 11:04 AM, lars hofhansl wrote:
If I execute in parallel multiple scans to different parts of the same region,
they appear to be
Yes, the limit is at 65535.
/David
On Sun, Feb 10, 2013 at 4:22 AM, Marcos Ortiz mlor...@uci.cu wrote:
Did you increase the number of open files in your
/etc/security/limits.conf in your system?
On 02/09/2013 09:17 PM, David Koch wrote:
Hello,
Thank you for your reply, I checked the
On Sun, Feb 10, 2013 at 6:21 PM, David Koch ogd...@googlemail.com wrote:
problems but could not find any. The settings
increase the u limit for the user using you are starting the hadoop and
hbase services, in os
∞
Shashwat Shriparv
Hi Jean,
Steps need to followed during migration of namenode.
1.Make New Server with same hostname.
2.Install hadoop
3.copy the metadata from old server and paste it in new server.
4.Make sure all the datanodes are down.
5.Stop old namenode
6.Start New namenode with old metadata.
7.if it come up
Like I said, the maximum permissible number of filehandlers is set to 65535
for users hbase (the one who starts HBase), mapred and hdfs
The too many files warning occurs on the region servers but not on the HDFS
namenode.
/David
On Sun, Feb 10, 2013 at 3:53 PM, shashwat shriparv
The master does not have any local storage in a fully distributed
setup, so the transfer can also be as easy as starting the new master
on the new host and failing it over (by killing the original one).
The NameNode move part is the one that gets tricky. HBase may store NN
URLs in its ZK
Back to BulkDeleteEndpoint, i got it to work but why are the scanner.next()
calls executing on the Priority handler queue ?
Varun
On Sat, Feb 9, 2013 at 8:46 AM, lars hofhansl la...@apache.org wrote:
The answer is probably :)
It's disabled in 0.96 by default. Check out HBASE-7008 (
ColumnPaginationFilter wouldn't load the entire row into memory:
public ReturnCode filterKeyValue(KeyValue v)
{
if(count = offset + limit)
{
return ReturnCode.NEXT_ROW;
}
Cheers
On Sat, Feb 9, 2013 at 8:53 PM, Varun Sharma va...@pinterest.com wrote:
Hi,
If I am
Hi Joarder,
Welcome to the HBase world. Let me take some time to address your
questions the best I can:
1. How often you are facing Region or Table Hotspotting in HBase
production systems? --- Hotspotting is not something that just happens.
This is usually caused by bad key design and
Hi Kevin,
Thanks a lot for your great answers.
Regarding Q5. To clarify,
lets say Facebook is using HBase for the integrated messaging/chat/email
system in a very large-scale setup. And schema design of such system can
change over the years (even over the months). Workload patterns may also
Hi David,
Have you changed anything on the configurations related to compactions?
If there are more store files created and if the compactions are not run
frequently we end up in this problem. Atleast there will be a consistent
increase in the file handler count.
Could you run compactions
Matt Corgan summarized the pro and con of having large number of regions
here:
https://issues.apache.org/jira/browse/HBASE-7667?focusedCommentId=13575024page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13575024
Cheers
On Sun, Feb 10, 2013 at 7:43 PM, Joarder KAMAL
The most common cause for hotspotting is inserting rows with monotonically
increasing row keys.
In that case only the last region will get the writes and no amount of
splitting will fix that (only one region serer will hold the last region of the
table regardless of how small it is).
There are
I think it might be reason for the splits. From 0.94.0, seems the default
split policy has changes
http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/regionserver/ConstantSizeRegionSplitPolicy.html
On Sat, Feb 9, 2013 at 3:37 PM, ramkrishna vasudevan
ramkrishna.s.vasude...@gmail.com
Thanks Lars for explaining the reasons for hotspotting and key design
techniques.
Just wondering, is it possible to alter key design (e.g. from sequential
keys to salt keys) at run time in the production system? What are the
impacts?
To Ted,
Thanks a lot for point out at [HBASE-7667]. Interesting
15 matches
Mail list logo
