[jira] [Created] (HDFS-6951) Saving namespace and restarting NameNode will remove existing encryption zones

2014-08-26 Thread Stephen Chu (JIRA) 
Stephen Chu created HDFS-6951:
-

 Summary: Saving namespace and restarting NameNode will remove 
existing encryption zones
 Key: HDFS-6951
 URL: https://issues.apache.org/jira/browse/HDFS-6951
 Project: Hadoop HDFS
  Issue Type: Sub-task
  Components: encryption
Affects Versions: 3.0.0
Reporter: Stephen Chu
 Fix For: 3.0.0
 Attachments: HDFS-6951-testrepo.patch

Currently, when users save namespace and restart the NameNode, pre-existing 
encryption zones will be wiped out.

To reproduce:
* Create an encryption zone
* List encryption zones and verify the newly created zone is present
* Save the namespace
* Kill and restart the NameNode
* List the encryption zones and you'll find the encryption zone is missing

I've attached a test case for {{TestEncryptionZones}} that reproduces this as 
well. Removing the saveNamespace call will get the test to pass.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: Updates on migration to git

2014-08-26 Thread Karthik Kambatla 
Yes, we have requested for force-push disabled on trunk and branch-*
branches. I didn't test it though :P, it is not writable yet.


On Tue, Aug 26, 2014 at 5:48 PM, Todd Lipcon  wrote:

> Hey Karthik,
>
> Just to confirm, have we disabled force-push support on the repo?
>
> In my experience, especially when a project has committers new to git,
> force-push support causes more trouble than it's worth.
>
> -Todd
>
>
> On Tue, Aug 26, 2014 at 4:39 PM, Karthik Kambatla 
> wrote:
>
> > Looks like our git repo is good to go.
> >
> > On INFRA-8195, I am asking Daniel to enable writing to it. In case you
> find
> > any issues, please comment on the JIRA.
> >
> > Thanks
> > Karthik
> >
> >
> > On Tue, Aug 26, 2014 at 3:28 PM, Arpit Agarwal  >
> > wrote:
> >
> > > I cloned the new repo, built trunk and branch-2, verified all the
> > branches
> > > are present. Also checked a few branches and the recent commit history
> > > matches our existing repo. Everything looks good so far.
> > >
> > >
> > > On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla 
> > > wrote:
> > >
> > > > The git repository is now ready for inspection. I ll take a look
> > shortly,
> > > > but it would be great if a few others could too.
> > > >
> > > > Once we are okay with it, we can ask it to be writable.
> > > >
> > > > On Tuesday, August 26, 2014, Karthik Kambatla 
> > > wrote:
> > > >
> > > > > Hi Suresh
> > > > >
> > > > > There was one vote thread on whether to migrate to git, and the
> > > > > implications to the commit process for individual patches and
> feature
> > > > > branches -
> > > > >
> > >
> https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html
> > > > .
> > > > > Prior to that, there was a discuss thread on the same topic.
> > > > >
> > > > > As INFRA handles the actual migration from subversion to git, the
> > vote
> > > > > didn't include those specifics. The migration is going on as we
> speak
> > > > (See
> > > > > INFRA-8195). The initial expectation was that the migration would
> be
> > > done
> > > > > in a few hours, but it has been several hours and the last I heard
> > the
> > > > > import was still running.
> > > > >
> > > > > I have elaborated on the points in the vote thread and drafted up a
> > > wiki
> > > > > page on how-to-commit -
> > > > https://wiki.apache.org/hadoop/HowToCommitWithGit
> > > > > . We can work on improving this further and call a vote thread on
> > those
> > > > > items if need be.
> > > > >
> > > > > Thanks
> > > > > Karthik
> > > > >
> > > > >
> > > > > On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas <
> > > > sur...@hortonworks.com
> > > > > > wrote:
> > > > >
> > > > >> Karthik,
> > > > >>
> > > > >> I would like to see detailed information on how this migration
> will
> > be
> > > > >> done, how it will affect the existing project and commit process.
> > This
> > > > >> should be done in a document that can be reviewed instead of in an
> > > email
> > > > >> thread on an ad-hoc basis. Was there any voting on this in PMC and
> > > > should
> > > > >> we have a vote to ensure everyone is one the same page on doing
> this
> > > and
> > > > >> how to go about it?
> > > > >>
> > > > >> Regards,
> > > > >> Suresh
> > > > >>
> > > > >>
> > > > >> On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla <
> > ka...@cloudera.com
> > > > >> >
> > > > >> wrote:
> > > > >>
> > > > >> > Last I heard, the import is still going on and appears closer to
> > > > getting
> > > > >> > done. Thanks for your patience with the migration.
> > > > >> >
> > > > >> > I ll update you as and when there is something. Eventually, the
> > git
> > > > repo
> > > > >> > should be at the location in the wiki.
> > > > >> >
> > > > >> >
> > > > >> > On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla <
> > > ka...@cloudera.com
> > > > >> >
> > > > >> > wrote:
> > > > >> >
> > > > >> > > Thanks for bringing these points up, Zhijie.
> > > > >> > >
> > > > >> > > By the way, a revised How-to-commit wiki is at:
> > > > >> > > https://wiki.apache.org/hadoop/HowToCommitWithGit . Please
> feel
> > > > free
> > > > >> to
> > > > >> > > make changes and improve it.
> > > > >> > >
> > > > >> > > On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen <
> > > > zs...@hortonworks.com
> > > > >> >
> > > > >> > > wrote:
> > > > >> > >
> > > > >> > >> Do we have any convention about "user.name" and
> "user.email"?
> > > For
> > > > >> > >> example,
> > > > >> > >> we'd like to use @apache.org for the email.
> > > > >> > >>
> > > > >> > >
> > > > >> > > May be, we can ask people to use project-specific configs here
> > and
> > > > use
> > > > >> > > their real name and @apache.org address.
> > > > >> > >
> > > > >> > > Is there any downside to letting people use their global
> values
> > > for
> > > > >> these
> > > > >> > > configs?
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > > >> > >>
> > > > >> > >> Moreover, do we want to use "--author="Author Name <
> > > > >> em...@address.com  > > ');>>"
> > > > >> > >> when committing on

Re: Updates on migration to git

2014-08-26 Thread Todd Lipcon 
Hey Karthik,

Just to confirm, have we disabled force-push support on the repo?

In my experience, especially when a project has committers new to git,
force-push support causes more trouble than it's worth.

-Todd


On Tue, Aug 26, 2014 at 4:39 PM, Karthik Kambatla 
wrote:

> Looks like our git repo is good to go.
>
> On INFRA-8195, I am asking Daniel to enable writing to it. In case you find
> any issues, please comment on the JIRA.
>
> Thanks
> Karthik
>
>
> On Tue, Aug 26, 2014 at 3:28 PM, Arpit Agarwal 
> wrote:
>
> > I cloned the new repo, built trunk and branch-2, verified all the
> branches
> > are present. Also checked a few branches and the recent commit history
> > matches our existing repo. Everything looks good so far.
> >
> >
> > On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla 
> > wrote:
> >
> > > The git repository is now ready for inspection. I ll take a look
> shortly,
> > > but it would be great if a few others could too.
> > >
> > > Once we are okay with it, we can ask it to be writable.
> > >
> > > On Tuesday, August 26, 2014, Karthik Kambatla 
> > wrote:
> > >
> > > > Hi Suresh
> > > >
> > > > There was one vote thread on whether to migrate to git, and the
> > > > implications to the commit process for individual patches and feature
> > > > branches -
> > > >
> > https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html
> > > .
> > > > Prior to that, there was a discuss thread on the same topic.
> > > >
> > > > As INFRA handles the actual migration from subversion to git, the
> vote
> > > > didn't include those specifics. The migration is going on as we speak
> > > (See
> > > > INFRA-8195). The initial expectation was that the migration would be
> > done
> > > > in a few hours, but it has been several hours and the last I heard
> the
> > > > import was still running.
> > > >
> > > > I have elaborated on the points in the vote thread and drafted up a
> > wiki
> > > > page on how-to-commit -
> > > https://wiki.apache.org/hadoop/HowToCommitWithGit
> > > > . We can work on improving this further and call a vote thread on
> those
> > > > items if need be.
> > > >
> > > > Thanks
> > > > Karthik
> > > >
> > > >
> > > > On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas <
> > > sur...@hortonworks.com
> > > > > wrote:
> > > >
> > > >> Karthik,
> > > >>
> > > >> I would like to see detailed information on how this migration will
> be
> > > >> done, how it will affect the existing project and commit process.
> This
> > > >> should be done in a document that can be reviewed instead of in an
> > email
> > > >> thread on an ad-hoc basis. Was there any voting on this in PMC and
> > > should
> > > >> we have a vote to ensure everyone is one the same page on doing this
> > and
> > > >> how to go about it?
> > > >>
> > > >> Regards,
> > > >> Suresh
> > > >>
> > > >>
> > > >> On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla <
> ka...@cloudera.com
> > > >> >
> > > >> wrote:
> > > >>
> > > >> > Last I heard, the import is still going on and appears closer to
> > > getting
> > > >> > done. Thanks for your patience with the migration.
> > > >> >
> > > >> > I ll update you as and when there is something. Eventually, the
> git
> > > repo
> > > >> > should be at the location in the wiki.
> > > >> >
> > > >> >
> > > >> > On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla <
> > ka...@cloudera.com
> > > >> >
> > > >> > wrote:
> > > >> >
> > > >> > > Thanks for bringing these points up, Zhijie.
> > > >> > >
> > > >> > > By the way, a revised How-to-commit wiki is at:
> > > >> > > https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel
> > > free
> > > >> to
> > > >> > > make changes and improve it.
> > > >> > >
> > > >> > > On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen <
> > > zs...@hortonworks.com
> > > >> >
> > > >> > > wrote:
> > > >> > >
> > > >> > >> Do we have any convention about "user.name" and "user.email"?
> > For
> > > >> > >> example,
> > > >> > >> we'd like to use @apache.org for the email.
> > > >> > >>
> > > >> > >
> > > >> > > May be, we can ask people to use project-specific configs here
> and
> > > use
> > > >> > > their real name and @apache.org address.
> > > >> > >
> > > >> > > Is there any downside to letting people use their global values
> > for
> > > >> these
> > > >> > > configs?
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > >>
> > > >> > >> Moreover, do we want to use "--author="Author Name <
> > > >> em...@address.com  > ');>>"
> > > >> > >> when committing on behalf of a particular contributor?
> > > >> > >>
> > > >> > >
> > > >> > > Fetching the email-address is complicated here. Should we use
> the
> > > >> > > contributor's email from JIRA? What if that is not their @apache
> > > >> address?
> > > >> > >
> > > >> > >
> > > >> > >>
> > > >> > >>
> > > >> > >> On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla <
> > > >> ka...@cloudera.com  > > ');>>
> > > >> > >> wrote:
> > > >> > >>
> > > >> > >> > Thanks for your input, Steve. Sorry for sending the email o

