Re: Updates on migration to git
some of this info is here https://git-wip-us.apache.org/ 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 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 ka...@cloudera.com 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 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. -- CONFIDENTIALITY NOTICE NOTICE: This message is
[jira] [Created] (HADOOP-10343) Change info to debug log in LossyRetryInvocationHandler
Arpit Gupta created HADOOP-10343: Summary: Change info to debug log in LossyRetryInvocationHandler Key: HADOOP-10343 URL: https://issues.apache.org/jira/browse/HADOOP-10343 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.2.0 Reporter: Arpit Gupta Assignee: Arpit Gupta Priority: Minor Attachments: HADOOP-10343.patch in LossyRetryInvocationHandler we print logs at info level when we drop responses. This causes lot of noise on the console. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: Logistics for releasing 2.4
There are a couple of minor doc changes if they can be included in the next release that will be great. https://issues.apache.org/jira/browse/HADOOP-10050 https://issues.apache.org/jira/browse/HADOOP-10065 Thanks -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On Jan 22, 2014, at 6:09 PM, Arun Murthy a...@hortonworks.com wrote: Sounds good, thanks. I'll ping you off-thread. Arun On Wed, Jan 22, 2014 at 6:01 PM, Andrew Wang andrew.w...@cloudera.comwrote: Hi Arun, thanks for the reply. I hope that I've come across as an earnest and motivated contributor who wants to help make high-quality releases. Volunteering myself as RM and pushing for a 2.4 was not a reflection on your stewardship of 2.x so far. I know it's a lot of work. I didn't mean to suggest 12 releases per year. I was trying to couch my terminology with monthly-ish and regular cadence. I must have missed the email thread where we decided on this, but 6-8 weeks per cycle is 100% fine with me. I obviously don't want meaningless releases just for the sake of releases, but I think HDFS-2832, HDFS-4949, and all the other improvements in branch-2 add enough value that cutting something is not meaningless. My impression of the two YARN JIRAs is that they're still roughly a month from being prod-ready, which is why I figured they could wait 6 weeks for the next 2.x. That was also not a slight on the YARN developers, it's that I think we should follow through if we're serious about a regular release cadence. As you allude to, we need to get used to slipping features to the next release. Symlinks one such example that I've personally been involved with, so I do understand. As an aside, I think this means that we should be more judicious about branch-2 merges in the future, since a regular cadence means branch-2 should stay in a releasable state. I hope we can avoid burdonsome code divergence through hard-disable patches (e.g. symlinks) or pushing down just refactors (sort of like HDFS-2832), but that remains to be seen. I can abandon the 2.3rc, and then release current branch-2 as 2.3. Would that be better? That'd be great. All I'm after here is a regular release cadence with good integration testing, so if you're willing to RM it, awesome. As I stated way back in the thread, feel free to email me if you think I can help with the release process. Thanks, Andrew -- -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/ -- 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. -- 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.
[jira] [Created] (HADOOP-10215) Cannot create hftp filesystem when using a proxy user ugi on a secure cluster
Arpit Gupta created HADOOP-10215: Summary: Cannot create hftp filesystem when using a proxy user ugi on a secure cluster Key: HADOOP-10215 URL: https://issues.apache.org/jira/browse/HADOOP-10215 Project: Hadoop Common Issue Type: Bug Components: security Affects Versions: 2.2.0 Reporter: Arpit Gupta Noticed this while debugging issues in another application. We saw an error when trying to do a FileSystem.get using an hftp file system on a secure cluster using a proxy user ugi. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (HADOOP-10065) Fix namenode format documentation
Arpit Gupta created HADOOP-10065:
Summary: Fix namenode format documentation
Key: HADOOP-10065
URL: https://issues.apache.org/jira/browse/HADOOP-10065
Project: Hadoop Common
Issue Type: Bug
Components: documentation
Affects Versions: 2.2.0
Reporter: Arpit Gupta
Assignee: Arpit Gupta
Priority: Minor
Fix For: 2.2.1
Current namenode format doc
http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/CommandsManual.html#namenode
Does not list the various options format can be called with and their use.
{code}
[-format [-clusterid cid ] [-force] [-nonInteractive] ]
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (HADOOP-10050) Update single node and cluster install instructions to work with latest bits
Arpit Gupta created HADOOP-10050: Summary: Update single node and cluster install instructions to work with latest bits Key: HADOOP-10050 URL: https://issues.apache.org/jira/browse/HADOOP-10050 Project: Hadoop Common Issue Type: Bug Components: documentation Affects Versions: 2.2.0 Reporter: Arpit Gupta Assignee: Arpit Gupta Priority: Minor A few things i noticed 1. changes to yarn.nodemanager.aux-services 2. Set the framework to yarn in mapred-site.xml 3. Start the history server Also noticed no change to the capacity scheduler configs was needed. -- This message was sent by Atlassian JIRA (v6.1#6144)
Re: [VOTE] Release Apache Hadoop 2.2.0
+1 (non binding) Ran secure and non secure multi node clusters and tested HA and RM recovery tests. -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On Oct 7, 2013, at 12:00 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, I've created a release candidate (rc0) for hadoop-2.2.0 that I would like to get released - this release fixes a small number of bugs and some protocol/api issues which should ensure they are now stable and will not change in hadoop-2.x. The RC is available at: http://people.apache.org/~acmurthy/hadoop-2.2.0-rc0 The RC tag in svn is here: http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.2.0-rc0 The maven artifacts are available via repository.apache.org. Please try the release and vote; the vote will run for the usual 7 days. thanks, Arun P.S.: Thanks to Colin, Andrew, Daryn, Chris and others for helping nail down the symlinks-related issues. I'll release note the fact that we have disabled it in 2.2. Also, thanks to Vinod for some heavy-lifting on the YARN side in the last couple of weeks. -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/ -- 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. -- 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.
[jira] [Created] (HADOOP-10012) Secure Oozie jobs with delegation token renewal exception in HA setup
Arpit Gupta created HADOOP-10012: Summary: Secure Oozie jobs with delegation token renewal exception in HA setup Key: HADOOP-10012 URL: https://issues.apache.org/jira/browse/HADOOP-10012 Project: Hadoop Common Issue Type: Bug Components: ha Affects Versions: 2.1.1-beta Reporter: Arpit Gupta Assignee: Suresh Srinivas -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (HADOOP-9886) Turn warning message in RetryInvocationHandler to a debub
Arpit Gupta created HADOOP-9886: --- Summary: Turn warning message in RetryInvocationHandler to a debub Key: HADOOP-9886 URL: https://issues.apache.org/jira/browse/HADOOP-9886 Project: Hadoop Common Issue Type: Bug Affects Versions: 2.1.0-beta Reporter: Arpit Gupta Assignee: Arpit Gupta Priority: Minor Fix For: 2.1.1-beta Currently if debug is not enabled we display a warning message when the client fails over to another namenode. This will happen for every call that goes to the failed over namenode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Heads up: branch-2.1-beta
We are running into an issue where link to the AM leads to a 500 https://issues.apache.org/jira/browse/YARN-800 We should fix this before we release 2.1.0 beta. -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On Jun 10, 2013, at 4:49 AM, Arun C Murthy a...@hortonworks.com wrote: On Jun 4, 2013, at 8:32 AM, Arun C Murthy wrote: Folks, The vast majority of of the planned features and API work is complete, thanks to everyone who contributed! I've created a branch-2.1-beta branch from which I anticipate I can make the first of our beta releases very shortly. Thanks to Giri we now have a jenkins for daily branch-2.1-beta builds: https://builds.apache.org/job/Hadoop-branch-2.1-beta/ Arun -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
+1 -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On May 21, 2013, at 2:10 PM, Matt Foley ma...@apache.org wrote: Hi all, This has been a side topic in several email threads recently. Currently we have an ambiguity. We have a tradition in the dev community that any committer can create a branch, and propose release candidates from it. Yet the Hadoop bylaws say that releases have to be planned in advance, the plan needs to be voted on, and presumably can be denied. Apache policies (primarily here http://www.apache.org/dev/release.html and here http://www.apache.org/foundation/voting.html, with non-normative commentary herehttp://incubator.apache.org/guides/releasemanagement.html#best-practice) are very clear on how Releases have to be approved, and our bylaws are consistent with those policies. But Apache policies don't say anything I've found about Release Plans, nor about voting on Release Plans. I propose the following change, to remove Release Plan votes, and give a simple definition of Release Manager role. I'm opening discussion with this proposal, and will put it to a vote if we seem to be getting consensus. Here's the changes I suggest in the Bylawshttp://hadoop.apache.org/bylaws.html document: === 1. In the Decision Making : Actions section of the Bylaws, the following text is removed: ** Release Plan* Defines the timetable and actions for a release. The plan also nominates a Release Manager. Lazy majority of active committers 2. In the Roles and Responsibilities section of the Bylaws, an additional role is defined: ** Release Manager* A Release Manager (RM) is a committer who volunteers to produce a Release Candidate according to HowToReleasehttps://wiki.apache.org/hadoop/HowToRelease. The RM shall publish a Release Plan on the *common-dev@* list stating the branch from which they intend to make a Release Candidate, at least one week before they do so. The RM is responsible for building consensus around the content of the Release Candidate, in order to achieve a successful Product Release vote. === Please share your views. Best regards, --Matt (long-time release manager)
Re: [VOTE] Plan to create release candidate for 0.23.8
+1 -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On May 17, 2013, at 2:10 PM, Thomas Graves tgra...@yahoo-inc.com wrote: Hello all, We've had a few critical issues come up in 0.23.7 that I think warrants a 0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of other issues that I want finished up and get in before we spin it. Those include HDFS-3875, HDFS-4805, and HDFS-4835. I think those are on track to finish up early next week. So I hope to spin 0.23.8 soon after this vote completes. Please vote '+1' to approve this plan. Voting will close on Friday May 24th at 2:00pm PDT. Thanks, Tom Graves
[jira] [Created] (HADOOP-9379) capture the ulimit info after printing the log to the console
Arpit Gupta created HADOOP-9379: --- Summary: capture the ulimit info after printing the log to the console Key: HADOOP-9379 URL: https://issues.apache.org/jira/browse/HADOOP-9379 Project: Hadoop Common Issue Type: Improvement Affects Versions: 1.2.0, 2.0.4-alpha Reporter: Arpit Gupta Assignee: Arpit Gupta Priority: Trivial -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Snappy build warning
Snappy libraries needs to be available on your system for hadoop to use them during the build. If you are on a centos based system epel repositories have the snappy and snappy-devel rpm's which need to be installed before you build hadoop. -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On Mar 7, 2013, at 9:07 AM, Amir Sanjar v1san...@us.ibm.com wrote: During build of hadoop 1.1.2 we get a warning Snappy headers were not found... building without snappy.. I though snappy was included in hadoop, what is missing? thanks in advance ..
Re: [VOTE] Hadoop 1.1.2-rc5 release candidate vote
+1 non binding Deployed on multi node clusters with secure and non secure setup and ran full system tests. No new regressions were found. -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On Jan 31, 2013, at 7:13 PM, Matt Foley ma...@apache.org wrote: (resending with modified Subject line for RC5) Hadoop-1.1.2-rc4 is withdrawn. Hadoop-1.1.2-rc5 is available at http://people.apache.org/~mattf/hadoop-1.1.2-rc5/ or in SVN at http://svn.apache.org/viewvc/hadoop/common/tags/release-1.1.2-rc5/ or in the Maven repo. This candidate for a stabilization release of the Hadoop-1.1 branch has 24 patches and several cleanups compared to the Hadoop-1.1.1 release. Release notes are available at http://people.apache.org/~mattf/hadoop-1.1.2-rc5/releasenotes.html Please vote for this as the next release of Hadoop-1. Voting will close next Thursday, 7 Feb, at 3:00pm PST. Thanks, --Matt On Tue, Jan 29, 2013 at 9:47 PM, Chris Nauroth cnaur...@hortonworks.comwrote: HDFS-4423 has been committed to branch-1. Thank you, Matt. --Chris On Tue, Jan 29, 2013 at 11:57 AM, Matt Foley mfo...@hortonworks.com wrote: Hi Chris, Okay, please get it in as soon as possible, and I'll respin the build. Suresh, can you code review? Thanks, --Matt On Tue, Jan 29, 2013 at 11:11 AM, Chris Nauroth cnaur...@hortonworks.com wrote: Hello Matt, Would it be better to wait for committing the fix of blocker HDFS-4423: Checkpoint exception causes fatal damage to fsimage? I have uploaded a patch, and I expect to receive a code review in the next day or two. Thank you, --Chris On Mon, Jan 28, 2013 at 3:32 PM, Matt Foley mfo...@hortonworks.com wrote: A new build of Hadoop-1.1.2 is available at http://people.apache.org/~mattf/hadoop-1.1.2-rc4/ or in SVN at http://svn.apache.org/viewvc/hadoop/common/tags/release-1.1.2-rc4/ or in the Maven repo. This candidate for a stabilization release of the Hadoop-1.1 branch has 23 patches and several cleanups compared to the Hadoop-1.1.1 release. Release notes are available at http://people.apache.org/~mattf/hadoop-1.1.2-rc4/releasenotes.html Please vote for this as the next release of Hadoop-1. Voting will close next Monday, 4 Feb, at 3:30pm PST. Thanks, --Matt
[jira] [Created] (HADOOP-9253) Capture ulimit info in the logs at service start time
Arpit Gupta created HADOOP-9253: --- Summary: Capture ulimit info in the logs at service start time Key: HADOOP-9253 URL: https://issues.apache.org/jira/browse/HADOOP-9253 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.2-alpha, 1.1.1 Reporter: Arpit Gupta Assignee: Arpit Gupta output of ulimit -a is helpful while debugging issues on the system. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-9251) mvn eclipse:eclipse fails on trunk
[ https://issues.apache.org/jira/browse/HADOOP-9251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Gupta resolved HADOOP-9251. - Resolution: Invalid mvn eclipse:eclipse fails on trunk -- Key: HADOOP-9251 URL: https://issues.apache.org/jira/browse/HADOOP-9251 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Arpit Gupta [ERROR] Failed to execute goal org.apache.maven.plugins:maven-eclipse-plugin:2.8:eclipse (default-cli) on project hadoop-common: Request to merge when 'filtering' is not identical. Original=resource src/main/resources: output=target/classes, include=[], exclude=[common-version-info.properties|**/*.java], test=false, filtering=false, merging with=resource src/main/resources: output=target/classes, include=[common-version-info.properties], exclude=[**/*.java], test=false, filtering=true - [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/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :hadoop-common -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9115) Deadlock in configuration when writing configuration to hdfs
Arpit Gupta created HADOOP-9115: --- Summary: Deadlock in configuration when writing configuration to hdfs Key: HADOOP-9115 URL: https://issues.apache.org/jira/browse/HADOOP-9115 Project: Hadoop Common Issue Type: Bug Reporter: Arpit Gupta Priority: Blocker Attachments: hive-jstack.log This was noticed when using hive with hadoop-1.1.1 and running select count(*) from tbl; This would cause a deadlock configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Hadoop Release 1.1.1
+1, non binding ran system tests on secure and non secure clusters and no new regressions were found. -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On Nov 20, 2012, at 2:07 PM, Matt Foley ma...@apache.org wrote: Hello, Hadoop-1.1.1-rc0 is now available for evaluation and vote: http://people.apache.org/~mattf/hadoop-1.1.1-rc0/ or in the Nexus repository. The release notes are available at http://people.apache.org/~mattf/hadoop-1.1.1-rc0/releasenotes.html 20 bugs have been fixed, compared to release 1.1.0, with no backward incompatibilities. I took the opportunity to assure that all branch-1.0 changes are in 1.1.1, and all branch-1.1 changes are in branch-1. The jira database has been made consistent. Please vote. Voting will end on Tuesday 27 Nov., at 2:05pm PST. Thank you, --Matt Foley release manager
[jira] [Resolved] (HADOOP-8888) add the ability to suppress the deprecated warnings when using hadoop cli
[
https://issues.apache.org/jira/browse/HADOOP-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta resolved HADOOP-.
-
Resolution: Won't Fix
add the ability to suppress the deprecated warnings when using hadoop cli
-
Key: HADOOP-
URL: https://issues.apache.org/jira/browse/HADOOP-
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 3.0.0
Reporter: Arpit Gupta
Assignee: Arpit Gupta
some this similar to what HADOOP_HOME_WARN_SUPPRESS is used for in branch-1
May be we can introduce
HADOOP_DEPRECATED_WARN_SUPPRESS
which if set to yes will suppress the various warnings that are thrown.
For example commands like
{code}
hadoop dfs
hadoop jar
{code}
etc will print out deprecated warnings.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-8917) add LOCALE.US to toLowerCase in SecurityUtil.replacePattern
Arpit Gupta created HADOOP-8917: --- Summary: add LOCALE.US to toLowerCase in SecurityUtil.replacePattern Key: HADOOP-8917 URL: https://issues.apache.org/jira/browse/HADOOP-8917 Project: Hadoop Common Issue Type: Bug Affects Versions: 1.2.0, 3.0.0 Reporter: Arpit Gupta Assignee: Arpit Gupta see https://issues.apache.org/jira/browse/HADOOP-8878?focusedCommentId=13472245page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13472245 for more details -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Hadoop-1.1.0 release candidate 5
+1 (non-binding) ran tests on multi node secure and un secure clusters and everything worked as expected. -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On Oct 5, 2012, at 2:31 PM, Matt Foley ma...@apache.org wrote: Here at long last is a votable release candidate for Hadoop 1.1.0. Please download and test Hadoop-1.1.0-rc5. It is available at http://people.apache.org/~mattf/hadoop-1.1.0-rc5/http://people.apache.org/~mattf/hadoop-1.1.0-rc05/ or from the Nexus maven repo. Release notes are at http://people.apache.org/~mattf/hadoop-1.1.0-rc5/releasenotes.html Vote will run for 1 week as usual, terminating at 2:30pm PDT, Fri 12 Oct 2012. Thank you, --Matt Foley Release Manager
Re: [VOTE] Hadoop-1.0.4-rc0
+1 (non binding) ran regression tests and no issues were found. -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On Oct 4, 2012, at 1:59 PM, Matt Foley ma...@apache.org wrote: Hi, There has been a request from several PMC members for a maintenance release of hadoop-1.0. Please download and test this release candidate, Hadoop-1.0.4-rc0. It is available at http://people.apache.org/~mattf/hadoop-1.0.4-rc0/ or from the Nexus maven repo. Release notes are at http://people.apache.org/~mattf/hadoop-1.0.4-rc0/releasenotes.html Vote will run for 1 week as usual, terminating at 2pm PDT, Thur 11 Oct 2012. Thank you, --Matt Foley Release Manager
[jira] [Created] (HADOOP-8888) add the ability to suppress the deprecated warnings when using hadoop cli
Arpit Gupta created HADOOP-: --- Summary: add the ability to suppress the deprecated warnings when using hadoop cli Key: HADOOP- URL: https://issues.apache.org/jira/browse/HADOOP- Project: Hadoop Common Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Arpit Gupta Assignee: Arpit Gupta some this similar to what HADOOP_HOME_WARN_SUPPRESS is used for in branch-1 May we can introduce HADOOP_DEPRECATED_WARN_SUPPRESS which if set to yes will suppress the various warnings that are thrown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-8882) uppercase namenode host name causes fsck to fail when useKsslAuth is on
Arpit Gupta created HADOOP-8882:
---
Summary: uppercase namenode host name causes fsck to fail when
useKsslAuth is on
Key: HADOOP-8882
URL: https://issues.apache.org/jira/browse/HADOOP-8882
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 1.2.0
Reporter: Arpit Gupta
Assignee: Arpit Gupta
{code}
public static void fetchServiceTicket(URL remoteHost) throws IOException {
if(!UserGroupInformation.isSecurityEnabled())
return;
String serviceName = host/ + remoteHost.getHost();
{code}
the hostname should be converted to lower case. Saw this in branch 1, will look
at trunk and update the bug accordingly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-8878) uppercase hostname causes hadoop dfs calls with webhdfs filesystem to fail
Arpit Gupta created HADOOP-8878: --- Summary: uppercase hostname causes hadoop dfs calls with webhdfs filesystem to fail Key: HADOOP-8878 URL: https://issues.apache.org/jira/browse/HADOOP-8878 Project: Hadoop Common Issue Type: Bug Affects Versions: 1.0.3, 1.1.0, 1.2.0 Reporter: Arpit Gupta Assignee: Arpit Gupta This was noticed on a secure cluster where the namenode had an upper case hostname and the following command was issued hadoop dfs -ls webhdfs://NN:PORT/PATH the above command failed because delegation token retrieval failed. Upon looking at the kerberos logs it was determined that we tried to get the ticket for kerberos principal with upper case hostnames and that host did not exit in kerberos. We should convert the hostnames to lower case. Take a look at HADOOP-7988 where the same fix was applied on a different class. I have noticed this issue exists on branch-1. Will investigate trunk and branch-2 and update accordingly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: 答复: regarding _HOST token replacement in security hadoop
That does seem to be valid issue. Could you log a jira for it. Thanks On Thu, Jul 26, 2012 at 7:32 PM, Wangwenli wangwe...@huawei.com wrote: Could you spent one minute to check whether below code will cause issue or not? In org.apache.hadoop.hdfs.server.namenode.NameNode.loginAsNameNodeUser(), it use socAddr.getHostName() to get _HOST, But in org.apache.hadoop.security.SecurityUtil.replacePattern(), in getLocalHostName(), it use getCanonicalHostName() to get _HOST Meanwhile I will check what you said. Thank you~ -邮件原件- 发件人: Arpit Gupta [mailto:ar...@hortonworks.com] 发送时间: 2012年7月27日 10:03 收件人: common-dev@hadoop.apache.org 主题: Re: regarding _HOST token replacement in security hadoop you need to use HTTP/_h...@site.com as that is the principal needed by spnego. So you would need create the HTTP/_HOST principal and add it to the same keytab (/home/hdfs/keytab/nn.service.keytab). -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On Jul 26, 2012, at 6:54 PM, Wangwenli wangwe...@huawei.com wrote: Thank yours response. I am using hadoop-2.0.0-alpha from apache site. In which version it should configure with HTTP/_h...@site.com? I think not in hadoop-2.0.0-alpha. Because I login successful with other principal, pls refer below log: 2012-07-23 22:48:17,303 INFO org.apache.hadoop.security.authentication.server.KerberosAuthenticationHandler: Login using keytab /home/hdfs/keytab/nn.service.keytab, for principal nn/167-52-0-56.site@site 2012-07-23 22:48:17,310 INFO org.apache.hadoop.security.authentication.server.KerberosAuthenticationHandler: Initialized, principal [nn/167-52-0-56.site@site] from keytab [/home/hdfs/keytab/nn.service.keytab] -邮件原件- 发件人: Arpit Gupta [mailto:ar...@hortonworks.com] 发送时间: 2012年7月27日 9:22 收件人: common-dev@hadoop.apache.org 主题: Re: regarding _HOST token replacement in security hadoop what version of hadoop are you using? also dfs.web.authentication.kerberos.principal should be set to HTTP/_ h...@site.com -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On Jul 26, 2012, at 6:11 PM, Wangwenli wangwe...@huawei.com wrote: Hi all, I configured like below in hdfs-site.xml: property namedfs.namenode.kerberos.principal/name valuenn/_HOST@site/value /property property namedfs.web.authentication.kerberos.principal/name valuenn/_HOST@site/value /property When start up namenode, I found, namenode will use principal : nn/167-52-0-56@site to login, but the http server will use nn/167-52-0-56.site@sitemailto:nn/167-52-0-56.site@site to lgin, so it start failed. I checked the code, Namenode will use socAddr.getHostName() to get hostname in org.apache.hadoop.hdfs.server.namenode.NameNode.loginAsNameNodeUser. But httpserver 's default hostname is 0.0.0.0, so in org.apache.hadoop.security.SecurityUtil.replacePattern, it will get the hostname by invoking getLocalHostName,there it use getCanonicalHostName(), I think this inconsistent is wrong, can someone confirm this? Need raise one bug ? Thanks
Re: regarding _HOST token replacement in security hadoop
you need to use HTTP/_h...@site.com as that is the principal needed by spnego. So you would need create the HTTP/_HOST principal and add it to the same keytab (/home/hdfs/keytab/nn.service.keytab). -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On Jul 26, 2012, at 6:54 PM, Wangwenli wangwe...@huawei.com wrote: Thank yours response. I am using hadoop-2.0.0-alpha from apache site. In which version it should configure with HTTP/_h...@site.com? I think not in hadoop-2.0.0-alpha. Because I login successful with other principal, pls refer below log: 2012-07-23 22:48:17,303 INFO org.apache.hadoop.security.authentication.server.KerberosAuthenticationHandler: Login using keytab /home/hdfs/keytab/nn.service.keytab, for principal nn/167-52-0-56.site@site 2012-07-23 22:48:17,310 INFO org.apache.hadoop.security.authentication.server.KerberosAuthenticationHandler: Initialized, principal [nn/167-52-0-56.site@site] from keytab [/home/hdfs/keytab/nn.service.keytab] -邮件原件- 发件人: Arpit Gupta [mailto:ar...@hortonworks.com] 发送时间: 2012年7月27日 9:22 收件人: common-dev@hadoop.apache.org 主题: Re: regarding _HOST token replacement in security hadoop what version of hadoop are you using? also dfs.web.authentication.kerberos.principal should be set to HTTP/_h...@site.com -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On Jul 26, 2012, at 6:11 PM, Wangwenli wangwe...@huawei.com wrote: Hi all, I configured like below in hdfs-site.xml: property namedfs.namenode.kerberos.principal/name valuenn/_HOST@site/value /property property namedfs.web.authentication.kerberos.principal/name valuenn/_HOST@site/value /property When start up namenode, I found, namenode will use principal : nn/167-52-0-56@site to login, but the http server will use nn/167-52-0-56.site@sitemailto:nn/167-52-0-56.site@site to lgin, so it start failed. I checked the code, Namenode will use socAddr.getHostName() to get hostname in org.apache.hadoop.hdfs.server.namenode.NameNode.loginAsNameNodeUser. But httpserver 's default hostname is 0.0.0.0, so in org.apache.hadoop.security.SecurityUtil.replacePattern, it will get the hostname by invoking getLocalHostName,there it use getCanonicalHostName(), I think this inconsistent is wrong, can someone confirm this? Need raise one bug ? Thanks
Re: [VOTE] Hadoop-1.0.3-rc1
+1 (non binding) ran system tests on secure and non secure deploys and found no regression issues. -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On May 8, 2012, at 6:25 PM, Matt Foley wrote: Hi all, release Candidate for Hadoop-1.0.3 is now available for vote, at http://people.apache.org/~mattf/hadoop-1.0.3-rc1/ There are 29 bug fixes and enhancements in this release, including: 4 patches in support of non-Oracle JDKs several patches to clean up error handling and log messages various production issues Please see the Release Notes for the full list, at: http://people.apache.org/~mattf/hadoop-1.0.3-rc1/releasenotes.html Vote will run the statutory 7 days, and close on Tuesday 15 May, at 6:30pm PDT. Thank you, --Matt Release Manager, Hadoop 1.0
Re: Problem in installing hive
Make sure you are on hive 0.8.1 that has the fix for this issue. -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On Apr 1, 2012, at 11:54 AM, Ranjan Banerjee wrote: Hello, I am trying to install hive. However I am facing the following problem. After following all the procedures, when I try to get the command line interface by typing the command hive, I get the following message: Warning: $HADOOP_HOME is deprecated. Hive requires Hadoop 0.20.x (x = 1). 'hadoop version' returned: Warning: $HADOOP_HOME is deprecated. Hadoop 1.0.0 Subversion https://svn.apache.org/repos/asf/hadoop/common/branches/branch-1.0 -r 1214675 Compiled by hortonfo on Thu Dec 15 16:36:35 UTC 2011 The cli hive does not appear. Can someone please give inputs as to how to solve this problem. Thanking you Yours faithfully Ranjan Banerjee
[jira] [Created] (HADOOP-8185) Update namenode -format documentation and add -nonInteractive and -force
Update namenode -format documentation and add -nonInteractive and -force Key: HADOOP-8185 URL: https://issues.apache.org/jira/browse/HADOOP-8185 Project: Hadoop Common Issue Type: Improvement Reporter: Arpit Gupta Assignee: Arpit Gupta documentation changes related to HDFS-3094 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-8171) add -force option to namenode -format command
add -force option to namenode -format command - Key: HADOOP-8171 URL: https://issues.apache.org/jira/browse/HADOOP-8171 Project: Hadoop Common Issue Type: Improvement Affects Versions: 0.24.0, 1.0.2 Reporter: Arpit Gupta Assignee: Arpit Gupta Currently the bin/hadoop namenode -format prompts the user for a Y/N to setup the directories in the local file system. We should add a -force option which when present the user is not prompted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-8132) 64bit secure datanodes do not start as the jsvc path is wrong
64bit secure datanodes do not start as the jsvc path is wrong - Key: HADOOP-8132 URL: https://issues.apache.org/jira/browse/HADOOP-8132 Project: Hadoop Common Issue Type: Bug Affects Versions: 1.0.1 Reporter: Arpit Gupta Assignee: Arpit Gupta 64bit secure datanodes were looking for /usr/libexec/../libexec/jsvc. instead of /usr/libexec/../libexec/jsvc.amd64 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-8106) hadoop-config.sh script defaults to /usr/etc/hadoop rather than /etc/hadoop for the default location of the conf dir
hadoop-config.sh script defaults to /usr/etc/hadoop rather than /etc/hadoop for the default location of the conf dir Key: HADOOP-8106 URL: https://issues.apache.org/jira/browse/HADOOP-8106 Project: Hadoop Common Issue Type: Bug Affects Versions: 1.0.0, 0.24.0 Reporter: Arpit Gupta Assignee: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Hadoop-1.0.1 Release Candidate 1
+1 (non binding) tested on secure and non secure clusters and no regressions were found.On Feb 14, 2012, at 2:29 PM, Matt Foley wrote:Hi all,Hadoop-1.0.1-rc1 is now available at http://people.apache.org/~mattf/hadoop-1.0.1-rc1/Please download it, test it, and vote on whether to accept it as Release1.0.1.Voting will close at 2:30pm PST on Tuesday 21 February.Thank you,--Matt (Release Manager)This is a maintenance release from 1.0.0, but a number ofproduction-relevant bug fixes were requested for inclusion in the last weekor so. The complete release notes are available athttp://people.apache.org/~mattf/hadoop-1.0.1-rc1/RELEASE_NOTES_HADOOP-1.0.1.htmlThe summary list is: - HADOOP-8009 https://issues.apache.org/jira/browse/HADOOP-8009. Create hadoop-client and hadoop-minicluster artifacts for downstream projects - HADOOP-8037 https://issues.apache.org/jira/browse/HADOOP-8037. Binary tarball does not preserve platform info for native builds, and RPMs fail to provide needed symlinks for libhadoop.so - MAPREDUCE-3184https://issues.apache.org/jira/browse/MAPREDUCE-3184. Improve handling of fetch failures when a tasktracker is not responding on HTTP - HADOOP-7470 https://issues.apache.org/jira/browse/HADOOP-7470. move up to Jackson 1.8.8 - HADOOP-7960 https://issues.apache.org/jira/browse/HADOOP-7960. Port HADOOP-5203 to branch-1, build version comparison is too restrictive - HADOOP-7964 https://issues.apache.org/jira/browse/HADOOP-7964. Deadlock in class init. - HADOOP-7987 https://issues.apache.org/jira/browse/HADOOP-7987. Support setting the run-as user in unsecure mode - HADOOP-7988 https://issues.apache.org/jira/browse/HADOOP-7988. Upper case in hostname part of the principals doesn't work with kerberos. - HADOOP-8010 https://issues.apache.org/jira/browse/HADOOP-8010.hadoop-config.sh spews error message when HADOOP_HOME_WARN_SUPPRESS is set to true and HADOOP_HOME is present - HADOOP-8052 https://issues.apache.org/jira/browse/HADOOP-8052. Hadoop Metrics2 should emit Float.MAX_VALUE (instead of Double.MAX_VALUE) to avoid making Ganglia's gmetad core - HDFS-2379 https://issues.apache.org/jira/browse/HDFS-2379. 0.20: Allow block reports to proceed without holding FSDataset lock - HDFS-2814 https://issues.apache.org/jira/browse/HDFS-2814.NamenodeMXBean does not account for svn revision in the version information - MAPREDUCE-3343https://issues.apache.org/jira/browse/MAPREDUCE-3343. TaskTracker Out of Memory because of distributed cache - MAPREDUCE-3607https://issues.apache.org/jira/browse/MAPREDUCE-3607. Port missing new API mapreduce lib classes to 1.x --ArpitHortonworks, Inc.email: ar...@hortonworks.com
[jira] [Created] (HADOOP-8000) fetchdt command not available in bin/hadoop
fetchdt command not available in bin/hadoop --- Key: HADOOP-8000 URL: https://issues.apache.org/jira/browse/HADOOP-8000 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.24.0, 0.23.1 Reporter: Arpit Gupta Assignee: Arpit Gupta fetchdt command needs to be added to bin/hadoop to allow for backwards compatibility. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-8002) SecurityUtil acquired token message should be a debug rather than info
SecurityUtil acquired token message should be a debug rather than info -- Key: HADOOP-8002 URL: https://issues.apache.org/jira/browse/HADOOP-8002 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.24.0, 0.23.1 Reporter: Arpit Gupta Assignee: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7867) jobtracker ui issues
jobtracker ui issues Key: HADOOP-7867 URL: https://issues.apache.org/jira/browse/HADOOP-7867 Project: Hadoop Common Issue Type: Bug Affects Versions: 1.0.0 Reporter: Arpit Gupta Jobtracker UI in 1.0.0 is different from the 0.20.205.0 release. I used firefox on mac os x. Progress bars on the running jobs was blue colored and now has no color and also the quick links used float on the top left rather on on top right. I will attach screen shots to show the differences. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7848) hadoop rpm does not set the correct ownership and permission for the task-controller
hadoop rpm does not set the correct ownership and permission for the task-controller Key: HADOOP-7848 URL: https://issues.apache.org/jira/browse/HADOOP-7848 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Giridharan Kesavan currently the hadoop rpm installs the task-controller binary with the permission -rwxr-xr-x 1 root root 39434 Oct 7 06:26 /usr/bin/task-controller It should belong to user root and group hadoop with permission 6050 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7849) hadoop rpm overwrites the existing /etc/hadoop/hadoop-env.sh
hadoop rpm overwrites the existing /etc/hadoop/hadoop-env.sh Key: HADOOP-7849 URL: https://issues.apache.org/jira/browse/HADOOP-7849 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Giridharan Kesavan The following steps were used to deploy 1. Create /etc/hadoop dir 2. create a file hadoop-env.sh in the above dir 3. install the hadoop rpm (rpm -ivh hadoop-0.20.205.0-1.amd64.rpm) The following console output is displayed Preparing...### [100%] 1:hadoop warning: /etc/hadoop/hadoop-env.sh created as /etc/hadoop/hadoop-env.sh.rpmnew ### [100%] After the install open up the /etc/hadoop/hadoop-env.sh and notice that the file has been replaced. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7850) hadoop rpm does not create the appropriate link for the native files
hadoop rpm does not create the appropriate link for the native files Key: HADOOP-7850 URL: https://issues.apache.org/jira/browse/HADOOP-7850 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Giridharan Kesavan hadoop rpm installs the following files /usr/lib/libhadoop.so /usr/lib/libhadoop.so.1.0.0 From the size it looks like the libhadoop.so.1.0.0 points to the 64 bit native files ls -latr /usr/lib/libhadoop.so.1.0.0 /usr/lib/native/Linux-amd64-64/libhadoop.so -rw-r--r-- 1 root root 177483 Oct 7 06:22 /usr/lib/native/Linux-amd64-64/libhadoop.so -rw-r--r-- 1 root root 177483 Oct 7 06:25 /usr/lib/libhadoop.so.1.0.0 And the libhadoop.so file points to the 32 bit version ls -latr /usr/lib/libhadoop.so /usr/lib/native/Linux-i386-32/libhadoop.so -rw-r--r-- 1 root root 160438 Oct 7 06:20 /usr/lib/native/Linux-i386-32/libhadoop.so -rw-r--r-- 1 root root 160438 Oct 7 06:20 /usr/lib/libhadoop.so This causes the 64bit tasktracker to not load the native libraries unless the libhadoop.so file is linked to the libhadoop.so.1.0.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7812) http call when no authorization is sent throws a 401 with no error resonse
http call when no authorization is sent throws a 401 with no error resonse
--
Key: HADOOP-7812
URL: https://issues.apache.org/jira/browse/HADOOP-7812
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 0.20.205.0
Reporter: Arpit Gupta
Currently if you make an http call to the namenode and do not send any
authorization returns 401 as expected but no response content.
I would be nice if we could return some error response stating that the user
provided no authorization. It would make it a little easier for people making
the call from a browser to find out if something went wrong.
curl call
{code}
curl -i http://NN:PORT/webhdfs/v1/tmp/webhdfs_data?op=gethomedirectory;
HTTP/1.1 401 Unauthorized
Content-Type: text/html; charset=utf-8
WWW-Authenticate: Negotiate
Content-Length: 0
Server: Jetty(6.1.26)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7784) secure datanodes fail to come up stating jscv not found
secure datanodes fail to come up stating jscv not found Key: HADOOP-7784 URL: https://issues.apache.org/jira/browse/HADOOP-7784 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.20.205.1 Reporter: Arpit Gupta building 205.1 and trying to startup a secure dn leads to the following /usr/libexec/../bin/hadoop: line 386: /usr/libexec/../libexec/jsvc.amd64: No such file or directory /usr/libexec/../bin/hadoop: line 386: exec: /usr/libexec/../libexec/jsvc.amd64: cannot execute: No such file or directory -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7751) rpm version is not being picked from the -Dversion option in 205
rpm version is not being picked from the -Dversion option in 205 Key: HADOOP-7751 URL: https://issues.apache.org/jira/browse/HADOOP-7751 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Eric Yang ran ant build -Dversion=0.20.205.1 and the rpm generated is the following hadoop-0.20.205.0-1.amd64.rpm Where as the tar.gz has the correct value hadoop-0.20.205.1.tar.gz the same version string should be applied to tarball and rpms -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] 0.20.205.0 Release Candidate 2
Deployed to a cluster of 20 servers, with security and append features enabled. Passed our internal test suite. Looks good! +1 (non binding) -- Arpit ar...@hortonworks.com On Oct 7, 2011, at 5:10 PM, Matt Foley wrote: Many thanks to the community members who tried out RC1, and found several critical or blocker bugs. These have been resolved and I have now posted RC2 at http://people.apache.org/~mattf/hadoop-0.20.205.0-rc2/ A copy of the Release Notes are provided at the top level of that directory. Appropriate artifacts have also been pushed to the Maven staging repo. Please download and evaluate it, then vote on accepting it as a public release. Voting will close at 1am GMT on Saturday 15 October (6pm PDT, Fri 14 Oct). Best regards, --Matt RM for 0.20.205.0
[jira] [Created] (HADOOP-7732) 204 java docs missing hdfs package
204 java docs missing hdfs package -- Key: HADOOP-7732 URL: https://issues.apache.org/jira/browse/HADOOP-7732 Project: Hadoop Common Issue Type: Bug Components: documentation Affects Versions: 0.20.204.0, 0.20.205.0 Reporter: Arpit Gupta the following link http://hadoop.apache.org/common/docs/current/api/org/apache/hadoop/hdfs/package-summary.html leads to a 404 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7720) improve the hadoop-setup-conf.sh to read in the hbase and setup the configs
improve the hadoop-setup-conf.sh to read in the hbase and setup the configs --- Key: HADOOP-7720 URL: https://issues.apache.org/jira/browse/HADOOP-7720 Project: Hadoop Common Issue Type: Improvement Components: conf Reporter: Arpit Gupta Assignee: Arpit Gupta Read in the hbase user in the script to set the auth to local mapping appropriately in hadoop so hbase can write. If the value is not sent default to 'hbase' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7721) kerberos.principal expects the full hostname and does not replace _HOST with the hostname
kerberos.principal expects the full hostname and does not replace _HOST with the hostname - Key: HADOOP-7721 URL: https://issues.apache.org/jira/browse/HADOOP-7721 Project: Hadoop Common Issue Type: Bug Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7715) see log4j Error when running mr jobs and certain dfs calls
see log4j Error when running mr jobs and certain dfs calls -- Key: HADOOP-7715 URL: https://issues.apache.org/jira/browse/HADOOP-7715 Project: Hadoop Common Issue Type: Bug Components: conf Reporter: Arpit Gupta Fix For: 0.20.205.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7707) improve config generator to allow users to specify proxy user, turn append on or off, turn webhdfs on or off
improve config generator to allow users to specify proxy user, turn append on or off, turn webhdfs on or off Key: HADOOP-7707 URL: https://issues.apache.org/jira/browse/HADOOP-7707 Project: Hadoop Common Issue Type: Improvement Components: conf Affects Versions: 0.20.205.1 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7708) config generator does not update the properties file if on exists already
config generator does not update the properties file if on exists already - Key: HADOOP-7708 URL: https://issues.apache.org/jira/browse/HADOOP-7708 Project: Hadoop Common Issue Type: Bug Components: conf Affects Versions: 0.20.205.1 Reporter: Arpit Gupta We are copying configs to the hadoop conf dir but are not using the -f option. This leads to conf file not getting replaced in case the file exists and thus the user never gets the new conf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7710) create a script to setup application in order to create root directories for application such hbase, hcat, hive etc
create a script to setup application in order to create root directories for application such hbase, hcat, hive etc --- Key: HADOOP-7710 URL: https://issues.apache.org/jira/browse/HADOOP-7710 Project: Hadoop Common Issue Type: Improvement Affects Versions: 0.20.205.1 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7683) hdfs-site.xml template has properties that are not used in 20
hdfs-site.xml template has properties that are not used in 20 - Key: HADOOP-7683 URL: https://issues.apache.org/jira/browse/HADOOP-7683 Project: Hadoop Common Issue Type: Bug Reporter: Arpit Gupta Assignee: Arpit Gupta Priority: Minor properties dfs.namenode.http-address and dfs.namenode.https-address should be removed -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7633) log4j.properties should be added to the hadoop conf on deploy
log4j.properties should be added to the hadoop conf on deploy - Key: HADOOP-7633 URL: https://issues.apache.org/jira/browse/HADOOP-7633 Project: Hadoop Common Issue Type: Bug Components: conf Reporter: Arpit Gupta Fix For: 0.20.205.0 currently the log4j properties are not present in the hadoop conf dir. We should add them so that log rotation happens appropriately and also define other logs that hadoop can generate for example the audit and the auth logs as well as the mapred summary logs etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
