[jira] [Created] (HBASE-20848) Backport HBASE-20616 "TruncateTableProcedure is stuck in retry loop in TRUNCATE_TABLE_CREATE_FS_LAYOUT state" to branch-1

2018-07-04 Thread Toshihiro Suzuki (JIRA)
Toshihiro Suzuki created HBASE-20848:


 Summary: Backport HBASE-20616 "TruncateTableProcedure is stuck in 
retry loop in TRUNCATE_TABLE_CREATE_FS_LAYOUT state" to branch-1
 Key: HBASE-20848
 URL: https://issues.apache.org/jira/browse/HBASE-20848
 Project: HBase
  Issue Type: Sub-task
  Components: backport
Reporter: Toshihiro Suzuki


Backport parent issue to branch-1.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (HBASE-20847) The parent procedure of RegionTransitionProcedure may not have the table lock

2018-07-04 Thread Duo Zhang (JIRA)
Duo Zhang created HBASE-20847:
-

 Summary: The parent procedure of RegionTransitionProcedure may not 
have the table lock
 Key: HBASE-20847
 URL: https://issues.apache.org/jira/browse/HBASE-20847
 Project: HBase
  Issue Type: Sub-task
  Components: proc-v2, Region Assignment
Reporter: Duo Zhang


For example, SCP can also schedule AssignProcedure and obviously it will not 
hold the table lock.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (HBASE-20846) Table's shared lock is not hold by sub-procedures after master restart

2018-07-04 Thread Allan Yang (JIRA)
Allan Yang created HBASE-20846:
--

 Summary: Table's shared lock is not hold by sub-procedures after 
master restart
 Key: HBASE-20846
 URL: https://issues.apache.org/jira/browse/HBASE-20846
 Project: HBase
  Issue Type: Bug
Affects Versions: 2.1.0
Reporter: Allan Yang
Assignee: Allan Yang
 Fix For: 3.0.0, 2.1.0, 2.0.2


Found this one when investigating ModifyTableProcedure got stuck while there 
was a MoveRegionProcedure going on after master restart.
Though this issue can be solved by HBASE-20752. But I discovered something else.
Before a MoveRegionProcedure can execute, it will hold the table's shared lock. 
so,, when a UnassignProcedure was spwaned, it will not check the table's shared 
lock since it is sure that its parent(MoveRegionProcedure) has aquired the 
table's lock.
{code:java}
// If there is parent procedure, it would have already taken xlock, so no need 
to take
  // shared lock here. Otherwise, take shared lock.
  if (!procedure.hasParent()
  && waitTableQueueSharedLock(procedure, table) == null) {
  return true;
  }
{code}

But, it is not the case when Master was restarted. The child 
procedure(UnassignProcedure) will be executed first after restart. Though it 
has a parent(MoveRegionProcedure), but apprently the parent didn't hold the 
table's lock.
So, since it began to execute without hold the table's shared lock. A 
ModifyTableProcedure can aquire the table's exclusive lock and execute at the 
same time. Which is not possible if the master was not restarted.
This will cause a stuck before HBASE-20752. But since HBASE-20752 has fixed, I 
wrote a simple UT to repo this case.

I think we don't have to check the parent for table's shared lock. It is a 
shared lock, right? I think we can acquire it every time we need it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (HBASE-20845) Support set the consistency for Gets and Scans in thrift2

2018-07-04 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-20845:
-

 Summary: Support set the consistency for Gets and Scans in thrift2
 Key: HBASE-20845
 URL: https://issues.apache.org/jira/browse/HBASE-20845
 Project: HBase
  Issue Type: Improvement
  Components: Thrift
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng
 Fix For: 3.0.0, 2.1.0, 2.2.0


Support set the consistency for Gets and Scans in thrift2



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (HBASE-20844) Duplicate rows returned while hbase snapshot reads

2018-07-04 Thread ShivaKumar SS (JIRA)
ShivaKumar SS created HBASE-20844:
-

 Summary: Duplicate rows returned while hbase snapshot reads
 Key: HBASE-20844
 URL: https://issues.apache.org/jira/browse/HBASE-20844
 Project: HBase
  Issue Type: Bug
  Components: mapreduce, spark
Affects Versions: 1.3.1
 Environment: Cluster Details 

Java1.7
Hbase 1.3.1
Spark  1.6.1
Reporter: ShivaKumar SS


We are trying to take snapshot from code and read data using MR and spark, both 
approaches are returning duplicate records.

On the API side, {{org.apache.hadoop.hbase.mapreduce.TableSnapshotInputFormat 
}} is used. 

Snapshot was taken during the table is being in the region split state. 

We suspect it is due to data is being returned for both parent and daughter 
regions.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (HBASE-20843) Add HBase-2.1 to support matrix

2018-07-04 Thread Duo Zhang (JIRA)
Duo Zhang created HBASE-20843:
-

 Summary: Add HBase-2.1 to support matrix
 Key: HBASE-20843
 URL: https://issues.apache.org/jira/browse/HBASE-20843
 Project: HBase
  Issue Type: Sub-task
Reporter: Duo Zhang






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)