Re: Updates on migration to git

2014-08-26 Thread Karthik Kambatla 
Looks like our git repo is good to go.

On INFRA-8195, I am asking Daniel to enable writing to it. In case you find
any issues, please comment on the JIRA.

Thanks
Karthik


On Tue, Aug 26, 2014 at 3:28 PM, Arpit Agarwal 
wrote:

> I cloned the new repo, built trunk and branch-2, verified all the branches
> are present. Also checked a few branches and the recent commit history
> matches our existing repo. Everything looks good so far.
>
>
> On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla 
> wrote:
>
> > The git repository is now ready for inspection. I ll take a look shortly,
> > but it would be great if a few others could too.
> >
> > Once we are okay with it, we can ask it to be writable.
> >
> > On Tuesday, August 26, 2014, Karthik Kambatla 
> wrote:
> >
> > > Hi Suresh
> > >
> > > There was one vote thread on whether to migrate to git, and the
> > > implications to the commit process for individual patches and feature
> > > branches -
> > >
> https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html
> > .
> > > Prior to that, there was a discuss thread on the same topic.
> > >
> > > As INFRA handles the actual migration from subversion to git, the vote
> > > didn't include those specifics. The migration is going on as we speak
> > (See
> > > INFRA-8195). The initial expectation was that the migration would be
> done
> > > in a few hours, but it has been several hours and the last I heard the
> > > import was still running.
> > >
> > > I have elaborated on the points in the vote thread and drafted up a
> wiki
> > > page on how-to-commit -
> > https://wiki.apache.org/hadoop/HowToCommitWithGit
> > > . We can work on improving this further and call a vote thread on those
> > > items if need be.
> > >
> > > Thanks
> > > Karthik
> > >
> > >
> > > On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas <
> > sur...@hortonworks.com
> > > > wrote:
> > >
> > >> Karthik,
> > >>
> > >> I would like to see detailed information on how this migration will be
> > >> done, how it will affect the existing project and commit process. This
> > >> should be done in a document that can be reviewed instead of in an
> email
> > >> thread on an ad-hoc basis. Was there any voting on this in PMC and
> > should
> > >> we have a vote to ensure everyone is one the same page on doing this
> and
> > >> how to go about it?
> > >>
> > >> Regards,
> > >> Suresh
> > >>
> > >>
> > >> On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla  > >> >
> > >> wrote:
> > >>
> > >> > Last I heard, the import is still going on and appears closer to
> > getting
> > >> > done. Thanks for your patience with the migration.
> > >> >
> > >> > I ll update you as and when there is something. Eventually, the git
> > repo
> > >> > should be at the location in the wiki.
> > >> >
> > >> >
> > >> > On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla <
> ka...@cloudera.com
> > >> >
> > >> > wrote:
> > >> >
> > >> > > Thanks for bringing these points up, Zhijie.
> > >> > >
> > >> > > By the way, a revised How-to-commit wiki is at:
> > >> > > https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel
> > free
> > >> to
> > >> > > make changes and improve it.
> > >> > >
> > >> > > On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen <
> > zs...@hortonworks.com
> > >> >
> > >> > > wrote:
> > >> > >
> > >> > >> Do we have any convention about "user.name" and "user.email"?
> For
> > >> > >> example,
> > >> > >> we'd like to use @apache.org for the email.
> > >> > >>
> > >> > >
> > >> > > May be, we can ask people to use project-specific configs here and
> > use
> > >> > > their real name and @apache.org address.
> > >> > >
> > >> > > Is there any downside to letting people use their global values
> for
> > >> these
> > >> > > configs?
> > >> > >
> > >> > >
> > >> > >
> > >> > >>
> > >> > >> Moreover, do we want to use "--author="Author Name <
> > >> em...@address.com  ');>>"
> > >> > >> when committing on behalf of a particular contributor?
> > >> > >>
> > >> > >
> > >> > > Fetching the email-address is complicated here. Should we use the
> > >> > > contributor's email from JIRA? What if that is not their @apache
> > >> address?
> > >> > >
> > >> > >
> > >> > >>
> > >> > >>
> > >> > >> On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla <
> > >> ka...@cloudera.com  > ');>>
> > >> > >> wrote:
> > >> > >>
> > >> > >> > Thanks for your input, Steve. Sorry for sending the email out
> > that
> > >> > >> late, I
> > >> > >> > sent it as soon as I could.
> > >> > >> >
> > >> > >> >
> > >> > >> > On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran <
> > >> > ste...@hortonworks.com
> > >> 
> > >> > >> >
> > >> > >> > wrote:
> > >> > >> >
> > >> > >> > > just caught up with this after some offlininess...15:48 PST
> is
> > >> too
> > >> > >> late
> > >> > >> > for
> > >> > >> > > me.
> > >> > >> > >
> > >> > >> > > I'd be -1 to a change to "master" because of that risk that
> it
> > >> does
> > >> > >> break
> > >> > >> > > existing code -especially people that have trunk off the git

[jira] [Created] (HDFS-6950) Add Additional unit tests for HDFS-6581

2014-08-26 Thread Xiaoyu Yao (JIRA) 
Xiaoyu Yao created HDFS-6950:


 Summary: Add Additional unit tests for HDFS-6581
 Key: HDFS-6950
 URL: https://issues.apache.org/jira/browse/HDFS-6950
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: Xiaoyu Yao


Create additional unit tests for HDFS-6581 in addition to existing ones in 
HDFS-6927.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: Updates on migration to git

2014-08-26 Thread Arpit Agarwal 
I cloned the new repo, built trunk and branch-2, verified all the branches
are present. Also checked a few branches and the recent commit history
matches our existing repo. Everything looks good so far.


On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla 
wrote:

