[jira] [Created] (HBASE-21809) Add retry thrift client for ThriftTable/Admin

2019-01-29 Thread Allan Yang (JIRA)
Allan Yang created HBASE-21809:
--

 Summary: Add retry thrift client for ThriftTable/Admin
 Key: HBASE-21809
 URL: https://issues.apache.org/jira/browse/HBASE-21809
 Project: HBase
  Issue Type: Sub-task
Reporter: Allan Yang
Assignee: Allan Yang
 Fix For: 3.0.0, 2.2.0


This is for ThriftTable/Admin to handle exceptions like connection loss.
And only available for http thrift client. For client using TSocket, it is not 
so easy to implement a retry client, maybe later.



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


Re: Requesting access to hbase slack channel

2019-01-29 Thread 车 珣


Could you please invite me: singleon...@gmail.com . Thank you~
On 01/30/2019 13:25,William 
Shen wrote:
Can you please invite me as well? Thank you.

On Sat, Jan 19, 2019 at 7:50 AM Robert Yokota  wrote:

Me too please :) rayok...@gmail.com

On Fri, Jan 18, 2019 at 2:06 AM Peter Somogyi  wrote:

Sent.

On Fri, Jan 18, 2019 at 7:48 AM Abhishek Gupta 
wrote:

Hi,

I would like an invitation too abhila...@gmail.com

Thanks

On Fri, Jan 18, 2019 at 11:38 AM Manjeet Singh <
manjeet.chand...@gmail.com

wrote:

Done

On Fri, 18 Jan 2019, 11:24 Buchi Reddy Busi Reddy <
mailtobu...@gmail.com
wrote:

Can you also invite mailtobu...@gmail.com please?

On Thu, Jan 17, 2019 at 8:34 PM Manjeet Singh <
manjeet.chand...@gmail.com>
wrote:

Seems someone else already did it

Manjeet

On Wed, 16 Jan 2019, 17:33 Nihal Jain 
wrote:

Hi Team,

I was wondering if I could get access to the HBase user
slack
channel

https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapache-hbase.slack.comdata=02%7C01%7C%7Cc2b9d9be2f9f498e25a208d686734bcb%7C84df9e7fe9f640afb435%7C1%7C0%7C636844227076460951sdata=XJDTTVDIXh3k0mnUt4cSTvM0uCmScUAPUZSfzxAi4eM%3Dreserved=0

It says here <
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHBASE-16413data=02%7C01%7C%7Cc2b9d9be2f9f498e25a208d686734bcb%7C84df9e7fe9f640afb435%7C1%7C0%7C636844227076460951sdata=MStwCobJY76EyALeoOClqPI%2FjkRrjp93qgjEEKYPAQA%3Dreserved=0>
that I
should email you guys  :)

Thanks,
Madhur Pant











Re: Requesting access to hbase slack channel

2019-01-29 Thread William Shen
Can you please invite me as well? Thank you.

On Sat, Jan 19, 2019 at 7:50 AM Robert Yokota  wrote:

> Me too please :) rayok...@gmail.com
>
> On Fri, Jan 18, 2019 at 2:06 AM Peter Somogyi  wrote:
>
> > Sent.
> >
> > On Fri, Jan 18, 2019 at 7:48 AM Abhishek Gupta 
> > wrote:
> >
> > > Hi,
> > >
> > > I would like an invitation too abhila...@gmail.com
> > >
> > > Thanks
> > >
> > > On Fri, Jan 18, 2019 at 11:38 AM Manjeet Singh <
> > manjeet.chand...@gmail.com
> > > >
> > > wrote:
> > >
> > > > Done
> > > >
> > > > On Fri, 18 Jan 2019, 11:24 Buchi Reddy Busi Reddy <
> > mailtobu...@gmail.com
> > > > wrote:
> > > >
> > > > > Can you also invite mailtobu...@gmail.com please?
> > > > >
> > > > > On Thu, Jan 17, 2019 at 8:34 PM Manjeet Singh <
> > > > manjeet.chand...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Seems someone else already did it
> > > > > >
> > > > > > Manjeet
> > > > > >
> > > > > > On Wed, 16 Jan 2019, 17:33 Nihal Jain  > wrote:
> > > > > >
> > > > > > > Hi
> > > > > > >
> > > > > > > Could you please invite me: nihaljain...@gmail.com <
> > > > > > nihaljain...@gmail.com
> > > > > > > >?
> > > > > > >
> > > > > > > Regards,
> > > > > > > Nihal
> > > > > > >
> > > > > > > On Wed, 16 Jan, 2019, 2:54 PM Peter Somogyi <
> psomo...@apache.org
> > > > > wrote:
> > > > > > >
> > > > > > > > Sent invitation to madhurpan...@gmail.com.
> > > > > > > >
> > > > > > > > On Wed, Jan 16, 2019 at 7:27 AM Madhur Pant <
> > > > madhurpan...@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Team,
> > > > > > > > >
> > > > > > > > > I was wondering if I could get access to the HBase user
> slack
> > > > > channel
> > > > > > > > >
> > > > > > > > > https://apache-hbase.slack.com
> > > > > > > > >
> > > > > > > > > It says here <
> > > https://issues.apache.org/jira/browse/HBASE-16413>
> > > > > > > that I
> > > > > > > > > should email you guys  :)
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Madhur Pant
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>


