[jira] [Updated] (HBASE-9392) Add RestartBackupMastersAction for ChaosMonkey
[ https://issues.apache.org/jira/browse/HBASE-9392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chendihao updated HBASE-9392: - Attachment: RestartBackupMastersAction.patch patch for trunk > Add RestartBackupMastersAction for ChaosMonkey > -- > > Key: HBASE-9392 > URL: https://issues.apache.org/jira/browse/HBASE-9392 > Project: HBase > Issue Type: Improvement > Components: test >Affects Versions: 0.94.3 >Reporter: chendihao >Priority: Minor > Attachments: RestartBackupMastersAction.patch > > > Just implement RestartBackupMastersAction for more failures. -- 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-9392) Add RestartBackupMastersAction for ChaosMonkey
chendihao created HBASE-9392: Summary: Add RestartBackupMastersAction for ChaosMonkey Key: HBASE-9392 URL: https://issues.apache.org/jira/browse/HBASE-9392 Project: HBase Issue Type: Improvement Components: test Affects Versions: 0.94.3 Reporter: chendihao Priority: Minor Attachments: RestartBackupMastersAction.patch Just implement RestartBackupMastersAction for more failures. -- 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-9249) Add cp hook before setting PONR in split
[ https://issues.apache.org/jira/browse/HBASE-9249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rajeshbabu updated HBASE-9249: -- Attachment: HBASE-9249_v4.patch Fixing javadoc and findbug warnings. > Add cp hook before setting PONR in split > > > Key: HBASE-9249 > URL: https://issues.apache.org/jira/browse/HBASE-9249 > Project: HBase > Issue Type: Sub-task >Reporter: rajeshbabu >Assignee: rajeshbabu > Attachments: HBASE-9249.patch, HBASE-9249_v2.patch, > HBASE-9249_v3.patch, HBASE-9249_v4.patch > > > This hook helps to perform split on user region and corresponding index > region such that both will be split or none. > With this hook split for user and index region as follows > user region > === > 1) Create splitting znode for user region split > 2) Close parent user region > 3) split user region storefiles > 4) instantiate child regions of user region > Through the new hook we can call index region transitions as below > index region > === > 5) Create splitting znode for index region split > 6) Close parent index region > 7) Split storefiles of index region > 8) instantiate child regions of the index region > If any failures in 5,6,7,8 rollback the steps and return null, on null return > throw exception to rollback for 1,2,3,4 > 9) set PONR > 10) do batch put of offline and split entries for user and index regions > index region > > 11) open daughers of index regions and transition znode to split. This step > we will do through preSplitAfterPONR hook. Opening index regions before > opening user regions helps to avoid put failures if there is colocation > mismatch(this can happen if user regions opening completed but index regions > opening in progress) > user region > === > 12) open daughers of user regions and transition znode to split. > Even if region server crashes also at the end both user and index regions > will be split or none -- 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] [Resolved] (HBASE-9391) Compilation problem in AccessController with JDK 6
[
https://issues.apache.org/jira/browse/HBASE-9391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-9391.
---
Resolution: Cannot Reproduce
Tried to reproduce this on another box and couldn't. Switched JDKs on the
troublesome box, compiled ok, switched back, compiled ok.
> Compilation problem in AccessController with JDK 6
> --
>
> Key: HBASE-9391
> URL: https://issues.apache.org/jira/browse/HBASE-9391
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.98.0, 0.95.2
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>
> Seeing this with a fresh checkout of trunk and 0.95, only with JDK 6:
> {noformat}
> [ERROR]
> hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java:[541,56]
> incompatible types; no instance(s) of type variable(s) K,V exist so that
> java.util.TreeMap conforms to java.util.Map>
> [ERROR] found : java.util.TreeMap
> [ERROR] required: java.util.Map>
> [ERROR]
> hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java:[1072,56]
> incompatible types; no instance(s) of type variable(s) K,V exist so that
> java.util.TreeMap conforms to java.util.Map>
> [ERROR] found : java.util.TreeMap
> [ERROR] required: java.util.Map>
> [ERROR]
> hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java:[1383,64]
> incompatible types; no instance(s) of type variable(s) K,V exist so that
> java.util.TreeMap conforms to java.util.Map>
> [ERROR] found : java.util.TreeMap
> [ERROR] required: java.util.Map>
> [ERROR]
> hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java:[1473,63]
> incompatible types; no instance(s) of type variable(s) K,V exist so that
> java.util.TreeMap conforms to
> java.util.Map>
> [ERROR] found : java.util.TreeMap
> [ERROR] required: java.util.Map>
> {noformat}
--
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-9391) Compilation problem in AccessController with JDK 6
Andrew Purtell created HBASE-9391:
-
Summary: Compilation problem in AccessController with JDK 6
Key: HBASE-9391
URL: https://issues.apache.org/jira/browse/HBASE-9391
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.2, 0.98.0
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Seeing this with a fresh checkout of trunk and 0.95, only with JDK 6:
{noformat}
[ERROR]
hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java:[541,56]
incompatible types; no instance(s) of type variable(s) K,V exist so that
java.util.TreeMap conforms to java.util.Map>
[ERROR] found : java.util.TreeMap
[ERROR] required: java.util.Map>
[ERROR]
hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java:[1072,56]
incompatible types; no instance(s) of type variable(s) K,V exist so that
java.util.TreeMap conforms to java.util.Map>
[ERROR] found : java.util.TreeMap
[ERROR] required: java.util.Map>
[ERROR]
hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java:[1383,64]
incompatible types; no instance(s) of type variable(s) K,V exist so that
java.util.TreeMap conforms to java.util.Map>
[ERROR] found : java.util.TreeMap
[ERROR] required: java.util.Map>
[ERROR]
hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java:[1473,63]
incompatible types; no instance(s) of type variable(s) K,V exist so that
java.util.TreeMap conforms to
java.util.Map>
[ERROR] found : java.util.TreeMap
[ERROR] required: java.util.Map>
{noformat}
--
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-9314) Dropping a table always prints a TableInfoMissingException in the master log
[
https://issues.apache.org/jira/browse/HBASE-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-9314:
--
Attachment: 9314-0.94.patch
9314.patch
Testing the attached patches now.
> Dropping a table always prints a TableInfoMissingException in the master log
>
>
> Key: HBASE-9314
> URL: https://issues.apache.org/jira/browse/HBASE-9314
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 0.95.2, 0.94.10
>Reporter: Jean-Daniel Cryans
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 0.98.0, 0.94.12, 0.96.0
>
> Attachments: 9314-0.94.patch, 9314.patch
>
>
> Everytime I drop a table I get the same stack trace in the master's log:
> {noformat}
> 2013-08-22 23:11:31,939 DEBUG
> [MASTER_TABLE_OPERATIONS-jdec2hbase0403-1:6-0]
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Table 't' archived!
> 2013-08-22 23:11:31,939 DEBUG
> [MASTER_TABLE_OPERATIONS-jdec2hbase0403-1:6-0]
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Removing 't'
> descriptor.
> 2013-08-22 23:11:31,940 DEBUG
> [MASTER_TABLE_OPERATIONS-jdec2hbase0403-1:6-0]
> org.apache.hadoop.hbase.master.handler.DeleteTableHandler: Marking 't' as
> deleted.
> 2013-08-22 23:11:31,944 DEBUG
> [MASTER_TABLE_OPERATIONS-jdec2hbase0403-1:6-0]
> org.apache.hadoop.hbase.zookeeper.lock.ZKInterProcessLockBase: Released
> /hbase/table-lock/t/write-master:602
> 2013-08-22 23:11:32,024 DEBUG [RpcServer.handler=0,port=6]
> org.apache.hadoop.hbase.util.FSTableDescriptors: Exception during
> readTableDecriptor. Current table name = t
> org.apache.hadoop.hbase.TableInfoMissingException: No table descriptor file
> under hdfs://jdec2hbase0403-1.vpc.cloudera.com:9000/hbase/data/default/t
> at
> org.apache.hadoop.hbase.util.FSTableDescriptors.getTableDescriptorAndModtime(FSTableDescriptors.java:503)
> at
> org.apache.hadoop.hbase.util.FSTableDescriptors.getTableDescriptorAndModtime(FSTableDescriptors.java:496)
> at
> org.apache.hadoop.hbase.util.FSTableDescriptors.get(FSTableDescriptors.java:170)
> at
> org.apache.hadoop.hbase.master.HMaster.getTableDescriptors(HMaster.java:2629)
> at
> org.apache.hadoop.hbase.protobuf.generated.MasterMonitorProtos$MasterMonitorService$2.callBlockingMethod(MasterMonitorProtos.java:4634)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2156)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1861)
> 2013-08-22 23:11:32,024 WARN [RpcServer.handler=0,port=6]
> org.apache.hadoop.hbase.util.FSTableDescriptors: The following folder is in
> HBase's root directory and doesn't contain a table descriptor, do consider
> deleting it: t
> {noformat}
> But the operation completes.
--
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-9390) coprocessors observers are not called during a recovery with the new log replay algorithm
Nicolas Liochon created HBASE-9390: -- Summary: coprocessors observers are not called during a recovery with the new log replay algorithm Key: HBASE-9390 URL: https://issues.apache.org/jira/browse/HBASE-9390 Project: HBase Issue Type: Bug Components: Coprocessors, MTTR Affects Versions: 0.95.2 Reporter: Nicolas Liochon See the patch to reproduce the issue: If we activate log replay we don't have the events on WAL restore. Pinging [~jeffreyz], we discussed this offline. -- 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-9390) coprocessors observers are not called during a recovery with the new log replay algorithm
[ https://issues.apache.org/jira/browse/HBASE-9390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Liochon updated HBASE-9390: --- Attachment: copro.patch > coprocessors observers are not called during a recovery with the new log > replay algorithm > - > > Key: HBASE-9390 > URL: https://issues.apache.org/jira/browse/HBASE-9390 > Project: HBase > Issue Type: Bug > Components: Coprocessors, MTTR >Affects Versions: 0.95.2 >Reporter: Nicolas Liochon > Attachments: copro.patch > > > See the patch to reproduce the issue: If we activate log replay we don't have > the events on WAL restore. > Pinging [~jeffreyz], we discussed this offline. -- 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-9389) Favorednodes command line not verifying assignments correctly
[
https://issues.apache.org/jira/browse/HBASE-9389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754533#comment-13754533
]
Nicolas Liochon commented on HBASE-9389:
for verifyRegionPlacement:
bq. + * @param report
It should be @ return
But while this method now returns a report it's never used?
+if (cfStatus.getPath().getName().startsWith(".") ||
+
HConstants.HBASE_NON_USER_TABLE_DIRS.contains(cfStatus.getPath().getName())) {
We were skipping the "technical directories", and .META., and now explicitly
the system tables, but are we right to skip the system tables, .META. included?
I could imagine that we want to use the favored node configuration for them as
well.
> Favorednodes command line not verifying assignments correctly
> -
>
> Key: HBASE-9389
> URL: https://issues.apache.org/jira/browse/HBASE-9389
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.96.0
>Reporter: Devaraj Das
>Assignee: Devaraj Das
>Priority: Critical
> Fix For: 0.96.0
>
> Attachments: verification-fix.1.txt
>
>
> In manual testing, encountered an issue to do with the command line tool
> (HBASE-9116) not verifying the assignments correctly. Although the regions
> are assigned to the favored nodes, the verification/print showed otherwise.
> The command to reproduce the problem (after having created the tables, and
> loading some data):
> bin/hbase org.apache.hadoop.hbase.master.RegionPlacementMaintainer -tables
> cluster_test1,cluster_test2 -hbase_root /apps/hbase/data -v
--
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-9359) Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter
[
https://issues.apache.org/jira/browse/HBASE-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754519#comment-13754519
]
Hadoop QA commented on HBASE-9359:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12600739/hbase-9359-9334.v6.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 231
new or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
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 cause Findbugs
(version 1.3.9) to fail.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6982//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6982//console
This message is automatically generated.
> Convert KeyValue to Cell in hbase-client module - Result/Put/Delete,
> ColumnInterpreter
> --
>
> Key: HBASE-9359
> URL: https://issues.apache.org/jira/browse/HBASE-9359
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Affects Versions: 0.95.2
>Reporter: Jonathan Hsieh
>Assignee: Jonathan Hsieh
> Fix For: 0.98.0, 0.96.0
>
> Attachments: hbase-9334-9359.v4.patch, hbase-9359-9334.v5.patch,
> hbase-9359-9334.v6.patch, hbase-9359.patch, hbase-9359.v2.patch,
> hbase-9359.v3.patch, hbase-9359.v5.patch, hbase-9359.v6.patch
>
>
> This path is the second half of eliminating KeyValue from the client
> interfaces. This percolated through quite a bit.
--
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-5954) Allow proper fsync support for HBase
[ https://issues.apache.org/jira/browse/HBASE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754495#comment-13754495 ] Liang Xie commented on HBASE-5954: -- [~haosd...@gmail.com], IMHO, fsync + write barrier combination should has guarantee the data be written to disk (with issuing a disk cache flush instruction). is it relatived with "data=ordered" mount option? thanks > Allow proper fsync support for HBase > > > Key: HBASE-5954 > URL: https://issues.apache.org/jira/browse/HBASE-5954 > Project: HBase > Issue Type: Improvement >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl >Priority: Critical > Fix For: 0.98.0 > > Attachments: 5954-trunk-hdfs-trunk.txt, 5954-trunk-hdfs-trunk-v2.txt, > 5954-trunk-hdfs-trunk-v3.txt, 5954-trunk-hdfs-trunk-v4.txt, > 5954-trunk-hdfs-trunk-v5.txt, 5954-trunk-hdfs-trunk-v6.txt, hbase-hdfs-744.txt > > > At least get recommendation into 0.96 doc and some numbers running w/ this > hdfs feature enabled. -- 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-5954) Allow proper fsync support for HBase
[ https://issues.apache.org/jira/browse/HBASE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754475#comment-13754475 ] haosdent commented on HBASE-5954: - Only when we open write barrier and mount disk with "data=ordered", we could make sure that the data have been flush to physics disk after we call fsync system call. > Allow proper fsync support for HBase > > > Key: HBASE-5954 > URL: https://issues.apache.org/jira/browse/HBASE-5954 > Project: HBase > Issue Type: Improvement >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl >Priority: Critical > Fix For: 0.98.0 > > Attachments: 5954-trunk-hdfs-trunk.txt, 5954-trunk-hdfs-trunk-v2.txt, > 5954-trunk-hdfs-trunk-v3.txt, 5954-trunk-hdfs-trunk-v4.txt, > 5954-trunk-hdfs-trunk-v5.txt, 5954-trunk-hdfs-trunk-v6.txt, hbase-hdfs-744.txt > > > At least get recommendation into 0.96 doc and some numbers running w/ this > hdfs feature enabled. -- 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-9359) Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter
[
https://issues.apache.org/jira/browse/HBASE-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754470#comment-13754470
]
Hadoop QA commented on HBASE-9359:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12600739/hbase-9359-9334.v6.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 231
new or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any 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 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6979//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6979//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6979//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6979//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6979//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6979//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6979//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6979//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6979//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6979//console
This message is automatically generated.
> Convert KeyValue to Cell in hbase-client module - Result/Put/Delete,
> ColumnInterpreter
> --
>
> Key: HBASE-9359
> URL: https://issues.apache.org/jira/browse/HBASE-9359
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Affects Versions: 0.95.2
>Reporter: Jonathan Hsieh
>Assignee: Jonathan Hsieh
> Fix For: 0.98.0, 0.96.0
>
> Attachments: hbase-9334-9359.v4.patch, hbase-9359-9334.v5.patch,
> hbase-9359-9334.v6.patch, hbase-9359.patch, hbase-9359.v2.patch,
> hbase-9359.v3.patch, hbase-9359.v5.patch, hbase-9359.v6.patch
>
>
> This path is the second half of eliminating KeyValue from the client
> interfaces. This percolated through quite a bit.
--
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-9359) Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter
[ https://issues.apache.org/jira/browse/HBASE-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754469#comment-13754469 ] Jonathan Hsieh commented on HBASE-9359: --- v6 applies cleanly to 0.95/0.96. > Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, > ColumnInterpreter > -- > > Key: HBASE-9359 > URL: https://issues.apache.org/jira/browse/HBASE-9359 > Project: HBase > Issue Type: Sub-task > Components: Client >Affects Versions: 0.95.2 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > Fix For: 0.98.0, 0.96.0 > > Attachments: hbase-9334-9359.v4.patch, hbase-9359-9334.v5.patch, > hbase-9359-9334.v6.patch, hbase-9359.patch, hbase-9359.v2.patch, > hbase-9359.v3.patch, hbase-9359.v5.patch, hbase-9359.v6.patch > > > This path is the second half of eliminating KeyValue from the client > interfaces. This percolated through quite a bit. -- 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-5954) Allow proper fsync support for HBase
[ https://issues.apache.org/jira/browse/HBASE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754467#comment-13754467 ] haosdent commented on HBASE-5954: - [~lhofhansl] My test result: Without WAL/HFile sync: ~13s With WAL/HFile sync: ~120s Anything wrong? > Allow proper fsync support for HBase > > > Key: HBASE-5954 > URL: https://issues.apache.org/jira/browse/HBASE-5954 > Project: HBase > Issue Type: Improvement >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl >Priority: Critical > Fix For: 0.98.0 > > Attachments: 5954-trunk-hdfs-trunk.txt, 5954-trunk-hdfs-trunk-v2.txt, > 5954-trunk-hdfs-trunk-v3.txt, 5954-trunk-hdfs-trunk-v4.txt, > 5954-trunk-hdfs-trunk-v5.txt, 5954-trunk-hdfs-trunk-v6.txt, hbase-hdfs-744.txt > > > At least get recommendation into 0.96 doc and some numbers running w/ this > hdfs feature enabled. -- 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-7525) A canary monitoring program specifically for regionserver
[
https://issues.apache.org/jira/browse/HBASE-7525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754458#comment-13754458
]
takeshi.miao commented on HBASE-7525:
-
Dear [~stack]
Here is the answer for your questions
{quote}
./hbase-0.95.3-SNAPSHOT/bin/hbase --config /home/stack/conf_hbase
org.apache.hadoop.hbase.tool.Canary
... it goes off and does something; default looks to go and get from all
regions.
{quote}
Yes, it's default behavior is just align with the old one, does the all regions
monitoring
bq. You add 2013-08-29 09:32:16,463 DEBUG [main] tool.Canary: runCount=2. What
does it mean ?
It is the internal DEBUG msg, for counting how many loop of this monitor
instance did; It can help user to observe the monitor instance's behavior
whether as expected
Following are the questions you asked about _'-regionserver'_ option
{quote}
{code}
Usage: bin/hbase org.apache.hadoop.hbase.tool.Canary [opts] [table/regionserver
1 [table/regionserver 2...]]
...
{code}
{quote}
{quote}
Would it be clearer if the -regionserver option took arguments as in
-regionserver=rs1,rs2,rs3 etc.?
How to interpret this then:
Usage: bin/hbase org.apache.hadoop.hbase.tool.Canary -regionserver=rs1 table1
Would above only get regions from table1 on rs1? If no regions from table1 then
it would print out there are none?
{quote}
The option _'-regionserver'_ (regionserver mode) is exclusive with the default
mode (region mode), which means user can only choose to use default mode or
regionserver mode either
bq. I do not know how to read 'table/regionserver 1'. What is the '1'?
So it seems the usage output confuses the user, I would like to change it to
following, how do you think ?
{code}
Usage: bin/hbase org.apache.hadoop.hbase.tool.Canary [opts] [table|regionserver
[table|regionserver ...]]
...
{code}
{quote}
Or if you pass a table1 when you have a -regionserver option specified, you
could just fail with "Cannot pass a tablename when using the -regionserver
option" – that'd probably be simplest.
{quote}
Yes, this is a good suggestion, but currently I would not check this if the
passed arguments are whether tableNames in HBase, due to I need to new a
HBaseAdim instance to get the table list firstly, then compare them with the
passed argument.
How do you think that I modify the usage output more precisely for
-regionserver option ? such as...
{code}
...
-regionserver replace the table argument to regionserver,
which means to enable regionserver mode, instead of region mode (default)
...
{code}
Either way is ok for me.
I will upload the new patches after we confirm which way to go, and tks for
your questions and suggestions :)
> A canary monitoring program specifically for regionserver
> -
>
> Key: HBASE-7525
> URL: https://issues.apache.org/jira/browse/HBASE-7525
> Project: HBase
> Issue Type: New Feature
> Components: monitoring
>Affects Versions: 0.94.0
>Reporter: takeshi.miao
>Priority: Critical
> Fix For: 0.98.0
>
> Attachments: HBASE-7525-0.95-v0.patch, HBASE-7525-0.95-v1.patch,
> HBASE-7525-0.95-v3.patch, HBASE-7525-0.95-v4.patch, HBASE-7525-0.95-v6.patch,
> HBASE-7525-trunk-v2.patch, HBASE-7525-v0.patch, RegionServerCanary.java
>
>
> *Motivation*
> This ticket is to provide a canary monitoring tool specifically for
> HRegionserver, details as follows
> 1. This tool is required by operation team due to they thought that the
> canary for each region of a HBase is too many for them, so I implemented this
> coarse-granular one based on the original o.a.h.h.tool.Canary for them
> 2. And this tool is implemented by multi-threading, which means the each Get
> request sent by a thread. the reason I use this way is due to we suffered the
> region server hung issue by now the root cause is still not clear. so this
> tool can help operation team to detect hung region server if any.
> *example*
> 1. the tool docs
> ./bin/hbase org.apache.hadoop.hbase.tool.RegionServerCanary -help
> Usage: [opts] [regionServerName 1 [regionServrName 2...]]
> regionServerName - FQDN serverName, can use linux command:hostname -f to
> check your serverName
> where [-opts] are:
>-help Show this help and exit.
>-eUse regionServerName as regular expression
> which means the regionServerName is regular expression pattern
>-f stop whole program if first error occurs, default is true
>-t timeout for a check, default is 60 (milisecs)
>-daemonContinuous check at defined intervals.
>-interval Interval between checks (sec)
> 2. Will send a request to each regionserver in a HBase cluster
> ./bin/hbase org.apache.hadoop.hbase.tool.RegionServerCanary
> 3. Will send a request to a regionserver by give