> The git repository is now ready for inspection. I ll take a look shortly,
> but it would be great if a few others could too.
>
> Once we are okay with it, we can ask it to be writable.
>
> On Tuesday, August 26, 2014, Karthik Kambatla  wrote:
>
> > Hi Suresh
> >
> > There was one vote thread on whether to migrate to git, and the
> > implications to the commit process for individual patches and feature
> > branches -
> > https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html
> .
> > Prior to that, there was a discuss thread on the same topic.
> >
> > As INFRA handles the actual migration from subversion to git, the vote
> > didn't include those specifics. The migration is going on as we speak
> (See
> > INFRA-8195). The initial expectation was that the migration would be done
> > in a few hours, but it has been several hours and the last I heard the
> > import was still running.
> >
> > I have elaborated on the points in the vote thread and drafted up a wiki
> > page on how-to-commit -
> https://wiki.apache.org/hadoop/HowToCommitWithGit
> > . We can work on improving this further and call a vote thread on those
> > items if need be.
> >
> > Thanks
> > Karthik
> >
> >
> > On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas <
> sur...@hortonworks.com
> > > wrote:
> >
> >> Karthik,
> >>
> >> I would like to see detailed information on how this migration will be
> >> done, how it will affect the existing project and commit process. This
> >> should be done in a document that can be reviewed instead of in an email
> >> thread on an ad-hoc basis. Was there any voting on this in PMC and
> should
> >> we have a vote to ensure everyone is one the same page on doing this and
> >> how to go about it?
> >>
> >> Regards,
> >> Suresh
> >>
> >>
> >> On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla  >> >
> >> wrote:
> >>
> >> > Last I heard, the import is still going on and appears closer to
> getting
> >> > done. Thanks for your patience with the migration.
> >> >
> >> > I ll update you as and when there is something. Eventually, the git
> repo
> >> > should be at the location in the wiki.
> >> >
> >> >
> >> > On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla  >> >
> >> > wrote:
> >> >
> >> > > Thanks for bringing these points up, Zhijie.
> >> > >
> >> > > By the way, a revised How-to-commit wiki is at:
> >> > > https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel
> free
> >> to
> >> > > make changes and improve it.
> >> > >
> >> > > On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen <
> zs...@hortonworks.com
> >> >
> >> > > wrote:
> >> > >
> >> > >> Do we have any convention about "user.name" and "user.email"? For
> >> > >> example,
> >> > >> we'd like to use @apache.org for the email.
> >> > >>
> >> > >
> >> > > May be, we can ask people to use project-specific configs here and
> use
> >> > > their real name and @apache.org address.
> >> > >
> >> > > Is there any downside to letting people use their global values for
> >> these
> >> > > configs?
> >> > >
> >> > >
> >> > >
> >> > >>
> >> > >> Moreover, do we want to use "--author="Author Name <
> >> em...@address.com >"
> >> > >> when committing on behalf of a particular contributor?
> >> > >>
> >> > >
> >> > > Fetching the email-address is complicated here. Should we use the
> >> > > contributor's email from JIRA? What if that is not their @apache
> >> address?
> >> > >
> >> > >
> >> > >>
> >> > >>
> >> > >> On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla <
> >> ka...@cloudera.com  ');>>
> >> > >> wrote:
> >> > >>
> >> > >> > Thanks for your input, Steve. Sorry for sending the email out
> that
> >> > >> late, I
> >> > >> > sent it as soon as I could.
> >> > >> >
> >> > >> >
> >> > >> > On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran <
> >> > ste...@hortonworks.com
> >> 
> >> > >> >
> >> > >> > wrote:
> >> > >> >
> >> > >> > > just caught up with this after some offlininess...15:48 PST is
> >> too
> >> > >> late
> >> > >> > for
> >> > >> > > me.
> >> > >> > >
> >> > >> > > I'd be -1 to a change to "master" because of that risk that it
> >> does
> >> > >> break
> >> > >> > > existing code -especially people that have trunk off the git
> >> mirrors
> >> > >> and
> >> > >> > > automated builds/merges to go with it.
> >> > >> > >
> >> > >> >
> >> > >> > Fair enough. It makes sense to leave it as "trunk", unless
> someone
> >> is
> >> > >> > against it being trunk.
> >> > >> >
> >> > >> >
> >> > >> > >
> >> > >> > > "master" may be viewed as the official git way, but it doesn't
> >> have
> >> > to
> >> > >> > be.
> >> > >> > > For git-flow workflows (which we use in slider) master/ is for
> >> > >> releases,
> >> > >> > > develop/ for dev.
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >>

Re: Updates on migration to git

2014-08-26 Thread Suresh Srinivas 
:) I missed that voting thread. Thanks Karthik!

Arpit Agarwal also told me offline that commit process has been updated -
https://wiki.apache.org/hadoop/HowToCommit and git setup also has also been
documented - https://www.apache.org/dev/git.html. Thanks Arpit!



On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas 
wrote:

> Karthik,
>
> I would like to see detailed information on how this migration will be
> done, how it will affect the existing project and commit process. This
> should be done in a document that can be reviewed instead of in an email
> thread on an ad-hoc basis. Was there any voting on this in PMC and should
> we have a vote to ensure everyone is one the same page on doing this and
> how to go about it?
>
> Regards,
> Suresh
>
>
> On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla 
> wrote:
>
>> Last I heard, the import is still going on and appears closer to getting
>> done. Thanks for your patience with the migration.
>>
>> I ll update you as and when there is something. Eventually, the git repo
>> should be at the location in the wiki.
>>
>>
>> On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla 
>> wrote:
>>
>> > Thanks for bringing these points up, Zhijie.
>> >
>> > By the way, a revised How-to-commit wiki is at:
>> > https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to
>> > make changes and improve it.
>> >
>> > On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen 
>> > wrote:
>> >
>> >> Do we have any convention about "user.name" and "user.email"? For
>> >> example,
>> >> we'd like to use @apache.org for the email.
>> >>
>> >
>> > May be, we can ask people to use project-specific configs here and use
>> > their real name and @apache.org address.
>> >
>> > Is there any downside to letting people use their global values for
>> these
>> > configs?
>> >
>> >
>> >
>> >>
>> >> Moreover, do we want to use "--author="Author Name > >"
>> >> when committing on behalf of a particular contributor?
>> >>
>> >
>> > Fetching the email-address is complicated here. Should we use the
>> > contributor's email from JIRA? What if that is not their @apache
>> address?
>> >
>> >
>> >>
>> >>
>> >> On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla 
>> >> wrote:
>> >>
>> >> > Thanks for your input, Steve. Sorry for sending the email out that
>> >> late, I
>> >> > sent it as soon as I could.
>> >> >
>> >> >
>> >> > On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran <
>> ste...@hortonworks.com
>> >> >
>> >> > wrote:
>> >> >
>> >> > > just caught up with this after some offlininess...15:48 PST is too
>> >> late
>> >> > for
>> >> > > me.
>> >> > >
>> >> > > I'd be -1 to a change to "master" because of that risk that it does
>> >> break
>> >> > > existing code -especially people that have trunk off the git
>> mirrors
>> >> and
>> >> > > automated builds/merges to go with it.
>> >> > >
>> >> >
>> >> > Fair enough. It makes sense to leave it as "trunk", unless someone is
>> >> > against it being trunk.
>> >> >
>> >> >
>> >> > >
>> >> > > "master" may be viewed as the official git way, but it doesn't
>> have to
>> >> > be.
>> >> > > For git-flow workflows (which we use in slider) master/ is for
>> >> releases,
>> >> > > develop/ for dev.
>> >> > >
>> >> > >
>> >> > >
>> >> > >
>> >> > > On 24 August 2014 02:31, Karthik Kambatla 
>> wrote:
>> >> > >
>> >> > > > Couple of things:
>> >> > > >
>> >> > > > 1. Since no one expressed any reservations against doing this on
>> >> Sunday
>> >> > > or
>> >> > > > renaming trunk to master, I ll go ahead and confirm that. I think
>> >> that
>> >> > > > serves us better in the long run.
>> >> > > >
>> >> > > > 2. Arpit brought up the precommit builds - we should definitely
>> fix
>> >> > them
>> >> > > as
>> >> > > > soon as we can. I understand Giri maintains those builds, do we
>> have
>> >> > > anyone
>> >> > > > else who has access in case Giri is not reachable? Giri - please
>> >> shout
>> >> > > out
>> >> > > > if you can help us with this either on Sunday or Monday.
>> >> > > >
>> >> > > > Thanks
>> >> > > > Karthik
>> >> > > >
>> >> > > >
>> >> > > >
>> >> > > >
>> >> > > > On Fri, Aug 22, 2014 at 3:50 PM, Karthik Kambatla <
>> >> ka...@cloudera.com>
>> >> > > > wrote:
>> >> > > >
>> >> > > > > Also, does anyone know what we use for integration between JIRA
>> >> and
>> >> > > svn?
>> >> > > > I
>> >> > > > > am assuming svn2jira.
>> >> > > > >
>> >> > > > >
>> >> > > > > On Fri, Aug 22, 2014 at 3:48 PM, Karthik Kambatla <
>> >> > ka...@cloudera.com>
>> >> > > > > wrote:
>> >> > > > >
>> >> > > > >> Hi folks,
>> >> > > > >>
>> >> > > > >> For the SCM migration, feel free to follow
>> >> > > > >> https://issues.apache.org/jira/browse/INFRA-8195
>> >> > > > >>
>> >> > > > >> Most of this is planned to be handled this Sunday. As a
>> result,
>> >> the
>> >> > > > >> subversion repository would be read-only. If this is a major
>> >> issue
>> >> > for
>> >> > > > you,
>> >> > > > >> please shout out.
>> >> > > > >>
>> >> > > > >> Daniel Gruno, the one helping us with t

Re: Updates on migration to git

2014-08-26 Thread Allen Wittenauer 

Did a build. Started some stuff. Have a patch ready to be committed. ;)

Thanks Karthik and Daniel!



