[jira] [Resolved] (HBASE-25569) Adding region count and average region size in a table at regionserver level

2021-02-12 Thread Viraj Jasani (Jira)


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

Viraj Jasani resolved HBASE-25569.
--
Hadoop Flags: Reviewed
  Resolution: Fixed

Thanks for the contribution [~mnpoonia].

> Adding region count and average region size in a table at regionserver level
> 
>
> Key: HBASE-25569
> URL: https://issues.apache.org/jira/browse/HBASE-25569
> Project: HBase
>  Issue Type: New Feature
>  Components: metrics
>Affects Versions: 1.6.0
>Reporter: Aman Poonia
>Assignee: Aman Poonia
>Priority: Minor
> Fix For: 1.7.0
>
>
> Currently we have these two metrics - regionCount and avgRegionSize in 
> branch-2+. Adding them to branch-1. These will give better insight into 
> whether we should enable region normalizer on a table or not.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (HBASE-25573) release script generated vote template has incorrect staging area

2021-02-12 Thread Sean Busbey (Jira)
Sean Busbey created HBASE-25573:
---

 Summary: release script generated vote template has incorrect 
staging area
 Key: HBASE-25573
 URL: https://issues.apache.org/jira/browse/HBASE-25573
 Project: HBase
  Issue Type: Bug
  Components: community
Reporter: Sean Busbey
Assignee: Sean Busbey


I noticed while making the hbase-thirdparty 3.5.0 RC0 that the generated vote 
email showed the location of the RC using just the version and RC number:

https://dist.apache.org/repos/dist/dev/hbase/3.5.0RC0/

The correct location needs to include the project name when the release is for 
something other than the main project, e.g.:

https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty-3.5.0RC0/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (HBASE-25572) HBase filesystem repo should have a "release" maven profile

2021-02-12 Thread Sean Busbey (Jira)
Sean Busbey created HBASE-25572:
---

 Summary: HBase filesystem repo should have a "release" maven 
profile
 Key: HBASE-25572
 URL: https://issues.apache.org/jira/browse/HBASE-25572
 Project: HBase
  Issue Type: Bug
  Components: community
Reporter: Sean Busbey
Assignee: Sean Busbey
 Fix For: hbase-filesystem-1.0.0-alpha2


Trying to run a RC for the hbase-filesystem project fails in dryrun because 
there isn't a "release" profile and the RC creation scripts require one.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (HBASE-25571) Compilation in branch-2 after HBASE-25364

2021-02-12 Thread Mohammad Arshad (Jira)
Mohammad Arshad created HBASE-25571:
---

 Summary: Compilation in branch-2 after  HBASE-25364
 Key: HBASE-25571
 URL: https://issues.apache.org/jira/browse/HBASE-25571
 Project: HBase
  Issue Type: Bug
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad


{code:java}
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] 
/D:/code/apache/forked/hbaseBranch2/hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/TestHFile.java:[737,12]
 cannot find symbol
  symbol:   method getCell(byte[],byte[],byte[])
  location: class org.apache.hadoop.hbase.io.hfile.TestHFile
[ERROR] 
/D:/code/apache/forked/hbaseBranch2/hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/TestHFile.java:[738,13]
 cannot find symbol
  symbol:   method getCell(byte[],byte[],byte[])
  location: class org.apache.hadoop.hbase.io.hfile.TestHFile
[ERROR] 
/D:/code/apache/forked/hbaseBranch2/hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/TestHFile.java:[744,12]
 cannot find symbol
  symbol:   method getCell(byte[],byte[],byte[])
  location: class org.apache.hadoop.hbase.io.hfile.TestHFile
[ERROR] 
/D:/code/apache/forked/hbaseBranch2/hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/TestHFile.java:[745,13]
 cannot find symbol
  symbol:   method getCell(byte[],byte[],byte[])
  location: class org.apache.hadoop.hbase.io.hfile.TestHFile
