Re: [hbase] Refactoring idea: Move classes into Client, Master, and RegionServer packages

Sounds great. Lets do it first thing after the 0.16.x branch. St.Ack Bryan Duxbury wrote: All, I've been crawling around the HBase codebase for a little while now, and I think I have a proposal that would make it easer to find your way around in the codebase in general. I think that we sh

New DFSClient INFO-level logging

Billy Pearson over in hadoop-user reports that a bunch of new DFSClient INFO-level logging has started showing in hbase logs where previous there was none. HADOOP-1707 committed a few days ago added the below new LOG.infos: $ svn diff -r612699 DFSClient.java |grep LOG.info +LOG

Re: [ANNOUNCE] New Build Server

Nigel Daley wrote: Also, you'll notice that the patch queue has moved to: It's now an html page that has links to the issues in the queue. Very fancy! Let me know if you see a

Re: [VOTE] Release Hadoop 0.16.0 (candidate 1)

+0 from an hbase point of view. I deployed candidate 1 on a little hbase cluster of 4 machines. hbase ran on top of a distributed hdfs and mapreduce was used to run a distributed performance test. The performance test ran without issue. Whats in the way of a +1 is the fact that the scripts

Re: [VOTE] Release Hadoop 0.16.0 (candidate 1)

Changing my vote to a +1. I took another look at this. Its our (hbase's) fault that scripts are not executable and they probably shouldn't be being in the src dir of a packaged hadoop. The execute bit IS set on contrib/hbase/bin scripts. St.Ack stack wrote: +0 from an hbas

Re: [VOTE] Release Hadoop 0.16.0 (candidate 1)

here was a JIRA regarding this; will try to hunt that out. Thanks Hemanth On Thu, 2008-02-07 at 21:54 -0800, stack wrote: +0 from an hbase point of view. I deployed candidate 1 on a little hbase cluster of 4 machines. hbase ran on top of a distributed hdfs and mapreduce was used to run a d

Re: [hbase]How to distribute tables in hbase?

Hey Mafish: There is no such provision in hbase at the moment. Tables are distributed across the hbase cluster as it sees fit (We'd be interested in hearing more about why you need this facility). Regards helping us out w/ a HOWTO, that'd be great. Here's what we have at the moment: http:/

Re: [VOTE] Release Hadoop 0.16.1 (candidate 0)

Nigel Daley wrote: I've created a candidate build for Hadoop 0.16.1. Note that 3 HBase unit tests fail on my machine with this build, but I'm not sure that matters now that HBase is a sub-project with a separate release. Sorry about the failures. Is it too late to fix/remove them? As I und

Re: [VOTE] Release Hadoop 0.16.1 (candidate 0)

+1 from hbase perspective. I downloaded and ran a hbase load test using the HDFS from 0.16.1 as filesystem host and the MR from 0.16.1 as the loader. No anomalies in log. Ran like 0.16.0. On failing hbase tests, if we end up rolling a new candidate, could we just disable running of hbase u

Re: add incompatible flag to Jira

-Original Message- From: Nigel Daley [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 11, 2008 11:49 AM To: core-dev@hadoop.apache.org Subject: Re: add incompatible flag to Jira Good idea Rob. I think these 2 ideas are orthogonal. So I suggest these 2 additions to Jira: 1. an incompatib

Re: [VOTE] Hadoop 0.17.2 release candidate 0

+1 Ran hbase bulk upload successfully. Basic review of the documentation. St.Ack Owen O'Malley wrote: I've created Hadoop 0.17.2 rc 0 and uploaded it to: http://people.apache.org/~omalley/hadoop-0.17.2-rc0/ Please try it out. Thanks, Owen

Re: [VOTE] Hadoop 0.17.2 release candidate 1

+1 Have been using it today without issue doing hbase tests. St.Ack Owen O'Malley wrote: On Aug 12, 2008, at 10:52 PM, Owen O'Malley wrote: I've created Hadoop 0.17.2 rc 1 and uploaded it to: http://people.apache.org/~omalley/hadoop-0.17.2-rc1/ I should also mention that it felt too str

Re: [VOTE] Release 0.17.2.1 rc 0

+1 On Wed, Aug 20, 2008 at 4:06 PM, Owen O'Malley <[EMAIL PROTECTED]> wrote: > The 0.17.2 release only had the native code compiled in 32 bit. While that > matches our current release process, which considers the 64 bit optional, > some users would like to have the 64 bit libraries also. Since t

jython license review

Over in hbase-land we're evaluating replacements for our SQL-like shell (HBASE-487). An amended jython is a possibility but I was wondering if the license was Apache-amenable? It looks OK to me -- http://www.jython.org/Project/license.html -- but I'm not an expert. JRuby and beanshell for

Permissions on mail dir? Accessing mail archives throws "You don't have permission to access /mail/core-dev/ on this server."

Accessing hadoop and hbase mail archives, users get "You don't have permission to access /mail/core-dev/ on this server.". [EMAIL PROTECTED] /www/hadoop.apache.org]$ ls -lad mail core drwxrwxr-x 7 cutting hadoop 1024 Apr 3 15:36 core lrwxr-xr-x 1 root hadoop42 Jan 18 02:45 mail ->

licensing question

Can HBase include CPL licensed code? License seems fine (though I'm not a lawyer) and junit used to be in Hadoop and its CPL. But back in 2004, emails from Bryan Behlendorf would seem to rule out anything but Apache licenses been distributed off Apache servers: http://209.85.165.104/search?q

Re: licensing question

stack wrote: Can HBase include CPL licensed code? License seems fine (though I'm not a lawyer) and junit used to be in Hadoop and its CPL. Above statement about junit is a little off; hadoop currently bundles junit. Has the jar under lib and then a junit-X.X.X-LICENSE.txt file beside

Re: licensing question

Thanks for the opinion Owen (and thanks for the resource Nigel). St.Ack Owen O'Malley wrote: On Apr 16, 2008, at 8:10 AM, stack wrote: stack wrote: Can HBase include CPL licensed code? License seems fine (though I'm not a lawyer) and junit used to be in Hadoop and its CP

Re: Apache Hbase architecture

The wiki has an old architecture document that needs updating but should get you going: http://wiki.apache.org/hadoop/Hbase/HbaseArchitecture Also, HBase has its own mailing lists. HBase questions sit better there: http://hadoop.apache.org/hbase/mailing_lists.html#Developers Yours, St.Ack A

Re: [VOTE] Release Hadoop 0.16.4 (candidate 0)

+1 Downloaded it, checked documentation using lynx, did basic config. and made sure it all came up, and ran unit tests on a Fedora Core Release 6 box. St.Ack Nigel Daley wrote: I've created a candidate build for Hadoop 0.16.4. This fixes 4 issues in 0.16.3. Please download and try it out.

[ANN] hbase-0.1.2 release now available for download

hbase-0.1.2 resolves 27 issues including critical fixes for 'missing' edits and unreliable onlining/offlining of tables. We recommend all upgrade to this latest version. To download, please go to http://hadoop.apache.org/hbase/releases.html. Thanks to all who contributed to this release. You

Re: [jira] Commented: (HADOOP-3177) Expose DFSOutputStream.fsync API though the FileSystem interface

All tests are failing because they can't write /tmp: [exec] == [exec] == [exec] Applying patch. [exec] ==

Re: [VOTE] Release Hadoop 0.18.2 (candidate 0)

+1 - I took a run through the documentation and the UIs - Ran hbase unit tests and load test St.Ack Nigel Daley wrote: I have created a candidate build for Hadoop 0.18.2. This fixes 25 issues in 0.18.1. *** Please download and test it before the *** vote closes on Monday, November 3. htt

Re: short-circuiting HDFS reads

On Thu, Jan 8, 2009 at 10:39 AM, Doug Cutting wrote: > So this sort of optimization may only have a significant impact for jobs > whose maps do not produce much output. Don't forget the lowly non-MR users of HDFS. The short-circuit looks promising improving HDFS random access times. St.Ack

hudson and patch submissions

HADOOP-5079 has been in patch-submitted state with a few days now and the few times I've looked, hudson patch queue is empty. Maybe I missed a flag on the JIRA? Could a kind soul tell me where I went awry? Thanks, St.Ack

Re: Hadoop 0.19.1

The below proposes pushing a working append out 6 months or so. Can we have pointers as to what is meant by 'quality issues' in the below so we can make a more informed vote or is it just the hdfs issue posted against 0.19.1? Is it there also that we would find what is involved making append work

Re: Hadoop 0.19.1

On Tue, Feb 3, 2009 at 7:02 PM, Sanjay Radia wrote: > > Many in the team have come to the conclusion that complex projects like > append should be done on a separate branch in the first place and integrated > with trunk when the project is stable. > How do we determine when a feature on the bra

Re: Hadoop 0.19.1

On Thu, Jan 29, 2009 at 4:16 PM, Nigel Daley wrote: > > I would like to propose that we apply this same "fix" to sync in 0.19.1 and > 0.20.0. Since append requires the full semantics of sync, I propose we also > disable append (perhaps throw UnsupportedOperationException from API?). > Yes, this

[jira] Commented: (HADOOP-2604) [hbase] Create an HBase-specific MapFile implementation

[ https://issues.apache.org/jira/browse/HADOOP-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561173#action_12561173 ] stack commented on HADOOP-2604: --- Bloom Filters: + Turns out, particularly since the ch

[jira] Commented: (HADOOP-2654) CountingBloomFilter can overflow its storage

[ https://issues.apache.org/jira/browse/HADOOP-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561190#action_12561190 ] stack commented on HADOOP-2654: --- Patch looks good Stu. Let me apply it after we make

[jira] Commented: (HADOOP-1398) Add in-memory caching of data

[ https://issues.apache.org/jira/browse/HADOOP-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561191#action_12561191 ] stack commented on HADOOP-1398: --- Patch looks good Tom. I changed my mind since IRC

[jira] Commented: (HADOOP-2671) [HQL discuss] HQL spec definition

[ https://issues.apache.org/jira/browse/HADOOP-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561194#action_12561194 ] stack commented on HADOOP-2671: --- This is a useful looking table Edward in that its expl

[jira] Commented: (HADOOP-2591) [HQL] Addition of start command for execute the *.hql query file

[ https://issues.apache.org/jira/browse/HADOOP-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561195#action_12561195 ] stack commented on HADOOP-2591: --- Thanks for making the change Edward. I'll commit

[jira] Commented: (HADOOP-2668) [hbase] Documentation and improved logging so fact that hbase now requires migration comes as less of a surprise

[ https://issues.apache.org/jira/browse/HADOOP-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561200#action_12561200 ] stack commented on HADOOP-2668: --- This patch looks great. Shouldn't the '

[jira] Commented: (HADOOP-2554) Add a HTable get method that retrieves all versions of a particular column and row between two timestamps

[ https://issues.apache.org/jira/browse/HADOOP-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561221#action_12561221 ] stack commented on HADOOP-2554: --- So, sounds like you need to add another method to

[jira] Created: (HADOOP-2675) [hbase] Options not passed to rest/thrift

Reporter: stack Priority: Minor Billy Pearson over in HADOOP-2593 reported: {code} bin/hbase-daemon.sh start rest --bind=127.0.0.1 2008-01-21 03:11:14,916 INFO org.mortbay.http.HttpServer: Version Jetty/5.1.4 2008-01-21 03:11:14,941 INFO org.mortbay.util.Credential: Checking Resource

[jira] Resolved: (HADOOP-2593) Rest & thrift interfase can not be started and stop with hbase-daemon.sh

[ https://issues.apache.org/jira/browse/HADOOP-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HADOOP-2593. --- Resolution: Fixed Closed again. Opened HADOOP-2675 to address not passing of options rather than re-open

[jira] Updated: (HADOOP-2675) [hbase] Options not passed to rest/thrift

[ https://issues.apache.org/jira/browse/HADOOP-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2675: -- Attachment: args.patch If start or stop arg., we'd act on it without waiting to see if any options for

[jira] Commented: (HADOOP-2674) memcache size reported in debug log doesn ot add up

[ https://issues.apache.org/jira/browse/HADOOP-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561236#action_12561236 ] stack commented on HADOOP-2674: --- Do you have other examples of this Billy (You don&#x

[jira] Resolved: (HADOOP-2671) [HQL discuss] HQL spec definition

[ https://issues.apache.org/jira/browse/HADOOP-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HADOOP-2671. --- Resolution: Invalid Closing as invalid since Edward moved the comparison table to a better location, http

[jira] Commented: (HADOOP-2636) [hbase] Make cache flush triggering less simplistic

[ https://issues.apache.org/jira/browse/HADOOP-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561369#action_12561369 ] stack commented on HADOOP-2636: --- .bg [Copied from HADOOP-2674] Optional cache flushing

[jira] Commented: (HADOOP-2636) [hbase] Make cache flush triggering less simplistic

[ https://issues.apache.org/jira/browse/HADOOP-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561371#action_12561371 ] stack commented on HADOOP-2636: --- .bq [Copied from HADOOP-2674] ... size reported is

[jira] Created: (HADOOP-2685) [hbase] Delete table does not remove the table directory in the FS

Components: contrib/hbase Reporter: stack Priority: Minor I deleted a table but its directory stays behind in hdfs. See listing below. TestTable is the table removed. {code} $ ./bin/hadoop fs -lsr / /hbase123 2008-01-23 00:47rwxr-xr-x

[jira] Created: (HADOOP-2686) [hbase] Removed tables stick around

[hbase] Removed tables stick around --- Key: HADOOP-2686 URL: https://issues.apache.org/jira/browse/HADOOP-2686 Project: Hadoop Issue Type: Bug Components: contrib/hbase Reporter: stack

[jira] Updated: (HADOOP-2686) [hbase] Removed tables stick around

[ https://issues.apache.org/jira/browse/HADOOP-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2686: -- Attachment: deletetable-v3.patch Make a method to delete rows from META. Have all deletions use it (removes

[jira] Created: (HADOOP-2687) 1707 added errant INFO-level logging to DFSClient

Reporter: stack Priority: Blocker Fix For: 0.16.0 Marking this a blocker because it looks bad and it looks unintentional. If it this turns out to not be a blocker for hadoop, it will become one for hbase because 2/3rds of our DEBUG-level logs are filled with

[jira] Updated: (HADOOP-2687) 1707 added errant INFO-level logging to DFSClient

[ https://issues.apache.org/jira/browse/HADOOP-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2687: -- Attachment: dfsclient.patch Converted 4 INFO level logs to be DEBUG instead. > 1707 added errant INFO-le

[jira] Updated: (HADOOP-2686) [hbase] Removed tables stick around in .META.

[ https://issues.apache.org/jira/browse/HADOOP-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2686: -- Summary: [hbase] Removed tables stick around in .META. (was: [hbase] Removed tables stick around) > [hb

[jira] Updated: (HADOOP-2686) [hbase] Removed tables stick around in .META.

[ https://issues.apache.org/jira/browse/HADOOP-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2686: -- Attachment: deletetable-v4.patch Patch that passes tests locally > [hbase] Removed tables stick around

[jira] Updated: (HADOOP-2686) [hbase] Removed tables stick around in .META.

[ https://issues.apache.org/jira/browse/HADOOP-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2686: -- Status: Patch Available (was: Open) Passing to hudson > [hbase] Removed tables stick around in .M

[jira] Updated: (HADOOP-2687) 1707 added errant INFO-level logging to DFSClient

[ https://issues.apache.org/jira/browse/HADOOP-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2687: -- Status: Patch Available (was: Open) Passing to hudson > 1707 added errant INFO-level logging to DFSCli

[jira] Updated: (HADOOP-2687) 1707 added errant INFO-level logging to DFSClient

[ https://issues.apache.org/jira/browse/HADOOP-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2687: -- Component/s: (was: contrib/hbase) dfs > 1707 added errant INFO-level logging

[jira] Created: (HADOOP-2688) [hbase] IllegalArgumentException processing a shutdown

: contrib/hbase Reporter: stack Priority: Minor {code} 2008-01-23 02:38:54,537 WARN org.apache.hadoop.hbase.HMaster: Processing pending operations: ProcessServerShutdown of XX.XX.XX.128:60020 java.lang.IllegalArgumentException: Can't build a writable with empty bytes

[jira] Commented: (HADOOP-2682) regionserver wedged: thread holds lock during blocking read (?)

[ https://issues.apache.org/jira/browse/HADOOP-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561567#action_12561567 ] stack commented on HADOOP-2682: --- I see a second instance later in the logs: {code} Th

[jira] Updated: (HADOOP-2686) [hbase] Removed tables stick around in .META.

[ https://issues.apache.org/jira/browse/HADOOP-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2686: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed. > [hbase] Removed tables st

[jira] Updated: (HADOOP-2688) [hbase] IllegalArgumentException processing a shutdown stops server going down and results in millions of lines of output

[ https://issues.apache.org/jira/browse/HADOOP-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2688: -- Priority: Blocker (was: Minor) Fix Version/s: 0.16.0 Summary: [hbase

[jira] Assigned: (HADOOP-2687) 1707 added errant INFO-level logging to DFSClient

[ https://issues.apache.org/jira/browse/HADOOP-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HADOOP-2687: - Assignee: stack > 1707 added errant INFO-level logging to DFSCli

[jira] Updated: (HADOOP-2687) 1707 added errant INFO-level logging to DFSClient

[ https://issues.apache.org/jira/browse/HADOOP-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2687: -- Status: In Progress (was: Patch Available) The failure in core looks radically unrelated to this patch

[jira] Updated: (HADOOP-2687) 1707 added errant INFO-level logging to DFSClient

[ https://issues.apache.org/jira/browse/HADOOP-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2687: -- Status: Patch Available (was: In Progress) Retry > 1707 added errant INFO-level logging to DFSCli

[jira] Updated: (HADOOP-2584) Web UI displays an IOException instead of the Tables

[ https://issues.apache.org/jira/browse/HADOOP-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2584: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed (a while back). Resolving

[jira] Updated: (HADOOP-2688) [hbase] IllegalArgumentException processing a shutdown stops server going down and results in millions of lines of output

[ https://issues.apache.org/jira/browse/HADOOP-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2688: -- Attachment: emptywritable.patch Jim, please review this patch. In the name of minimal changes this close to

[jira] Updated: (HADOOP-2688) [hbase] IllegalArgumentException processing a shutdown stops server going down and results in millions of lines of output

[ https://issues.apache.org/jira/browse/HADOOP-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2688: -- Attachment: emptywritable-v2.patch v2 addresses jim comment (Made RowMap private) > [hb

[jira] Updated: (HADOOP-2688) [hbase] IllegalArgumentException processing a shutdown stops server going down and results in millions of lines of output

[ https://issues.apache.org/jira/browse/HADOOP-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2688: -- Status: Patch Available (was: Open) Passes tests locally. Passing to hudson. > [hb

[jira] Created: (HADOOP-2692) [hbase] Client exits with IllegalStateException

Reporter: stack Running a load test, I see clients exiting with the below exception: {code} 08/01/23 22:12:12 ERROR hbase.PerformanceEvaluation: Failed java.lang.IllegalStateException: region offline: TestTable,099498,1201125579414 at

[jira] Created: (HADOOP-2693) [hbase] NPE in getClosestRowBefore

: stack Just saw this in a load test: {code} 2008-01-23 22:43:42,831 INFO org.apache.hadoop.ipc.Server: IPC Server handler 8 on 60020, call getClosestRowBefore(.META.,,1, TestTable,,999, 9223372036854775807) from XX.XX.XX.141:49068: error: java.io.IOException

[jira] Commented: (HADOOP-2692) [hbase] Client exits with IllegalStateException

[ https://issues.apache.org/jira/browse/HADOOP-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561860#action_12561860 ] stack commented on HADOOP-2692: --- This could be problem w/ server returning ISE when per

[jira] Commented: (HADOOP-2693) [hbase] NPE in getClosestRowBefore

[ https://issues.apache.org/jira/browse/HADOOP-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561862#action_12561862 ] stack commented on HADOOP-2693: --- This is what it looks like client-side: {code} 08/01/2

[jira] Resolved: (HADOOP-2682) regionserver wedged: thread holds lock during blocking read (?)

[ https://issues.apache.org/jira/browse/HADOOP-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HADOOP-2682. --- Resolution: Invalid Fix Version/s: 0.16.0 Chatting w/ Michael, turns out a bunch of datanodes were

[jira] Commented: (HADOOP-2692) [hbase] Client exits with IllegalStateException

[ https://issues.apache.org/jira/browse/HADOOP-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561874#action_12561874 ] stack commented on HADOOP-2692: --- Client does right thing if region is closed: {code} 0

[jira] Commented: (HADOOP-2660) Regions getting messages from master to MSG_REGION_CLOSE_WITHOUT_REPORT

[ https://issues.apache.org/jira/browse/HADOOP-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561892#action_12561892 ] stack commented on HADOOP-2660: --- I concur that hbase startup is kinda ugly when there

[jira] Updated: (HADOOP-2688) [hbase] IllegalArgumentException processing a shutdown stops server going down and results in millions of lines of output

[ https://issues.apache.org/jira/browse/HADOOP-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2688: -- Status: In Progress (was: Patch Available) I don't see this in Nigel's fancy-pants new queue up

[jira] Updated: (HADOOP-2688) [hbase] IllegalArgumentException processing a shutdown stops server going down and results in millions of lines of output

[ https://issues.apache.org/jira/browse/HADOOP-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2688: -- Status: Patch Available (was: In Progress) > [hbase] IllegalArgumentException processing a shutdown st

[jira] Updated: (HADOOP-2688) [hbase] IllegalArgumentException processing a shutdown stops server going down and results in millions of lines of output

[ https://issues.apache.org/jira/browse/HADOOP-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2688: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed. > [hb

[jira] Updated: (HADOOP-2687) 1707 added errant INFO-level logging to DFSClient

[ https://issues.apache.org/jira/browse/HADOOP-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2687: -- Status: In Progress (was: Patch Available) Trying to get a +1 (though the -1 was in an unrelated test

[jira] Updated: (HADOOP-2687) 1707 added errant INFO-level logging to DFSClient

[ https://issues.apache.org/jira/browse/HADOOP-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2687: -- Status: Patch Available (was: In Progress) > 1707 added errant INFO-level logging to DFSCli

[jira] Created: (HADOOP-2698) [hbase] hregioninfo cell empty in meta table

Reporter: stack Priority: Minor When we notice one of these, instead of reporting on it over and over -- see below -- lets just axe the whole row. Its never going to get better on its own. We should also figure how these horked rows get manufactured. Below is about split

[jira] Updated: (HADOOP-2687) 1707 added errant INFO-level logging to DFSClient

[ https://issues.apache.org/jira/browse/HADOOP-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2687: -- Status: Open (was: Patch Available) Good to know. Cancelling patch. > 1707 added errant INFO-level logg

[jira] Created: (HADOOP-2701) [hbase] hql exceptions when no cluster to connect to

: contrib/hbase Reporter: stack Priority: Trivial Here's a couple of exceptions thrown by hql that should be fixed as we go: {code} 08/01/24 10:39:42 INFO hbase.HConnectionManager$TableServers: Attempt 3 of 5 failed with . Retrying after sleep of

[jira] Created: (HADOOP-2702) [hbase] A sequence of create/delete/create/etc. generates 'info:regioninfo is empty; has keys:' and eventually fails

URL: https://issues.apache.org/jira/browse/HADOOP-2702 Project: Hadoop Core Issue Type: Bug Components: contrib/hbase Reporter: stack Priority: Minor Marking as minor issue since its a concurrency issue in admin function. Though that said,

[jira] Updated: (HADOOP-2702) [hbase] A sequence of create/delete/create/etc. generates 'info:regioninfo is empty; has keys:' and eventually fails

[ https://issues.apache.org/jira/browse/HADOOP-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2702: -- Attachment: hbase-dave-master-hendrix.log master log > [hbase] A sequence of create/delete/create/

[jira] Updated: (HADOOP-2706) HBase Shell crash

[ https://issues.apache.org/jira/browse/HADOOP-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2706: -- Priority: Blocker (was: Minor) Fix Version/s: 0.16.0 Attached file fixes the NPE. Its pretty bad

[jira] Updated: (HADOOP-2706) HBase Shell crash

[ https://issues.apache.org/jira/browse/HADOOP-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2706: -- Attachment: helpnpe.patch > HBase Shell crash > - > > Key:

[jira] Updated: (HADOOP-2706) HBase Shell crash

[ https://issues.apache.org/jira/browse/HADOOP-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2706: -- Status: Patch Available (was: Open) Passing via hudson > HBase Shell cr

[jira] Commented: (HADOOP-2615) Add max number of mapfiles to compact at one time giveing us a minor & major compaction

[ https://issues.apache.org/jira/browse/HADOOP-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562335#action_12562335 ] stack commented on HADOOP-2615: --- Doing some load testing, I'm seeing compactio

[jira] Resolved: (HADOOP-2710) [hbase] start command line option causes further command line options to be ignored in REST

[ https://issues.apache.org/jira/browse/HADOOP-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HADOOP-2710. --- Resolution: Duplicate Duplicate of HADOOP-2675 (It has a fix too) > [hbase] start command line opt

[jira] Commented: (HADOOP-2615) Add max number of mapfiles to compact at one time giveing us a minor & major compaction

[ https://issues.apache.org/jira/browse/HADOOP-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562361#action_12562361 ] stack commented on HADOOP-2615: --- Here's the next two compactions: {code} 2008-01

[jira] Updated: (HADOOP-2615) Add max number of mapfiles to compact at one time giveing us a minor & major compaction

[ https://issues.apache.org/jira/browse/HADOOP-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2615: -- Attachment: twice.patch Patch that only compacts a maximum of twice the compaction threshold. Testing to

[jira] Updated: (HADOOP-2615) Add max number of mapfiles to compact at one time giveing us a minor & major compaction

[ https://issues.apache.org/jira/browse/HADOOP-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2615: -- Attachment: flag.patch This is a better patch. Moves the setting of writesEnabled before we go into the wait

[jira] Updated: (HADOOP-2615) Add max number of mapfiles to compact at one time giveing us a minor & major compaction

[ https://issues.apache.org/jira/browse/HADOOP-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2615: -- Attachment: flag-v2.patch Add a new disable compactions. Gets set when trying to close a region so no more

[jira] Created: (HADOOP-2712) [hbase] under load, regions won't split

hbase Reporter: stack Priority: Blocker Fix For: 0.16.0 First reported by Billy Preston over in HADOOP-2615, hbase won't split a region when under load; runaway compactions prevent it. This is a blocker because under load, we'll just make a region so big, we just

[jira] Updated: (HADOOP-2712) [hbase] under load, regions won't split

[ https://issues.apache.org/jira/browse/HADOOP-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2712: -- Attachment: flag-v4.patch Move setting of block compactions flag outside of while loop. This improves the

[jira] Updated: (HADOOP-2712) [hbase] under load, regions won't split

[ https://issues.apache.org/jira/browse/HADOOP-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2712: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed. > [hbase] under load, regi

[jira] Commented: (HADOOP-2705) io.file.buffer.size should default to a value larger than 4k

[ https://issues.apache.org/jira/browse/HADOOP-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562764#action_12562764 ] stack commented on HADOOP-2705: --- +1 on reverting. 5% improvement on reads is always

[jira] Updated: (HADOOP-2712) [hbase] under load, regions won't split

[ https://issues.apache.org/jira/browse/HADOOP-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2712: -- Status: Patch Available (was: Open) Passes tests locally. Passing to hudson. > [hbase] under load, regi

[jira] Updated: (HADOOP-2712) [hbase] under load, regions won't split

[ https://issues.apache.org/jira/browse/HADOOP-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2712: -- Attachment: flag-v2.patch Add flag that blocks compactions. Gets set when trying to close a region

[jira] Resolved: (HADOOP-2706) HBase Shell crash

[ https://issues.apache.org/jira/browse/HADOOP-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HADOOP-2706. --- Resolution: Fixed Committed. > HBase Shell crash > - > > Key:

[jira] Commented: (HADOOP-2705) io.file.buffer.size should default to a value larger than 4k

[ https://issues.apache.org/jira/browse/HADOOP-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562719#action_12562719 ] stack commented on HADOOP-2705: --- Description says upping buffer size improves read time

[jira] Commented: (HADOOP-2615) Add max number of mapfiles to compact at one time giveing us a minor & major compaction

[ https://issues.apache.org/jira/browse/HADOOP-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562709#action_12562709 ] stack commented on HADOOP-2615: --- I made issue HADOOP-2712 to cover not-splitting under

[jira] Resolved: (HADOOP-2578) HBaseConfiguration(Configuration c) constructor shouldn't overwrite passed conf with defaults

[ https://issues.apache.org/jira/browse/HADOOP-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HADOOP-2578. --- Resolution: Duplicate This issue seems to have died. Its taken up anew in HADOOP-2718, a duplicate

[jira] Updated: (HADOOP-2718) Copy Constructor HBaseConfiguration(Configuration) will override hbase configurations if argumant is not an instance of HBaseConfiguration.

[ https://issues.apache.org/jira/browse/HADOOP-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-2718: -- Attachment: conf.patch Does this work for you Clint? It overlays the passed Configuration atop a new

  1   2   3   >