On Aug 26, 2014, at 2:26 PM, Karthik Kambatla  wrote:

> I compared the new asf git repo against the svn and github repos (mirrored
> from svn). Here is what I see:
> - for i in *; do git diff $i ../hadoop-github/$i; done showed no
> differences between the two. So, I think all the source is there.
> - The branches match
> - All svn tags exist in git, but git has a few more. These additional ones
> are those that we "deleted" from svn.
> - git rev-list --remotes | wc -l shows 27006 revisions in the new git repo
> and 29549 revisions in the github repo. Checking with Daniel, he said the
> git svn import works differently compared to the git mirroring.
> 
> Are we comfortable with making the git repo writable under these
> conditions? I ll let other people poke around and report.
> 
> Thanks for your cooperation,
> Karthik
> 
> 
> On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla 
> wrote:
> 
>> The git repository is now ready for inspection. I ll take a look shortly,
>> but it would be great if a few others could too.
>> 
>> Once we are okay with it, we can ask it to be writable.
>> 
>> 
>> On Tuesday, August 26, 2014, Karthik Kambatla  wrote:
>> 
>>> Hi Suresh
>>> 
>>> There was one vote thread on whether to migrate to git, and the
>>> implications to the commit process for individual patches and feature
>>> branches -
>>> https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html
>>> . Prior to that, there was a discuss thread on the same topic.
>>> 
>>> As INFRA handles the actual migration from subversion to git, the vote
>>> didn't include those specifics. The migration is going on as we speak (See
>>> INFRA-8195). The initial expectation was that the migration would be done
>>> in a few hours, but it has been several hours and the last I heard the
>>> import was still running.
>>> 
>>> I have elaborated on the points in the vote thread and drafted up a wiki
>>> page on how-to-commit - https://wiki.apache.org/hadoop/HowToCommitWithGit
>>> . We can work on improving this further and call a vote thread on those
>>> items if need be.
>>> 
>>> Thanks
>>> Karthik
>>> 
>>> 
>>> On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas >>> wrote:
>>> 
 Karthik,
 
 I would like to see detailed information on how this migration will be
 done, how it will affect the existing project and commit process. This
 should be done in a document that can be reviewed instead of in an email
 thread on an ad-hoc basis. Was there any voting on this in PMC and should
 we have a vote to ensure everyone is one the same page on doing this and
 how to go about it?
 
 Regards,
 Suresh
 
 
 On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla 
 wrote:
 
> Last I heard, the import is still going on and appears closer to
 getting
> done. Thanks for your patience with the migration.
> 
> I ll update you as and when there is something. Eventually, the git
 repo
> should be at the location in the wiki.
> 
> 
> On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla 
> wrote:
> 
>> Thanks for bringing these points up, Zhijie.
>> 
>> By the way, a revised How-to-commit wiki is at:
>> https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel
 free to
>> make changes and improve it.
>> 
>> On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen  
>> wrote:
>> 
>>> Do we have any convention about "user.name" and "user.email"? For
>>> example,
>>> we'd like to use @apache.org for the email.
>>> 
>> 
>> May be, we can ask people to use project-specific configs here and
 use
>> their real name and @apache.org address.
>> 
>> Is there any downside to letting people use their global values for
 these
>> configs?
>> 
>> 
>> 
>>> 
>>> Moreover, do we want to use "--author="Author Name <
 em...@address.com>"
>>> when committing on behalf of a particular contributor?
>>> 
>> 
>> Fetching the email-address is complicated here. Should we use the
>> contributor's email from JIRA? What if that is not their @apache
 address?
>> 
>> 
>>> 
>>> 
>>> On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla <
 ka...@cloudera.com>
>>> wrote:
>>> 
 Thanks for your input, Steve. Sorry for sending the email out that
>>> late, I
 sent it as soon as I could.
 
 
 On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran <
> ste...@hortonworks.com
 
 wrote:
 
> just caught up with this after some offlininess...15:48 PST is
 too
>>> late
 for
> me.
> 
> I'd be -1 to a change to "master" because of that risk that it
 does
>>> break
> existing code -especially people that have tru

Re: Updates on migration to git

2014-08-26 Thread Alejandro Abdelnur 
I've just did some work on top of trunk and branch-2, all good.

Thanks Karthik.



On Tue, Aug 26, 2014 at 2:26 PM, Karthik Kambatla 
wrote:

> I compared the new asf git repo against the svn and github repos (mirrored
> from svn). Here is what I see:
> - for i in *; do git diff $i ../hadoop-github/$i; done showed no
> differences between the two. So, I think all the source is there.
> - The branches match
> - All svn tags exist in git, but git has a few more. These additional ones
> are those that we "deleted" from svn.
> - git rev-list --remotes | wc -l shows 27006 revisions in the new git repo
> and 29549 revisions in the github repo. Checking with Daniel, he said the
> git svn import works differently compared to the git mirroring.
>
> Are we comfortable with making the git repo writable under these
> conditions? I ll let other people poke around and report.
>
> Thanks for your cooperation,
> Karthik
>
>
> On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla 
> wrote:
>
> > The git repository is now ready for inspection. I ll take a look shortly,
> > but it would be great if a few others could too.
> >
> > Once we are okay with it, we can ask it to be writable.
> >
> >
> > On Tuesday, August 26, 2014, Karthik Kambatla 
> wrote:
> >
> >> Hi Suresh
> >>
> >> There was one vote thread on whether to migrate to git, and the
> >> implications to the commit process for individual patches and feature
> >> branches -
> >> https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html
> >> . Prior to that, there was a discuss thread on the same topic.
> >>
> >> As INFRA handles the actual migration from subversion to git, the vote
> >> didn't include those specifics. The migration is going on as we speak
> (See
> >> INFRA-8195). The initial expectation was that the migration would be
> done
> >> in a few hours, but it has been several hours and the last I heard the
> >> import was still running.
> >>
> >> I have elaborated on the points in the vote thread and drafted up a wiki
> >> page on how-to-commit -
> https://wiki.apache.org/hadoop/HowToCommitWithGit
> >> . We can work on improving this further and call a vote thread on those
> >> items if need be.
> >>
> >> Thanks
> >> Karthik
> >>
> >>
> >> On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas <
> sur...@hortonworks.com
> >> > wrote:
> >>
> >>> Karthik,
> >>>
> >>> I would like to see detailed information on how this migration will be
> >>> done, how it will affect the existing project and commit process. This
> >>> should be done in a document that can be reviewed instead of in an
> email
> >>> thread on an ad-hoc basis. Was there any voting on this in PMC and
> should
> >>> we have a vote to ensure everyone is one the same page on doing this
> and
> >>> how to go about it?
> >>>
> >>> Regards,
> >>> Suresh
> >>>
> >>>
> >>> On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla 
> >>> wrote:
> >>>
> >>> > Last I heard, the import is still going on and appears closer to
> >>> getting
> >>> > done. Thanks for your patience with the migration.
> >>> >
> >>> > I ll update you as and when there is something. Eventually, the git
> >>> repo
> >>> > should be at the location in the wiki.
> >>> >
> >>> >
> >>> > On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla <
> ka...@cloudera.com>
> >>> > wrote:
> >>> >
> >>> > > Thanks for bringing these points up, Zhijie.
> >>> > >
> >>> > > By the way, a revised How-to-commit wiki is at:
> >>> > > https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel
> >>> free to
> >>> > > make changes and improve it.
> >>> > >
> >>> > > On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen <
> zs...@hortonworks.com
> >>> >
> >>> > > wrote:
> >>> > >
> >>> > >> Do we have any convention about "user.name" and "user.email"? For
> >>> > >> example,
> >>> > >> we'd like to use @apache.org for the email.
> >>> > >>
> >>> > >
> >>> > > May be, we can ask people to use project-specific configs here and
> >>> use
> >>> > > their real name and @apache.org address.
> >>> > >
> >>> > > Is there any downside to letting people use their global values for
> >>> these
> >>> > > configs?
> >>> > >
> >>> > >
> >>> > >
> >>> > >>
> >>> > >> Moreover, do we want to use "--author="Author Name <
> >>> em...@address.com>"
> >>> > >> when committing on behalf of a particular contributor?
> >>> > >>
> >>> > >
> >>> > > Fetching the email-address is complicated here. Should we use the
> >>> > > contributor's email from JIRA? What if that is not their @apache
> >>> address?
> >>> > >
> >>> > >
> >>> > >>
> >>> > >>
> >>> > >> On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla <
> >>> ka...@cloudera.com>
> >>> > >> wrote:
> >>> > >>
> >>> > >> > Thanks for your input, Steve. Sorry for sending the email out
> that
> >>> > >> late, I
> >>> > >> > sent it as soon as I could.
> >>> > >> >
> >>> > >> >
> >>> > >> > On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran <
> >>> > ste...@hortonworks.com
> >>> > >> >
> >>> > >> > wrote:
> >>> > >> >
> >>> > >> > > just caught up

