Mingliang Liu created HADOOP-13470:
--
Summary: GenericTestUtils$LogCapturer is flaky
Key: HADOOP-13470
URL: https://issues.apache.org/jira/browse/HADOOP-13470
Project: Hadoop Common
Issue Typ
Rakesh R created HADOOP-13469:
-
Summary: Fix
TestRefreshUserMappings.testRefreshSuperUserGroupsConfiguration test failure
Key: HADOOP-13469
URL: https://issues.apache.org/jira/browse/HADOOP-13469
Project:
On Thu, Aug 4, 2016 at 11:20 AM, Andrew Wang
wrote:
> Hi Konst, thanks for commenting,
>
> On Wed, Aug 3, 2016 at 11:29 PM, Konstantin Shvachko > wrote:
>
>> 1. I probably missed something but I didn't get it how "alpha"s made
>> their way into release numbers again. This was discussed on severa
Hi Team, Pls check this and let me your comment(s) ..
--Senthil
On Aug 4, 2016 7:22 PM, "Senthil Kumar" wrote:
> Hi Team ,
>
>
> Current HDFS NFS gateway Supports exporting only one Directory..
>
> Example :
>
> nfs.export.point
> /user
>
>
> This property helps us to export particular direct
> I'm certainly open to alternate proposals for versioning and fix versions,
> but to reiterate, I like this versioning since it imitates other enterprise
> software. RHEL has versions like 6.2 Beta 2 and 7.0 Beta, so versions like
> 3.0.0-alpha1 will be immediately familiar to end users. Conversel
Could a YARN person please comment on these two issues, one of which Vinay
also hit? If someone already triaged or filed JIRAs, I missed it.
On Mon, Jul 25, 2016 at 11:52 AM, Andrew Wang
wrote:
> I'll also add that, as a YARN newbie, I did hit two usability issues.
> These are very unlikely to b
On Thu, Aug 4, 2016 at 12:41 PM, Chris Douglas wrote:
> I agree with Konst. The virtues of branching (instead of releasing
> from trunk) and using the version suffix for the 3.x releases are lost
> on me. Both introduce opportunities for error, in commits, in
> consistent JIRA tagging, in packagi
On Fri, Aug 5, 2016 at 7:52 AM, Sean Busbey wrote:
> On Thu, Aug 4, 2016 at 4:16 PM, Gav wrote:
> >
> >
> > On Fri, Aug 5, 2016 at 3:14 AM, Sean Busbey wrote:
> >>
> >> > Why? yahoo-not-h2 is really not required since H2 is the same as all
> the
> >> > other H* nodes.
> >>
> >> The yahoo-not-h2
[
https://issues.apache.org/jira/browse/HADOOP-13119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey E Rodriguez resolved HADOOP-13119.
---
Resolution: Invalid
Release Note: This Jira should have been a HDFS Jir
On Thu, Aug 4, 2016 at 4:16 PM, Gav wrote:
>
>
> On Fri, Aug 5, 2016 at 3:14 AM, Sean Busbey wrote:
>>
>> > Why? yahoo-not-h2 is really not required since H2 is the same as all the
>> > other H* nodes.
>>
>> The yahoo-not-h2 label exists because the H2 node was misconfigured
>> for a long time an
On Fri, Aug 5, 2016 at 7:28 AM, Andrew Bayer wrote:
> fwiw, I think the docker label should remain - the Rackspace dynamically
> provisioned agents, for example, are too small to really be a good option
> for most, if not all, jobs that use Docker. *shrug*
>
Too small how? Disk space, RAM, CPU,
fwiw, I think the docker label should remain - the Rackspace dynamically
provisioned agents, for example, are too small to really be a good option
for most, if not all, jobs that use Docker. *shrug*
Alternatively, a label that distinguishes between the-same-in-configuration
physical vs non-physica
On Fri, Aug 5, 2016 at 3:14 AM, Sean Busbey wrote:
> > Why? yahoo-not-h2 is really not required since H2 is the same as all the
> other H* nodes.
>
> The yahoo-not-h2 label exists because the H2 node was misconfigured
> for a long time and would fail builds as a result.
Yes I know, but now its
I agree with Konst. The virtues of branching (instead of releasing
from trunk) and using the version suffix for the 3.x releases are lost
on me. Both introduce opportunities for error, in commits, in
consistent JIRA tagging, in packaging...
We can mark stability on the website. If someone builds a
Hi Konst, thanks for commenting,
On Wed, Aug 3, 2016 at 11:29 PM, Konstantin Shvachko
wrote:
> 1. I probably missed something but I didn't get it how "alpha"s made their
> way into release numbers again. This was discussed on several occasions and
> I thought the common perception was to use jus
Karthik Palanisamy created HADOOP-13468:
---
Summary: In HA, Namenode is failed to start If any of the Quorum
hostname is unresolved
Key: HADOOP-13468
URL: https://issues.apache.org/jira/browse/HADOOP-13468
> Why? yahoo-not-h2 is really not required since H2 is the same as all the
> other H* nodes.
The yahoo-not-h2 label exists because the H2 node was misconfigured
for a long time and would fail builds as a result. What label will
jobs taht are currently configured to avoid H2 be migrated to? Will
t
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/123/
[Aug 3, 2016 2:31:49 PM] (kihwal) HADOOP-13426. More efficiently build IPC
responses. Contributed by Daryn
[Aug 3, 2016 4:53:41 PM] (kihwal) HDFS-10656. Optimize conversion of byte
arrays back to path stri
Hi All,
Following on from my earlier mails regarding Java, Maven and Ant
consolidations, I thought
you might like a page detailing the Jenkins Labels and which nodes they
belong to.
I've put it up here :-
https://cwiki.apache.org/confluence/display/INFRA/Jenkins+node+labels
I hope you find it u
19 matches
Mail list logo