[INFO] 4 errors

{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (HBASE-25570) On largish cluster, "CleanerChore: Could not delete dir..." makes master log unreadable

2021-02-12 Thread Michael Stack (Jira)
Michael Stack created HBASE-25570:
-

 Summary: On largish cluster, "CleanerChore: Could not delete 
dir..." makes master log unreadable
 Key: HBASE-25570
 URL: https://issues.apache.org/jira/browse/HBASE-25570
 Project: HBase
  Issue Type: Improvement
Reporter: Michael Stack


Looking at a running master on a largish cluster, the master log is full of 
spew to this effect:
{{
2021-02-10 23:16:49,330 INFO  [dir-scan-pool4-thread-206391] 
cleaner.CleanerChore: Could not delete dir under 
hdfs://web2-dfs:8020/hbase/archive/data/default/crawl_graph. might be 
transient; we'll retry. if it keeps happening, use following exception when 
asking on mailing list.
org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.fs.PathIsNotEmptyDirectoryException):
 `/hbase/archive/data/default/crawl_graph is non empty': Directory is not empty
at 
org.apache.hadoop.hdfs.server.namenode.FSDirDeleteOp.delete(FSDirDeleteOp.java:116)
at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.delete(FSNamesystem.java:2962)
at 
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.delete(NameNodeRpcServer.java:1092)
at 
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.delete(ClientNamenodeProtocolServerSideTranslatorPB.java:681)
at 
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
at 
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:523)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:991)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:869)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:815)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1875)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2675)

at org.apache.hadoop.ipc.Client.getRpcResponse(Client.java:1499)
at org.apache.hadoop.ipc.Client.call(Client.java:1445)
at org.apache.hadoop.ipc.Client.call(Client.java:1355)
at 
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:228)
at 
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:116)
at com.sun.proxy.$Proxy19.delete(Unknown Source)
at 
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.delete(ClientNamenodeProtocolTranslatorPB.java:621)
at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:422)
at 
org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeMethod(RetryInvocationHandler.java:165)
at 
org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invoke(RetryInvocationHandler.java:157)
at 
org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeOnce(RetryInvocationHandler.java:95)
at 
org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:359)
at com.sun.proxy.$Proxy20.delete(Unknown Source)
at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.hbase.fs.HFileSystem$1.invoke(HFileSystem.java:372)
at com.sun.proxy.$Proxy21.delete(Unknown Source)
at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.hbase.fs.HFileSystem$1.invoke(HFileSystem.java:372)
at com.sun.proxy.$Proxy21.delete(Unknown Source)
at org.apache.hadoop.hdfs.DFSClient.delete(DFSClient.java:1572)
at 
org.apache.hadoop.hdfs.DistributedFileSystem$19.doCall(DistributedFileSystem.java:880)
at 
org.apache.hadoop.hdfs.DistributedFileSystem$19.doCall(DistributedFileSystem.java:877)
at 
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
at 
org.apache.hadoop.hdfs.DistributedFileSystem.delete(DistributedFileSystem.java:887)
at 
org.apache.hadoop.hbase.master.cleaner.CleanerChore.lambda$null$4(CleanerChore.java:441)
at 
org.apache.hadoop.hbase.master.cleaner.CleanerChore.deleteAction(CleanerChore.java:466)
at 
org.apache.ha

[jira] [Resolved] (HBASE-25551) Hbase connector with apache spark

2021-02-12 Thread Balazs Meszaros (Jira)


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

Balazs Meszaros resolved HBASE-25551.
-
Resolution: Invalid

Timed out, closing it.

> Hbase connector with apache spark
> -
>
> Key: HBASE-25551
> URL: https://issues.apache.org/jira/browse/HBASE-25551
> Project: HBase
>  Issue Type: Wish
>Reporter: Shubham swaraj
>Priority: Major
>
> Hbase connector with apache



--
This message was sent by Atlassian Jira
(v8.3.4#803005)