Re: Updates on migration to git

2014-08-26 Thread Karthik Kambatla 
I compared the new asf git repo against the svn and github repos (mirrored
from svn). Here is what I see:
- for i in *; do git diff $i ../hadoop-github/$i; done showed no
differences between the two. So, I think all the source is there.
- The branches match
- All svn tags exist in git, but git has a few more. These additional ones
are those that we "deleted" from svn.
- git rev-list --remotes | wc -l shows 27006 revisions in the new git repo
and 29549 revisions in the github repo. Checking with Daniel, he said the
git svn import works differently compared to the git mirroring.

Are we comfortable with making the git repo writable under these
conditions? I ll let other people poke around and report.

Thanks for your cooperation,
Karthik


On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla 
wrote:

> The git repository is now ready for inspection. I ll take a look shortly,
> but it would be great if a few others could too.
>
> Once we are okay with it, we can ask it to be writable.
>
>
> On Tuesday, August 26, 2014, Karthik Kambatla  wrote:
>
>> Hi Suresh
>>
>> There was one vote thread on whether to migrate to git, and the
>> implications to the commit process for individual patches and feature
>> branches -
>> https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html
>> . Prior to that, there was a discuss thread on the same topic.
>>
>> As INFRA handles the actual migration from subversion to git, the vote
>> didn't include those specifics. The migration is going on as we speak (See
>> INFRA-8195). The initial expectation was that the migration would be done
>> in a few hours, but it has been several hours and the last I heard the
>> import was still running.
>>
>> I have elaborated on the points in the vote thread and drafted up a wiki
>> page on how-to-commit - https://wiki.apache.org/hadoop/HowToCommitWithGit
>> . We can work on improving this further and call a vote thread on those
>> items if need be.
>>
>> Thanks
>> Karthik
>>
>>
>> On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas > > wrote:
>>
>>> Karthik,
>>>
>>> I would like to see detailed information on how this migration will be
>>> done, how it will affect the existing project and commit process. This
>>> should be done in a document that can be reviewed instead of in an email
>>> thread on an ad-hoc basis. Was there any voting on this in PMC and should
>>> we have a vote to ensure everyone is one the same page on doing this and
>>> how to go about it?
>>>
>>> Regards,
>>> Suresh
>>>
>>>
>>> On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla 
>>> wrote:
>>>
>>> > Last I heard, the import is still going on and appears closer to
>>> getting
>>> > done. Thanks for your patience with the migration.
>>> >
>>> > I ll update you as and when there is something. Eventually, the git
>>> repo
>>> > should be at the location in the wiki.
>>> >
>>> >
>>> > On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla 
>>> > wrote:
>>> >
>>> > > Thanks for bringing these points up, Zhijie.
>>> > >
>>> > > By the way, a revised How-to-commit wiki is at:
>>> > > https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel
>>> free to
>>> > > make changes and improve it.
>>> > >
>>> > > On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen >> >
>>> > > wrote:
>>> > >
>>> > >> Do we have any convention about "user.name" and "user.email"? For
>>> > >> example,
>>> > >> we'd like to use @apache.org for the email.
>>> > >>
>>> > >
>>> > > May be, we can ask people to use project-specific configs here and
>>> use
>>> > > their real name and @apache.org address.
>>> > >
>>> > > Is there any downside to letting people use their global values for
>>> these
>>> > > configs?
>>> > >
>>> > >
>>> > >
>>> > >>
>>> > >> Moreover, do we want to use "--author="Author Name <
>>> em...@address.com>"
>>> > >> when committing on behalf of a particular contributor?
>>> > >>
>>> > >
>>> > > Fetching the email-address is complicated here. Should we use the
>>> > > contributor's email from JIRA? What if that is not their @apache
>>> address?
>>> > >
>>> > >
>>> > >>
>>> > >>
>>> > >> On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla <
>>> ka...@cloudera.com>
>>> > >> wrote:
>>> > >>
>>> > >> > Thanks for your input, Steve. Sorry for sending the email out that
>>> > >> late, I
>>> > >> > sent it as soon as I could.
>>> > >> >
>>> > >> >
>>> > >> > On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran <
>>> > ste...@hortonworks.com
>>> > >> >
>>> > >> > wrote:
>>> > >> >
>>> > >> > > just caught up with this after some offlininess...15:48 PST is
>>> too
>>> > >> late
>>> > >> > for
>>> > >> > > me.
>>> > >> > >
>>> > >> > > I'd be -1 to a change to "master" because of that risk that it
>>> does
>>> > >> break
>>> > >> > > existing code -especially people that have trunk off the git
>>> mirrors
>>> > >> and
>>> > >> > > automated builds/merges to go with it.
>>> > >> > >
>>> > >> >
>>> > >> > Fair enough. It makes sense to leave it as "trunk", unless
>>> someone is
>>> > >> > against it being tr

[jira] [Created] (HDFS-6949) Add NFS-ACL protocol support

2014-08-26 Thread Brandon Li (JIRA) 
Brandon Li created HDFS-6949:


 Summary: Add NFS-ACL protocol support
 Key: HDFS-6949
 URL: https://issues.apache.org/jira/browse/HDFS-6949
 Project: Hadoop HDFS
  Issue Type: New Feature
  Components: nfs
Reporter: Brandon Li


This is the umbrella JIRA to track the effort of adding NFS ACL support.

ACL support for NFSv3 is known as NFSACL. It is a separate out of band protocol 
(for NFSv3) to support ACL operations (GETACL and SETACL). There is no formal 
documentation or RFC on this protocol.

NFSACL program number is 100227 and version is 3. 
The program listens on tcp port 38467.

More reference:
http://lwn.net/Articles/120338/
http://cateee.net/lkddb/web-lkddb/NFS_V3_ACL.html




--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: Updates on migration to git

2014-08-26 Thread Karthik Kambatla 
The git repository is now ready for inspection. I ll take a look shortly,
but it would be great if a few others could too.

Once we are okay with it, we can ask it to be writable.

On Tuesday, August 26, 2014, Karthik Kambatla  wrote:

> Hi Suresh
>
> There was one vote thread on whether to migrate to git, and the
> implications to the commit process for individual patches and feature
> branches -
> https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html .
> Prior to that, there was a discuss thread on the same topic.
>
> As INFRA handles the actual migration from subversion to git, the vote
> didn't include those specifics. The migration is going on as we speak (See
> INFRA-8195). The initial expectation was that the migration would be done
> in a few hours, but it has been several hours and the last I heard the
> import was still running.
>
> I have elaborated on the points in the vote thread and drafted up a wiki
> page on how-to-commit - https://wiki.apache.org/hadoop/HowToCommitWithGit
> . We can work on improving this further and call a vote thread on those
> items if need be.
>
> Thanks
> Karthik
>
>
> On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas  > wrote:
>
>> Karthik,
>>
>> I would like to see detailed information on how this migration will be
>> done, how it will affect the existing project and commit process. This
>> should be done in a document that can be reviewed instead of in an email
>> thread on an ad-hoc basis. Was there any voting on this in PMC and should
>> we have a vote to ensure everyone is one the same page on doing this and
>> how to go about it?
>>
>> Regards,
>> Suresh
>>
>>
>> On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla > >
>> wrote:
>>
>> > Last I heard, the import is still going on and appears closer to getting
>> > done. Thanks for your patience with the migration.
>> >
>> > I ll update you as and when there is something. Eventually, the git repo
>> > should be at the location in the wiki.
>> >
>> >
>> > On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla > >
>> > wrote:
>> >
>> > > Thanks for bringing these points up, Zhijie.
>> > >
>> > > By the way, a revised How-to-commit wiki is at:
>> > > https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free
>> to
>> > > make changes and improve it.
>> > >
>> > > On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen > >
>> > > wrote:
>> > >
>> > >> Do we have any convention about "user.name" and "user.email"? For
>> > >> example,
>> > >> we'd like to use @apache.org for the email.
>> > >>
>> > >
>> > > May be, we can ask people to use project-specific configs here and use
>> > > their real name and @apache.org address.
>> > >
>> > > Is there any downside to letting people use their global values for
>> these
>> > > configs?
>> > >
>> > >
>> > >
>> > >>
>> > >> Moreover, do we want to use "--author="Author Name <
>> em...@address.com >"
>> > >> when committing on behalf of a particular contributor?
>> > >>
>> > >
>> > > Fetching the email-address is complicated here. Should we use the
>> > > contributor's email from JIRA? What if that is not their @apache
>> address?
>> > >
>> > >
>> > >>
>> > >>
>> > >> On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla <
>> ka...@cloudera.com >
>> > >> wrote:
>> > >>
>> > >> > Thanks for your input, Steve. Sorry for sending the email out that
>> > >> late, I
>> > >> > sent it as soon as I could.
>> > >> >
>> > >> >
>> > >> > On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran <
>> > ste...@hortonworks.com
>> 
>> > >> >
>> > >> > wrote:
>> > >> >
>> > >> > > just caught up with this after some offlininess...15:48 PST is
>> too
>> > >> late
>> > >> > for
>> > >> > > me.
>> > >> > >
>> > >> > > I'd be -1 to a change to "master" because of that risk that it
>> does
>> > >> break
>> > >> > > existing code -especially people that have trunk off the git
>> mirrors
>> > >> and
>> > >> > > automated builds/merges to go with it.
>> > >> > >
>> > >> >
>> > >> > Fair enough. It makes sense to leave it as "trunk", unless someone
>> is
>> > >> > against it being trunk.
>> > >> >
>> > >> >
>> > >> > >
>> > >> > > "master" may be viewed as the official git way, but it doesn't
>> have
>> > to
>> > >> > be.
>> > >> > > For git-flow workflows (which we use in slider) master/ is for
>> > >> releases,
>> > >> > > develop/ for dev.
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > > On 24 August 2014 02:31, Karthik Kambatla > >
>> > wrote:
>> > >> > >
>> > >> > > > Couple of things:
>> > >> > > >
>> > >> > > > 1. Since no one expressed any reservations against doing this
>> on
>> > >> Sunday
>> > >> > > or
>> > >> > > > renaming trunk to master, I ll go ahead and confirm that. I
>> think
>> > >> that
>> > >> > > > serves us better in the long run.
>> > >> > > >
>> > >> > > > 2. Arpit brought up the precommit builds - we should definitely
>> > fix
>> > >> > them
>> > >> > > as
>> > >> > > > soon as we can. I understand Giri maintains those builds, do we
>> > have
>> > >> > > anyone
>> > >>

