[jira] [Resolved] (HBASE-20146) Regions are stuck while opening when WAL is disabled

[ https://issues.apache.org/jira/browse/HBASE-20146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-20146. --- Resolution: Fixed Pushed the addendum to branch-1.2+. > Regions are stuck while opening when WAL is

Re: TSaslServerTransport.TSaslServerDefinition serverName should get from principal , not DNS

Some concepts need to be clarified before further discussions. A host principal should be "host/FQDN@REALM", host is the keyword for a host principal, NOT bq. Let's call... as host principal... A service principal should be "service_name/FDQN@REALM", so hbase/_h...@domain.com is also a

Re: TSaslServerTransport.TSaslServerDefinition serverName should get from principal , not DNS

*Hi, Josh * *Let's call "hbase/_h...@domain.com " as host principal and "hbase/thriftserv...@domain.com " as services principal。 * *In most services , like RegionServer on HBase or DataNode on HDFS, we should configure SASL bye hostname. * *But when I do

[jira] [Created] (HBASE-20204) Add locking to RefreshFileConnections in BucketCache

Zach York created HBASE-20204: - Summary: Add locking to RefreshFileConnections in BucketCache Key: HBASE-20204 URL: https://issues.apache.org/jira/browse/HBASE-20204 Project: HBase Issue Type:

[jira] [Reopened] (HBASE-20146) Regions are stuck while opening when WAL is disabled

[ https://issues.apache.org/jira/browse/HBASE-20146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell reopened HBASE-20146: Reopened because there is an addendum in progress and some discussion about it. Please commit

[jira] [Created] (HBASE-20203) [AMv2] CODE-BUG: Uncaught runtime exception for pid=...., state=SUCCESS; AssignProcedure

stack created HBASE-20203: - Summary: [AMv2] CODE-BUG: Uncaught runtime exception for pid=, state=SUCCESS; AssignProcedure Key: HBASE-20203 URL: https://issues.apache.org/jira/browse/HBASE-20203 Project:

[jira] [Created] (HBASE-20202) [AMv2] Don't move region if its a split parent or offlined

stack created HBASE-20202: - Summary: [AMv2] Don't move region if its a split parent or offlined Key: HBASE-20202 URL: https://issues.apache.org/jira/browse/HBASE-20202 Project: HBase Issue Type:

[jira] [Created] (HBASE-20201) HBase must provide commons-cli-1.4 for mapreduce jobs with H3

Josh Elser created HBASE-20201: -- Summary: HBase must provide commons-cli-1.4 for mapreduce jobs with H3 Key: HBASE-20201 URL: https://issues.apache.org/jira/browse/HBASE-20201 Project: HBase

[jira] [Reopened] (HBASE-18864) NullPointerException thrown when adding rows to a table from peer cluster, table with replication factor other than 0 or 1

[ https://issues.apache.org/jira/browse/HBASE-18864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe reopened HBASE-18864: -- > NullPointerException thrown when adding rows to a table from peer cluster, > table with

Re: 1.3.2 status is incorrect in JIRA

Thanks for the clarification Andrew! On Wed, Mar 14, 2018 at 5:26 PM, Andrew Purtell wrote: > The RMs release in JIRA for voting on release candidates. It helps with > assembling CHANGES and makes it less likely someone will set a fix version > to something in the

Re: [DISCUSS] our stable release pointer and EOM

Even when claiming a code line stable we can call out specific features as experimental, and have done so in the past. Some examples: - encryption - HFileV3 - ZK-less assignment My thinking is in 1.4 RSGroups is the experimental feature, and in 1.5 it will be storage class aware file placement.

Re: TSaslServerTransport.TSaslServerDefinition serverName should get from principal , not DNS

No, the principal should definitely get pulled from DNS. Remember that you must consistently use the same naming to refer to a service when Kerberos in the mix. This is why the FQDN (and DNS) is so important for services. Your issue seems to be that you have multiple different names for a

[jira] [Created] (HBASE-20200) list_procedures fails in shell

Balazs Meszaros created HBASE-20200: --- Summary: list_procedures fails in shell Key: HBASE-20200 URL: https://issues.apache.org/jira/browse/HBASE-20200 Project: HBase Issue Type: Bug

Re: 1.3.2 status is incorrect in JIRA

The RMs release in JIRA for voting on release candidates. It helps with assembling CHANGES and makes it less likely someone will set a fix version to something in the process of release. When I do this I set the release date to the expected conclusion of voting. The date can be adjusted if

1.3.2 status is incorrect in JIRA

Hi, I noticed that 1.3.2 is marked as "released" in JIRA but it is still an unreleased version. What is the reason for that? Thanks, Peter

[jira] [Created] (HBASE-20199) Add test to prevent further permission regression around table flush and snapshot

Josh Elser created HBASE-20199: -- Summary: Add test to prevent further permission regression around table flush and snapshot Key: HBASE-20199 URL: https://issues.apache.org/jira/browse/HBASE-20199

[jira] [Created] (HBASE-20198) ReplicationSource::initialize shouldn't always retry

Mike Drob created HBASE-20198: - Summary: ReplicationSource::initialize shouldn't always retry Key: HBASE-20198 URL: https://issues.apache.org/jira/browse/HBASE-20198 Project: HBase Issue Type:

[jira] [Created] (HBASE-20196) Maintain all regions with same size in memstore flusher

Ted Yu created HBASE-20196: -- Summary: Maintain all regions with same size in memstore flusher Key: HBASE-20196 URL: https://issues.apache.org/jira/browse/HBASE-20196 Project: HBase Issue Type:

[jira] [Created] (HBASE-20197) Review of ByteBufferWriterOutputStream.java

BELUGA BEHR created HBASE-20197: --- Summary: Review of ByteBufferWriterOutputStream.java Key: HBASE-20197 URL: https://issues.apache.org/jira/browse/HBASE-20197 Project: HBase Issue Type:

TSaslServerTransport.TSaslServerDefinition serverName should get from principal , not DNS

Hi, guys I use ThriftServer2 in kerberos , and I found some wrong when all server's principal is "hbase/thriftserv...@domain.com". when I look at the code and I found something maybe not right ! When we start Thrift Server , we get host from DNS if (securityEnabled) { host =

Re: Missing jira number

Good. Thanks for the quick fix. 2018-03-14 18:55 GMT+08:00 Peter Somogyi : > I haven't noticed the missing jira id when committing. Fixed now. > > On Wed, Mar 14, 2018 at 11:39 AM, 张铎(Duo Zhang) > wrote: > > > commit

Re: Missing jira number

I haven't noticed the missing jira id when committing. Fixed now. On Wed, Mar 14, 2018 at 11:39 AM, 张铎(Duo Zhang) wrote: > commit 641c87ddf93f88758b5db0b5b506ec53dc826a62 > Author: Sakthi > Date: Tue Mar 13 23:40:09 2018 -0700 > > Fixed typo

Missing jira number

commit 641c87ddf93f88758b5db0b5b506ec53dc826a62 Author: Sakthi Date: Tue Mar 13 23:40:09 2018 -0700 Fixed typo in Required Java Version error message while building HBase Signed-off-by: Umesh Agashe

[jira] [Resolved] (HBASE-20195) happybase connection password

[ https://issues.apache.org/jira/browse/HBASE-20195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Somogyi resolved HBASE-20195. --- Resolution: Invalid Please use the user mailing list with similar questions. Thanks. >

[jira] [Created] (HBASE-20195) happybase connection password

sanghyunkwon created HBASE-20195: Summary: happybase connection password Key: HBASE-20195 URL: https://issues.apache.org/jira/browse/HBASE-20195 Project: HBase Issue Type: Task

[jira] [Created] (HBASE-20194) Basic Replication WebUI - Master

Jingyun Tian created HBASE-20194: Summary: Basic Replication WebUI - Master Key: HBASE-20194 URL: https://issues.apache.org/jira/browse/HBASE-20194 Project: HBase Issue Type: Task

[jira] [Created] (HBASE-20193) Basic Replication Web UI - Regionserver

Jingyun Tian created HBASE-20193: Summary: Basic Replication Web UI - Regionserver Key: HBASE-20193 URL: https://issues.apache.org/jira/browse/HBASE-20193 Project: HBase Issue Type: Task

[jira] [Created] (HBASE-20192) RedirectServlet not getting registered in HMaster.putUpJettyServer() in local mode

Samir Ahmic created HBASE-20192: --- Summary: RedirectServlet not getting registered in HMaster.putUpJettyServer() in local mode Key: HBASE-20192 URL: https://issues.apache.org/jira/browse/HBASE-20192

Re: Flush requires global ADMIN permission on 2.0

Not a fan of allowing users (including table and namespace admins) access to HBase apis that directly allow them to create new files, etc. There's potential for misuse spamming the NN, broadening the issue. My 2 cents. Francis On Tue, Mar 13, 2018 at 1:49 PM Josh Elser

[jira] [Created] (HBASE-20191) Deal with the cleanup of replication barrier for deleted table

Duo Zhang created HBASE-20191: - Summary: Deal with the cleanup of replication barrier for deleted table Key: HBASE-20191 URL: https://issues.apache.org/jira/browse/HBASE-20191 Project: HBase