[
https://issues.apache.org/jira/browse/HBASE-14659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Heng Chen resolved HBASE-14659.
---
Resolution: Won't Fix
> Fix flakey TestHFileOutputFormat
>
>
>
I just profiled trunk running YCSB workload A. I was looking for something
else but found completely unexpected results.
I see 60% of all allocation pressure in TLABs coming from
ProcedureExecutors, allocating 16 GB of
java.util.AbstractMap$SimpleImmutableEntry in this code:
Stack Trace TLABs
> In particular, can we end the passes-locally-for-me practice
+1
Although this depends on the sanity and stability of precommit builds. We (at
least I) resorted to posting locally sourced "proof" of clean test suite runs
to make forward progress in the limited amount of time I had to work on
No toes stepped to be sure; the cadence must be maintained. I don't know if
14712 has been observed on 1.1, but IIRC the procV2 code should be
identical as on 1.2. How about this: I will plan to spin bits this weekend
(likely Sunday afternoon Pacific), whether 14712 is in or not. Hopefully
in, but
Thanks so much for banging on our tests and builds.a.o setup such that some
sanity there has now been restored!
> Hanging tests have been fixed and or disabled to be put back after scrubbing.
What do you think about an interim step that adds a flakey test category and a
profile that disables
Huge kudos to you, Stack, for making the time to run these down.
As a contributor, I'm very moved by the thought of treating what Jenkins
reports as truth.
Stack wrote:
Since I wrote the below, we've figured who the surefire-killer was
[HBASE-14589]. 9 of the last 10 1.2 builds passed (even
You are looking at master process only?
I've been looking at branch-1 only of late.
St.Ack
On Thu, Nov 5, 2015 at 12:06 AM, Andrew Purtell wrote:
> I just profiled trunk running YCSB workload A. I was looking for something
> else but found completely unexpected results.
>
what operation do you have going on the HMaster?
I did a simple test where there are no operation going on and poll doesn't
get out of the waitCond.await()
so unless you have operations on the master you'll never call queue.poll()
or maybe, there's a bug and the previous ops where hanging and
stack created HBASE-14772:
-
Summary: Improve zombie detector; be more discerning
Key: HBASE-14772
URL: https://issues.apache.org/jira/browse/HBASE-14772
Project: HBase
Issue Type: Sub-task
let me take a look, but branch-1 and master should be the same on the proc
stuff
Matteo
On Thu, Nov 5, 2015 at 10:23 AM, Stack wrote:
> You are looking at master process only?
>
> I've been looking at branch-1 only of late.
>
> St.Ack
>
> On Thu, Nov 5, 2015 at 12:06 AM,
If Maven has trouble grabbing a pom but not an artifact, it'll
substitute in a placeholder pom that doesn't have e.g. license
information. That can result in a local repo that fails this way until
the refresh timeout hits for grabbing a pom again.
On Wed, Nov 4, 2015 at 5:33 PM, Stack
On Thu, Nov 5, 2015 at 8:07 AM, Andrew Purtell
wrote:
> > Hanging tests have been fixed and or disabled to be put back after
> scrubbing.
>
> What do you think about an interim step that adds a flakey test category
> and a profile that disables them only on builds.a.o.,
Elliott Clark created HBASE-14773:
-
Summary: Fix HBase shell tests are skipped when skipping server
tests.
Key: HBASE-14773
URL: https://issues.apache.org/jira/browse/HBASE-14773
Project: HBase
Hi HBase contributors,
The Hadoop community is considering adding Gerrit as a review / commit
tool. Since this will require support from the Apache Infra team, it makes
more sense if multiple projects can benefit from the effort.
The main benefit of Gerrit over ReviewBoard is better integration
[
https://issues.apache.org/jira/browse/HBASE-14773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark resolved HBASE-14773.
---
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 1.3.0
Gary Helmling created HBASE-14775:
-
Summary: Replication can't authenticate with peer Zookeeper with
different server principal
Key: HBASE-14775
URL: https://issues.apache.org/jira/browse/HBASE-14775
Misty Stanley-Jones created HBASE-14776:
---
Summary: Rewrite smart-patch.sh to use 'git am' or 'git apply'
rather than 'patch'
Key: HBASE-14776
URL: https://issues.apache.org/jira/browse/HBASE-14776
Misty Stanley-Jones created HBASE-14774:
---
Summary: Raise the font size on high-DPI small-screen devices like
iphone 6+
Key: HBASE-14774
URL: https://issues.apache.org/jira/browse/HBASE-14774
+1, perhaps we can set up an autocommit workflow that only commits after
code review and a successful precommit build. This would automate much of
our community best practice.
On Thu, Nov 5, 2015 at 6:56 PM, Colin P. McCabe wrote:
> +1. Gerrit sounds great... definitely
No that sounds good Nick. Thanks for that.
On Thu, Nov 5, 2015 at 9:01 AM, Nick Dimiduk wrote:
> No toes stepped to be sure; the cadence must be maintained. I don't know if
> 14712 has been observed on 1.1, but IIRC the procV2 code should be
> identical as on 1.2. How
On Thu, Nov 5, 2015 at 12:18 PM, Matteo Bertozzi
wrote:
> what is the shutdown and restart? a clean stop? kill?
>
The shutdown of a ^C of the minicluster as launched out of the dev tree.
The termination looked normal to be but I did see the SSH handler kick in
upon
It was definitely something to do with SSH. I was able to reproduce, then
ran through this again but manually cleared away all files in WALs/* after
shutdown, and then the profile was what I'd expect.
On Thu, Nov 5, 2015 at 8:41 PM, Andrew Purtell wrote:
>
>
> On Thu, Nov
Hi Zhe,
This is promising! One question: is it possible to enfore fast-forward
only commits when pushing upstream via the web UI? A history full of merge
commits is not very palatable from our community perspective.
Thanks,
Nick
On Thursday, November 5, 2015, Zhe Zhang wrote:
+1. Gerrit sounds great... definitely better than the old "attach a
patch" workflow. I think it's worth trying out.
On Thu, Nov 5, 2015 at 6:38 PM, Nick Dimiduk wrote:
> Hi Zhe,
>
> This is promising! One question: is it possible to enfore fast-forward
> only commits when
>
> One question: is it possible to enfore fast-forward only commits when
> pushing upstream via the web UI? A history full of merge
> commits is not very palatable from our community perspective.
Thanks for the question Nick. Yes Gerrit can be configured to allow only
fast-forward commits
Rocking effort Stack!!! Thanks.
Regards
Ram
On Fri, Nov 6, 2015 at 1:40 AM, Stack wrote:
> On Thu, Nov 5, 2015 at 8:07 AM, Andrew Purtell
> wrote:
>
> > > Hanging tests have been fixed and or disabled to be put back after
> > scrubbing.
> >
> >
Abhishek Kumar created HBASE-14771:
--
Summary: RpcServer.getRemoteAddress always returns null.
Key: HBASE-14771
URL: https://issues.apache.org/jira/browse/HBASE-14771
Project: HBase
Issue
27 matches
Mail list logo