[jira] [Created] (HDFS-6948) DN rejects blocks if it has older UC block

2014-08-26 Thread Daryn Sharp (JIRA) 
Daryn Sharp created HDFS-6948:
-

 Summary: DN rejects blocks if it has older UC block
 Key: HDFS-6948
 URL: https://issues.apache.org/jira/browse/HDFS-6948
 Project: Hadoop HDFS
  Issue Type: Bug
Affects Versions: 2.0.0-alpha, 3.0.0
Reporter: Daryn Sharp


DNs appear to always reject blocks, even with newer genstamps, if it already 
has a UC copy in its tmp dir.

{noformat}ReplicaAlreadyExistsException: Block
XXX already
exists in state TEMPORARY and thus cannot be created{noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: Updates on migration to git

2014-08-26 Thread Karthik Kambatla 
Hi Suresh

There was one vote thread on whether to migrate to git, and the
implications to the commit process for individual patches and feature
branches -
https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html .
Prior to that, there was a discuss thread on the same topic.

As INFRA handles the actual migration from subversion to git, the vote
didn't include those specifics. The migration is going on as we speak (See
INFRA-8195). The initial expectation was that the migration would be done
in a few hours, but it has been several hours and the last I heard the
import was still running.

I have elaborated on the points in the vote thread and drafted up a wiki
page on how-to-commit - https://wiki.apache.org/hadoop/HowToCommitWithGit .
We can work on improving this further and call a vote thread on those items
if need be.

Thanks
Karthik


On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas 
wrote:

> Karthik,
>
> I would like to see detailed information on how this migration will be
> done, how it will affect the existing project and commit process. This
> should be done in a document that can be reviewed instead of in an email
> thread on an ad-hoc basis. Was there any voting on this in PMC and should
> we have a vote to ensure everyone is one the same page on doing this and
> how to go about it?
>
> Regards,
> Suresh
>
>
> On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla 
> wrote:
>
> > Last I heard, the import is still going on and appears closer to getting
> > done. Thanks for your patience with the migration.
> >
> > I ll update you as and when there is something. Eventually, the git repo
> > should be at the location in the wiki.
> >
> >
> > On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla 
> > wrote:
> >
> > > Thanks for bringing these points up, Zhijie.
> > >
> > > By the way, a revised How-to-commit wiki is at:
> > > https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free
> to
> > > make changes and improve it.
> > >
> > > On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen 
> > > wrote:
> > >
> > >> Do we have any convention about "user.name" and "user.email"? For
> > >> example,
> > >> we'd like to use @apache.org for the email.
> > >>
> > >
> > > May be, we can ask people to use project-specific configs here and use
> > > their real name and @apache.org address.
> > >
> > > Is there any downside to letting people use their global values for
> these
> > > configs?
> > >
> > >
> > >
> > >>
> > >> Moreover, do we want to use "--author="Author Name  >"
> > >> when committing on behalf of a particular contributor?
> > >>
> > >
> > > Fetching the email-address is complicated here. Should we use the
> > > contributor's email from JIRA? What if that is not their @apache
> address?
> > >
> > >
> > >>
> > >>
> > >> On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla  >
> > >> wrote:
> > >>
> > >> > Thanks for your input, Steve. Sorry for sending the email out that
> > >> late, I
> > >> > sent it as soon as I could.
> > >> >
> > >> >
> > >> > On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran <
> > ste...@hortonworks.com
> > >> >
> > >> > wrote:
> > >> >
> > >> > > just caught up with this after some offlininess...15:48 PST is too
> > >> late
> > >> > for
> > >> > > me.
> > >> > >
> > >> > > I'd be -1 to a change to "master" because of that risk that it
> does
> > >> break
> > >> > > existing code -especially people that have trunk off the git
> mirrors
> > >> and
> > >> > > automated builds/merges to go with it.
> > >> > >
> > >> >
> > >> > Fair enough. It makes sense to leave it as "trunk", unless someone
> is
> > >> > against it being trunk.
> > >> >
> > >> >
> > >> > >
> > >> > > "master" may be viewed as the official git way, but it doesn't
> have
> > to
> > >> > be.
> > >> > > For git-flow workflows (which we use in slider) master/ is for
> > >> releases,
> > >> > > develop/ for dev.
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > On 24 August 2014 02:31, Karthik Kambatla 
> > wrote:
> > >> > >
> > >> > > > Couple of things:
> > >> > > >
> > >> > > > 1. Since no one expressed any reservations against doing this on
> > >> Sunday
> > >> > > or
> > >> > > > renaming trunk to master, I ll go ahead and confirm that. I
> think
> > >> that
> > >> > > > serves us better in the long run.
> > >> > > >
> > >> > > > 2. Arpit brought up the precommit builds - we should definitely
> > fix
> > >> > them
> > >> > > as
> > >> > > > soon as we can. I understand Giri maintains those builds, do we
> > have
> > >> > > anyone
> > >> > > > else who has access in case Giri is not reachable? Giri - please
> > >> shout
> > >> > > out
> > >> > > > if you can help us with this either on Sunday or Monday.
> > >> > > >
> > >> > > > Thanks
> > >> > > > Karthik
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > On Fri, Aug 22, 2014 at 3:50 PM, Karthik Kambatla <
> > >> ka...@cloudera.com>
> > >> > > > wrote:
> > >> > > >
> > >> > > > > Also, does anyone know what we use for integration between

Re: Updates on migration to git

2014-08-26 Thread Suresh Srinivas 
Karthik,

I would like to see detailed information on how this migration will be
done, how it will affect the existing project and commit process. This
should be done in a document that can be reviewed instead of in an email
thread on an ad-hoc basis. Was there any voting on this in PMC and should
we have a vote to ensure everyone is one the same page on doing this and
how to go about it?

Regards,
Suresh


On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla 
wrote:

> Last I heard, the import is still going on and appears closer to getting
> done. Thanks for your patience with the migration.
>
> I ll update you as and when there is something. Eventually, the git repo
> should be at the location in the wiki.
>
>
> On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla 
> wrote:
>
> > Thanks for bringing these points up, Zhijie.
> >
> > By the way, a revised How-to-commit wiki is at:
> > https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to
> > make changes and improve it.
> >
> > On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen 
> > wrote:
> >
> >> Do we have any convention about "user.name" and "user.email"? For
> >> example,
> >> we'd like to use @apache.org for the email.
> >>
> >
> > May be, we can ask people to use project-specific configs here and use
> > their real name and @apache.org address.
> >
> > Is there any downside to letting people use their global values for these
> > configs?
> >
> >
> >
> >>
> >> Moreover, do we want to use "--author="Author Name "
> >> when committing on behalf of a particular contributor?
> >>
> >
> > Fetching the email-address is complicated here. Should we use the
> > contributor's email from JIRA? What if that is not their @apache address?
> >
> >
> >>
> >>
> >> On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla 
> >> wrote:
> >>
> >> > Thanks for your input, Steve. Sorry for sending the email out that
> >> late, I
> >> > sent it as soon as I could.
> >> >
> >> >
> >> > On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran <
> ste...@hortonworks.com
> >> >
> >> > wrote:
> >> >
> >> > > just caught up with this after some offlininess...15:48 PST is too
> >> late
> >> > for
> >> > > me.
> >> > >
> >> > > I'd be -1 to a change to "master" because of that risk that it does
> >> break
> >> > > existing code -especially people that have trunk off the git mirrors
> >> and
> >> > > automated builds/merges to go with it.
> >> > >
> >> >
> >> > Fair enough. It makes sense to leave it as "trunk", unless someone is
> >> > against it being trunk.
> >> >
> >> >
> >> > >
> >> > > "master" may be viewed as the official git way, but it doesn't have
> to
> >> > be.
> >> > > For git-flow workflows (which we use in slider) master/ is for
> >> releases,
> >> > > develop/ for dev.
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > On 24 August 2014 02:31, Karthik Kambatla 
> wrote:
> >> > >
> >> > > > Couple of things:
> >> > > >
> >> > > > 1. Since no one expressed any reservations against doing this on
> >> Sunday
> >> > > or
> >> > > > renaming trunk to master, I ll go ahead and confirm that. I think
> >> that
> >> > > > serves us better in the long run.
> >> > > >
> >> > > > 2. Arpit brought up the precommit builds - we should definitely
> fix
> >> > them
> >> > > as
> >> > > > soon as we can. I understand Giri maintains those builds, do we
> have
> >> > > anyone
> >> > > > else who has access in case Giri is not reachable? Giri - please
> >> shout
> >> > > out
> >> > > > if you can help us with this either on Sunday or Monday.
> >> > > >
> >> > > > Thanks
> >> > > > Karthik
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > On Fri, Aug 22, 2014 at 3:50 PM, Karthik Kambatla <
> >> ka...@cloudera.com>
> >> > > > wrote:
> >> > > >
> >> > > > > Also, does anyone know what we use for integration between JIRA
> >> and
> >> > > svn?
> >> > > > I
> >> > > > > am assuming svn2jira.
> >> > > > >
> >> > > > >
> >> > > > > On Fri, Aug 22, 2014 at 3:48 PM, Karthik Kambatla <
> >> > ka...@cloudera.com>
> >> > > > > wrote:
> >> > > > >
> >> > > > >> Hi folks,
> >> > > > >>
> >> > > > >> For the SCM migration, feel free to follow
> >> > > > >> https://issues.apache.org/jira/browse/INFRA-8195
> >> > > > >>
> >> > > > >> Most of this is planned to be handled this Sunday. As a result,
> >> the
> >> > > > >> subversion repository would be read-only. If this is a major
> >> issue
> >> > for
> >> > > > you,
> >> > > > >> please shout out.
> >> > > > >>
> >> > > > >> Daniel Gruno, the one helping us with the migration, was asking
> >> if
> >> > we
> >> > > > are
> >> > > > >> open to renaming "trunk" to "master" to better conform to git
> >> > lingo. I
> >> > > > am
> >> > > > >> tempted to say yes, but wanted to check.
> >> > > > >>
> >> > > > >> Would greatly appreciate any help with checking the git repo
> has
> >> > > > >> everything.
> >> > > > >>
> >> > > > >> Thanks
> >> > > > >> Karthik
> >> > > > >>
> >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >> > > --
> >> > > CONFIDENTIALITY NOTICE
> >> > >

[jira] [Created] (HDFS-6947) Enhance HAR integration with encryption zones

2014-08-26 Thread Andrew Wang (JIRA) 
Andrew Wang created HDFS-6947:
-

 Summary: Enhance HAR integration with encryption zones
 Key: HDFS-6947
 URL: https://issues.apache.org/jira/browse/HDFS-6947
 Project: Hadoop HDFS
  Issue Type: Sub-task
Affects Versions: 3.0.0
Reporter: Andrew Wang
Assignee: Charles Lamb






--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: Updates on migration to git

2014-08-26 Thread Karthik Kambatla 
Last I heard, the import is still going on and appears closer to getting
done. Thanks for your patience with the migration.

I ll update you as and when there is something. Eventually, the git repo
should be at the location in the wiki.


On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla 
wrote:

> Thanks for bringing these points up, Zhijie.
>
> By the way, a revised How-to-commit wiki is at:
> https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to
> make changes and improve it.
>
> On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen 
> wrote:
>
>> Do we have any convention about "user.name" and "user.email"? For
>> example,
>> we'd like to use @apache.org for the email.
>>
>
> May be, we can ask people to use project-specific configs here and use
> their real name and @apache.org address.
>
> Is there any downside to letting people use their global values for these
> configs?
>
>
>
>>
>> Moreover, do we want to use "--author="Author Name "
>> when committing on behalf of a particular contributor?
>>
>
> Fetching the email-address is complicated here. Should we use the
> contributor's email from JIRA? What if that is not their @apache address?
>
>
>>
>>
>> On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla 
>> wrote:
>>
>> > Thanks for your input, Steve. Sorry for sending the email out that
>> late, I
>> > sent it as soon as I could.
>> >
>> >
>> > On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran > >
>> > wrote:
>> >
>> > > just caught up with this after some offlininess...15:48 PST is too
>> late
>> > for
>> > > me.
>> > >
>> > > I'd be -1 to a change to "master" because of that risk that it does
>> break
>> > > existing code -especially people that have trunk off the git mirrors
>> and
>> > > automated builds/merges to go with it.
>> > >
>> >
>> > Fair enough. It makes sense to leave it as "trunk", unless someone is
>> > against it being trunk.
>> >
>> >
>> > >
>> > > "master" may be viewed as the official git way, but it doesn't have to
>> > be.
>> > > For git-flow workflows (which we use in slider) master/ is for
>> releases,
>> > > develop/ for dev.
>> > >
>> > >
>> > >
>> > >
>> > > On 24 August 2014 02:31, Karthik Kambatla  wrote:
>> > >
>> > > > Couple of things:
>> > > >
>> > > > 1. Since no one expressed any reservations against doing this on
>> Sunday
>> > > or
>> > > > renaming trunk to master, I ll go ahead and confirm that. I think
>> that
>> > > > serves us better in the long run.
>> > > >
>> > > > 2. Arpit brought up the precommit builds - we should definitely fix
>> > them
>> > > as
>> > > > soon as we can. I understand Giri maintains those builds, do we have
>> > > anyone
>> > > > else who has access in case Giri is not reachable? Giri - please
>> shout
>> > > out
>> > > > if you can help us with this either on Sunday or Monday.
>> > > >
>> > > > Thanks
>> > > > Karthik
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > On Fri, Aug 22, 2014 at 3:50 PM, Karthik Kambatla <
>> ka...@cloudera.com>
>> > > > wrote:
>> > > >
>> > > > > Also, does anyone know what we use for integration between JIRA
>> and
>> > > svn?
>> > > > I
>> > > > > am assuming svn2jira.
>> > > > >
>> > > > >
>> > > > > On Fri, Aug 22, 2014 at 3:48 PM, Karthik Kambatla <
>> > ka...@cloudera.com>
>> > > > > wrote:
>> > > > >
>> > > > >> Hi folks,
>> > > > >>
>> > > > >> For the SCM migration, feel free to follow
>> > > > >> https://issues.apache.org/jira/browse/INFRA-8195
>> > > > >>
>> > > > >> Most of this is planned to be handled this Sunday. As a result,
>> the
>> > > > >> subversion repository would be read-only. If this is a major
>> issue
>> > for
>> > > > you,
>> > > > >> please shout out.
>> > > > >>
>> > > > >> Daniel Gruno, the one helping us with the migration, was asking
>> if
>> > we
>> > > > are
>> > > > >> open to renaming "trunk" to "master" to better conform to git
>> > lingo. I
>> > > > am
>> > > > >> tempted to say yes, but wanted to check.
>> > > > >>
>> > > > >> Would greatly appreciate any help with checking the git repo has
>> > > > >> everything.
>> > > > >>
>> > > > >> Thanks
>> > > > >> Karthik
>> > > > >>
>> > > > >
>> > > > >
>> > > >
>> > >
>> > > --
>> > > CONFIDENTIALITY NOTICE
>> > > NOTICE: This message is intended for the use of the individual or
>> entity
>> > to
>> > > which it is addressed and may contain information that is
>> confidential,
>> > > privileged and exempt from disclosure under applicable law. If the
>> reader
>> > > of this message is not the intended recipient, you are hereby notified
>> > that
>> > > any printing, copying, dissemination, distribution, disclosure or
>> > > forwarding of this communication is strictly prohibited. If you have
>> > > received this communication in error, please contact the sender
>> > immediately
>> > > and delete it from your system. Thank You.
>> > >
>> >
>>
>>
>>
>> --
>> Zhijie Shen
>> Hortonworks Inc.
>> http://hortonworks.com/
>>
>> --
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or e

Build failed in Jenkins: Hadoop-Hdfs-trunk #1849

2014-08-26 Thread Apache Jenkins Server 
See 

