[jira] [Created] (HBASE-17053) Remove LogRollerExitedChecker

2016-11-08 Thread Duo Zhang (JIRA)
Duo Zhang created HBASE-17053:
-

 Summary: Remove LogRollerExitedChecker
 Key: HBASE-17053
 URL: https://issues.apache.org/jira/browse/HBASE-17053
 Project: HBase
  Issue Type: Sub-task
  Components: wal
Affects Versions: 2.0.0
Reporter: Duo Zhang
Assignee: Duo Zhang
 Fix For: 2.0.0


Now the LogRoll may exit before WAL exit but we will still write some close 
event to WAL when shutting down RS. And for AsyncFSWAL, we will open a new wal 
writer when error occur. If LogRoller has already exited then AsyncFSWAL will 
wait for ever and cause RS to hang.

It does not make sense to quit LogRoller ahead of WAL, this jira aims to change 
the shutdown order.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (HBASE-17052) compile-protobuf profile does not compile protobufs in some modules anymore

2016-11-08 Thread Enis Soztutar (JIRA)
Enis Soztutar created HBASE-17052:
-

 Summary: compile-protobuf profile does not compile protobufs in 
some modules anymore
 Key: HBASE-17052
 URL: https://issues.apache.org/jira/browse/HBASE-17052
 Project: HBase
  Issue Type: Bug
Reporter: Enis Soztutar
Assignee: Enis Soztutar
 Fix For: 2.0.0


Due to recent changes, we are not compiling the protobuf files in 
hbase-endpoint, hbase-rsgroup, etc anymore. 

{code}
[INFO] --- protobuf-maven-plugin:0.5.0:compile (compile-protoc) @ hbase-rsgroup 
---
[INFO] 
/Users/enis/projects/hbase-sal/hbase-rsgroup/src/main/protobuf/,/Users/enis/projects/hbase-sal/hbase-rsgroup/../hbase-protocol/src/main/protobuf
 does not exist. Review the configuration or consider disabling the plugin.
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (HBASE-17035) Check why we roll a wal writer at 10MB when the configured roll size is 120M+ with AsyncFSWAL

2016-11-08 Thread Duo Zhang (JIRA)

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

Duo Zhang resolved HBASE-17035.
---
Resolution: Fixed

Fixed by HBASE-17021.

> Check why we roll a wal writer at 10MB when the configured roll size is 120M+ 
> with AsyncFSWAL
> -
>
> Key: HBASE-17035
> URL: https://issues.apache.org/jira/browse/HBASE-17035
> Project: HBase
>  Issue Type: Sub-task
>  Components: wal
>Affects Versions: 2.0.0
>Reporter: Duo Zhang
>Assignee: Duo Zhang
> Fix For: 2.0.0
>
>
> Found this when addressing HBASE-16890. It is one of the possible reason that 
> why AsyncFSWAL performs worse than FSHLog when running PE tool.
> https://issues.apache.org/jira/browse/HBASE-16890?focusedCommentId=15636688=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15636688



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: [NOTICE] breaking precommit checks

2016-11-08 Thread Sean Busbey
Should be all set now.

On Tue, Nov 8, 2016 at 6:00 PM, Sean Busbey  wrote:
> Hi folks!
>
> some of our precommit checks are currently timing out due to an update
> to our job configs (the timeout is currently set to 50 minutes).
>
> I'm in the process of giving things more time based on our historic
> usage, but if your check fails in the mean time and
>
> 1) the total run time is close to 50 minutes
>
> 2) the jenkins job when you click through shows status "aborted"
>
> then please resubmit your patch.
>
> --
> busbey



-- 
busbey


[NOTICE] breaking precommit checks

2016-11-08 Thread Sean Busbey
Hi folks!

some of our precommit checks are currently timing out due to an update
to our job configs (the timeout is currently set to 50 minutes).

I'm in the process of giving things more time based on our historic
usage, but if your check fails in the mean time and

1) the total run time is close to 50 minutes

2) the jenkins job when you click through shows status "aborted"

then please resubmit your patch.

-- 
busbey


[jira] [Created] (HBASE-17051) libhbase++: implement RPC connection management

2016-11-08 Thread Xiaobing Zhou (JIRA)
Xiaobing Zhou created HBASE-17051:
-

 Summary: libhbase++: implement RPC connection management
 Key: HBASE-17051
 URL: https://issues.apache.org/jira/browse/HBASE-17051
 Project: HBase
  Issue Type: Sub-task
Reporter: Xiaobing Zhou
Assignee: Xiaobing Zhou






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Reopened] (HBASE-14955) OOME: cannot create native thread is back

2016-11-08 Thread stack (JIRA)

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

stack reopened HBASE-14955:
---

Reopening to try against master branch... try and keep the two branches the 
same (as suggested by [~Apache9])

