date:20121004

[jira] [Commented] (HBASE-6439) Ignore .archive directory as a table

2012-10-04 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469179#comment-13469179
 ] 

Hudson commented on HBASE-6439:
---

Integrated in HBase-TRUNK #3420 (See 
[https://builds.apache.org/job/HBase-TRUNK/3420/])
HBASE-6439 Ignore .archive directory as a table (Revision 1393916)

 Result = FAILURE
stack : 
Files : 
* 
/hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/io/HFileLink.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HFileArchiveUtil.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/backup/example/TestZooKeeperTableArchiveClient.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/cleaner/TestHFileCleaner.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestFSTableDescriptors.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHFileArchiveUtil.java


 Ignore .archive directory as a table
 

 Key: HBASE-6439
 URL: https://issues.apache.org/jira/browse/HBASE-6439
 Project: HBase
  Issue Type: Bug
  Components: io, regionserver
Affects Versions: 0.96.0
Reporter: Jesse Yates
Assignee: Jesse Yates
  Labels: newbie
 Fix For: 0.96.0

 Attachments: hbase-6439-r0.patch


 From a recent test run:
 {quote}
 2012-07-22 02:27:30,699 WARN  [IPC Server handler 0 on 47087] 
 util.FSTableDescriptors(168): The following folder is in HBase's root 
 directory and doesn't contain a table descriptor, do consider deleting it: 
 .archive
 {quote}
 With the addition of HBASE-5547, table-level folders are no-longer all table 
 folders. FSTableDescriptors needs to then have a 'gold-list' that we can 
 update with directories that aren't tables so we don't have this kind of 
 thing showing up in the logs.
 Currently, we have the following block:
 {quote}
 invocations++;
 if (HTableDescriptor.ROOT_TABLEDESC.getNameAsString().equals(tablename)) {
   cachehits++;
   return HTableDescriptor.ROOT_TABLEDESC;
 }
 if (HTableDescriptor.META_TABLEDESC.getNameAsString().equals(tablename)) {
   cachehits++;
   return HTableDescriptor.META_TABLEDESC;
 }
 {quote}
 to handle special cases, but that's a bit clunky and not clean in terms of 
 table-level directories that need to be ignored.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6707) TEST org.apache.hadoop.hbase.backup.example.TestZooKeeperTableArchiveClient.testMultipleTables flaps

2012-10-04 Thread Jesse Yates (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469183#comment-13469183
 ] 

Jesse Yates commented on HBASE-6707:


bq.  If it passes hadoopqa, that is enough up to this. 

I think that's reasonable. If we want to support both 1.6 and 1.7 that should 
be part of the official test process. Wanna file a ticket Ted?

 TEST 
 org.apache.hadoop.hbase.backup.example.TestZooKeeperTableArchiveClient.testMultipleTables
  flaps
 

 Key: HBASE-6707
 URL: https://issues.apache.org/jira/browse/HBASE-6707
 Project: HBase
  Issue Type: Bug
  Components: test