[jira] [Created] (HBASE-21808) Ensure we can build with JDK11 targetting JDK8

2019-01-29 Thread Sean Busbey (JIRA)
Sean Busbey created HBASE-21808:
---

 Summary: Ensure we can build with JDK11 targetting JDK8
 Key: HBASE-21808
 URL: https://issues.apache.org/jira/browse/HBASE-21808
 Project: HBase
  Issue Type: Improvement
  Components: build, community, java
Affects Versions: 3.0.0
Reporter: Sean Busbey
Assignee: Sean Busbey


When folks "install a JDK" they're likely to get JDK11 now (e.g. from homebrew, 
in RHEL/CentOS 7.6). For new contributors this results in confusing errors on 
first run.

Make it so that a non-release build using JDK11 and using our default compiler 
source/target versions of JDK8 can complete.



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


[jira] [Created] (HBASE-21807) Backport HBASE-21225 to branch-2.0 and branch-2.1

2019-01-29 Thread Sakthi (JIRA)
Sakthi created HBASE-21807:
--

 Summary: Backport HBASE-21225 to branch-2.0 and branch-2.1
 Key: HBASE-21807
 URL: https://issues.apache.org/jira/browse/HBASE-21807
 Project: HBase
  Issue Type: Task
Reporter: Sakthi
Assignee: Sakthi


Backport HBASE-21225 to branch-2.0 and branch-2.1. The specified Jira is 
closed, hence filing this one to track the backport.



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


[jira] [Created] (HBASE-21806) add an option to roll WAL on very slow syncs

2019-01-29 Thread Sergey Shelukhin (JIRA)
Sergey Shelukhin created HBASE-21806:


 Summary: add an option to roll WAL on very slow syncs
 Key: HBASE-21806
 URL: https://issues.apache.org/jira/browse/HBASE-21806
 Project: HBase
  Issue Type: Bug
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin


In large heterogeneous clusters sometimes a slow datanode can cause WAL syncs 
to be very slow. In this case, before the bad datanode recovers, or is 
discovered and repaired, it would be helpful to roll WAL on a very slow sync to 
get a new pipeline.



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


Re: HBase Website Cleanup task

2019-01-29 Thread Sakthi
FYI: This is the job I'm talking about:
https://builds.apache.org/job/HBase%20Website%20Link%20Checker/

Regards,
Sakthi

On Tue, Jan 29, 2019 at 11:17 AM Sakthi  wrote:

> Hello all,
>
> The most recent (and many of the previous) "*HBase Website Link Checker*"
> job of ours has reported several issues with the website. The job takes
> roughly 20+ hours to finish and has reported "*1458 missing files*" and "*7143
> missing named anchors*".
>
> *Quick facts:* Of the 1400+ missing files issues, around 1200 are from
> 1.2, 90 from 0.94, 40 from 2.0, 30 from 2.1 and rest from the master.
>
> I have filed an *Umbrella JIRA:* HBASE-21803
>  ("HBase Website
> Cleanup"). If folks find any other website related issues that we would
> like to address, we can use this umbrella to track it.
>
> Any suggestions are welcome!
>
> Regards,
> Sakthi
>


HBase Website Cleanup task

2019-01-29 Thread Sakthi
Hello all,

The most recent (and many of the previous) "*HBase Website Link Checker*"
job of ours has reported several issues with the website. The job takes
roughly 20+ hours to finish and has reported "*1458 missing files*" and "*7143
missing named anchors*".

*Quick facts:* Of the 1400+ missing files issues, around 1200 are from 1.2,
90 from 0.94, 40 from 2.0, 30 from 2.1 and rest from the master.

I have filed an *Umbrella JIRA:* HBASE-21803
 ("HBase Website
Cleanup"). If folks find any other website related issues that we would
like to address, we can use this umbrella to track it.

Any suggestions are welcome!

Regards,
Sakthi


[jira] [Created] (HBASE-21805) Extend per table metrics with some RPC layer measures

2019-01-29 Thread Andrew Purtell (JIRA)
Andrew Purtell created HBASE-21805:
--

 Summary: Extend per table metrics with some RPC layer measures
 Key: HBASE-21805
 URL: https://issues.apache.org/jira/browse/HBASE-21805
 Project: HBase
  Issue Type: Improvement
  Components: metrics, rpc
Reporter: Andrew Purtell


RPC metrics are whole server in scope. We should extend the per-table metrics 
to also track a subset of RPC metrics on a per table basis. This would give 
better insight into the subjective experience of each use case. 

Consider TotalCallTime, ProcessCallTime, QueueCallTime. Table metrics already 
track request counts and server side processing latencies, just not queueing 
effects at the RPC layer.

Ideally we avoid introducing another configuration option but this could be 
made optional, if overheads are significant (measure them)



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


[jira] [Created] (HBASE-21804) Remove 0.94 check from the Linkchecker job

2019-01-29 Thread Sakthi (JIRA)
Sakthi created HBASE-21804:
--

 Summary: Remove 0.94 check from the Linkchecker job
 Key: HBASE-21804
 URL: https://issues.apache.org/jira/browse/HBASE-21804
 Project: HBase
  Issue Type: Sub-task
Reporter: Sakthi
Assignee: Sakthi


This is a pretty old release. Even though we don't have the link to the doc 
from our main page, the linkchecker job lands directly at 
[https://hbase.apache.org/0.94/] which has around 90 odd missing file issues. I 
haven't yet looked at the missing anchors stuff yet.

We can set linkchecker to not check 0.94.



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


[jira] [Created] (HBASE-21803) HBase website cleanup

2019-01-29 Thread Sakthi (JIRA)
Sakthi created HBASE-21803:
--

 Summary: HBase website cleanup
 Key: HBASE-21803
 URL: https://issues.apache.org/jira/browse/HBASE-21803
 Project: HBase
  Issue Type: Umbrella
  Components: website
Reporter: Sakthi
Assignee: Sakthi


This umbrella is to track the HBase website cleanup. The last Linkchecker 
job(which was run on 25th jan (takes approximately 20+ hours to finish)) has 
reported "1458 missing files" and "7143 missing named anchors". Have filed this 
Jira to track several sub-jiras that might follow.

 
{code:java}
Index of Linklint results 
Sat, 26-Jan-2019 05:04:24 (local)
Linklint version: 2.3.5_ingo_020
  summary.txt: summary of results
  log.txt: log of progress
file.html: found 51187 files
   fileX.html: found 51187 files (cross referenced)
   fileF.html: found 51051 files with forward links
  remote.html: found 3431 other links
 remoteX.html: found 3431 other links (cross referenced)
  anchor.html: found 21525313 named anchors
 anchorX.html: found 21525313 named anchors (cross referenced)
  action.html: -   1 action skipped
 actionX.html: -   1 action skipped (cross referenced)
 skipped.html: -   2 files skipped
   skipX.html: -   2 files skipped (cross referenced)
warn.html: warn  696 warnings
   warnX.html: warn  696 warnings (cross referenced)
   warnF.html: warn  253 files with warnings
   error.html: ERROR 1458 missing files
  errorX.html: ERROR 1458 missing files (cross referenced)
  errorF.html: ERROR 1417 files had broken links
  errorA.html: ERROR 7145 missing named anchors
 errorAX.html: ERROR 7145 missing named anchors (cross referenced)
httpfail.html: - 1458 links: failed via http
  httpok.html: - 51187 links: ok via http
  mapped.html: -   4 links were mapped
urlindex.html: results for remote urls
{code}



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


[jira] [Reopened] (HBASE-21775) The BufferedMutator doesn't ever refresh region location cache

2019-01-29 Thread Duo Zhang (JIRA)


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

Duo Zhang reopened HBASE-21775:
---

This breaks TestAsyncProcess, please try to fix it. Plan release 2.1.3 and 
2.0.5 because of a security issues so please be quick, otherwise will revert 
from at least branch-2.1 and branch-2.0.

Thanks.

> The BufferedMutator doesn't ever refresh region location cache
> --
>
> Key: HBASE-21775
> URL: https://issues.apache.org/jira/browse/HBASE-21775
> Project: HBase
>  Issue Type: Bug
>  Components: Client
>Reporter: Tommy Li
>Assignee: Tommy Li
>Priority: Major
> Fix For: 3.0.0, 1.5.0, 2.2.0, 1.4.10, 2.1.3, 2.0.5, 1.3.4
>
> Attachments: HBASE-21775.master.001.patch
>
>
> {color:#22}I noticed in some of my writing jobs that the BufferedMutator 
> would get stuck retrying writes against a dead server.{color}
> {code:java}
> 19/01/18 15:15:47 INFO [Executor task launch worker for task 0] 
> client.AsyncRequestFutureImpl: #2, waiting for 1  actions to finish on table: 
> dummy_table
> 19/01/18 15:15:54 WARN [htable-pool3-t56] client.AsyncRequestFutureImpl: 
> id=2, table=dummy_table, attempt=15/21, failureCount=1ops, last 
> exception=org.apache.hadoop.hbase.DoNotRetryIOException: Operation rpcTimeout 
> on ,17020,1547848193782, tracking started Fri Jan 18 14:55:37 PST 
> 2019; NOT retrying, failed=1 -- final attempt!
> 19/01/18 15:15:54 ERROR [Executor task launch worker for task 0] 
> IngestRawData.map(): [B@258bc2c7: 
> org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1 
> action: Operation rpcTimeout: 1 time, servers with issues: 
> ,17020,1547848193782
> {code}
>  
> After the single remaining action permanently failed, it would resume 
> progress only to get stuck again retrying against the same dead server:
> {code:java}
> 19/01/18 15:21:18 INFO [Executor task launch worker for task 0] 
> client.AsyncRequestFutureImpl: #2, waiting for 1  actions to finish on table: 
> dummy_table
> 19/01/18 15:21:18 INFO [Executor task launch worker for task 0] 
> client.AsyncRequestFutureImpl: #2, waiting for 1  actions to finish on table: 
> dummy_table
> 19/01/18 15:21:20 INFO [htable-pool3-t55] client.AsyncRequestFutureImpl: 
> id=2, table=dummy_table, attempt=6/21, failureCount=1ops, last 
> exception=java.net.ConnectException: Call to  failed on connection 
> exception: 
> org.apache.hbase.thirdparty.io.netty.channel.ConnectTimeoutException: 
> connection timed out:  on ,17020,1547848193782, tracking 
> started null, retrying after=20089ms, operationsToReplay=1
> {code}
>  
> Only restarting the client process to generate a new BufferedMutator instance 
> would fix the issue, at least until the next regionserver crash
>  The logs I've pasted show the issue happening with a 
> ConnectionTimeoutException, but we've also seen it with 
> NotServingRegionException and some others



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


[jira] [Created] (HBASE-21802) Release 2.0.5

2019-01-29 Thread Duo Zhang (JIRA)
Duo Zhang created HBASE-21802:
-

 Summary: Release 2.0.5
 Key: HBASE-21802
 URL: https://issues.apache.org/jira/browse/HBASE-21802
 Project: HBase
  Issue Type: Umbrella
Reporter: Duo Zhang






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


[jira] [Created] (HBASE-21801) Release 2.1.3

2019-01-29 Thread Duo Zhang (JIRA)
Duo Zhang created HBASE-21801:
-

 Summary: Release 2.1.3
 Key: HBASE-21801
 URL: https://issues.apache.org/jira/browse/HBASE-21801
 Project: HBase
  Issue Type: Umbrella
Reporter: Duo Zhang






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