> OOME: cannot create native thread is back
> -
>
> Key: HBASE-14955
> URL: https://issues.apache.org/jira/browse/HBASE-14955
> Project: HBase
>  Issue Type: Sub-task
>  Components: test
>Reporter: stack
>Assignee: Heng Chen
> Fix For: 1.3.0
>
> Attachments: HBASE-14955-branch-1.patch
>
>
> This fail is OOME cannot create native thread.  Two MR jobs fail:
>  
> org.apache.hadoop.hbase.mapreduce.TestImportTSVWithVisibilityLabels.org.apache.hadoop.hbase.mapreduce.TestImportTSVWithVisibilityLabels46
>  ms1 
> org.apache.hadoop.hbase.mapreduce.TestTableInputFormatScan1.org.apache.hadoop.hbase.mapreduce.TestTableInputFormatScan142
>  ms1
> Was running 1.3 tests on H0.
> Could try and purge resources used by these tests.
> Making issue in meantime to keep an eye on it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: Update apache cli version from 1.2 to 1.3.1?

2016-11-08 Thread Sean Busbey
Sounds good to me then.

On Tue, Nov 8, 2016 at 1:59 AM, Apekshit Sharma  wrote:
> It's for 2.0. The work am planning to do, using apache cli in our tools,
> will be in master only to avoid compatibility issues.
>
> On Mon, Oct 31, 2016 at 8:37 PM, Sean Busbey  wrote:
>
>> update for which version(s) of HBase?
>>
>> On Mon, Oct 31, 2016 at 6:31 PM, Apekshit Sharma  wrote:
>> > 1.3 came out in 2015,  6 years  after 1.2. It was few bug fixes and new
>> > features.
>> >
>> > These are few good/important ones:
>> > - HelpFormatter now prints command-line options in the same order as they
>> > have been added. Fixes CLI-212.
>> > - Standard help text now shows mandatory arguments also for the first
>> > option. Fixes CLI-186.
>> > - A new parser is available: DefaultParser. It combines the features of
>> the
>> > GnuParser and the PosixParser. It also provides additional features like
>> > partial matching for the long options, and long options without separator
>> > (i.e like the JVM memory settings: -Xmx512m). This new parser deprecates
>> > the previous ones. Fixes CLI-161,CLI-167,CLI-181.
>> >
>> > For full list of changes:
>> > https://commons.apache.org/proper/commons-cli/changes-report.html#a1.3
>> >
>> > If there are no objections, i'll update it in few days.
>> >
>> > Regards,
>> > -- Appy
>>
>
>
>
> --
>
> -- Appy



-- 
busbey


[jira] [Created] (HBASE-17049) Find out why AsyncFSWAL issues much more syncs than FSHLog

2016-11-08 Thread Duo Zhang (JIRA)
Duo Zhang created HBASE-17049:
-

 Summary: Find out why AsyncFSWAL issues much more syncs than FSHLog
 Key: HBASE-17049
 URL: https://issues.apache.org/jira/browse/HBASE-17049
 Project: HBase
  Issue Type: Sub-task
  Components: wal
Affects Versions: 2.0.0
Reporter: Duo Zhang
 Fix For: 2.0.0


https://issues.apache.org/jira/browse/HBASE-16890?focusedCommentId=15647590=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15647590



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (HBASE-17048) Introduce a helper class to calcuate suitable ByteBuf size when allocating send buffer in FanOutOneBlockAsyncDFSOutputHelper

2016-11-08 Thread Duo Zhang (JIRA)
Duo Zhang created HBASE-17048:
-

 Summary: Introduce a helper class to calcuate suitable ByteBuf 
size when allocating send buffer in FanOutOneBlockAsyncDFSOutputHelper
 Key: HBASE-17048
 URL: https://issues.apache.org/jira/browse/HBASE-17048
 Project: HBase
  Issue Type: Sub-task
  Components: wal
Affects Versions: 2.0.0
Reporter: Duo Zhang
 Fix For: 2.0.0


As [~ram_krish] mentioned in HBASE-17021

https://issues.apache.org/jira/browse/HBASE-17021?focusedCommentId=15646938=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15646938

The default ByteBuf size is 256B which is too small.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: Update apache cli version from 1.2 to 1.3.1?

2016-11-08 Thread Apekshit Sharma
It's for 2.0. The work am planning to do, using apache cli in our tools,
will be in master only to avoid compatibility issues.

On Mon, Oct 31, 2016 at 8:37 PM, Sean Busbey  wrote:

> update for which version(s) of HBase?
>
> On Mon, Oct 31, 2016 at 6:31 PM, Apekshit Sharma  wrote:
> > 1.3 came out in 2015,  6 years  after 1.2. It was few bug fixes and new
> > features.
> >
> > These are few good/important ones:
> > - HelpFormatter now prints command-line options in the same order as they
> > have been added. Fixes CLI-212.
> > - Standard help text now shows mandatory arguments also for the first
> > option. Fixes CLI-186.
> > - A new parser is available: DefaultParser. It combines the features of
> the
> > GnuParser and the PosixParser. It also provides additional features like
> > partial matching for the long options, and long options without separator
> > (i.e like the JVM memory settings: -Xmx512m). This new parser deprecates
> > the previous ones. Fixes CLI-161,CLI-167,CLI-181.
> >
> > For full list of changes:
> > https://commons.apache.org/proper/commons-cli/changes-report.html#a1.3
> >
> > If there are no objections, i'll update it in few days.
> >
> > Regards,
> > -- Appy
>



-- 

-- Appy