--
[...truncated 13758 lines...]
Running org.apache.hadoop.hdfs.TestParallelReadUtil
Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.032 sec - in 
org.apache.hadoop.hdfs.TestParallelReadUtil
Running org.apache.hadoop.hdfs.TestAppendDifferentChecksum
Tests run: 3, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 8.579 sec - in 
org.apache.hadoop.hdfs.TestAppendDifferentChecksum
Running org.apache.hadoop.hdfs.TestEncryptedTransfer
Tests run: 24, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 97.107 sec - 
in org.apache.hadoop.hdfs.TestEncryptedTransfer
Running org.apache.hadoop.hdfs.TestFileConcurrentReader
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.554 sec - in 
org.apache.hadoop.hdfs.TestFileConcurrentReader
Running org.apache.hadoop.hdfs.TestDFSPermission
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.263 sec - in 
org.apache.hadoop.hdfs.TestDFSPermission
Running org.apache.hadoop.hdfs.TestModTime
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.368 sec - in 
org.apache.hadoop.hdfs.TestModTime
Running org.apache.hadoop.hdfs.TestDataTransferKeepalive
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.78 sec - in 
org.apache.hadoop.hdfs.TestDataTransferKeepalive
Running org.apache.hadoop.hdfs.shortcircuit.TestShortCircuitLocalRead
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.842 sec - 
in org.apache.hadoop.hdfs.shortcircuit.TestShortCircuitLocalRead
Running org.apache.hadoop.hdfs.shortcircuit.TestShortCircuitShm
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.468 sec - in 
org.apache.hadoop.hdfs.shortcircuit.TestShortCircuitShm
Running org.apache.hadoop.hdfs.shortcircuit.TestShortCircuitCache
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.993 sec - in 
org.apache.hadoop.hdfs.shortcircuit.TestShortCircuitCache
Running org.apache.hadoop.hdfs.TestRestartDFS
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.406 sec - in 
org.apache.hadoop.hdfs.TestRestartDFS
Running org.apache.hadoop.hdfs.TestLeaseRecovery
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.834 sec - in 
org.apache.hadoop.hdfs.TestLeaseRecovery
Running org.apache.hadoop.hdfs.TestSetTimes
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.176 sec - in 
org.apache.hadoop.hdfs.TestSetTimes
Running org.apache.hadoop.hdfs.TestDefaultNameNodePort
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.855 sec - in 
org.apache.hadoop.hdfs.TestDefaultNameNodePort
Running org.apache.hadoop.hdfs.TestParallelShortCircuitLegacyRead
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.14 sec - in 
org.apache.hadoop.hdfs.TestParallelShortCircuitLegacyRead
Running org.apache.hadoop.hdfs.TestClose
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.372 sec - in 
org.apache.hadoop.hdfs.TestClose
Running org.apache.hadoop.hdfs.TestDFSMkdirs
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.819 sec - in 
org.apache.hadoop.hdfs.TestDFSMkdirs
Running org.apache.hadoop.hdfs.TestFileCreationEmpty
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.455 sec - in 
org.apache.hadoop.hdfs.TestFileCreationEmpty
Running org.apache.hadoop.hdfs.TestWriteRead
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 24.516 sec - in 
org.apache.hadoop.hdfs.TestWriteRead
Running org.apache.hadoop.hdfs.TestMiniDFSCluster
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.635 sec - in 
org.apache.hadoop.hdfs.TestMiniDFSCluster
Running org.apache.hadoop.hdfs.TestDFSFinalize
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.784 sec - in 
org.apache.hadoop.hdfs.TestDFSFinalize
Running org.apache.hadoop.hdfs.TestHDFSFileSystemContract
Tests run: 44, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 42.877 sec - 
in org.apache.hadoop.hdfs.TestHDFSFileSystemContract
Running org.apache.hadoop.hdfs.TestEncryptionZones
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.648 sec - in 
org.apache.hadoop.hdfs.TestEncryptionZones
Running org.apache.hadoop.hdfs.TestRollingUpgradeDowngrade
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.515 sec - in 
org.apache.hadoop.hdfs.TestRollingUpgradeDowngrade
Running org.apache.hadoop.hdfs.TestParallelShortCircuitReadUnCached
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 31.615 sec - in 
org.apache.hadoop.hdfs.TestParallelShortCircuitReadUnCached
Running org.apache.hadoop.hdfs.TestClientProtocolForPipelineRecovery
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.633 sec - in 
org.apache.hadoop.hdfs.TestClientProtocolForPipelineRecovery
Running org.apache.hadoop.hdfs.TestWriteBlockGetsBlockLengthHint
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.33 sec - in 
org

Hadoop-Hdfs-trunk - Build # 1849 - Still Failing

2014-08-26 Thread Apache Jenkins Server 
See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1849/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 13951 lines...]
[INFO] 
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ hadoop-hdfs-project 
---
[INFO] Deleting 
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk/trunk/hadoop-hdfs-project/target
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (create-testdirs) @ hadoop-hdfs-project 
---
[INFO] Executing tasks

main:
[mkdir] Created dir: 
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk/trunk/hadoop-hdfs-project/target/test-dir
[INFO] Executed tasks
[INFO] 
[INFO] --- maven-source-plugin:2.1.2:jar-no-fork (hadoop-java-sources) @ 
hadoop-hdfs-project ---
[INFO] 
[INFO] --- maven-source-plugin:2.1.2:test-jar-no-fork (hadoop-java-sources) @ 
hadoop-hdfs-project ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (dist-enforce) @ 
hadoop-hdfs-project ---
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
hadoop-hdfs-project ---
[INFO] 
[INFO] --- maven-javadoc-plugin:2.8.1:jar (module-javadocs) @ 
hadoop-hdfs-project ---
[INFO] Not executing Javadoc as the project is not a Java classpath-capable 
package
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (depcheck) @ hadoop-hdfs-project 
---
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.6:checkstyle (default-cli) @ 
hadoop-hdfs-project ---
[INFO] 
[INFO] --- findbugs-maven-plugin:2.3.2:findbugs (default-cli) @ 
hadoop-hdfs-project ---
[INFO] ** FindBugsMojo execute ***
[INFO] canGenerate is false
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Hadoop HDFS  FAILURE [  02:11 h]
[INFO] Apache Hadoop HttpFS .. SKIPPED
[INFO] Apache Hadoop HDFS BookKeeper Journal . SKIPPED
[INFO] Apache Hadoop HDFS-NFS  SKIPPED
[INFO] Apache Hadoop HDFS Project  SUCCESS [  2.189 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 02:11 h
[INFO] Finished at: 2014-08-26T13:46:36+00:00
[INFO] Final Memory: 65M/879M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on 
project hadoop-hdfs: ExecutionException; nested exception is 
java.util.concurrent.ExecutionException: java.lang.RuntimeException: The forked 
VM terminated without saying properly goodbye. VM crash or System.exit called ?
[ERROR] Command was/bin/sh -c cd 
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk/trunk/hadoop-hdfs-project/hadoop-hdfs
 && /home/jenkins/tools/java/jdk1.6.0_45-64/jre/bin/java -Xmx1024m 
-XX:+HeapDumpOnOutOfMemoryError -jar 
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk/trunk/hadoop-hdfs-project/hadoop-hdfs/target/surefire/surefirebooter2817965309910602247.jar
 
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk/trunk/hadoop-hdfs-project/hadoop-hdfs/target/surefire/surefire8460618076296137435tmp
 
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk/trunk/hadoop-hdfs-project/hadoop-hdfs/target/surefire/surefire_3171017441613315715103tmp
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
Sending e-mails to: hdfs-dev@hadoop.apache.org
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
1 tests failed.
REGRESSION:  
org.apache.hadoop.hdfs.server.balancer.TestBalancerWithSaslDataTransfer.testBalancer0Integrity

Error Message:
Cluster failed to reached expected values of totalSpace (current: 750, 
expected: 750), or usedSpace (current: 140, expected: 150), in more than 4 
msec.

Stack Trace:
java.util.concurrent.TimeoutException: Cluster failed to reached expected 
values of totalSpace (current: 750, expected: 750), or usedSpace (current: 140, 
expected: 150), in more than 4 msec.
at 
org.apache.hadoop.hdfs.server.balancer.TestBalancer.waitForHeartBeat(TestBalancer.java:253)
at 
org.apache.hadoop.hdfs.server.balancer.TestBalancer.runBalancer(TestBalancer.jav

[jira] [Created] (HDFS-6945) ExcessBlocks metric may not be decremented if there are no over replicated blocks

2014-08-26 Thread Akira AJISAKA (JIRA) 
Akira AJISAKA created HDFS-6945:
---

 Summary: ExcessBlocks metric may not be decremented if there are 
no over replicated blocks
 Key: HDFS-6945
 URL: https://issues.apache.org/jira/browse/HDFS-6945
 Project: Hadoop HDFS
  Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Akira AJISAKA


I'm seeing ExcessBlocks metric increases to more than 300K in some clusters, 
however, there are no over-replicated blocks (confirmed by fsck).



--
This message was sent by Atlassian JIRA
(v6.2#6252)