Reporter: Sameer Vaishampayan
Assignee: Jesse Yates
Priority: Critical
 Fix For: 0.96.0

 Attachments: hbase-6707-v0.patch, hbase-6707-v1.patch, 
 hbase-6707-v2.patch, hbase-6707-v3.patch, hbase-6707-v4-addendum.patch, 
 hbase-6707-v4.patch


 https://builds.apache.org/job/HBase-TRUNK/3293/
 Error Message
 Archived HFiles 
 (hdfs://localhost:59986/user/jenkins/hbase/.archive/otherTable/01ced3b55d7220a9c460273a4a57b198/fam)
  should have gotten deleted, but didn't, remaining 
 files:[hdfs://localhost:59986/user/jenkins/hbase/.archive/otherTable/01ced3b55d7220a9c460273a4a57b198/fam/fc872572a1f5443eb55b6e2567cfeb1c]
 Stacktrace
 java.lang.AssertionError: Archived HFiles 
 (hdfs://localhost:59986/user/jenkins/hbase/.archive/otherTable/01ced3b55d7220a9c460273a4a57b198/fam)
  should have gotten deleted, but didn't, remaining 
 files:[hdfs://localhost:59986/user/jenkins/hbase/.archive/otherTable/01ced3b55d7220a9c460273a4a57b198/fam/fc872572a1f5443eb55b6e2567cfeb1c]
   at org.junit.Assert.fail(Assert.java:93)
   at org.junit.Assert.assertTrue(Assert.java:43)
   at org.junit.Assert.assertNull(Assert.java:551)
   at 
 org.apache.hadoop.hbase.backup.example.TestZooKeeperTableArchiveClient.testMultipleTables(TestZooKeeperTableArchiveClient.java:291)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6928) TestStoreFile sometimes fails with 'Column family prefix used twice'

2012-10-04 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469190#comment-13469190
 ] 

Hudson commented on HBASE-6928:
---

Integrated in HBase-TRUNK #3421 (See 
[https://builds.apache.org/job/HBase-TRUNK/3421/])
HBASE-6928 TestStoreFile sometimes fails with 'Column family prefix used 
twice' -- ATTEMPTED FIX (Revision 1393923)

 Result = FAILURE
stack : 
Files : 
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestStoreFile.java


 TestStoreFile sometimes fails with 'Column family prefix used twice'
 

 Key: HBASE-6928
 URL: https://issues.apache.org/jira/browse/HBASE-6928
 Project: HBase
  Issue Type: Bug
Reporter: Ted Yu
 Attachments: 6928_attempted_fix.txt, 6928-debug.txt


 In build #3406, I saw:
 {code}
 java.lang.AssertionError: Column family prefix used twice: 
 cf.cf.bt.Data.fsReadnumops
   at 
 org.apache.hadoop.hbase.regionserver.metrics.SchemaMetrics.validateMetricChanges(SchemaMetrics.java:822)
   at 
 org.apache.hadoop.hbase.regionserver.TestStoreFile.tearDown(TestStoreFile.java:89)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6942) Endpoint implementation for bulk delete

2012-10-04 Thread Anoop Sam John (JIRA)


 [ 
https://issues.apache.org/jira/browse/HBASE-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anoop Sam John updated HBASE-6942:
--

Description: 
We can provide an end point implementation for doing a bulk delete (based on a 
scan) at the server side. This can reduce the time taken for such an operation 
as right now it need to do a scan to client and issue delete(s) using rowkeys.

Query like  delete from table1 where...

  was:We can provide an end point implementation for doing a bulk delete (based 
on a scan) at the server side. This can reduce the time taken for such an 
operation as right now it need to do a scan to client and issue delete(s) using 
rowkeys.


 Endpoint implementation for bulk delete
 ---

 Key: HBASE-6942
 URL: https://issues.apache.org/jira/browse/HBASE-6942
 Project: HBase
  Issue Type: Improvement
  Components: Coprocessors, Performance
Reporter: Anoop Sam John
Assignee: Anoop Sam John

 We can provide an end point implementation for doing a bulk delete (based on 
 a scan) at the server side. This can reduce the time taken for such an 
 operation as right now it need to do a scan to client and issue delete(s) 
 using rowkeys.
 Query like  delete from table1 where...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6707) TEST org.apache.hadoop.hbase.backup.example.TestZooKeeperTableArchiveClient.testMultipleTables flaps

2012-10-04 Thread Jesse Yates (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469194#comment-13469194
 ] 

Jesse Yates commented on HBASE-6707:


bq. Why the addition of 3 above ?

So it checks each of the directories on the way down - tablename/region/family 
- hence the plus three. 

The way CleanerChore works is that it looks at the main directory, and then if 
it has files under it, attempts to see if those files are deleteable. If they 
aren't deletable, it skips checking the directory and continues on to the next 
directory to check. If all the files are deletable, then if checks to see if 
the directory is deletable.

bq. The above change deviates from original assumption. Please explain why a 
directory can be deleted regardless of whether it has files under it.

Therefore, we can always consider directories deletable because there is 
nothing special about a directory, but only the files under the directory. 
Perhaps that was a flaw in the design, but we should file another ticket to 
change that behavior such that we only check for files and delete directories 
when there are no files for that directory.

Further note, for the original quote, that we need only have +3 for the 
non-archived table's directories, but not an extra +3 (which would make a total 
of +6) for the archived table because we don't attempt to delete the directory 
containing hfiles that are retained.

 TEST 
 org.apache.hadoop.hbase.backup.example.TestZooKeeperTableArchiveClient.testMultipleTables
  flaps
 

 Key: HBASE-6707
 URL: https://issues.apache.org/jira/browse/HBASE-6707
 Project: HBase
  Issue Type: Bug
  Components: test
Reporter: Sameer Vaishampayan
Assignee: Jesse Yates
Priority: Critical
 Fix For: 0.96.0

 Attachments: hbase-6707-v0.patch, hbase-6707-v1.patch, 
 hbase-6707-v2.patch, hbase-6707-v3.patch, hbase-6707-v4-addendum.patch, 
 hbase-6707-v4.patch


 https://builds.apache.org/job/HBase-TRUNK/3293/
 Error Message
 Archived HFiles 
 (hdfs://localhost:59986/user/jenkins/hbase/.archive/otherTable/01ced3b55d7220a9c460273a4a57b198/fam)
  should have gotten deleted, but didn't, remaining 
 files:[hdfs://localhost:59986/user/jenkins/hbase/.archive/otherTable/01ced3b55d7220a9c460273a4a57b198/fam/fc872572a1f5443eb55b6e2567cfeb1c]
 Stacktrace
 java.lang.AssertionError: Archived HFiles 
 (hdfs://localhost:59986/user/jenkins/hbase/.archive/otherTable/01ced3b55d7220a9c460273a4a57b198/fam)
  should have gotten deleted, but didn't, remaining 
 files:[hdfs://localhost:59986/user/jenkins/hbase/.archive/otherTable/01ced3b55d7220a9c460273a4a57b198/fam/fc872572a1f5443eb55b6e2567cfeb1c]
   at org.junit.Assert.fail(Assert.java:93)
   at org.junit.Assert.assertTrue(Assert.java:43)
   at org.junit.Assert.assertNull(Assert.java:551)
   at 
 org.apache.hadoop.hbase.backup.example.TestZooKeeperTableArchiveClient.testMultipleTables(TestZooKeeperTableArchiveClient.java:291)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6939) Add the possibility to set the ZK port in HBaseTestingUtility

2012-10-04 Thread nkeywal (JIRA)


 [ 
https://issues.apache.org/jira/browse/HBASE-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

nkeywal updated HBASE-6939:
---

Attachment: 6939.v2.patch

 Add the possibility to set the ZK port in HBaseTestingUtility
 -

 Key: HBASE-6939
 URL: https://issues.apache.org/jira/browse/HBASE-6939
 Project: HBase
  Issue Type: Improvement
  Components: test
Affects Versions: 0.94.1, 0.96.0
Reporter: nkeywal
Assignee: nkeywal
Priority: Trivial
 Attachments: 6939.094.v1.patch, 6939.v1.patch, 6939.v1.patch, 
 6939.v2.patch


 It's useful when embedding the HBaseTestingUtility into another test server: 
 fixing the ZK port allows it to put it simply into a shared instance.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6939) Add the possibility to set the ZK port in HBaseTestingUtility

2012-10-04 Thread nkeywal (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469205#comment-13469205
 ] 

nkeywal commented on HBASE-6939:


Committed revision 1393940.
With the fixed space. Thanks for the review!


 Add the possibility to set the ZK port in HBaseTestingUtility
 -

 Key: HBASE-6939
 URL: https://issues.apache.org/jira/browse/HBASE-6939
 Project: HBase
  Issue Type: Improvement
  Components: test
Affects Versions: 0.94.1, 0.96.0
Reporter: nkeywal
Assignee: nkeywal
Priority: Trivial
 Attachments: 6939.094.v1.patch, 6939.v1.patch, 6939.v1.patch, 
 6939.v2.patch


 It's useful when embedding the HBaseTestingUtility into another test server: 
 fixing the ZK port allows it to put it simply into a shared instance.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6939) Add the possibility to set the ZK port in HBaseTestingUtility

2012-10-04 Thread nkeywal (JIRA)


 [ 
https://issues.apache.org/jira/browse/HBASE-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

nkeywal updated HBASE-6939:
---

   Resolution: Fixed
Fix Version/s: 0.96.0
 Release Note: In HBaseTestingUtility class, a new property 
(test.hbase.zookeeper.property.clientPort) allows to launch the mini 
ZooKeeper on a predefined port.
 Hadoop Flags: Reviewed
   Status: Resolved  (was: Patch Available)

 Add the possibility to set the ZK port in HBaseTestingUtility
 -

 Key: HBASE-6939
 URL: https://issues.apache.org/jira/browse/HBASE-6939
 Project: HBase
  Issue Type: Improvement
  Components: test
Affects Versions: 0.94.1, 0.96.0
Reporter: nkeywal
Assignee: nkeywal
Priority: Trivial
 Fix For: 0.96.0

 Attachments: 6939.094.v1.patch, 6939.v1.patch, 6939.v1.patch, 
 6939.v2.patch


 It's useful when embedding the HBaseTestingUtility into another test server: 
 fixing the ZK port allows it to put it simply into a shared instance.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6939) Add the possibility to set the ZK port in HBaseTestingUtility

2012-10-04 Thread Hadoop QA (JIRA)

[
https://issues.apache.org/jira/browse/HBASE-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469214#comment-13469214
]

Hadoop QA commented on HBASE-6939:
--

{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12547691/6939.v2.patch
against trunk revision .

{color:green}+1 @author{color}. The patch does not contain any @author
tags.

{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.

{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.

{color:red}-1 javadoc{color}. The javadoc tool appears to have generated
81 warning messages.

{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.

{color:red}-1 findbugs{color}. The patch appears to introduce 5 new
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.

{color:green}+1 core tests{color}. The patch passed unit tests in .

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/3002//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3002//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3002//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3002//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3002//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3002//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/3002//console

This message is automatically generated.

Add the possibility to set the ZK port in HBaseTestingUtility
-

Key: HBASE-6939
URL: https://issues.apache.org/jira/browse/HBASE-6939
Project: HBase
Issue Type: Improvement
Components: test
Affects Versions: 0.94.1, 0.96.0
Reporter: nkeywal
Assignee: nkeywal
Priority: Trivial
Fix For: 0.96.0

Attachments: 6939.094.v1.patch, 6939.v1.patch, 6939.v1.patch,
6939.v2.patch

It's useful when embedding the HBaseTestingUtility into another test server:
fixing the ZK port allows it to put it simply into a shared instance.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HBASE-6943) [89-fbDo not catch certain exceptions trying

2012-10-04 Thread Mikhail Bautin (JIRA)

Mikhail Bautin created HBASE-6943:
-

 Summary: [89-fbDo not catch certain exceptions trying 
 Key: HBASE-6943
 URL: https://issues.apache.org/jira/browse/HBASE-6943
 Project: HBase
  Issue Type: Bug
Reporter: Mikhail Bautin




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6943) [89-fb] Do not catch certain exceptions trying to get an RS connection

2012-10-04 Thread Mikhail Bautin (JIRA)

[
https://issues.apache.org/jira/browse/HBASE-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mikhail Bautin updated HBASE-6943:
--

Description: When getting a regionserver connection in 0.89-fb in
HBaseClient, we catch all types of Throwable. I have observed a real case when
the client looked stuck. On debugging it turned out that a NoSuchMethodError
was thrown and caught, leaving the connection in an inconsistent state
(initialized socket but null streams). All following attempts resulted in NPEs
that were also caught, and no errors were logged. From the user's perspective
the client was just stuck. The root cause was the absence of a required jar
(hence the NoSuchMethodError) but it was not reported properly.
Summary: [89-fb] Do not catch certain exceptions trying to get an RS
connection (was: [89-fbDo not catch certain exceptions trying )

[89-fb] Do not catch certain exceptions trying to get an RS connection
--

Key: HBASE-6943
URL: https://issues.apache.org/jira/browse/HBASE-6943
Project: HBase
Issue Type: Bug
Reporter: Mikhail Bautin

When getting a regionserver connection in 0.89-fb in HBaseClient, we catch
all types of Throwable. I have observed a real case when the client looked
stuck. On debugging it turned out that a NoSuchMethodError was thrown and
caught, leaving the connection in an inconsistent state (initialized socket
but null streams). All following attempts resulted in NPEs that were also
caught, and no errors were logged. From the user's perspective the client was
just stuck. The root cause was the absence of a required jar (hence the
NoSuchMethodError) but it was not reported properly.

[jira] [Commented] (HBASE-6872) Number of records written/read per second on regionserver level

2012-10-04 Thread Phabricator (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469222#comment-13469222
 ] 

Phabricator commented on HBASE-6872:


mbautin has closed the revision [jira] [HBASE-6872] [89-fb] Fix 
TestRegionServerMetrics.testNumReadsAndWrites.

CHANGED PRIOR TO COMMIT
  https://reviews.facebook.net/D5853?vs=19311id=19359#differential-review-toc

REVISION DETAIL
  https://reviews.facebook.net/D5853

COMMIT
  https://reviews.facebook.net/rHBASEEIGHTNINEFBBRANCH1393955

To: Kannan, Karthik, JIRA, Liyin, mbautin
Cc: adela, Liyin, aaiyer, avf


 Number of records written/read per second on regionserver level
 ---

 Key: HBASE-6872
 URL: https://issues.apache.org/jira/browse/HBASE-6872
 Project: HBase
  Issue Type: New Feature
  Components: regionserver
Reporter: Adela Maznikar
Priority: Minor
 Attachments: D5853.1.patch, D5853.2.patch, D5853.3.patch


 Regionserver level metrics that shows the number of records written/read per 
 second. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6944) Enhance test-patch.sh to run against both jdk 1.6 and jdk 1.7

2012-10-04 Thread Ted Yu (JIRA)


 [ 
https://issues.apache.org/jira/browse/HBASE-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated HBASE-6944:
--

Issue Type: Task  (was: Bug)

 Enhance test-patch.sh to run against both jdk 1.6 and jdk 1.7
 -

 Key: HBASE-6944
 URL: https://issues.apache.org/jira/browse/HBASE-6944
 Project: HBase
  Issue Type: Task
Reporter: Ted Yu

 Currently test-patch.sh only runs against jdk 1.6
 However trunk build is using jdk 1.7
 test-patch.sh should be enhanced to run against both jdk versions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HBASE-6944) Enhance test-patch.sh to run against both jdk 1.6 and jdk 1.7

2012-10-04 Thread Ted Yu (JIRA)

Ted Yu created HBASE-6944:
-

 Summary: Enhance test-patch.sh to run against both jdk 1.6 and jdk 
1.7
 Key: HBASE-6944
 URL: https://issues.apache.org/jira/browse/HBASE-6944
 Project: HBase
  Issue Type: Bug
Reporter: Ted Yu


Currently test-patch.sh only runs against jdk 1.6
However trunk build is using jdk 1.7

test-patch.sh should be enhanced to run against both jdk versions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6707) TEST org.apache.hadoop.hbase.backup.example.TestZooKeeperTableArchiveClient.testMultipleTables flaps

2012-10-04 Thread Ted Yu (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469227#comment-13469227
 ] 

Ted Yu commented on HBASE-6707:
---

bq. If we want to support both 1.6 and 1.7 that should be part of the official 
test process. Wanna file a ticket Ted?
Done. I logged HBASE-6944

bq. Perhaps that was a flaw in the design, but we should file another ticket to 
change that behavior such that we only check for files and delete directories 
when there are no files for that directory.
Want to file a ticket Jesse ?

 TEST 
 org.apache.hadoop.hbase.backup.example.TestZooKeeperTableArchiveClient.testMultipleTables
  flaps
 

 Key: HBASE-6707
 URL: https://issues.apache.org/jira/browse/HBASE-6707
 Project: HBase
  Issue Type: Bug
  Components: test
Reporter: Sameer Vaishampayan
Assignee: Jesse Yates
Priority: Critical
 Fix For: 0.96.0

 Attachments: hbase-6707-v0.patch, hbase-6707-v1.patch, 
 hbase-6707-v2.patch, hbase-6707-v3.patch, hbase-6707-v4-addendum.patch, 
 hbase-6707-v4.patch


 https://builds.apache.org/job/HBase-TRUNK/3293/
 Error Message
 Archived HFiles 
 (hdfs://localhost:59986/user/jenkins/hbase/.archive/otherTable/01ced3b55d7220a9c460273a4a57b198/fam)
  should have gotten deleted, but didn't, remaining 
 files:[hdfs://localhost:59986/user/jenkins/hbase/.archive/otherTable/01ced3b55d7220a9c460273a4a57b198/fam/fc872572a1f5443eb55b6e2567cfeb1c]
 Stacktrace
 java.lang.AssertionError: Archived HFiles 
 (hdfs://localhost:59986/user/jenkins/hbase/.archive/otherTable/01ced3b55d7220a9c460273a4a57b198/fam)
  should have gotten deleted, but didn't, remaining 
 files:[hdfs://localhost:59986/user/jenkins/hbase/.archive/otherTable/01ced3b55d7220a9c460273a4a57b198/fam/fc872572a1f5443eb55b6e2567cfeb1c]
   at org.junit.Assert.fail(Assert.java:93)
   at org.junit.Assert.assertTrue(Assert.java:43)
   at org.junit.Assert.assertNull(Assert.java:551)
   at 
 org.apache.hadoop.hbase.backup.example.TestZooKeeperTableArchiveClient.testMultipleTables(TestZooKeeperTableArchiveClient.java:291)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6939) Add the possibility to set the ZK port in HBaseTestingUtility

2012-10-04 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469228#comment-13469228
 ] 

Hudson commented on HBASE-6939:
---

Integrated in HBase-TRUNK #3422 (See 
[https://builds.apache.org/job/HBase-TRUNK/3422/])
HBASE-6939 Add the possibility to set the ZK port in HBaseTestingUtility 
(Revision 1393940)

 Result = FAILURE
nkeywal : 
Files : 
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java


 Add the possibility to set the ZK port in HBaseTestingUtility
 -

 Key: HBASE-6939
 URL: https://issues.apache.org/jira/browse/HBASE-6939
 Project: HBase
  Issue Type: Improvement
  Components: test
Affects Versions: 0.94.1, 0.96.0
Reporter: nkeywal
Assignee: nkeywal
Priority: Trivial
 Fix For: 0.96.0

 Attachments: 6939.094.v1.patch, 6939.v1.patch, 6939.v1.patch, 
 6939.v2.patch


 It's useful when embedding the HBaseTestingUtility into another test server: 
 fixing the ZK port allows it to put it simply into a shared instance.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6943) [89-fb] Do not catch certain exceptions trying to get an RS connection

2012-10-04 Thread Phabricator (JIRA)


 [ 
https://issues.apache.org/jira/browse/HBASE-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Phabricator updated HBASE-6943:
---

Attachment: D5877.1.patch

mbautin requested code review of [jira] [HBASE-6943] [89-fb] Do not catch 
certain exceptions trying to get an RS connection.
Reviewers: Kannan, Liyin, Karthik, JIRA

  When getting a regionserver connection in 0.89-fb in HBaseClient, we catch 
all types of Throwable. I have observed a real case when the client looked 
stuck. On debugging it turned out that a NoSuchMethodError was thrown and 
caught, leaving the connection in an inconsistent state (initialized socket but 
null streams). All following attempts resulted in NPEs that were also caught, 
and no errors were logged. From the user's perspective the client was just 
stuck. The root cause was the absence of a required jar (hence the 
NoSuchMethodError) but it was not reported properly.

TEST PLAN
  Run a client with the same configuration as before and verify it does not get 
stuck.

REVISION DETAIL
  https://reviews.facebook.net/D5877

AFFECTED FILES
  src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java
  src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java

MANAGE HERALD DIFFERENTIAL RULES
  https://reviews.facebook.net/herald/view/differential/

WHY DID I GET THIS EMAIL?
  https://reviews.facebook.net/herald/transcript/13929/

To: Kannan, Liyin, Karthik, JIRA, mbautin


 [89-fb] Do not catch certain exceptions trying to get an RS connection
 --

 Key: HBASE-6943
 URL: https://issues.apache.org/jira/browse/HBASE-6943
 Project: HBase
  Issue Type: Bug
Reporter: Mikhail Bautin
 Attachments: D5877.1.patch


 When getting a regionserver connection in 0.89-fb in HBaseClient, we catch 
 all types of Throwable. I have observed a real case when the client looked 
 stuck. On debugging it turned out that a NoSuchMethodError was thrown and 
 caught, leaving the connection in an inconsistent state (initialized socket 
 but null streams). All following attempts resulted in NPEs that were also 
 caught, and no errors were logged. From the user's perspective the client was 
 just stuck. The root cause was the absence of a required jar (hence the 
 NoSuchMethodError) but it was not reported properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6939) Add the possibility to set the ZK port in HBaseTestingUtility

2012-10-04 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469300#comment-13469300
 ] 

Hudson commented on HBASE-6939:
---

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #207 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/207/])
HBASE-6939 Add the possibility to set the ZK port in HBaseTestingUtility 
(Revision 1393940)

 Result = SUCCESS
nkeywal : 
Files : 
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java


 Add the possibility to set the ZK port in HBaseTestingUtility
 -

 Key: HBASE-6939
 URL: https://issues.apache.org/jira/browse/HBASE-6939
 Project: HBase
  Issue Type: Improvement
  Components: test
Affects Versions: 0.94.1, 0.96.0
Reporter: nkeywal
Assignee: nkeywal
Priority: Trivial
 Fix For: 0.96.0

 Attachments: 6939.094.v1.patch, 6939.v1.patch, 6939.v1.patch, 
 6939.v2.patch


 It's useful when embedding the HBaseTestingUtility into another test server: 
 fixing the ZK port allows it to put it simply into a shared instance.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6562) Fake KVs are sometimes passed to filters

2012-10-04 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469301#comment-13469301
 ] 

Hudson commented on HBASE-6562:
---

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #207 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/207/])
HBASE-6912 Filters are not properly applied in certain cases (revert 
HBASE-6562) (Revision 1393853)

 Result = SUCCESS
larsh : 
Files : 
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFakeKeyInFilter.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java


 Fake KVs are sometimes passed to filters
 

 Key: HBASE-6562
 URL: https://issues.apache.org/jira/browse/HBASE-6562
 Project: HBase
  Issue Type: Bug
Reporter: Lars Hofhansl
Assignee: Lars Hofhansl
Priority: Minor
 Fix For: 0.94.3, 0.96.0

 Attachments: 6562.txt, 6562-v2.txt, 6562-v3.txt, minimalTest.java


 In internal tests at Salesforce we found that fake row keys sometimes are 
 passed to filters (Filter.filterRowKey(...) specifically).
 The KVs are eventually filtered by the StoreScanner/ScanQueryMatcher, but the 
 row key is passed to filterRowKey in RegionScannImpl *before* that happens.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6439) Ignore .archive directory as a table

2012-10-04 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469302#comment-13469302
 ] 

Hudson commented on HBASE-6439:
---

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #207 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/207/])
HBASE-6439 Ignore .archive directory as a table (Revision 1393916)

 Result = SUCCESS
stack : 
Files : 
* 
/hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/io/HFileLink.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HFileArchiveUtil.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/backup/example/TestZooKeeperTableArchiveClient.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/cleaner/TestHFileCleaner.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestFSTableDescriptors.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHFileArchiveUtil.java


 Ignore .archive directory as a table
 

 Key: HBASE-6439
 URL: https://issues.apache.org/jira/browse/HBASE-6439
 Project: HBase
  Issue Type: Bug
  Components: io, regionserver
Affects Versions: 0.96.0
Reporter: Jesse Yates
Assignee: Jesse Yates
  Labels: newbie
 Fix For: 0.96.0

 Attachments: hbase-6439-r0.patch


 From a recent test run:
 {quote}
 2012-07-22 02:27:30,699 WARN  [IPC Server handler 0 on 47087] 
 util.FSTableDescriptors(168): The following folder is in HBase's root 
 directory and doesn't contain a table descriptor, do consider deleting it: 
 .archive
 {quote}
 With the addition of HBASE-5547, table-level folders are no-longer all table 
 folders. FSTableDescriptors needs to then have a 'gold-list' that we can 
 update with directories that aren't tables so we don't have this kind of 
 thing showing up in the logs.
 Currently, we have the following block:
 {quote}
 invocations++;
 if (HTableDescriptor.ROOT_TABLEDESC.getNameAsString().equals(tablename)) {
   cachehits++;
   return HTableDescriptor.ROOT_TABLEDESC;
 }
 if (HTableDescriptor.META_TABLEDESC.getNameAsString().equals(tablename)) {
   cachehits++;
   return HTableDescriptor.META_TABLEDESC;
 }
 {quote}
 to handle special cases, but that's a bit clunky and not clean in terms of 
 table-level directories that need to be ignored.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6912) Filters are not properly applied in certain cases

2012-10-04 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469303#comment-13469303
 ] 

Hudson commented on HBASE-6912:
---

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #207 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/207/])
HBASE-6912 Filters are not properly applied in certain cases (revert 
HBASE-6562) (Revision 1393853)

 Result = SUCCESS
larsh : 
Files : 
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFakeKeyInFilter.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java


 Filters are not properly applied in certain cases
 -

 Key: HBASE-6912
 URL: https://issues.apache.org/jira/browse/HBASE-6912
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.1
Reporter: Alex Newman
Assignee: Lars Hofhansl
 Fix For: 0.94.2, 0.96.0

 Attachments: 6912-0.94.txt, 6912-0.96.txt, minimalTest.java


 Steps to reproduce:
 Create a table, load data into it. Flush the table.
 Do a scan with
 1. Some filter which should not match the first entry in the scan
 2. Where one specifies a family and column.
 You will notice that the first entry is returned even though it doesn't match 
 the filter.
 It looks like the when the first KeyValue of a scan in the column from the 
 point of view of the code
 HRegion.java
 {code}
 } else if (kv != null  !kv.isInternal()  filterRowKey(currentRow)) {
 {code}
 Is generated by
 {code}
 public static KeyValue createLastOnRow(final byte [] row,
 final int roffset, final int rlength, final byte [] family,
 final int foffset, final int flength, final byte [] qualifier,
 final int qoffset, final int qlength) { return new KeyValue(row, roffset, 
 rlength, family, foffset, flength, qualifier, qoffset, qlength, 
 HConstants.OLDEST_TIMESTAMP, Type.Minimum, null, 0, 0); }
 {code}
 So it is always internal from that point of the code.
 Only later from within
 StoreScanner.java
 {code}
 public synchronized boolean next(ListKeyValue outResult, int limit, String 
 metric) throws IOException {
 
 LOOP: while((kv = this.heap.peek()) != null) {
 {code}
 ( The second time through)
 Do we get the actual kv, with a proper type and timestamp. This seems to mess 
 with filtering.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6928) TestStoreFile sometimes fails with 'Column family prefix used twice'

2012-10-04 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469304#comment-13469304
 ] 

Hudson commented on HBASE-6928:
---

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #207 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/207/])
HBASE-6928 TestStoreFile sometimes fails with 'Column family prefix used 
twice' -- ATTEMPTED FIX (Revision 1393923)

 Result = SUCCESS
stack : 
Files : 
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestStoreFile.java


 TestStoreFile sometimes fails with 'Column family prefix used twice'
 

 Key: HBASE-6928
 URL: https://issues.apache.org/jira/browse/HBASE-6928
 Project: HBase
  Issue Type: Bug
Reporter: Ted Yu
 Attachments: 6928_attempted_fix.txt, 6928-debug.txt


 In build #3406, I saw:
 {code}
 java.lang.AssertionError: Column family prefix used twice: 
 cf.cf.bt.Data.fsReadnumops
   at 
 org.apache.hadoop.hbase.regionserver.metrics.SchemaMetrics.validateMetricChanges(SchemaMetrics.java:822)
   at 
 org.apache.hadoop.hbase.regionserver.TestStoreFile.tearDown(TestStoreFile.java:89)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (HBASE-6944) Enhance test-patch.sh to run against both jdk 1.6 and jdk 1.7

2012-10-04 Thread Ted Yu (JIRA)


 [ 
https://issues.apache.org/jira/browse/HBASE-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu reassigned HBASE-6944:
-

Assignee: Ted Yu

 Enhance test-patch.sh to run against both jdk 1.6 and jdk 1.7
 -

 Key: HBASE-6944
 URL: https://issues.apache.org/jira/browse/HBASE-6944
 Project: HBase
  Issue Type: Task
Reporter: Ted Yu
Assignee: Ted Yu
 Fix For: 0.96.0

 Attachments: 6944.txt


 Currently test-patch.sh only runs against jdk 1.6
 However trunk build is using jdk 1.7
 test-patch.sh should be enhanced to run against both jdk versions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6944) Enhance test-patch.sh to run against both jdk 1.6 and jdk 1.7

2012-10-04 Thread Ted Yu (JIRA)


 [ 
https://issues.apache.org/jira/browse/HBASE-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated HBASE-6944:
--

Attachment: 6944.txt

First attempt.
test-patch.sh now runs against both jdk's

 Enhance test-patch.sh to run against both jdk 1.6 and jdk 1.7
 -

 Key: HBASE-6944
 URL: https://issues.apache.org/jira/browse/HBASE-6944
 Project: HBase
  Issue Type: Task
Reporter: Ted Yu
 Fix For: 0.96.0

 Attachments: 6944.txt


 Currently test-patch.sh only runs against jdk 1.6
 However trunk build is using jdk 1.7
 test-patch.sh should be enhanced to run against both jdk versions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6944) Enhance test-patch.sh to run against both jdk 1.6 and jdk 1.7

2012-10-04 Thread Ted Yu (JIRA)


 [ 
https://issues.apache.org/jira/browse/HBASE-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated HBASE-6944:
--

Fix Version/s: 0.96.0

 Enhance test-patch.sh to run against both jdk 1.6 and jdk 1.7
 -

 Key: HBASE-6944
 URL: https://issues.apache.org/jira/browse/HBASE-6944
 Project: HBase
  Issue Type: Task
Reporter: Ted Yu
Assignee: Ted Yu
 Fix For: 0.96.0

 Attachments: 6944.txt


 Currently test-patch.sh only runs against jdk 1.6
 However trunk build is using jdk 1.7
 test-patch.sh should be enhanced to run against both jdk versions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

1 2 3 >

1 - 100 of 225 matches

Mail list logo