[jira] [Updated] (HBASE-13488) regionserver make lots of CLOSE_WAIT connection to dn
[ https://issues.apache.org/jira/browse/HBASE-13488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lv9 updated HBASE-13488: Affects Version/s: 1.2.0 > regionserver make lots of CLOSE_WAIT connection to dn > - > > Key: HBASE-13488 > URL: https://issues.apache.org/jira/browse/HBASE-13488 > Project: HBase > Issue Type: Bug > Components: hadoop2 >Affects Versions: 0.98.1, 1.2.0 > Environment: CentOS release 6.4 (Final) > hadoop-2.3.0 >Reporter: dirk.zhang > > when start hbase，regionserver make a lot sockets with CLOSE_WAIT connected > datanode,the default port is 50010 > I guest the datanode is closed or went away,but RS doesn't close > I have tried the issue HDFS-5671 , HBASE-11142 , HBASE-9393,but no help,and > I use hadoop-2.3.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15293) Handle TableNotFound and IllegalArgument exceptions in table.jsp.
[ https://issues.apache.org/jira/browse/HBASE-15293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samir Ahmic updated HBASE-15293: Attachment: HBASE-15293_v3.patch Here is new patch tabs cleaned. Thanks for tip [~tedyu] and sorry for inconvenience with tabs :) > Handle TableNotFound and IllegalArgument exceptions in table.jsp. > - > > Key: HBASE-15293 > URL: https://issues.apache.org/jira/browse/HBASE-15293 > Project: HBase > Issue Type: Sub-task > Components: UI >Affects Versions: 2.0.0 >Reporter: Samir Ahmic >Assignee: Samir Ahmic > Fix For: 2.0.0 > > Attachments: HBASE-15293_v0.patch, HBASE-15293_v1.patch, > HBASE-15293_v1.patch, HBASE-15293_v2.patch, HBASE-15293_v3.patch > > > table.jsp accepts "name" parameter for table name and in case when table does > not exist or empty parameter is passed it will throw 500 error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-7912) HBase Backup/Restore Based on HBase Snapshot
[
https://issues.apache.org/jira/browse/HBASE-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221184#comment-15221184
]
Vladimir Rodionov commented on HBASE-7912:
--
{quote}
This structure will allow the rest of the code base (like hfile links, etc) to
work seamlessly and also will help with a large number of files under WALs.
Also, all the table in the table set for a backup will be hosted together etc.
{quote}
How is that? For myself, personally, existing backup root layout is not a US
Constitution - can be changed. Two requirements:
# Must be justified and rational
# We have spare time to work on it.
> HBase Backup/Restore Based on HBase Snapshot
>
>
> Key: HBASE-7912
> URL: https://issues.apache.org/jira/browse/HBASE-7912
> Project: HBase
> Issue Type: Sub-task
>Reporter: Richard Ding
>Assignee: Vladimir Rodionov
> Labels: backup
> Fix For: 2.0.0
>
> Attachments: HBaseBackupRestore-Jira-7912-DesignDoc-v1.pdf,
> HBaseBackupRestore-Jira-7912-DesignDoc-v2.pdf,
> HBaseBackupRestore-Jira-7912-v4.pdf, HBaseBackupRestore-Jira-7912-v5 .pdf,
> HBaseBackupRestore-Jira-7912-v6.pdf, HBaseBackupandRestore.pdf,
> HBase_BackupRestore-Jira-7912-CLI-v1.pdf
>
>
> Finally, we completed the implementation of our backup/restore solution, and
> would like to share with community through this jira.
> We are leveraging existing hbase snapshot feature, and provide a general
> solution to common users. Our full backup is using snapshot to capture
> metadata locally and using exportsnapshot to move data to another cluster;
> the incremental backup is using offline-WALplayer to backup HLogs; we also
> leverage global distribution rolllog and flush to improve performance; other
> added-on values such as convert, merge, progress report, and CLI commands. So
> that a common user can backup hbase data without in-depth knowledge of hbase.
> Our solution also contains some usability features for enterprise users.
> The detail design document and CLI command will be attached in this jira. We
> plan to use 10~12 subtasks to share each of the following features, and
> document the detail implement in the subtasks:
> * *Full Backup* : provide local and remote back/restore for a list of tables
> * *offline-WALPlayer* to convert HLog to HFiles offline (for incremental
> backup)
> * *distributed* Logroll and distributed flush
> * Backup *Manifest* and history
> * *Incremental* backup: to build on top of full backup as daily/weekly backup
> * *Convert* incremental backup WAL files into hfiles
> * *Merge* several backup images into one(like merge weekly into monthly)
> * *add and remove* table to and from Backup image
> * *Cancel* a backup process
> * backup progress *status*
> * full backup based on *existing snapshot*
> *-*
> *Below is the original description, to keep here as the history for the
> design and discussion back in 2013*
> There have been attempts in the past to come up with a viable HBase
> backup/restore solution (e.g., HBASE-4618). Recently, there are many
> advancements and new features in HBase, for example, FileLink, Snapshot, and
> Distributed Barrier Procedure. This is a proposal for a backup/restore
> solution that utilizes these new features to achieve better performance and
> consistency.
>
> A common practice of backup and restore in database is to first take full
> baseline backup, and then periodically take incremental backup that capture
> the changes since the full baseline backup. HBase cluster can store massive
> amount data. Combination of full backups with incremental backups has
> tremendous benefit for HBase as well. The following is a typical scenario
> for full and incremental backup.
> # The user takes a full backup of a table or a set of tables in HBase.
> # The user schedules periodical incremental backups to capture the changes
> from the full backup, or from last incremental backup.
> # The user needs to restore table data to a past point of time.
> # The full backup is restored to the table(s) or to different table name(s).
> Then the incremental backups that are up to the desired point in time are
> applied on top of the full backup.
> We would support the following key features and capabilities.
> * Full backup uses HBase snapshot to capture HFiles.
> * Use HBase WALs to capture incremental changes, but we use bulk load of
> HFiles for fast incremental restore.
> * Support single table or a set of tables, and column family level backup and
> restore.
> * Restore to different table names.
> * Support adding additional tables or CF to backup set without interruption
> of incremental backup schedule.
> *
[jira] [Commented] (HBASE-15485) Filter.reset() should not be called between batches
[
https://issues.apache.org/jira/browse/HBASE-15485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221180#comment-15221180
]
Hadoop QA commented on HBASE-15485:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
11s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 47s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 32s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 4m
16s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
16s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
50s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 26s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 33s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
44s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 41s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 41s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 33s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 33s
{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 5m 4s
{color} | {color:red} hbase-server: patch generated 1 new + 220 unchanged - 1
fixed = 221 total (was 221) {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
16s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
26m 12s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
14s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 27s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 34s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 98m 41s {color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
16s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 148m 4s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Timed out junit tests |
org.apache.hadoop.hbase.snapshot.TestFlushSnapshotFromClient |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12796453/HBASE-15485-v5.patch |
| JIRA Issue | HBASE-15485 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux asf906.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 6905d27 |
| Default Java | 1.7.0_79 |
| Multi-JDK versions | /home/jenkins/tools/java/jdk1.8.0:1.8.0
[jira] [Updated] (HBASE-15521) Procedure V2 - RestoreSnapshot and CloneSnapshot
[ https://issues.apache.org/jira/browse/HBASE-15521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Yuan Jiang updated HBASE-15521: --- Labels: Rev (was: ) > Procedure V2 - RestoreSnapshot and CloneSnapshot > > > Key: HBASE-15521 > URL: https://issues.apache.org/jira/browse/HBASE-15521 > Project: HBase > Issue Type: Sub-task > Components: Client, master, proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > Labels: Rev > Fix For: 2.0.0 > > Attachments: HBASE-15521.v1-master.patch > > > Implement procedure-v2 based restore snapshot and clone snapshot (both server > and client side change). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15521) Procedure V2 - RestoreSnapshot and CloneSnapshot
[ https://issues.apache.org/jira/browse/HBASE-15521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Yuan Jiang updated HBASE-15521: --- Hadoop Flags: Incompatible change,Reviewed (was: Incompatible change) > Procedure V2 - RestoreSnapshot and CloneSnapshot > > > Key: HBASE-15521 > URL: https://issues.apache.org/jira/browse/HBASE-15521 > Project: HBase > Issue Type: Sub-task > Components: Client, master, proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > Labels: Rev > Fix For: 2.0.0 > > Attachments: HBASE-15521.v1-master.patch > > > Implement procedure-v2 based restore snapshot and clone snapshot (both server > and client side change). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15568) Procedure V2 - Remove CreateTableHandler in HBase Apache 2.0 release
[ https://issues.apache.org/jira/browse/HBASE-15568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Yuan Jiang updated HBASE-15568: --- Attachment: HBASE-15568.v1-master.patch > Procedure V2 - Remove CreateTableHandler in HBase Apache 2.0 release > > > Key: HBASE-15568 > URL: https://issues.apache.org/jira/browse/HBASE-15568 > Project: HBase > Issue Type: Sub-task > Components: master, proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > Fix For: 2.0.0 > > Attachments: HBASE-15568.v1-master.patch > > > With the 'create table' and 'clone snapshot' operation move to Procedure-V2 > based implementation in 2.0 release. There is no need to keep the > handler-based implementation. > Note: this JIRA is Apache 2.0 release only. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15568) Procedure V2 - Remove CreateTableHandler in HBase Apache 2.0 release
[ https://issues.apache.org/jira/browse/HBASE-15568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Yuan Jiang updated HBASE-15568: --- Hadoop Flags: Incompatible change Status: Patch Available (was: Open) > Procedure V2 - Remove CreateTableHandler in HBase Apache 2.0 release > > > Key: HBASE-15568 > URL: https://issues.apache.org/jira/browse/HBASE-15568 > Project: HBase > Issue Type: Sub-task > Components: master, proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > Fix For: 2.0.0 > > Attachments: HBASE-15568.v1-master.patch > > > With the 'create table' and 'clone snapshot' operation move to Procedure-V2 > based implementation in 2.0 release. There is no need to keep the > handler-based implementation. > Note: this JIRA is Apache 2.0 release only. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15575) Rename table DDL *Handler methods in MasterObserver to *Procedure
[ https://issues.apache.org/jira/browse/HBASE-15575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221176#comment-15221176 ] Stephen Yuan Jiang commented on HBASE-15575: The initial patch can be reviewed in https://reviews.apache.org/r/44294/ > Rename table DDL *Handler methods in MasterObserver to *Procedure > - > > Key: HBASE-15575 > URL: https://issues.apache.org/jira/browse/HBASE-15575 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang >Priority: Minor > Fix For: 2.0.0 > > > Procedure V2 replaced table DDL handler implementation to procedure > implementation. It does not make sense to keep the *Handler methods in > MasterObserver. This JIRA follows HBASE-13645 way to deprecate the existing > observers with *Handler and add the new observers with *Procedure name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-15575) Rename table DDL *Handler methods in MasterObserver to *Procedure
Stephen Yuan Jiang created HBASE-15575: -- Summary: Rename table DDL *Handler methods in MasterObserver to *Procedure Key: HBASE-15575 URL: https://issues.apache.org/jira/browse/HBASE-15575 Project: HBase Issue Type: Sub-task Components: Coprocessors Reporter: Stephen Yuan Jiang Assignee: Stephen Yuan Jiang Priority: Minor Fix For: 2.0.0 Procedure V2 replaced table DDL handler implementation to procedure implementation. It does not make sense to keep the *Handler methods in MasterObserver. This JIRA follows HBASE-13645 way to deprecate the existing observers with *Handler and add the new observers with *Procedure name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15571) Make MasterProcedureManagerHost accessible through MasterServices
[ https://issues.apache.org/jira/browse/HBASE-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221163#comment-15221163 ] Hudson commented on HBASE-15571: FAILURE: Integrated in HBase-Trunk_matrix #819 (See [https://builds.apache.org/job/HBase-Trunk_matrix/819/]) HBASE-15571 Make MasterProcedureManagerHost accessible through (tedyu: rev 8c7f044efbb8a84561d28a221343c7b65263934e) * hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterRpcServices.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterServices.java * hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestCatalogJanitor.java > Make MasterProcedureManagerHost accessible through MasterServices > - > > Key: HBASE-15571 > URL: https://issues.apache.org/jira/browse/HBASE-15571 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 2.0.0, 1.4.0 > > Attachments: 15571.v1.patch, 15571.v2.patch > > > One of the review comments for HBASE-15411 is to drop dependency on > HBaseAdmin in table backup procedure. > See the comments starting with: > https://issues.apache.org/jira/browse/HBASE-15411?focusedCommentId=15219215=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15219215 > In order to execute procedure inside table backup procedure, we need access > to MasterProcedureManagerHost. > This issue adds accessor to MasterServices for MasterProcedureManagerHost. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15521) Procedure V2 - RestoreSnapshot and CloneSnapshot
[ https://issues.apache.org/jira/browse/HBASE-15521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Yuan Jiang updated HBASE-15521: --- Resolution: Fixed Fix Version/s: 2.0.0 Status: Resolved (was: Patch Available) > Procedure V2 - RestoreSnapshot and CloneSnapshot > > > Key: HBASE-15521 > URL: https://issues.apache.org/jira/browse/HBASE-15521 > Project: HBase > Issue Type: Sub-task > Components: Client, master, proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > Fix For: 2.0.0 > > Attachments: HBASE-15521.v1-master.patch > > > Implement procedure-v2 based restore snapshot and clone snapshot (both server > and client side change). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15480) Bloom Filter check needs to be more efficient for array
[ https://issues.apache.org/jira/browse/HBASE-15480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221152#comment-15221152 ] stack commented on HBASE-15480: --- Group check sounds good. The new API would be used by upper layers? It looks at returned bitset and skips out on those that are positive? > Bloom Filter check needs to be more efficient for array > --- > > Key: HBASE-15480 > URL: https://issues.apache.org/jira/browse/HBASE-15480 > Project: HBase > Issue Type: Improvement > Components: Performance >Affects Versions: 1.0.3 >Reporter: Walter Koetke >Assignee: Walter Koetke > Fix For: 1.0.4 > > Attachments: BloomFilterCheckOneByOne.tiff, > HBASE-15480-branch-1.0.patch > > > It is currently inefficient to do lots of bloom filter checks. Each check has > overhead like going to the block cache to retrieve the block and recording > metrics. It would be good to have one bloom filter check api that does a > bunch of checks without so much block retrieval and metrics updates. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15521) Procedure V2 - RestoreSnapshot and CloneSnapshot
[
https://issues.apache.org/jira/browse/HBASE-15521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221151#comment-15221151
]
Stephen Yuan Jiang commented on HBASE-15521:
The white space is from generated proto java file.
The failures of unit tests have nothing to do with the change. Both
{{hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures}} and
{{org.apache.hadoop.hbase.security.access.TestNamespaceCommands}} passed when
running locally.
> Procedure V2 - RestoreSnapshot and CloneSnapshot
>
>
> Key: HBASE-15521
> URL: https://issues.apache.org/jira/browse/HBASE-15521
> Project: HBase
> Issue Type: Sub-task
> Components: Client, master, proc-v2
>Affects Versions: 2.0.0
>Reporter: Stephen Yuan Jiang
>Assignee: Stephen Yuan Jiang
> Attachments: HBASE-15521.v1-master.patch
>
>
> Implement procedure-v2 based restore snapshot and clone snapshot (both server
> and client side change).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15396) Enhance mapreduce.TableSplit to add encoded region name
[ https://issues.apache.org/jira/browse/HBASE-15396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221144#comment-15221144 ] Sean Busbey commented on HBASE-15396: - pushed to master. There were substantial conflicts on cherry-pick; can you make a branch-1 version please? > Enhance mapreduce.TableSplit to add encoded region name > --- > > Key: HBASE-15396 > URL: https://issues.apache.org/jira/browse/HBASE-15396 > Project: HBase > Issue Type: Improvement > Components: mapreduce >Affects Versions: 1.3.0 >Reporter: Harsh J >Assignee: Harsh J >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.4.0 > > Attachments: HBASE-15396.patch, HBASE-15396.patch, HBASE-15396.patch, > HBASE-15396.patch > > > When troubleshooting HBase-input MR job map failures, the TableSplit's > toString() definition comes very handy. However, it still does not tell us > directly which region ID it was created for (it does tell us the key and the > host, but not the exact region name, so there's a second lookup needed from > the UI to find the ID to then check the servers with). > It would be beneficial to have the encoded region name as part of the output, > so this extra manual lookup can be avoided. The encoded name is much easier > to find events with. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15569) Make Bytes.toStringBinary faster
[
https://issues.apache.org/jira/browse/HBASE-15569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15569:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 1.2.2
1.4.0
1.3.0
2.0.0
Status: Resolved (was: Patch Available)
Pushed to branch-1.2+ Thanks [~junegunn] for nice patch
> Make Bytes.toStringBinary faster
>
>
> Key: HBASE-15569
> URL: https://issues.apache.org/jira/browse/HBASE-15569
> Project: HBase
> Issue Type: Improvement
> Components: Performance
>Reporter: Junegunn Choi
>Assignee: Junegunn Choi
>Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2
>
> Attachments: HBASE-15569.patch
>
>
> Bytes.toStringBinary is quite expensive due to its use of {{String.format}}.
> It seems to me that {{String.format}} is overkill for the purpose and I could
> actually make the function up to 45-times faster by replacing the part with a
> simpler hand-crafted code.
> This is probably a non-issue for HBase server as the function is not used in
> performance-sensitive contexts but I figured it wouldn't hurt to make it
> faster as it's widely used in builtin tools - Shell, {{HFilePrettyPrinter}}
> with {{-p}} option, etc. - and it can be used in clients.
> h4. Background:
> We have [an HBase monitoring
> tool|https://github.com/kakao/hbase-region-inspector] that periodically
> collects the information of the regions and it calls {{Bytes.toStringBinary}}
> during the process to make some information suitable for display. Profiling
> revealed that a large portion of the processing time was spent in
> {{String.format}}.
> h4. Micro-benchmark:
> {code}
> byte[] bytes = new byte[256];
> for (int i = 0; i < bytes.length; ++i) {
> // Mixture of printable and non-printable characters.
> // Maximal performance gain (45x) is observed when the array is solely
> // composed of non-printable characters.
> bytes[i] = (byte) i;
> }
> long started = System.nanoTime();
> for (int i = 0; i < 100; ++i) {
> Bytes.toStringBinary(bytes);
> }
> System.out.println(TimeUnit.NANOSECONDS.toMillis(System.nanoTime() -
> started));
> {code}
> - Without the patch: 134176 ms
> - With the patch: 3890 ms
> I made sure that the new version returns the same value as before and
> simplified the check for non-printable characters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15571) Make MasterProcedureManagerHost accessible through MasterServices
[ https://issues.apache.org/jira/browse/HBASE-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221134#comment-15221134 ] Ted Yu commented on HBASE-15571: HMaster interacts with the loaded procedure manager through MasterProcedureManagerHost. So we need this class so that table backup procedure can execute globally barriered procedure. > Make MasterProcedureManagerHost accessible through MasterServices > - > > Key: HBASE-15571 > URL: https://issues.apache.org/jira/browse/HBASE-15571 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 2.0.0, 1.4.0 > > Attachments: 15571.v1.patch, 15571.v2.patch > > > One of the review comments for HBASE-15411 is to drop dependency on > HBaseAdmin in table backup procedure. > See the comments starting with: > https://issues.apache.org/jira/browse/HBASE-15411?focusedCommentId=15219215=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15219215 > In order to execute procedure inside table backup procedure, we need access > to MasterProcedureManagerHost. > This issue adds accessor to MasterServices for MasterProcedureManagerHost. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15571) Make MasterProcedureManagerHost accessible through MasterServices
[ https://issues.apache.org/jira/browse/HBASE-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221130#comment-15221130 ] stack commented on HBASE-15571: --- You fellows get the bit that we want to keep the *Services -- MasterServices and RegionServerServices -- narrow with minimal stuff in it because otherwise, we might as well just pass Master rather than MasterServices? What is a MasterProcedureManagerHost? It is important enough to be exposed in *Services? > Make MasterProcedureManagerHost accessible through MasterServices > - > > Key: HBASE-15571 > URL: https://issues.apache.org/jira/browse/HBASE-15571 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 2.0.0, 1.4.0 > > Attachments: 15571.v1.patch, 15571.v2.patch > > > One of the review comments for HBASE-15411 is to drop dependency on > HBaseAdmin in table backup procedure. > See the comments starting with: > https://issues.apache.org/jira/browse/HBASE-15411?focusedCommentId=15219215=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15219215 > In order to execute procedure inside table backup procedure, we need access > to MasterProcedureManagerHost. > This issue adds accessor to MasterServices for MasterProcedureManagerHost. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15574) Minor typo on HRegionServerCommandLine.java
[ https://issues.apache.org/jira/browse/HBASE-15574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221131#comment-15221131 ] Lim Chee Hau commented on HBASE-15574: -- I have created the pull request on Github, https://github.com/apache/hbase/pull/16 Thanks! > Minor typo on HRegionServerCommandLine.java > --- > > Key: HBASE-15574 > URL: https://issues.apache.org/jira/browse/HBASE-15574 > Project: HBase > Issue Type: Bug >Reporter: Lim Chee Hau >Assignee: Lim Chee Hau >Priority: Trivial > > Fix typo, add missing space between two words in HRegionServerCommandLine.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-15574) Minor typo on HRegionServerCommandLine.java
Lim Chee Hau created HBASE-15574: Summary: Minor typo on HRegionServerCommandLine.java Key: HBASE-15574 URL: https://issues.apache.org/jira/browse/HBASE-15574 Project: HBase Issue Type: Bug Reporter: Lim Chee Hau Assignee: Lim Chee Hau Priority: Trivial Fix typo, add missing space between two words in HRegionServerCommandLine.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[ https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221127#comment-15221127 ] Ted Yu commented on HBASE-15572: Please also note the reason for revert in the commit message. > Adding optional timestamp semantics to HBase-Spark > -- > > Key: HBASE-15572 > URL: https://issues.apache.org/jira/browse/HBASE-15572 > Project: HBase > Issue Type: New Feature > Components: spark >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Fix For: 2.0.0 > > Attachments: HBASE-15572-1.patch, HBASE-15572-2.patch, > HBASE-15572-3.patch > > > Right now the timestamp is always latest. With this patch, users can select > timestamps they want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15187) Integrate CSRF prevention filter to REST gateway
[ https://issues.apache.org/jira/browse/HBASE-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221119#comment-15221119 ] Ted Yu commented on HBASE-15187: Planning to commit the patch soon, if there is no further review comment. > Integrate CSRF prevention filter to REST gateway > > > Key: HBASE-15187 > URL: https://issues.apache.org/jira/browse/HBASE-15187 > Project: HBase > Issue Type: Bug >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 2.0.0 > > Attachments: HBASE-15187-branch-1.v13.patch, HBASE-15187.v1.patch, > HBASE-15187.v10.patch, HBASE-15187.v11.patch, HBASE-15187.v12.patch, > HBASE-15187.v13.patch, HBASE-15187.v2.patch, HBASE-15187.v3.patch, > HBASE-15187.v4.patch, HBASE-15187.v5.patch, HBASE-15187.v6.patch, > HBASE-15187.v7.patch, HBASE-15187.v8.patch, HBASE-15187.v9.patch > > > HADOOP-12691 introduced a filter in Hadoop Common to help REST APIs guard > against cross-site request forgery attacks. > This issue tracks the integration of that filter into HBase REST gateway. > From REST section of refguide: > To delete a table, use a DELETE request with the /schema endpoint: > http://example.com:8000/schema > Suppose an attacker hosts a malicious web form on a domain under his control. > The form uses the DELETE action targeting a REST URL. Through social > engineering, the attacker tricks an authenticated user into accessing the > form and submitting it. > The browser sends the HTTP DELETE request to the REST gateway. > At REST gateway, the call is executed and user table is dropped -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15396) Enhance mapreduce.TableSplit to add encoded region name
[ https://issues.apache.org/jira/browse/HBASE-15396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221117#comment-15221117 ] Harsh J commented on HBASE-15396: - Thank you for the review [~busbey]! > Enhance mapreduce.TableSplit to add encoded region name > --- > > Key: HBASE-15396 > URL: https://issues.apache.org/jira/browse/HBASE-15396 > Project: HBase > Issue Type: Improvement > Components: mapreduce >Affects Versions: 1.3.0 >Reporter: Harsh J >Assignee: Harsh J >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.4.0 > > Attachments: HBASE-15396.patch, HBASE-15396.patch, HBASE-15396.patch, > HBASE-15396.patch > > > When troubleshooting HBase-input MR job map failures, the TableSplit's > toString() definition comes very handy. However, it still does not tell us > directly which region ID it was created for (it does tell us the key and the > host, but not the exact region name, so there's a second lookup needed from > the UI to find the ID to then check the servers with). > It would be beneficial to have the encoded region name as part of the output, > so this extra manual lookup can be avoided. The encoded name is much easier > to find events with. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15505) ReplicationPeerConfig should be builder-style
[
https://issues.apache.org/jira/browse/HBASE-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221104#comment-15221104
]
Hadoop QA commented on HBASE-15505:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 4 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
12s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 12s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 39s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 3m
47s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
26s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
18s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 9s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 44s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
41s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 53s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 53s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 45s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 45s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 3m
10s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
22s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
49m 37s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 9s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 57s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 35s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 2m 47s {color}
| {color:red} hbase-client in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
38s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 80m 56s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestUnmodifyableHTableDescriptor |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12796446/HBASE-15505.3.patch |
| JIRA Issue | HBASE-15505 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux asf900.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / eec27ad |
| Default Java | 1.7.0_79 |
| Multi-JDK versions | /home/jenkins/tools/java/jdk1.8.0:1.8.0
/usr/local/jenkins/java/jdk1.7.0_79:1.7.0_79 |
| findbugs | v3.0.0 |
| unit |
[jira] [Commented] (HBASE-15556) need extensible ConsistencyControl interface
[ https://issues.apache.org/jira/browse/HBASE-15556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221102#comment-15221102 ] stack commented on HBASE-15556: --- bq. Hold that thought about our custom bit...don't want to attach it here yet. The community would be interested in perf improvements if you have some. Community would be more interested in that than making MVCC pluggable (IMO). > need extensible ConsistencyControl interface > > > Key: HBASE-15556 > URL: https://issues.apache.org/jira/browse/HBASE-15556 > Project: HBase > Issue Type: Improvement >Affects Versions: 1.0.3 >Reporter: Walter Koetke >Assignee: Walter Koetke > Fix For: 1.0.4 > > Attachments: HBASE-15556-branch-1.0-02.patch, > HBASE-15556-branch-1.0.patch > > > The class MultiVersionConsistencyControl should be abstracted into an > interface ConsistencyControl so it can be extended by a configured custom > implementation class, with MultiVersionConsistencyControl as the default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15187) Integrate CSRF prevention filter to REST gateway
[ https://issues.apache.org/jira/browse/HBASE-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-15187: --- Hadoop Flags: Reviewed Fix Version/s: 2.0.0 Release Note: Protection against CSRF attack can be turned on with config parameter, hbase.rest.csrf.enabled - default value is false. The custom header to be sent can be changed via config parameter, hbase.rest.csrf.custom.header whose default value is "X-XSRF-HEADER". Config parameter, hbase.rest.csrf.methods.to.ignore , controls which HTTP methods are not associated with customer header check. Config parameter, hbase.rest-csrf.browser-useragents-regex , is a comma-separated list of regular expressions used to match against an HTTP request's User-Agent header when protection against cross-site request forgery (CSRF) is enabled for REST server by setting hbase.rest.csrf.enabled to true. > Integrate CSRF prevention filter to REST gateway > > > Key: HBASE-15187 > URL: https://issues.apache.org/jira/browse/HBASE-15187 > Project: HBase > Issue Type: Bug >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 2.0.0 > > Attachments: HBASE-15187-branch-1.v13.patch, HBASE-15187.v1.patch, > HBASE-15187.v10.patch, HBASE-15187.v11.patch, HBASE-15187.v12.patch, > HBASE-15187.v13.patch, HBASE-15187.v2.patch, HBASE-15187.v3.patch, > HBASE-15187.v4.patch, HBASE-15187.v5.patch, HBASE-15187.v6.patch, > HBASE-15187.v7.patch, HBASE-15187.v8.patch, HBASE-15187.v9.patch > > > HADOOP-12691 introduced a filter in Hadoop Common to help REST APIs guard > against cross-site request forgery attacks. > This issue tracks the integration of that filter into HBase REST gateway. > From REST section of refguide: > To delete a table, use a DELETE request with the /schema endpoint: > http://example.com:8000/schema > Suppose an attacker hosts a malicious web form on a domain under his control. > The form uses the DELETE action targeting a REST URL. Through social > engineering, the attacker tricks an authenticated user into accessing the > form and submitting it. > The browser sends the HTTP DELETE request to the REST gateway. > At REST gateway, the call is executed and user table is dropped -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[ https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221086#comment-15221086 ] Ted Yu commented on HBASE-15572: Normally the docs mentioned above can be added to this JIRA after commit. Now that the patch has been reverted, please re-commit when docs is added. > Adding optional timestamp semantics to HBase-Spark > -- > > Key: HBASE-15572 > URL: https://issues.apache.org/jira/browse/HBASE-15572 > Project: HBase > Issue Type: New Feature > Components: spark >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Fix For: 2.0.0 > > Attachments: HBASE-15572-1.patch, HBASE-15572-2.patch, > HBASE-15572-3.patch > > > Right now the timestamp is always latest. With this patch, users can select > timestamps they want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15571) Make MasterProcedureManagerHost accessible through MasterServices
[ https://issues.apache.org/jira/browse/HBASE-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221057#comment-15221057 ] Hudson commented on HBASE-15571: SUCCESS: Integrated in HBase-1.3-IT #591 (See [https://builds.apache.org/job/HBase-1.3-IT/591/]) HBASE-15571 Make MasterProcedureManagerHost accessible through (tedyu: rev b7df66f1a811a130c6fcc57d110659601c9c0cdd) * hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterRpcServices.java * hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestCatalogJanitor.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterServices.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java > Make MasterProcedureManagerHost accessible through MasterServices > - > > Key: HBASE-15571 > URL: https://issues.apache.org/jira/browse/HBASE-15571 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 2.0.0, 1.4.0 > > Attachments: 15571.v1.patch, 15571.v2.patch > > > One of the review comments for HBASE-15411 is to drop dependency on > HBaseAdmin in table backup procedure. > See the comments starting with: > https://issues.apache.org/jira/browse/HBASE-15411?focusedCommentId=15219215=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15219215 > In order to execute procedure inside table backup procedure, we need access > to MasterProcedureManagerHost. > This issue adds accessor to MasterServices for MasterProcedureManagerHost. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14123) HBase Backup/Restore Phase 2
[
https://issues.apache.org/jira/browse/HBASE-14123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221054#comment-15221054
]
Hadoop QA commented on HBASE-14123:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 6s {color}
| {color:red} HBASE-14123 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.2.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12796448/HBASE-14123-v15.patch
|
| JIRA Issue | HBASE-14123 |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/1257/console |
| Powered by | Apache Yetus 0.2.0 http://yetus.apache.org |
This message was automatically generated.
> HBase Backup/Restore Phase 2
>
>
> Key: HBASE-14123
> URL: https://issues.apache.org/jira/browse/HBASE-14123
> Project: HBase
> Issue Type: Umbrella
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
> Attachments: 14123-v14.txt, HBASE-14123-v1.patch,
> HBASE-14123-v10.patch, HBASE-14123-v11.patch, HBASE-14123-v12.patch,
> HBASE-14123-v13.patch, HBASE-14123-v15.patch, HBASE-14123-v2.patch,
> HBASE-14123-v3.patch, HBASE-14123-v4.patch, HBASE-14123-v5.patch,
> HBASE-14123-v6.patch, HBASE-14123-v7.patch, HBASE-14123-v9.patch
>
>
> Phase 2 umbrella JIRA. See HBASE-7912 for design document and description.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15571) Make MasterProcedureManagerHost accessible through MasterServices
[
https://issues.apache.org/jira/browse/HBASE-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221042#comment-15221042
]
Hadoop QA commented on HBASE-15571:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
28s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 29s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 56s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 6m
0s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
22s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m 3s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 3s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 3s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
14s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 27s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 27s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 57s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 57s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 6m
22s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
22s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
44m 35s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
17s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 4s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 8s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 183m 30s
{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
25s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 264m 30s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures |
| Timed out junit tests |
org.apache.hadoop.hbase.snapshot.TestMobSecureExportSnapshot |
| | org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot |
| | org.apache.hadoop.hbase.security.access.TestNamespaceCommands |
| | org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot |
| | org.apache.hadoop.hbase.snapshot.TestExportSnapshot |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12796411/15571.v2.patch |
| JIRA Issue | HBASE-15571 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux penates.apache.org 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT
Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven
[jira] [Updated] (HBASE-15485) Filter.reset() should not be called between batches
[ https://issues.apache.org/jira/browse/HBASE-15485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Yang updated HBASE-15485: -- Attachment: HBASE-15485-v5.patch > Filter.reset() should not be called between batches > --- > > Key: HBASE-15485 > URL: https://issues.apache.org/jira/browse/HBASE-15485 > Project: HBase > Issue Type: Bug >Affects Versions: 1.2.0, 1.1.3 >Reporter: Phil Yang >Assignee: Phil Yang > Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.5, 1.2.2 > > Attachments: HBASE-15485-branch-1-v2.patch, > HBASE-15485-branch-1-v3.patch, HBASE-15485-branch-1.1-v1.patch, > HBASE-15485-branch-1.1-v2.patch, HBASE-15485-branch-1.patch, > HBASE-15485-v1.patch, HBASE-15485-v2.patch, HBASE-15485-v3.patch, > HBASE-15485-v4.patch, HBASE-15485-v5.patch > > > As discussed in HBASE-15325, now we will resetFilters if partial result not > formed, but we should not reset filters when batch limit reached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[ https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221037#comment-15221037 ] Sean Busbey commented on HBASE-15572: - I have reverted this from master, per my above request for docs. > Adding optional timestamp semantics to HBase-Spark > -- > > Key: HBASE-15572 > URL: https://issues.apache.org/jira/browse/HBASE-15572 > Project: HBase > Issue Type: New Feature > Components: spark >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Fix For: 2.0.0 > > Attachments: HBASE-15572-1.patch, HBASE-15572-2.patch, > HBASE-15572-3.patch > > > Right now the timestamp is always latest. With this patch, users can select > timestamps they want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[
https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221034#comment-15221034
]
Sean Busbey commented on HBASE-15572:
-
-1 [~tedyu] please do not commit before all feedback has been addressed.
{quote}
Please update docs to explain the feature and usage.
{quote}
> Adding optional timestamp semantics to HBase-Spark
> --
>
> Key: HBASE-15572
> URL: https://issues.apache.org/jira/browse/HBASE-15572
> Project: HBase
> Issue Type: New Feature
> Components: spark
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
> Fix For: 2.0.0
>
> Attachments: HBASE-15572-1.patch, HBASE-15572-2.patch,
> HBASE-15572-3.patch
>
>
> Right now the timestamp is always latest. With this patch, users can select
> timestamps they want.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15485) Filter.reset() should not be called between batches
[ https://issues.apache.org/jira/browse/HBASE-15485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Yang updated HBASE-15485: -- Attachment: HBASE-15485-branch-1-v3.patch > Filter.reset() should not be called between batches > --- > > Key: HBASE-15485 > URL: https://issues.apache.org/jira/browse/HBASE-15485 > Project: HBase > Issue Type: Bug >Affects Versions: 1.2.0, 1.1.3 >Reporter: Phil Yang >Assignee: Phil Yang > Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.5, 1.2.2 > > Attachments: HBASE-15485-branch-1-v2.patch, > HBASE-15485-branch-1-v3.patch, HBASE-15485-branch-1.1-v1.patch, > HBASE-15485-branch-1.1-v2.patch, HBASE-15485-branch-1.patch, > HBASE-15485-v1.patch, HBASE-15485-v2.patch, HBASE-15485-v3.patch, > HBASE-15485-v4.patch > > > As discussed in HBASE-15325, now we will resetFilters if partial result not > formed, but we should not reset filters when batch limit reached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14123) HBase Backup/Restore Phase 2
[ https://issues.apache.org/jira/browse/HBASE-14123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov updated HBASE-14123: -- Attachment: HBASE-14123-v15.patch v15 adds finalizes support for multiple backup destinations (data structure/model level only) The full support for multiple backup destinations is part of Phase 3. > HBase Backup/Restore Phase 2 > > > Key: HBASE-14123 > URL: https://issues.apache.org/jira/browse/HBASE-14123 > Project: HBase > Issue Type: Umbrella >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Attachments: 14123-v14.txt, HBASE-14123-v1.patch, > HBASE-14123-v10.patch, HBASE-14123-v11.patch, HBASE-14123-v12.patch, > HBASE-14123-v13.patch, HBASE-14123-v15.patch, HBASE-14123-v2.patch, > HBASE-14123-v3.patch, HBASE-14123-v4.patch, HBASE-14123-v5.patch, > HBASE-14123-v6.patch, HBASE-14123-v7.patch, HBASE-14123-v9.patch > > > Phase 2 umbrella JIRA. See HBASE-7912 for design document and description. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15505) ReplicationPeerConfig should be builder-style
[
https://issues.apache.org/jira/browse/HBASE-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221021#comment-15221021
]
Gabor Liptak commented on HBASE-15505:
--
I searched for InterfaceAudience.Public, and these are the additional classes I
identified.
PS Should UnmodifyableHTableDescriptor be renamed to
UnmodifiableHTableDescriptor?
> ReplicationPeerConfig should be builder-style
> -
>
> Key: HBASE-15505
> URL: https://issues.apache.org/jira/browse/HBASE-15505
> Project: HBase
> Issue Type: Sub-task
>Reporter: Enis Soztutar
>Assignee: Gabor Liptak
> Labels: beginner, beginners
> Fix For: 2.0.0
>
> Attachments: HBASE-15505.1.patch, HBASE-15505.2.patch,
> HBASE-15505.3.patch
>
>
> Similar to HTD, HCD, {{ReplicationPeerConfig}} should be builder-style:
> {code}
> ReplicationPeerConfig().setFoo(foo).setBar(bar);
> {code}
> See {{TestHTableDescriptor.testClassMethodsAreBuilderStyle()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15521) Procedure V2 - RestoreSnapshot and CloneSnapshot
[
https://issues.apache.org/jira/browse/HBASE-15521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221018#comment-15221018
]
Hadoop QA commented on HBASE-15521:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 8 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 27s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
11s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m 6s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 41s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 30m
48s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
26s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green} 1m
42s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 9m
57s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m 2s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 26s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 10s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
12s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m 57s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 3m 57s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 3m 57s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 42s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 2m 42s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m 42s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 30m
49s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
33s {color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m 0s
{color} | {color:red} The patch has 83 line(s) that end in whitespace. Use git
apply --whitespace=fix. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
26m 29s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green} 2m
1s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 12m
20s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m 13s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 22s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 20s
{color} | {color:green} hbase-protocol in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 22s
{color} | {color:green} hbase-protocol in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 33s
{color} | {color:green} hbase-procedure in the patch passed. {color} |
|
[jira] [Updated] (HBASE-15505) ReplicationPeerConfig should be builder-style
[
https://issues.apache.org/jira/browse/HBASE-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Liptak updated HBASE-15505:
-
Attachment: HBASE-15505.3.patch
> ReplicationPeerConfig should be builder-style
> -
>
> Key: HBASE-15505
> URL: https://issues.apache.org/jira/browse/HBASE-15505
> Project: HBase
> Issue Type: Sub-task
>Reporter: Enis Soztutar
>Assignee: Gabor Liptak
> Labels: beginner, beginners
> Fix For: 2.0.0
>
> Attachments: HBASE-15505.1.patch, HBASE-15505.2.patch,
> HBASE-15505.3.patch
>
>
> Similar to HTD, HCD, {{ReplicationPeerConfig}} should be builder-style:
> {code}
> ReplicationPeerConfig().setFoo(foo).setBar(bar);
> {code}
> See {{TestHTableDescriptor.testClassMethodsAreBuilderStyle()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15485) Filter.reset() should not be called between batches
[ https://issues.apache.org/jira/browse/HBASE-15485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Yang updated HBASE-15485: -- Attachment: HBASE-15485-branch-1.1-v2.patch > Filter.reset() should not be called between batches > --- > > Key: HBASE-15485 > URL: https://issues.apache.org/jira/browse/HBASE-15485 > Project: HBase > Issue Type: Bug >Affects Versions: 1.2.0, 1.1.3 >Reporter: Phil Yang >Assignee: Phil Yang > Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.5, 1.2.2 > > Attachments: HBASE-15485-branch-1-v2.patch, > HBASE-15485-branch-1.1-v1.patch, HBASE-15485-branch-1.1-v2.patch, > HBASE-15485-branch-1.patch, HBASE-15485-v1.patch, HBASE-15485-v2.patch, > HBASE-15485-v3.patch, HBASE-15485-v4.patch > > > As discussed in HBASE-15325, now we will resetFilters if partial result not > formed, but we should not reset filters when batch limit reached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15485) Filter.reset() should not be called between batches
[ https://issues.apache.org/jira/browse/HBASE-15485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221002#comment-15221002 ] Phil Yang commented on HBASE-15485: --- midRowResultFormed looks good, will upload new patch soon > Filter.reset() should not be called between batches > --- > > Key: HBASE-15485 > URL: https://issues.apache.org/jira/browse/HBASE-15485 > Project: HBase > Issue Type: Bug >Affects Versions: 1.2.0, 1.1.3 >Reporter: Phil Yang >Assignee: Phil Yang > Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.5, 1.2.2 > > Attachments: HBASE-15485-branch-1-v2.patch, > HBASE-15485-branch-1.1-v1.patch, HBASE-15485-branch-1.patch, > HBASE-15485-v1.patch, HBASE-15485-v2.patch, HBASE-15485-v3.patch, > HBASE-15485-v4.patch > > > As discussed in HBASE-15325, now we will resetFilters if partial result not > formed, but we should not reset filters when batch limit reached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[ https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-15572: --- Hadoop Flags: Reviewed Fix Version/s: 2.0.0 > Adding optional timestamp semantics to HBase-Spark > -- > > Key: HBASE-15572 > URL: https://issues.apache.org/jira/browse/HBASE-15572 > Project: HBase > Issue Type: New Feature > Components: spark >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Fix For: 2.0.0 > > Attachments: HBASE-15572-1.patch, HBASE-15572-2.patch, > HBASE-15572-3.patch > > > Right now the timestamp is always latest. With this patch, users can select > timestamps they want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15571) Make MasterProcedureManagerHost accessible through MasterServices
[ https://issues.apache.org/jira/browse/HBASE-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220985#comment-15220985 ] Hudson commented on HBASE-15571: FAILURE: Integrated in HBase-1.4 #64 (See [https://builds.apache.org/job/HBase-1.4/64/]) HBASE-15571 Make MasterProcedureManagerHost accessible through (tedyu: rev b7df66f1a811a130c6fcc57d110659601c9c0cdd) * hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterServices.java * hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestCatalogJanitor.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterRpcServices.java > Make MasterProcedureManagerHost accessible through MasterServices > - > > Key: HBASE-15571 > URL: https://issues.apache.org/jira/browse/HBASE-15571 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 2.0.0, 1.4.0 > > Attachments: 15571.v1.patch, 15571.v2.patch > > > One of the review comments for HBASE-15411 is to drop dependency on > HBaseAdmin in table backup procedure. > See the comments starting with: > https://issues.apache.org/jira/browse/HBASE-15411?focusedCommentId=15219215=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15219215 > In order to execute procedure inside table backup procedure, we need access > to MasterProcedureManagerHost. > This issue adds accessor to MasterServices for MasterProcedureManagerHost. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[
https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220976#comment-15220976
]
Ted Yu commented on HBASE-15572:
lgtm
{code}
+ val MIN_TIMESTAMP = "minTimeStamp"
+ val MAX_TIMESTAMP = "maxTimeStamp"
{code}
nit: 'S' can be lowercase - I can change it when I commit the patch.
> Adding optional timestamp semantics to HBase-Spark
> --
>
> Key: HBASE-15572
> URL: https://issues.apache.org/jira/browse/HBASE-15572
> Project: HBase
> Issue Type: New Feature
> Components: spark
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
> Attachments: HBASE-15572-1.patch, HBASE-15572-2.patch,
> HBASE-15572-3.patch
>
>
> Right now the timestamp is always latest. With this patch, users can select
> timestamps they want.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[
https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220963#comment-15220963
]
Hadoop QA commented on HBASE-15572:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
57s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 41s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 41s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green} 0m
43s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 32s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} scalac {color} | {color:green} 1m 32s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 34s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} scalac {color} | {color:green} 1m 34s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
39m 21s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green} 0m
43s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green} 0m
43s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 46s
{color} | {color:green} hbase-spark in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
12s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 55m 7s {color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12796434/HBASE-15572-3.patch |
| JIRA Issue | HBASE-15572 |
| Optional Tests | asflicense scalac scaladoc unit compile |
| uname | Linux pomona.apache.org 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT
Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 8c7f044 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/1253/testReport/ |
| modules | C: hbase-spark U: hbase-spark |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/1253/console |
| Powered by | Apache Yetus 0.2.0 http://yetus.apache.org |
This message was automatically generated.
> Adding optional timestamp semantics to HBase-Spark
> --
>
> Key: HBASE-15572
> URL: https://issues.apache.org/jira/browse/HBASE-15572
> Project: HBase
> Issue Type: New Feature
> Components: spark
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
> Attachments: HBASE-15572-1.patch, HBASE-15572-2.patch,
> HBASE-15572-3.patch
>
>
> Right now the timestamp is always latest. With this patch, users can select
> timestamps they want.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-7912) HBase Backup/Restore Based on HBase Snapshot
[
https://issues.apache.org/jira/browse/HBASE-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220933#comment-15220933
]
Enis Soztutar commented on HBASE-7912:
--
bq. -1. It is as it is. There is a reason for this layout: each table has a
list (set) of backup sessions. All depends on this layout.
Not sure I understand the objection. The dependency is from the backup history
information, not from the layout from what I can see. You already have the
backupId as the leading in the incremental case. Doing the same for full backup
case makes perfect sense. If you have only one layout type, then doing an
{{ls}} in the backup directory will give you all the backupId's etc. And again,
there are other advantages for using the exact same layout that we have inside
a backup directory. For example, again, file links and other stuff will work
transparently, and when we are finished with the new layout that is proposed
for 2.0, we can automatically migrate to that layout with very little changes.
bq. OK, this can be done, but some "unused" fields contains backup session
stats. We do not use it now, but in a future?
If we need them in the future, we can add them back. It is what PB is good for.
Can you please remove the stuff that is not needed to keep the patches simple.
bq. When you do incremental backup on t2, system automatically enhance backup
set and adds ALL tables to it, which have at least one full backup image. So it
will add t1 to t2. This is for free, because we copy only WAL files. No data
loss.
Alright. As long as these kind of cases are covered with a test, it should be
good.
> HBase Backup/Restore Based on HBase Snapshot
>
>
> Key: HBASE-7912
> URL: https://issues.apache.org/jira/browse/HBASE-7912
> Project: HBase
> Issue Type: Sub-task
>Reporter: Richard Ding
>Assignee: Vladimir Rodionov
> Labels: backup
> Fix For: 2.0.0
>
> Attachments: HBaseBackupRestore-Jira-7912-DesignDoc-v1.pdf,
> HBaseBackupRestore-Jira-7912-DesignDoc-v2.pdf,
> HBaseBackupRestore-Jira-7912-v4.pdf, HBaseBackupRestore-Jira-7912-v5 .pdf,
> HBaseBackupRestore-Jira-7912-v6.pdf, HBaseBackupandRestore.pdf,
> HBase_BackupRestore-Jira-7912-CLI-v1.pdf
>
>
> Finally, we completed the implementation of our backup/restore solution, and
> would like to share with community through this jira.
> We are leveraging existing hbase snapshot feature, and provide a general
> solution to common users. Our full backup is using snapshot to capture
> metadata locally and using exportsnapshot to move data to another cluster;
> the incremental backup is using offline-WALplayer to backup HLogs; we also
> leverage global distribution rolllog and flush to improve performance; other
> added-on values such as convert, merge, progress report, and CLI commands. So
> that a common user can backup hbase data without in-depth knowledge of hbase.
> Our solution also contains some usability features for enterprise users.
> The detail design document and CLI command will be attached in this jira. We
> plan to use 10~12 subtasks to share each of the following features, and
> document the detail implement in the subtasks:
> * *Full Backup* : provide local and remote back/restore for a list of tables
> * *offline-WALPlayer* to convert HLog to HFiles offline (for incremental
> backup)
> * *distributed* Logroll and distributed flush
> * Backup *Manifest* and history
> * *Incremental* backup: to build on top of full backup as daily/weekly backup
> * *Convert* incremental backup WAL files into hfiles
> * *Merge* several backup images into one(like merge weekly into monthly)
> * *add and remove* table to and from Backup image
> * *Cancel* a backup process
> * backup progress *status*
> * full backup based on *existing snapshot*
> *-*
> *Below is the original description, to keep here as the history for the
> design and discussion back in 2013*
> There have been attempts in the past to come up with a viable HBase
> backup/restore solution (e.g., HBASE-4618). Recently, there are many
> advancements and new features in HBase, for example, FileLink, Snapshot, and
> Distributed Barrier Procedure. This is a proposal for a backup/restore
> solution that utilizes these new features to achieve better performance and
> consistency.
>
> A common practice of backup and restore in database is to first take full
> baseline backup, and then periodically take incremental backup that capture
> the changes since the full baseline backup. HBase cluster can store massive
> amount data. Combination of full backups with incremental backups has
> tremendous benefit for HBase as well. The following is a typical
[jira] [Updated] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[ https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiqing Yang updated HBASE-15572: - Attachment: HBASE-15572-3.patch > Adding optional timestamp semantics to HBase-Spark > -- > > Key: HBASE-15572 > URL: https://issues.apache.org/jira/browse/HBASE-15572 > Project: HBase > Issue Type: New Feature > Components: spark >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Attachments: HBASE-15572-1.patch, HBASE-15572-2.patch, > HBASE-15572-3.patch > > > Right now the timestamp is always latest. With this patch, users can select > timestamps they want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15293) Handle TableNotFound and IllegalArgument exceptions in table.jsp.
[
https://issues.apache.org/jira/browse/HBASE-15293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220916#comment-15220916
]
Hadoop QA commented on HBASE-15293:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 10m
23s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
17s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 55s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m 20s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
37s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
40s {color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m 0s
{color} | {color:red} The patch has 4 line(s) with tabs. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
84m 23s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 40s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 40s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 169m 51s
{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 1m
9s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 280m 34s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Timed out junit tests |
org.apache.hadoop.hbase.regionserver.wal.TestLogRolling |
| | org.apache.hadoop.hbase.client.TestAdmin1 |
| | org.apache.hadoop.hbase.client.TestMobRestoreSnapshotFromClient |
| |
org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClientWithRegionReplicas |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12796374/HBASE-15293_v2.patch |
| JIRA Issue | HBASE-15293 |
| Optional Tests | asflicense javac javadoc unit |
| uname | Linux asf911.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / bcc |
| Default Java | 1.7.0_79 |
| Multi-JDK versions | /home/jenkins/tools/java/jdk1.8.0:1.8.0
/usr/local/jenkins/java/jdk1.7.0_79:1.7.0_79 |
| whitespace |
https://builds.apache.org/job/PreCommit-HBASE-Build/1248/artifact/patchprocess/whitespace-tabs.txt
|
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/1248/artifact/patchprocess/patch-unit-hbase-server.txt
|
| unit test logs |
https://builds.apache.org/job/PreCommit-HBASE-Build/1248/artifact/patchprocess/patch-unit-hbase-server.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/1248/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/1248/console |
| Powered by | Apache Yetus 0.2.0 http://yetus.apache.org |
This message was automatically generated.
> Handle TableNotFound and IllegalArgument exceptions in table.jsp.
> -
>
> Key: HBASE-15293
> URL: https://issues.apache.org/jira/browse/HBASE-15293
> Project: HBase
> Issue Type: Sub-task
> Components: UI
>Affects Versions: 2.0.0
>Reporter: Samir Ahmic
>Assignee: Samir Ahmic
> Fix For: 2.0.0
>
> Attachments: HBASE-15293_v0.patch, HBASE-15293_v1.patch,
> HBASE-15293_v1.patch, HBASE-15293_v2.patch
>
>
> table.jsp
[jira] [Commented] (HBASE-15505) ReplicationPeerConfig should be builder-style
[
https://issues.apache.org/jira/browse/HBASE-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220899#comment-15220899
]
Hadoop QA commented on HBASE-15505:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
56s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 27s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 18s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
9s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
14s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 2s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 27s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 18s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
19s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 26s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 26s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 18s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 18s
{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 2m 3s
{color} | {color:red} hbase-client: patch generated 1 new + 1 unchanged - 0
fixed = 2 total (was 1) {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
12s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
25m 12s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
16s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 20s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 18s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 54s
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
7s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 39m 43s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12796426/HBASE-15505.2.patch |
| JIRA Issue | HBASE-15505 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux pietas.apache.org 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT
Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 8c7f044 |
| Default Java | 1.7.0_79 |
| Multi-JDK versions | /home/jenkins/tools/java/jdk1.8.0:1.8.0
/usr/local/jenkins/java/jdk1.7.0_79:1.7.0_79 |
| findbugs | v3.0.0 |
| checkstyle |
[jira] [Updated] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[ https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-15572: Issue Type: New Feature (was: Improvement) > Adding optional timestamp semantics to HBase-Spark > -- > > Key: HBASE-15572 > URL: https://issues.apache.org/jira/browse/HBASE-15572 > Project: HBase > Issue Type: New Feature > Components: spark >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Attachments: HBASE-15572-1.patch, HBASE-15572-2.patch > > > Right now the timestamp is always latest. With this patch, users can select > timestamps they want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[ https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220892#comment-15220892 ] Sean Busbey commented on HBASE-15572: - Please update docs to explain the feature and usage. > Adding optional timestamp semantics to HBase-Spark > -- > > Key: HBASE-15572 > URL: https://issues.apache.org/jira/browse/HBASE-15572 > Project: HBase > Issue Type: Improvement > Components: spark >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Attachments: HBASE-15572-1.patch, HBASE-15572-2.patch > > > Right now the timestamp is always latest. With this patch, users can select > timestamps they want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15567) TestReplicationShell broken by recent replication changes
[ https://issues.apache.org/jira/browse/HBASE-15567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220872#comment-15220872 ] Hudson commented on HBASE-15567: FAILURE: Integrated in HBase-Trunk_matrix #818 (See [https://builds.apache.org/job/HBase-Trunk_matrix/818/]) HBASE-15567 TestReplicationShell broken by recent replication changes (enis: rev bcc420ab1ef9a397d5a299a46a3f22b09d84) * hbase-shell/src/main/ruby/hbase/replication_admin.rb * hbase-shell/src/test/ruby/hbase/replication_admin_test.rb > TestReplicationShell broken by recent replication changes > - > > Key: HBASE-15567 > URL: https://issues.apache.org/jira/browse/HBASE-15567 > Project: HBase > Issue Type: Bug > Components: Replication, shell >Affects Versions: 2.0.0 >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby >Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-15567.patch > > > Recent changes to the Ruby shell's add_peer method in HBASE-11393 have broken > TestReplicationShell, which went unnoticed because it's currently Ignored as > flaky. This test is useful when developing extensions to the replication > shell commands, and should be kept working (and hopefully re-enabled in the > near future.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[ https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220874#comment-15220874 ] Ted Yu commented on HBASE-15572: Can you move HBaseRelation to HBaseSparkConf, as Zhan requested ? Thanks > Adding optional timestamp semantics to HBase-Spark > -- > > Key: HBASE-15572 > URL: https://issues.apache.org/jira/browse/HBASE-15572 > Project: HBase > Issue Type: Improvement > Components: spark >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Attachments: HBASE-15572-1.patch, HBASE-15572-2.patch > > > Right now the timestamp is always latest. With this patch, users can select > timestamps they want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[
https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220868#comment-15220868
]
Hadoop QA commented on HBASE-15572:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
7s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 16s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 19s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green} 0m
35s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 14s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} scalac {color} | {color:green} 1m 14s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 20s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} scalac {color} | {color:green} 1m 20s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
32m 22s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green} 0m
34s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green} 0m
37s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 21s
{color} | {color:green} hbase-spark in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
8s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 45m 3s {color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12796420/HBASE-15572-2.patch |
| JIRA Issue | HBASE-15572 |
| Optional Tests | asflicense scalac scaladoc unit compile |
| uname | Linux asf910.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 8c7f044 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/1251/testReport/ |
| modules | C: hbase-spark U: hbase-spark |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/1251/console |
| Powered by | Apache Yetus 0.2.0 http://yetus.apache.org |
This message was automatically generated.
> Adding optional timestamp semantics to HBase-Spark
> --
>
> Key: HBASE-15572
> URL: https://issues.apache.org/jira/browse/HBASE-15572
> Project: HBase
> Issue Type: Improvement
> Components: spark
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
> Attachments: HBASE-15572-1.patch, HBASE-15572-2.patch
>
>
> Right now the timestamp is always latest. With this patch, users can select
> timestamps they want.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15187) Integrate CSRF prevention filter to REST gateway
[ https://issues.apache.org/jira/browse/HBASE-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220867#comment-15220867 ] Andrew Purtell commented on HBASE-15187: I don't have time. I did a quick skim and it looks like you convinced [~stack] If so then fine by me > Integrate CSRF prevention filter to REST gateway > > > Key: HBASE-15187 > URL: https://issues.apache.org/jira/browse/HBASE-15187 > Project: HBase > Issue Type: Bug >Reporter: Ted Yu >Assignee: Ted Yu > Attachments: HBASE-15187-branch-1.v13.patch, HBASE-15187.v1.patch, > HBASE-15187.v10.patch, HBASE-15187.v11.patch, HBASE-15187.v12.patch, > HBASE-15187.v13.patch, HBASE-15187.v2.patch, HBASE-15187.v3.patch, > HBASE-15187.v4.patch, HBASE-15187.v5.patch, HBASE-15187.v6.patch, > HBASE-15187.v7.patch, HBASE-15187.v8.patch, HBASE-15187.v9.patch > > > HADOOP-12691 introduced a filter in Hadoop Common to help REST APIs guard > against cross-site request forgery attacks. > This issue tracks the integration of that filter into HBase REST gateway. > From REST section of refguide: > To delete a table, use a DELETE request with the /schema endpoint: > http://example.com:8000/schema > Suppose an attacker hosts a malicious web form on a domain under his control. > The form uses the DELETE action targeting a REST URL. Through social > engineering, the attacker tricks an authenticated user into accessing the > form and submitting it. > The browser sends the HTTP DELETE request to the REST gateway. > At REST gateway, the call is executed and user table is dropped -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15234) ReplicationLogCleaner can abort due to transient ZK issues
[
https://issues.apache.org/jira/browse/HBASE-15234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220860#comment-15220860
]
Andrew Purtell commented on HBASE-15234:
Yeah it's not a big deal. More changes needed for the latter, never mind
> ReplicationLogCleaner can abort due to transient ZK issues
> --
>
> Key: HBASE-15234
> URL: https://issues.apache.org/jira/browse/HBASE-15234
> Project: HBase
> Issue Type: Bug
> Components: master, Replication
>Reporter: Gary Helmling
>Assignee: Gary Helmling
>Priority: Critical
> Attachments: HBASE-15234.001.patch, HBASE-15234.002.patch
>
>
> The ReplicationLogCleaner delegate for the LogCleaner chore can abort due to
> transient errors reading the replication znodes, leaving the log cleaner
> chore stopped, but the master still running. This causes logs to build up in
> the oldWALs directory, which can even hit storage or file count limits in
> HDFS, causing problems.
> We've seen this happen in a couple of clusters when a rolling restart was
> performed on the zk peers (only one restarted at a time).
> The full stack trace when the log cleaner aborts is:
> {noformat}
> 16/02/02 15:22:39 WARN zookeeper.ZKUtil:
> replicationLogCleaner-0x1522c8b93c2fbae, quorum=,
> baseZNode=/hbase Unable to get data of znode /hbase/replication/rs
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /hbase/replication/rs
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1155)
> at
> org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.getData(RecoverableZooKeeper.java:359)
> at
> org.apache.hadoop.hbase.zookeeper.ZKUtil.getDataNoWatch(ZKUtil.java:713)
> at
> org.apache.hadoop.hbase.replication.ReplicationQueuesClientZKImpl.getQueuesZNodeCversion(ReplicationQueuesClientZKImpl.java:80)
>
> at
> org.apache.hadoop.hbase.replication.master.ReplicationLogCleaner.loadWALsFromQueues(ReplicationLogCleaner.java:99)
>
> at
> org.apache.hadoop.hbase.replication.master.ReplicationLogCleaner.getDeletableFiles(ReplicationLogCleaner.java:70)
> at
> org.apache.hadoop.hbase.master.cleaner.CleanerChore.checkAndDeleteFiles(CleanerChore.java:233)
> at
> org.apache.hadoop.hbase.master.cleaner.CleanerChore.checkAndDeleteEntries(CleanerChore.java:157)
> at
> org.apache.hadoop.hbase.master.cleaner.CleanerChore.chore(CleanerChore.java:124)
> at org.apache.hadoop.hbase.ScheduledChore.run(ScheduledChore.java:185)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>
> at
> org.apache.hadoop.hbase.JitterScheduledThreadPoolExecutorImpl$JitteredRunnableScheduledFuture.run(JitterScheduledThreadPoolExecutorImpl.java:110)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> 16/02/02 15:22:39 ERROR zookeeper.ZooKeeperWatcher:
> replicationLogCleaner-0x1522c8b93c2fbae, quorum=,
> baseZNode=/hbase Received unexpected KeeperException, re-throwing exception
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /hbase/replication/rs
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
> at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1155)
> at
> org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.getData(RecoverableZooKeeper.java:359)
> at
> org.apache.hadoop.hbase.zookeeper.ZKUtil.getDataNoWatch(ZKUtil.java:713)
> at
> org.apache.hadoop.hbase.replication.ReplicationQueuesClientZKImpl.getQueuesZNodeCversion(ReplicationQueuesClientZKImpl.java:80)
>
> at
> org.apache.hadoop.hbase.replication.master.ReplicationLogCleaner.loadWALsFromQueues(ReplicationLogCleaner.java:99)
>
> at
> org.apache.hadoop.hbase.replication.master.ReplicationLogCleaner.getDeletableFiles(ReplicationLogCleaner.java:70)
> at
[jira] [Commented] (HBASE-15573) Indefinite pause while trying to cleanup data
[ https://issues.apache.org/jira/browse/HBASE-15573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220856#comment-15220856 ] Jorge Figueira commented on HBASE-15573: After 2 months with Hbase working fine this error occurred with the RPC java client. Hbase server tells its all OK with Region and Master but it cant scan any data with the same configuration i have from 2 months ago that was working perfectly until yesterday. After many tries(repairs,updates) i decided to clean all data and my client start working again (without any configuration changed). Something occurred with Hbase and it wasn't any change in any configuration file inside Hbase (server and client) or network. Clearly was a issue inside Hbase. I have a snapshot of that state to try to understand what occurred and prevent happening again. With the bug described above when i try to export data from Hbase using (hbase org.apache.hadoop.hbase.mapreduce.Export JAMES_MAILBOXES xpto.tmp) some nasty exceptions occur 2016-03-31 15:37:39,745 DEBUG [B.defaultRpcServer.handler=23,queue=2,port=16020] ipc.RpcServer: B.defaultRpcServer.handler=23,queue=2,port=16020: callId: 36796 service: ClientService methodName: Scan size: 586 connection: HBASE:57813 org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region JAMES_MAILBOXES,,1456359497674.b038389cb6f8d608abe86265dd90079f. is opening on HBASE,16020,1459435051912 at org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2895) at org.apache.hadoop.hbase.regionserver.RSRpcServices.getRegion(RSRpcServices.java:947) at org.apache.hadoop.hbase.regionserver.RSRpcServices.scan(RSRpcServices.java:2234) at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32205) at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2114) at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:101) at org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:130) at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:107) at java.lang.Thread.run(Thread.java:745) > Indefinite pause while trying to cleanup data > - > > Key: HBASE-15573 > URL: https://issues.apache.org/jira/browse/HBASE-15573 > Project: HBase > Issue Type: Bug >Affects Versions: 1.1.2, 1.1.4 >Reporter: Jorge Figueira >Priority: Blocker > Attachments: hbase-hadoop-master-HBASE.log, > hbase-hadoop-regionserver-HBASE.log, hbase-hadoop-zookeeper-HBASE.log > > > Can't retrieve any information with hbase rpc java client. > With hbase shell its possible to scan data and retrieve all the information > normally. > But with any rpc client region server don't retrieve data, all data come with > null values. > Region Server log: > DEBUG [RpcServer.reader=2,bindAddress=HBASE,port=16020] ipc.RpcServer: > RpcServer.listener,port=16020: DISCONNECTING client SERVER:37088 because read > count=-1 > DEBUG [RpcServer.reader=2,bindAddress=HBASE,port=16020] ipc.RpcServer: > RpcServer.listener,port=16020: DISCONNECTING client SERVER2:36997 because > read count=-1 > Master log: > 2016-03-31 18:16:27,998 DEBUG [ProcedureExecutorTimeout] > procedure2.ProcedureExecutor$CompletedProcedureCleaner: No completed > procedures to cleanup. > 2016-03-31 18:16:57,998 DEBUG [ProcedureExecutorTimeout] > procedure2.ProcedureExecutor$CompletedProcedureCleaner: No completed > procedures to cleanup. > 2016-03-31 18:17:27,998 DEBUG [ProcedureExecutorTimeout] > procedure2.ProcedureExecutor$CompletedProcedureCleaner: No completed > procedures to cleanup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15505) ReplicationPeerConfig should be builder-style
[
https://issues.apache.org/jira/browse/HBASE-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Liptak updated HBASE-15505:
-
Attachment: HBASE-15505.2.patch
> ReplicationPeerConfig should be builder-style
> -
>
> Key: HBASE-15505
> URL: https://issues.apache.org/jira/browse/HBASE-15505
> Project: HBase
> Issue Type: Sub-task
>Reporter: Enis Soztutar
>Assignee: Gabor Liptak
> Labels: beginner, beginners
> Fix For: 2.0.0
>
> Attachments: HBASE-15505.1.patch, HBASE-15505.2.patch
>
>
> Similar to HTD, HCD, {{ReplicationPeerConfig}} should be builder-style:
> {code}
> ReplicationPeerConfig().setFoo(foo).setBar(bar);
> {code}
> See {{TestHTableDescriptor.testClassMethodsAreBuilderStyle()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15505) ReplicationPeerConfig should be builder-style
[
https://issues.apache.org/jira/browse/HBASE-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220820#comment-15220820
]
Hadoop QA commented on HBASE-15505:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
47s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 24s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 22s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
30s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
13s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
13s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 30s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 20s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
24s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 29s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 29s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 21s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 21s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
18s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
32m 1s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
33s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 29s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 22s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 1m 2s {color} |
{color:red} hbase-client in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
10s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 49m 10s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.replication.TestReplicationPeerConfig |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12796408/HBASE-15505.1.patch |
| JIRA Issue | HBASE-15505 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux pietas.apache.org 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT
Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / bcc |
| Default Java | 1.7.0_79 |
| Multi-JDK versions | /home/jenkins/tools/java/jdk1.8.0:1.8.0
/usr/local/jenkins/java/jdk1.7.0_79:1.7.0_79 |
| findbugs | v3.0.0 |
| unit |
[jira] [Commented] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[ https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220815#comment-15220815 ] Weiqing Yang commented on HBASE-15572: -- Thanks for the comments. I have updated the patch. > Adding optional timestamp semantics to HBase-Spark > -- > > Key: HBASE-15572 > URL: https://issues.apache.org/jira/browse/HBASE-15572 > Project: HBase > Issue Type: Improvement > Components: spark >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Attachments: HBASE-15572-1.patch, HBASE-15572-2.patch > > > Right now the timestamp is always latest. With this patch, users can select > timestamps they want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[ https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiqing Yang updated HBASE-15572: - Attachment: HBASE-15572-2.patch > Adding optional timestamp semantics to HBase-Spark > -- > > Key: HBASE-15572 > URL: https://issues.apache.org/jira/browse/HBASE-15572 > Project: HBase > Issue Type: Improvement > Components: spark >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Attachments: HBASE-15572-1.patch, HBASE-15572-2.patch > > > Right now the timestamp is always latest. With this patch, users can select > timestamps they want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13639) SyncTable - rsync for HBase tables
[ https://issues.apache.org/jira/browse/HBASE-13639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220812#comment-15220812 ] Dave Latham commented on HBASE-13639: - If you run SyncTable on the a cluster that is not local to the target table, it should work but the tasks will be scanning all the data remotely which defeats the intent of avoiding transferring all the data across clusters. In that case you may be better off simply exporting the source table and replacing the target table with it. If you want to discuss further, please email the mailing list and let's continue there. > SyncTable - rsync for HBase tables > -- > > Key: HBASE-13639 > URL: https://issues.apache.org/jira/browse/HBASE-13639 > Project: HBase > Issue Type: New Feature > Components: mapreduce, Operability, tooling >Reporter: Dave Latham >Assignee: Dave Latham > Labels: tooling > Fix For: 2.0.0, 0.98.14, 1.2.0 > > Attachments: HBASE-13639-0.98-addendum-hadoop-1.patch, > HBASE-13639-0.98.patch, HBASE-13639-v1.patch, HBASE-13639-v2.patch, > HBASE-13639-v3-0.98.patch, HBASE-13639-v3.patch, HBASE-13639.patch > > > Given HBase tables in remote clusters with similar but not identical data, > efficiently update a target table such that the data in question is identical > to a source table. Efficiency in this context means using far less network > traffic than would be required to ship all the data from one cluster to the > other. Takes inspiration from rsync. > Design doc: > https://docs.google.com/document/d/1-2c9kJEWNrXf5V4q_wBcoIXfdchN7Pxvxv1IO6PW0-U/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15571) Make MasterProcedureManagerHost accessible through MasterServices
[ https://issues.apache.org/jira/browse/HBASE-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-15571: --- Hadoop Flags: Reviewed Fix Version/s: 1.4.0 2.0.0 > Make MasterProcedureManagerHost accessible through MasterServices > - > > Key: HBASE-15571 > URL: https://issues.apache.org/jira/browse/HBASE-15571 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 2.0.0, 1.4.0 > > Attachments: 15571.v1.patch, 15571.v2.patch > > > One of the review comments for HBASE-15411 is to drop dependency on > HBaseAdmin in table backup procedure. > See the comments starting with: > https://issues.apache.org/jira/browse/HBASE-15411?focusedCommentId=15219215=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15219215 > In order to execute procedure inside table backup procedure, we need access > to MasterProcedureManagerHost. > This issue adds accessor to MasterServices for MasterProcedureManagerHost. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15571) Make MasterProcedureManagerHost accessible through MasterServices
[ https://issues.apache.org/jira/browse/HBASE-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220792#comment-15220792 ] Stephen Yuan Jiang commented on HBASE-15571: +1 LGTM > Make MasterProcedureManagerHost accessible through MasterServices > - > > Key: HBASE-15571 > URL: https://issues.apache.org/jira/browse/HBASE-15571 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Attachments: 15571.v1.patch, 15571.v2.patch > > > One of the review comments for HBASE-15411 is to drop dependency on > HBaseAdmin in table backup procedure. > See the comments starting with: > https://issues.apache.org/jira/browse/HBASE-15411?focusedCommentId=15219215=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15219215 > In order to execute procedure inside table backup procedure, we need access > to MasterProcedureManagerHost. > This issue adds accessor to MasterServices for MasterProcedureManagerHost. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[ https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220791#comment-15220791 ] Weiqing Yang commented on HBASE-15572: -- Yes, I have attached the link. > Adding optional timestamp semantics to HBase-Spark > -- > > Key: HBASE-15572 > URL: https://issues.apache.org/jira/browse/HBASE-15572 > Project: HBase > Issue Type: Improvement > Components: spark >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Attachments: HBASE-15572-1.patch > > > Right now the timestamp is always latest. With this patch, users can select > timestamps they want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15411) Rewrite backup with Procedure V2
[ https://issues.apache.org/jira/browse/HBASE-15411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220786#comment-15220786 ] Enis Soztutar commented on HBASE-15411: --- Sounds good. > Rewrite backup with Procedure V2 > > > Key: HBASE-15411 > URL: https://issues.apache.org/jira/browse/HBASE-15411 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Attachments: 15411-v1.txt, 15411-v11.txt, 15411-v12.txt, > 15411-v13.txt, 15411-v14.txt, 15411-v15.txt, 15411-v16.txt, 15411-v18.txt, > 15411-v22.txt, 15411-v3.txt, 15411-v5.txt, 15411-v6.txt, 15411-v7.txt, > 15411-v9.txt, FullTableBackupProcedure.java > > > Currently full / incremental backup is driven by BackupHandler (see call() > method for flow). > This issue is to rewrite the flow using Procedure V2. > States (enum) for full / incremental backup would be introduced in > Backup.proto which correspond to the steps performed in BackupHandler#call(). > executeFromState() would pace the backup based on the current state. > serializeStateData() / deserializeStateData() would be used to persist state > into procedure WAL. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15571) Make MasterProcedureManagerHost accessible through MasterServices
[ https://issues.apache.org/jira/browse/HBASE-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220790#comment-15220790 ] Stephen Yuan Jiang commented on HBASE-15571: yeah > Make MasterProcedureManagerHost accessible through MasterServices > - > > Key: HBASE-15571 > URL: https://issues.apache.org/jira/browse/HBASE-15571 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Attachments: 15571.v1.patch, 15571.v2.patch > > > One of the review comments for HBASE-15411 is to drop dependency on > HBaseAdmin in table backup procedure. > See the comments starting with: > https://issues.apache.org/jira/browse/HBASE-15411?focusedCommentId=15219215=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15219215 > In order to execute procedure inside table backup procedure, we need access > to MasterProcedureManagerHost. > This issue adds accessor to MasterServices for MasterProcedureManagerHost. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14996) Some more API cleanup for 2.0
[ https://issues.apache.org/jira/browse/HBASE-14996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-14996: -- Priority: Critical (was: Major) > Some more API cleanup for 2.0 > -- > > Key: HBASE-14996 > URL: https://issues.apache.org/jira/browse/HBASE-14996 > Project: HBase > Issue Type: Improvement >Reporter: Enis Soztutar >Priority: Critical > Fix For: 2.0.0 > > > Parent jira to keep track of some more API cleanup that did not happen in 1.x > timeframe. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15505) ReplicationPeerConfig should be builder-style
[
https://issues.apache.org/jira/browse/HBASE-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-15505:
--
Assignee: Gabor Liptak
> ReplicationPeerConfig should be builder-style
> -
>
> Key: HBASE-15505
> URL: https://issues.apache.org/jira/browse/HBASE-15505
> Project: HBase
> Issue Type: Sub-task
>Reporter: Enis Soztutar
>Assignee: Gabor Liptak
> Labels: beginner, beginners
> Fix For: 2.0.0
>
> Attachments: HBASE-15505.1.patch
>
>
> Similar to HTD, HCD, {{ReplicationPeerConfig}} should be builder-style:
> {code}
> ReplicationPeerConfig().setFoo(foo).setBar(bar);
> {code}
> See {{TestHTableDescriptor.testClassMethodsAreBuilderStyle()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15505) ReplicationPeerConfig should be builder-style
[
https://issues.apache.org/jira/browse/HBASE-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220765#comment-15220765
]
Enis Soztutar commented on HBASE-15505:
---
Thanks Gabor for the patch. +1 for the patch.
bq. Could you point the other classes to test against? Thanks
I do not have the list, but I was thinking to go over all of the classes that
are marked with InterfaceAudience.Public, and if they are POJO-style classes
(like HTD, ReplicationPeerConfig, etc) change them to be builder style. Maybe
we have already covered everything.
> ReplicationPeerConfig should be builder-style
> -
>
> Key: HBASE-15505
> URL: https://issues.apache.org/jira/browse/HBASE-15505
> Project: HBase
> Issue Type: Sub-task
>Reporter: Enis Soztutar
> Labels: beginner, beginners
> Fix For: 2.0.0
>
> Attachments: HBASE-15505.1.patch
>
>
> Similar to HTD, HCD, {{ReplicationPeerConfig}} should be builder-style:
> {code}
> ReplicationPeerConfig().setFoo(foo).setBar(bar);
> {code}
> See {{TestHTableDescriptor.testClassMethodsAreBuilderStyle()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15571) Make MasterProcedureManagerHost accessible through MasterServices
[ https://issues.apache.org/jira/browse/HBASE-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-15571: --- Attachment: 15571.v2.patch > Make MasterProcedureManagerHost accessible through MasterServices > - > > Key: HBASE-15571 > URL: https://issues.apache.org/jira/browse/HBASE-15571 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Attachments: 15571.v1.patch, 15571.v2.patch > > > One of the review comments for HBASE-15411 is to drop dependency on > HBaseAdmin in table backup procedure. > See the comments starting with: > https://issues.apache.org/jira/browse/HBASE-15411?focusedCommentId=15219215=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15219215 > In order to execute procedure inside table backup procedure, we need access > to MasterProcedureManagerHost. > This issue adds accessor to MasterServices for MasterProcedureManagerHost. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15505) ReplicationPeerConfig should be builder-style
[
https://issues.apache.org/jira/browse/HBASE-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Liptak updated HBASE-15505:
-
Release Note: HBASE-15505 ReplicationPeerConfig should be builder-style
Status: Patch Available (was: Open)
> ReplicationPeerConfig should be builder-style
> -
>
> Key: HBASE-15505
> URL: https://issues.apache.org/jira/browse/HBASE-15505
> Project: HBase
> Issue Type: Sub-task
>Reporter: Enis Soztutar
> Labels: beginner, beginners
> Fix For: 2.0.0
>
> Attachments: HBASE-15505.1.patch
>
>
> Similar to HTD, HCD, {{ReplicationPeerConfig}} should be builder-style:
> {code}
> ReplicationPeerConfig().setFoo(foo).setBar(bar);
> {code}
> See {{TestHTableDescriptor.testClassMethodsAreBuilderStyle()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15505) ReplicationPeerConfig should be builder-style
[
https://issues.apache.org/jira/browse/HBASE-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220727#comment-15220727
]
Gabor Liptak commented on HBASE-15505:
--
[~enis] Could you point the other classes to test against? Thanks
> ReplicationPeerConfig should be builder-style
> -
>
> Key: HBASE-15505
> URL: https://issues.apache.org/jira/browse/HBASE-15505
> Project: HBase
> Issue Type: Sub-task
>Reporter: Enis Soztutar
> Labels: beginner, beginners
> Fix For: 2.0.0
>
> Attachments: HBASE-15505.1.patch
>
>
> Similar to HTD, HCD, {{ReplicationPeerConfig}} should be builder-style:
> {code}
> ReplicationPeerConfig().setFoo(foo).setBar(bar);
> {code}
> See {{TestHTableDescriptor.testClassMethodsAreBuilderStyle()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15505) ReplicationPeerConfig should be builder-style
[
https://issues.apache.org/jira/browse/HBASE-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Liptak updated HBASE-15505:
-
Attachment: HBASE-15505.1.patch
> ReplicationPeerConfig should be builder-style
> -
>
> Key: HBASE-15505
> URL: https://issues.apache.org/jira/browse/HBASE-15505
> Project: HBase
> Issue Type: Sub-task
>Reporter: Enis Soztutar
> Labels: beginner, beginners
> Fix For: 2.0.0
>
> Attachments: HBASE-15505.1.patch
>
>
> Similar to HTD, HCD, {{ReplicationPeerConfig}} should be builder-style:
> {code}
> ReplicationPeerConfig().setFoo(foo).setBar(bar);
> {code}
> See {{TestHTableDescriptor.testClassMethodsAreBuilderStyle()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15485) Filter.reset() should not be called between batches
[
https://issues.apache.org/jira/browse/HBASE-15485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220720#comment-15220720
]
Ted Yu commented on HBASE-15485:
lgtm
{code}
233* @return true when a mid-row result is formed.
234*/
235 boolean betweenCellsResultFormed() {
{code}
Why not naming the method midRowResultFormed ?
'Between cells' can happen inter row :-)
> Filter.reset() should not be called between batches
> ---
>
> Key: HBASE-15485
> URL: https://issues.apache.org/jira/browse/HBASE-15485
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.2.0, 1.1.3
>Reporter: Phil Yang
>Assignee: Phil Yang
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.5, 1.2.2
>
> Attachments: HBASE-15485-branch-1-v2.patch,
> HBASE-15485-branch-1.1-v1.patch, HBASE-15485-branch-1.patch,
> HBASE-15485-v1.patch, HBASE-15485-v2.patch, HBASE-15485-v3.patch,
> HBASE-15485-v4.patch
>
>
> As discussed in HBASE-15325, now we will resetFilters if partial result not
> formed, but we should not reset filters when batch limit reached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15293) Handle TableNotFound and IllegalArgument exceptions in table.jsp.
[ https://issues.apache.org/jira/browse/HBASE-15293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220711#comment-15220711 ] Ted Yu commented on HBASE-15293: Using vi, you can search for "\/t" > Handle TableNotFound and IllegalArgument exceptions in table.jsp. > - > > Key: HBASE-15293 > URL: https://issues.apache.org/jira/browse/HBASE-15293 > Project: HBase > Issue Type: Sub-task > Components: UI >Affects Versions: 2.0.0 >Reporter: Samir Ahmic >Assignee: Samir Ahmic > Fix For: 2.0.0 > > Attachments: HBASE-15293_v0.patch, HBASE-15293_v1.patch, > HBASE-15293_v1.patch, HBASE-15293_v2.patch > > > table.jsp accepts "name" parameter for table name and in case when table does > not exist or empty parameter is passed it will throw 500 error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15571) Make MasterProcedureManagerHost accessible through MasterServices
[ https://issues.apache.org/jira/browse/HBASE-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220704#comment-15220704 ] Ted Yu commented on HBASE-15571: Did you mean making mpmHost private and access it through getMasterProcedureManagerHost() ? > Make MasterProcedureManagerHost accessible through MasterServices > - > > Key: HBASE-15571 > URL: https://issues.apache.org/jira/browse/HBASE-15571 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Attachments: 15571.v1.patch > > > One of the review comments for HBASE-15411 is to drop dependency on > HBaseAdmin in table backup procedure. > See the comments starting with: > https://issues.apache.org/jira/browse/HBASE-15411?focusedCommentId=15219215=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15219215 > In order to execute procedure inside table backup procedure, we need access > to MasterProcedureManagerHost. > This issue adds accessor to MasterServices for MasterProcedureManagerHost. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15571) Make MasterProcedureManagerHost accessible through MasterServices
[
https://issues.apache.org/jira/browse/HBASE-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220698#comment-15220698
]
Stephen Yuan Jiang commented on HBASE-15571:
Could you replace all {{master.mpmHost}} usage with your change?
> Make MasterProcedureManagerHost accessible through MasterServices
> -
>
> Key: HBASE-15571
> URL: https://issues.apache.org/jira/browse/HBASE-15571
> Project: HBase
> Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: 15571.v1.patch
>
>
> One of the review comments for HBASE-15411 is to drop dependency on
> HBaseAdmin in table backup procedure.
> See the comments starting with:
> https://issues.apache.org/jira/browse/HBASE-15411?focusedCommentId=15219215=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15219215
> In order to execute procedure inside table backup procedure, we need access
> to MasterProcedureManagerHost.
> This issue adds accessor to MasterServices for MasterProcedureManagerHost.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15569) Make Bytes.toStringBinary faster
[
https://issues.apache.org/jira/browse/HBASE-15569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220699#comment-15220699
]
Ted Yu commented on HBASE-15569:
+1
> Make Bytes.toStringBinary faster
>
>
> Key: HBASE-15569
> URL: https://issues.apache.org/jira/browse/HBASE-15569
> Project: HBase
> Issue Type: Improvement
> Components: Performance
>Reporter: Junegunn Choi
>Assignee: Junegunn Choi
>Priority: Minor
> Attachments: HBASE-15569.patch
>
>
> Bytes.toStringBinary is quite expensive due to its use of {{String.format}}.
> It seems to me that {{String.format}} is overkill for the purpose and I could
> actually make the function up to 45-times faster by replacing the part with a
> simpler hand-crafted code.
> This is probably a non-issue for HBase server as the function is not used in
> performance-sensitive contexts but I figured it wouldn't hurt to make it
> faster as it's widely used in builtin tools - Shell, {{HFilePrettyPrinter}}
> with {{-p}} option, etc. - and it can be used in clients.
> h4. Background:
> We have [an HBase monitoring
> tool|https://github.com/kakao/hbase-region-inspector] that periodically
> collects the information of the regions and it calls {{Bytes.toStringBinary}}
> during the process to make some information suitable for display. Profiling
> revealed that a large portion of the processing time was spent in
> {{String.format}}.
> h4. Micro-benchmark:
> {code}
> byte[] bytes = new byte[256];
> for (int i = 0; i < bytes.length; ++i) {
> // Mixture of printable and non-printable characters.
> // Maximal performance gain (45x) is observed when the array is solely
> // composed of non-printable characters.
> bytes[i] = (byte) i;
> }
> long started = System.nanoTime();
> for (int i = 0; i < 100; ++i) {
> Bytes.toStringBinary(bytes);
> }
> System.out.println(TimeUnit.NANOSECONDS.toMillis(System.nanoTime() -
> started));
> {code}
> - Without the patch: 134176 ms
> - With the patch: 3890 ms
> I made sure that the new version returns the same value as before and
> simplified the check for non-printable characters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13639) SyncTable - rsync for HBase tables
[ https://issues.apache.org/jira/browse/HBASE-13639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220673#comment-15220673 ] My Ho commented on HBASE-13639: --- [~davelatham] what would happen if we run org.apache.hadoop.hbase.mapreduce.SyncTable on the source table's cluster? > SyncTable - rsync for HBase tables > -- > > Key: HBASE-13639 > URL: https://issues.apache.org/jira/browse/HBASE-13639 > Project: HBase > Issue Type: New Feature > Components: mapreduce, Operability, tooling >Reporter: Dave Latham >Assignee: Dave Latham > Labels: tooling > Fix For: 2.0.0, 0.98.14, 1.2.0 > > Attachments: HBASE-13639-0.98-addendum-hadoop-1.patch, > HBASE-13639-0.98.patch, HBASE-13639-v1.patch, HBASE-13639-v2.patch, > HBASE-13639-v3-0.98.patch, HBASE-13639-v3.patch, HBASE-13639.patch > > > Given HBase tables in remote clusters with similar but not identical data, > efficiently update a target table such that the data in question is identical > to a source table. Efficiency in this context means using far less network > traffic than would be required to ship all the data from one cluster to the > other. Takes inspiration from rsync. > Design doc: > https://docs.google.com/document/d/1-2c9kJEWNrXf5V4q_wBcoIXfdchN7Pxvxv1IO6PW0-U/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15571) Make MasterProcedureManagerHost accessible through MasterServices
[ https://issues.apache.org/jira/browse/HBASE-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220665#comment-15220665 ] Ted Yu commented on HBASE-15571: Failed tests didn't seem to be related to patch. > Make MasterProcedureManagerHost accessible through MasterServices > - > > Key: HBASE-15571 > URL: https://issues.apache.org/jira/browse/HBASE-15571 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Attachments: 15571.v1.patch > > > One of the review comments for HBASE-15411 is to drop dependency on > HBaseAdmin in table backup procedure. > See the comments starting with: > https://issues.apache.org/jira/browse/HBASE-15411?focusedCommentId=15219215=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15219215 > In order to execute procedure inside table backup procedure, we need access > to MasterProcedureManagerHost. > This issue adds accessor to MasterServices for MasterProcedureManagerHost. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15556) need extensible ConsistencyControl interface
[
https://issues.apache.org/jira/browse/HBASE-15556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220659#comment-15220659
]
Hadoop QA commented on HBASE-15556:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
20s {color} | {color:green} branch-1.0 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 9s
{color} | {color:green} branch-1.0 passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 41s
{color} | {color:green} branch-1.0 passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
26s {color} | {color:green} branch-1.0 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
23s {color} | {color:green} branch-1.0 passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m 20s
{color} | {color:red} hbase-server in branch-1.0 has 59 extant Findbugs
warnings. {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 1m 5s
{color} | {color:red} hbase-server in branch-1.0 failed with JDK v1.8.0.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 48s
{color} | {color:green} branch-1.0 passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
47s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 7s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 7s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 41s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 41s
{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m 23s
{color} | {color:red} hbase-server: patch generated 3 new + 62 unchanged - 0
fixed = 65 total (was 62) {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
18s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
14m 19s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
48s {color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m 55s
{color} | {color:red} hbase-server in the patch failed with JDK v1.8.0. {color}
|
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 4m 36s
{color} | {color:red} hbase-server-jdk1.7.0_79 with JDK v1.7.0_79 generated 6
new + 13 unchanged - 0 fixed = 19 total (was 13) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 51s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 160m 20s
{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
59s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 196m 24s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.master.handler.TestEnableTableHandler |
| Timed out junit tests |
org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer |
| | org.apache.hadoop.hbase.io.encoding.TestDataBlockEncoders |
| | org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat2 |
| | org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot |
| | org.apache.hadoop.hbase.snapshot.TestExportSnapshot |
| | org.apache.hadoop.hbase.mapreduce.TestImportExport |
| |
[jira] [Commented] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[ https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220657#comment-15220657 ] Zhan Zhang commented on HBASE-15572: Please open reviewboard for the review. > Adding optional timestamp semantics to HBase-Spark > -- > > Key: HBASE-15572 > URL: https://issues.apache.org/jira/browse/HBASE-15572 > Project: HBase > Issue Type: Improvement > Components: spark >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Attachments: HBASE-15572-1.patch > > > Right now the timestamp is always latest. With this patch, users can select > timestamps they want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15571) Make MasterProcedureManagerHost accessible through MasterServices
[
https://issues.apache.org/jira/browse/HBASE-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220651#comment-15220651
]
Hadoop QA commented on HBASE-15571:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
55s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 55s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 39s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 5m
16s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
19s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
24s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 48s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 45s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
0s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 0s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 0s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 39s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 39s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 5m
11s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
17s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
33m 22s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
58s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 42s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 43s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 132m 35s
{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
16s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 194m 15s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures |
| Timed out junit tests |
org.apache.hadoop.hbase.security.access.TestNamespaceCommands |
| | org.apache.hadoop.hbase.regionserver.TestHRegion |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12796349/15571.v1.patch |
| JIRA Issue | HBASE-15571 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux asf910.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / d6fd859 |
| Default Java | 1.7.0_79 |
|
[jira] [Resolved] (HBASE-15573) Indefinite pause while trying to cleanup data
[ https://issues.apache.org/jira/browse/HBASE-15573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Helmling resolved HBASE-15573. --- Resolution: Invalid This JIRA instance is used for tracking development issues and bugs. Please send an email to the u...@hbase.apache.org mailing list to ask any questions. Sounds like a configuration issue with your client application. > Indefinite pause while trying to cleanup data > - > > Key: HBASE-15573 > URL: https://issues.apache.org/jira/browse/HBASE-15573 > Project: HBase > Issue Type: Bug >Affects Versions: 1.1.2, 1.1.4 >Reporter: Jorge Figueira >Priority: Blocker > Attachments: hbase-hadoop-master-HBASE.log, > hbase-hadoop-regionserver-HBASE.log, hbase-hadoop-zookeeper-HBASE.log > > > Can't retrieve any information with hbase rpc java client. > With hbase shell its possible to scan data and retrieve all the information > normally. > But with any rpc client region server don't retrieve data, all data come with > null values. > Region Server log: > DEBUG [RpcServer.reader=2,bindAddress=HBASE,port=16020] ipc.RpcServer: > RpcServer.listener,port=16020: DISCONNECTING client SERVER:37088 because read > count=-1 > DEBUG [RpcServer.reader=2,bindAddress=HBASE,port=16020] ipc.RpcServer: > RpcServer.listener,port=16020: DISCONNECTING client SERVER2:36997 because > read count=-1 > Master log: > 2016-03-31 18:16:27,998 DEBUG [ProcedureExecutorTimeout] > procedure2.ProcedureExecutor$CompletedProcedureCleaner: No completed > procedures to cleanup. > 2016-03-31 18:16:57,998 DEBUG [ProcedureExecutorTimeout] > procedure2.ProcedureExecutor$CompletedProcedureCleaner: No completed > procedures to cleanup. > 2016-03-31 18:17:27,998 DEBUG [ProcedureExecutorTimeout] > procedure2.ProcedureExecutor$CompletedProcedureCleaner: No completed > procedures to cleanup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[
https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220579#comment-15220579
]
Ted Yu commented on HBASE-15572:
{code}
93val minStamp = parameters.get(HBaseRelation.MIN_STAMP).map(_.toLong)
94val maxStamp = parameters.get(HBaseRelation.MAX_STAMP).map(_.toLong)
{code}
MIN_STAMP -> MIN_TIMESTAMP
MAX_STAMP -> MAX_TIMESTAMP
{code}
243 case _ => throw new IllegalArgumentException("Invalid combination
of query/timestamp/time range provided")
{code}
Better include relation.timestamp, relation.minStamp, relation.maxStamp in the
message.
> Adding optional timestamp semantics to HBase-Spark
> --
>
> Key: HBASE-15572
> URL: https://issues.apache.org/jira/browse/HBASE-15572
> Project: HBase
> Issue Type: Improvement
> Components: spark
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
> Attachments: HBASE-15572-1.patch
>
>
> Right now the timestamp is always latest. With this patch, users can select
> timestamps they want.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[
https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220516#comment-15220516
]
Hadoop QA commented on HBASE-15572:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
12s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 52s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 7s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green} 0m
29s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 52s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} scalac {color} | {color:green} 0m 52s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 7s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} scalac {color} | {color:green} 1m 7s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
25m 46s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green} 0m
30s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green} 0m
29s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 8s
{color} | {color:green} hbase-spark in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
8s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 35m 50s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12796368/HBASE-15572-1.patch |
| JIRA Issue | HBASE-15572 |
| Optional Tests | asflicense scalac scaladoc unit compile |
| uname | Linux asf901.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / d6fd859 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/1246/testReport/ |
| modules | C: hbase-spark U: hbase-spark |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/1246/console |
| Powered by | Apache Yetus 0.2.0 http://yetus.apache.org |
This message was automatically generated.
> Adding optional timestamp semantics to HBase-Spark
> --
>
> Key: HBASE-15572
> URL: https://issues.apache.org/jira/browse/HBASE-15572
> Project: HBase
> Issue Type: Improvement
> Components: spark
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
> Attachments: HBASE-15572-1.patch
>
>
> Right now the timestamp is always latest. With this patch, users can select
> timestamps they want.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (HBASE-15472) replication_admin_test creates a table it doesn't use
[ https://issues.apache.org/jira/browse/HBASE-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby resolved HBASE-15472. - Resolution: Duplicate > replication_admin_test creates a table it doesn't use > - > > Key: HBASE-15472 > URL: https://issues.apache.org/jira/browse/HBASE-15472 > Project: HBase > Issue Type: Bug > Components: Replication, shell >Affects Versions: 2.0.0, 1.2.0 >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby >Priority: Minor > Labels: replication, shell > Attachments: HBASE-15472.patch > > > I noticed while adding tests to replication_admin_test.rb for HBASE-12940 > that it creates an HBase table "hbase_shell_tests_table" that is never used > in any of the suite's tests. Removing the table creation statements speeds up > the suite locally from 1min 10s to 2s. > Note that until HBASE-14562 is worked, this test suite doesn't run as part of > the automatic test runs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15521) Procedure V2 - RestoreSnapshot and CloneSnapshot
[ https://issues.apache.org/jira/browse/HBASE-15521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220490#comment-15220490 ] Matteo Bertozzi commented on HBASE-15521: - +1 > Procedure V2 - RestoreSnapshot and CloneSnapshot > > > Key: HBASE-15521 > URL: https://issues.apache.org/jira/browse/HBASE-15521 > Project: HBase > Issue Type: Sub-task > Components: Client, master, proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > Attachments: HBASE-15521.v1-master.patch > > > Implement procedure-v2 based restore snapshot and clone snapshot (both server > and client side change). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15472) replication_admin_test creates a table it doesn't use
[ https://issues.apache.org/jira/browse/HBASE-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby updated HBASE-15472: Status: Open (was: Patch Available) > replication_admin_test creates a table it doesn't use > - > > Key: HBASE-15472 > URL: https://issues.apache.org/jira/browse/HBASE-15472 > Project: HBase > Issue Type: Bug > Components: Replication, shell >Affects Versions: 1.2.0, 2.0.0 >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby >Priority: Minor > Labels: replication, shell > Attachments: HBASE-15472.patch > > > I noticed while adding tests to replication_admin_test.rb for HBASE-12940 > that it creates an HBase table "hbase_shell_tests_table" that is never used > in any of the suite's tests. Removing the table creation statements speeds up > the suite locally from 1min 10s to 2s. > Note that until HBASE-14562 is worked, this test suite doesn't run as part of > the automatic test runs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15521) Procedure V2 - RestoreSnapshot and CloneSnapshot
[ https://issues.apache.org/jira/browse/HBASE-15521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Yuan Jiang updated HBASE-15521: --- Hadoop Flags: Incompatible change > Procedure V2 - RestoreSnapshot and CloneSnapshot > > > Key: HBASE-15521 > URL: https://issues.apache.org/jira/browse/HBASE-15521 > Project: HBase > Issue Type: Sub-task > Components: Client, master, proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > Attachments: HBASE-15521.v1-master.patch > > > Implement procedure-v2 based restore snapshot and clone snapshot (both server > and client side change). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15521) Procedure V2 - RestoreSnapshot and CloneSnapshot
[ https://issues.apache.org/jira/browse/HBASE-15521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Yuan Jiang updated HBASE-15521: --- Component/s: Client > Procedure V2 - RestoreSnapshot and CloneSnapshot > > > Key: HBASE-15521 > URL: https://issues.apache.org/jira/browse/HBASE-15521 > Project: HBase > Issue Type: Sub-task > Components: Client, master, proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > Attachments: HBASE-15521.v1-master.patch > > > Implement procedure-v2 based restore snapshot and clone snapshot (both server > and client side change). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15521) Procedure V2 - RestoreSnapshot and CloneSnapshot
[ https://issues.apache.org/jira/browse/HBASE-15521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Yuan Jiang updated HBASE-15521: --- Status: Patch Available (was: Open) > Procedure V2 - RestoreSnapshot and CloneSnapshot > > > Key: HBASE-15521 > URL: https://issues.apache.org/jira/browse/HBASE-15521 > Project: HBase > Issue Type: Sub-task > Components: master, proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > Attachments: HBASE-15521.v1-master.patch > > > Implement procedure-v2 based restore snapshot and clone snapshot (both server > and client side change). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15521) Procedure V2 - RestoreSnapshot and CloneSnapshot
[ https://issues.apache.org/jira/browse/HBASE-15521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220479#comment-15220479 ] Stephen Yuan Jiang commented on HBASE-15521: The attached V1 patch implements RestoreSnapshotProcedure and CloneSnapshotProcedure using proc-v2: - implement restore snapshot and clone snapshot procedures to replace handlers code - implement async client API for restore/clone snapshot - remove now-useless isRestoreSnapshotDone RPC call - clean up and refactor SnapshotManager > Procedure V2 - RestoreSnapshot and CloneSnapshot > > > Key: HBASE-15521 > URL: https://issues.apache.org/jira/browse/HBASE-15521 > Project: HBase > Issue Type: Sub-task > Components: master, proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > Attachments: HBASE-15521.v1-master.patch > > > Implement procedure-v2 based restore snapshot and clone snapshot (both server > and client side change). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15521) Procedure V2 - RestoreSnapshot and CloneSnapshot
[ https://issues.apache.org/jira/browse/HBASE-15521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Yuan Jiang updated HBASE-15521: --- Attachment: HBASE-15521.v1-master.patch > Procedure V2 - RestoreSnapshot and CloneSnapshot > > > Key: HBASE-15521 > URL: https://issues.apache.org/jira/browse/HBASE-15521 > Project: HBase > Issue Type: Sub-task > Components: master, proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > Attachments: HBASE-15521.v1-master.patch > > > Implement procedure-v2 based restore snapshot and clone snapshot (both server > and client side change). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15293) Handle TableNotFound and IllegalArgument exceptions in table.jsp.
[ https://issues.apache.org/jira/browse/HBASE-15293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samir Ahmic updated HBASE-15293: Attachment: HBASE-15293_v2.patch [~tedyu] here is new patch addressing formating issues. How did you check for tabs? 'git diff --check' passed for v2. > Handle TableNotFound and IllegalArgument exceptions in table.jsp. > - > > Key: HBASE-15293 > URL: https://issues.apache.org/jira/browse/HBASE-15293 > Project: HBase > Issue Type: Sub-task > Components: UI >Affects Versions: 2.0.0 >Reporter: Samir Ahmic >Assignee: Samir Ahmic > Fix For: 2.0.0 > > Attachments: HBASE-15293_v0.patch, HBASE-15293_v1.patch, > HBASE-15293_v1.patch, HBASE-15293_v2.patch > > > table.jsp accepts "name" parameter for table name and in case when table does > not exist or empty parameter is passed it will throw 500 error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (HBASE-15507) Online modification of enabled ReplicationPeerConfig
[ https://issues.apache.org/jira/browse/HBASE-15507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-15507 started by Geoffrey Jacoby. --- > Online modification of enabled ReplicationPeerConfig > > > Key: HBASE-15507 > URL: https://issues.apache.org/jira/browse/HBASE-15507 > Project: HBase > Issue Type: Improvement > Components: Replication >Affects Versions: 2.0.0, 1.2.0, 1.3.0 >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby > > It's currently possible to update the table CFs for a replication peer while > it's running, but not the peer configuration or data maps introduced as part > of custom replication endpoints in HBASE-11367. > This means that if you have a custom endpoint that depends on some > configuration parameter, you have to remove the peer and recreate it in order > to change the param. In some use cases that's not possible without risking > data loss. > HBASE-11393, which will consolidate tableCFs in the same znode as the rest of > ReplicationPeerConfig, may help here, but with or without it it still seems > like there needs to be further work to add update config/data API support to > ReplicationAdmin and a callback mechanism to notify the endpoints of config > parameter changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15573) Indefinite pause while trying to cleanup data
[ https://issues.apache.org/jira/browse/HBASE-15573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Figueira updated HBASE-15573: --- Priority: Blocker (was: Major) > Indefinite pause while trying to cleanup data > - > > Key: HBASE-15573 > URL: https://issues.apache.org/jira/browse/HBASE-15573 > Project: HBase > Issue Type: Bug >Affects Versions: 1.1.2, 1.1.4 >Reporter: Jorge Figueira >Priority: Blocker > Attachments: hbase-hadoop-master-HBASE.log, > hbase-hadoop-regionserver-HBASE.log, hbase-hadoop-zookeeper-HBASE.log > > > Can't retrieve any information with hbase rpc java client. > With hbase shell its possible to scan data and retrieve all the information > normally. > But with any rpc client region server don't retrieve data, all data come with > null values. > Region Server log: > DEBUG [RpcServer.reader=2,bindAddress=HBASE,port=16020] ipc.RpcServer: > RpcServer.listener,port=16020: DISCONNECTING client SERVER:37088 because read > count=-1 > DEBUG [RpcServer.reader=2,bindAddress=HBASE,port=16020] ipc.RpcServer: > RpcServer.listener,port=16020: DISCONNECTING client SERVER2:36997 because > read count=-1 > Master log: > 2016-03-31 18:16:27,998 DEBUG [ProcedureExecutorTimeout] > procedure2.ProcedureExecutor$CompletedProcedureCleaner: No completed > procedures to cleanup. > 2016-03-31 18:16:57,998 DEBUG [ProcedureExecutorTimeout] > procedure2.ProcedureExecutor$CompletedProcedureCleaner: No completed > procedures to cleanup. > 2016-03-31 18:17:27,998 DEBUG [ProcedureExecutorTimeout] > procedure2.ProcedureExecutor$CompletedProcedureCleaner: No completed > procedures to cleanup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15567) TestReplicationShell broken by recent replication changes
[ https://issues.apache.org/jira/browse/HBASE-15567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-15567: -- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.0.0 Status: Resolved (was: Patch Available) I've committed this. Thanks Geoffrey for the patch. > TestReplicationShell broken by recent replication changes > - > > Key: HBASE-15567 > URL: https://issues.apache.org/jira/browse/HBASE-15567 > Project: HBase > Issue Type: Bug > Components: Replication, shell >Affects Versions: 2.0.0 >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby >Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-15567.patch > > > Recent changes to the Ruby shell's add_peer method in HBASE-11393 have broken > TestReplicationShell, which went unnoticed because it's currently Ignored as > flaky. This test is useful when developing extensions to the replication > shell commands, and should be kept working (and hopefully re-enabled in the > near future.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15570) renewable delegation tokens for long-lived spark applications
[ https://issues.apache.org/jira/browse/HBASE-15570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15220402#comment-15220402 ] Gary Helmling commented on HBASE-15570: --- bq. I'd strongly prefer to avoid changing the way the HBase server side handles tokens, so it'd be new tokens most likely. +1 to that. I'm really not familiar with the spark code. So they push a keytab into HDFS for the AM? That seems iffy, but should have the same effect as the Twill approach. Does the Spark AM then push out updated tokens to the running containers? FWIW, the Twill token update happens here in updateSecureStores / updateCredentials: https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=blob_plain;f=twill-yarn/src/main/java/org/apache/twill/yarn/YarnTwillRunnerService.java;hb=HEAD > renewable delegation tokens for long-lived spark applications > - > > Key: HBASE-15570 > URL: https://issues.apache.org/jira/browse/HBASE-15570 > Project: HBase > Issue Type: Improvement > Components: spark >Reporter: Sean Busbey >Assignee: Sean Busbey > > Right now our spark integration works on secure clusters by getting > delegation tokens and sending them to the executors. Unfortunately, > applications that need to run for longer than the delegation token lifetime > (by default 7 days) will fail. > In particular, this is an issue for Spark Streaming applications. Since they > expect to run indefinitely, we should have a means for renewing the > delegation tokens. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15572) Adding optional timestamp semantics to HBase-Spark
[ https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiqing Yang updated HBASE-15572: - Status: Patch Available (was: Open) > Adding optional timestamp semantics to HBase-Spark > -- > > Key: HBASE-15572 > URL: https://issues.apache.org/jira/browse/HBASE-15572 > Project: HBase > Issue Type: Improvement > Components: spark >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Attachments: HBASE-15572-1.patch > > > Right now the timestamp is always latest. With this patch, users can select > timestamps they want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
