[jira] [Created] (HADOOP-8314) HttpServer#hasAdminAccess should return false if authorization is enabled but user is not authenticated

[Alejandro Abdelnur (JIRA)]

Alejandro Abdelnur created HADOOP-8314:
--

 Summary: HttpServer#hasAdminAccess should return false if 
authorization is enabled but user is not authenticated
 Key: HADOOP-8314
 URL: https://issues.apache.org/jira/browse/HADOOP-8314
 Project: Hadoop Common
  Issue Type: Bug
  Components: security
Affects Versions: 2.0.0, 3.0.0
Reporter: Alejandro Abdelnur
Assignee: Alejandro Abdelnur
 Fix For: 2.0.0
 Attachments: HADOOP-8314.patch

If the user is not authenticated (request.getRemoteUser() returns NULL) or 
there is not authentication filter configured (thus returning also NULL), 
hasAdminAccess should return false. Note that a filter could allow anonymous 
access, thus the first case.


--
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] [Resolved] (HADOOP-8306) ZKFC: improve error message when ZK is not running

[Todd Lipcon (JIRA)]

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

Todd Lipcon resolved HADOOP-8306.
-

   Resolution: Fixed
Fix Version/s: Auto Failover (HDFS-3042)
 Hadoop Flags: Reviewed

Committed to branch, thanks Eli

> ZKFC: improve error message when ZK is not running
> --
>
> Key: HADOOP-8306
> URL: https://issues.apache.org/jira/browse/HADOOP-8306
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: auto-failover, ha
>Affects Versions: Auto Failover (HDFS-3042)
>Reporter: Todd Lipcon
>Assignee: Todd Lipcon
>Priority: Minor
> Fix For: Auto Failover (HDFS-3042)
>
> Attachments: hadoop-8306.txt
>
>
> Currently if you start the ZKFC without starting ZK, you get an ugly stack 
> trace. We should improve the error message and give it a unique exit 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

Re: Hadoop-1.0.3 and 1.1 release / code freeze proposals

[Eli Collins]

On Fri, Apr 20, 2012 at 6:02 PM, Matt Foley  wrote:
> Hi all,
> a couple major bugs have shown up in Hadoop-1.0.2.  I propose to make a
> 1.0.3 release containing fixes for:
>  - MAPREDUCE-4154
>  streaming
> MR job succeeds even if the streaming command fails
>  - HDFS-119  logSync() may
> block NameNode forever.
> We will also accept the following bug fixes already committed to branch-1.0
> (see
> CHANGES.txt): HADOOP-6924, HADOOP-6941, HADOOP-8188, HDFS-3127,
> MAPREDUCE-3377, HADOOP-5528, HADOOP-6963, HADOOP-8251, HADOOP-8293.
>
> If there are other critical bugs you would like to see in 1.0.3, please let
> me know by end of day Monday, 4/23.  I'll start the process of making a
> 1.0.3 RC-1 on Tuesday.
>
> Also, it seems that it is time to do a 1.1 release.  Some 80 bug fixes and
> enhancements have accumulated in branch-1.  Hopefully they've all been
> properly reviewed and unit tested!  Let's declare a code freeze for 1.1 at
> the end of this month.  At that time I will make a branch-1.1 and a release
> candidate for 1.1.0.
>
> Thank you,
> --Matt

I think HDFS-3310 is worth getting into 1.1, and potentially 1.0.3 (or
.4 if it's not done in time).

[jira] [Created] (HADOOP-8313) Add the ability for MetricsRegistry to remove metrics

[Elliott Clark (JIRA)]

Elliott Clark created HADOOP-8313:
-

 Summary: Add the ability for MetricsRegistry to remove metrics
 Key: HADOOP-8313
 URL: https://issues.apache.org/jira/browse/HADOOP-8313
 Project: Hadoop Common
  Issue Type: Improvement
  Components: metrics
Reporter: Elliott Clark


Currently HBase is exposing metrics about a region through 
org.apache.hadoop.metrics.  As regions are moved around or deleted we will want 
to remove the metrics.

--
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-8312) testpatch.sh should provide a simpler way to see which warnings changed

[Robert Joseph Evans (JIRA)]

Robert Joseph Evans created HADOOP-8312:
---

 Summary: testpatch.sh should provide a simpler way to see which 
warnings changed
 Key: HADOOP-8312
 URL: https://issues.apache.org/jira/browse/HADOOP-8312
 Project: Hadoop Common
  Issue Type: Improvement
Reporter: Robert Joseph Evans
Assignee: Robert Joseph Evans


test-patch.sh reports that a specific number of warnings has changed but it 
does not provide an easy way to see which ones have changed.  For at least the 
javac warnings we should be able to provide a diff of the warnings in addition 
to the total count, because we capture the full compile log both before and 
after applying the patch.

For javadoc warnings it would be nice to be able to provide a filtered list of 
the warnings based off of the files that were modified in the patch.

--
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] [Resolved] (HADOOP-3977) SequenceFile.Writer reopen (hdfs append)

[Harsh J (JIRA)]

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

Harsh J resolved HADOOP-3977.
-

Resolution: Duplicate

A fresher effort is ongoing at HADOOP-7139

(Resolving as duplicate)

> SequenceFile.Writer reopen (hdfs append)
> 
>
> Key: HADOOP-3977
> URL: https://issues.apache.org/jira/browse/HADOOP-3977
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: io
>Reporter: Karl Wettin
>Assignee: Karl Wettin
>Priority: Minor
> Attachments: HADOOP-3977.txt, HADOOP-3977.txt
>
>
> Allows for reopening and appending to a SequenceFile

--
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-8311) FSInputStream's positioned read fails to check seek

[Daryn Sharp (JIRA)]

Daryn Sharp created HADOOP-8311:
---

 Summary: FSInputStream's positioned read fails to check seek
 Key: HADOOP-8311
 URL: https://issues.apache.org/jira/browse/HADOOP-8311
 Project: Hadoop Common
  Issue Type: Bug
Affects Versions: 0.23.3, 0.24.0, 2.0.0
Reporter: Daryn Sharp


{{FSInputStream#read(long, byte[], int, int)}} will seek into the input stream, 
but does not check that the seek actually succeeded.

--
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: Hadoop-1.0.3 and 1.1 release / code freeze proposals

[Owen O'Malley]

I also think we need two minor build problems fixed:

HDFS-3316
HADOOP-8307

-- Owen

Re: Hadoop-1.0.3 and 1.1 release / code freeze proposals

[Owen O'Malley]

On Sat, Apr 21, 2012 at 8:18 AM, Kihwal Lee  wrote:
> I think HADOOP-8294 is a good candidate to include. Without this, a transient 
> dns problem can make a large number of data nodes unavailable.  The fix is 
> backport of HADOOP-7428.

I'm +1 on HADOOP-8294 (aka HADOOP-7428). Matt?

Re: Log file

[shashwat shriparv]

http://code.google.com/p/hop/source/browse/branches/hop-streaming/src/examples/org/apache/hadoop/examples/streams/StreamLogger.java?r=118

On Tue, Apr 24, 2012 at 10:46 AM, madhu phatak  wrote:

> Just see the $HADOOP_HOME/logs directory in tasktracker nodes.
>
> On Tue, Apr 24, 2012 at 6:28 AM, Ranjan Banerjee  >wrote:
>
> > Can someone point me to the java file that logs all the information in
> the
> > output of a mapreduce job,.
> >
>
>
>
> --
> https://github.com/zinnia-phatak-dev/Nectar
>



-- 


∞
Shashwat Shriparv

Jenkins build is back to normal : Hadoop-Common-0.23-Build #232

[Apache Jenkins Server]

See 

Build failed in Jenkins: Hadoop-Common-trunk #386

[Apache Jenkins Server]

See 

Changes:

[eli] HADOOP-8152. Expand public APIs for security library classes. Contributed 
by Aaron T. Myers

[tucu] MAPREDUCE-4141. clover integration broken, also mapreduce poms are 
pulling in clover as a dependency. (phunt via tucu)

[tucu] HADOOP-8284. clover integration broken, also mapreduce poms are pulling 
in clover as a dependency. (phunt via tucu)

[szetszwo] HDFS-3312. In HftpFileSystem, the namenode URI is non-secure but the 
delegation tokens have to use secure URI.  Contributed by Daryn Sharp

[bobby] MAPREDUCE-4133. MR over viewfs is broken (John George via bobby)

[bobby] MAPREDUCE-4190. Improve web UI for task attempts userlog link (Tom 
Graves via bobby)

[sradia] HADOOP-8285 Use ProtoBuf for RpcPayLoadHeader (sanjay radia)

[bobby] MAPREDUCE-3812. Lower default allocation sizes, fix allocation 
configurations and document them (Harsh J via bobby)

--
[...truncated 44831 lines...]
[DEBUG]   (f) reactorProjects = [MavenProject: 
org.apache.hadoop:hadoop-annotations:3.0.0-SNAPSHOT @ 

 MavenProject: org.apache.hadoop:hadoop-auth:3.0.0-SNAPSHOT @ 

 MavenProject: org.apache.hadoop:hadoop-auth-examples:3.0.0-SNAPSHOT @ 

 MavenProject: org.apache.hadoop:hadoop-common:3.0.0-SNAPSHOT @ 

 MavenProject: org.apache.hadoop:hadoop-common-project:3.0.0-SNAPSHOT @ 

[DEBUG]   (f) useDefaultExcludes = true
[DEBUG]   (f) useDefaultManifestFile = false
[DEBUG] -- end configuration --
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0:enforce (dist-enforce) @ 
hadoop-common-project ---
[DEBUG] Configuring mojo 
org.apache.maven.plugins:maven-enforcer-plugin:1.0:enforce from plugin realm 
ClassRealm[plugin>org.apache.maven.plugins:maven-enforcer-plugin:1.0, parent: 
sun.misc.Launcher$AppClassLoader@126b249]
[DEBUG] Configuring mojo 
'org.apache.maven.plugins:maven-enforcer-plugin:1.0:enforce' with basic 
configurator -->
[DEBUG]   (s) fail = true
[DEBUG]   (s) failFast = false
[DEBUG]   (f) ignoreCache = false
[DEBUG]   (s) project = MavenProject: 
org.apache.hadoop:hadoop-common-project:3.0.0-SNAPSHOT @ 

[DEBUG]   (s) version = [3.0.2,)
[DEBUG]   (s) version = 1.6
[DEBUG]   (s) rules = 
[org.apache.maven.plugins.enforcer.RequireMavenVersion@4c9105, 
org.apache.maven.plugins.enforcer.RequireJavaVersion@c51ae9]
[DEBUG]   (s) session = org.apache.maven.execution.MavenSession@1184a4f
[DEBUG]   (s) skip = false
[DEBUG] -- end configuration --
[DEBUG] Executing rule: org.apache.maven.plugins.enforcer.RequireMavenVersion
[DEBUG] Rule org.apache.maven.plugins.enforcer.RequireMavenVersion is cacheable.
[DEBUG] Key org.apache.maven.plugins.enforcer.RequireMavenVersion -937312197 
was found in the cache
[DEBUG] The cached results are still valid. Skipping the rule: 
org.apache.maven.plugins.enforcer.RequireMavenVersion
[DEBUG] Executing rule: org.apache.maven.plugins.enforcer.RequireJavaVersion
[DEBUG] Rule org.apache.maven.plugins.enforcer.RequireJavaVersion is cacheable.
[DEBUG] Key org.apache.maven.plugins.enforcer.RequireJavaVersion 48569 was 
found in the cache
[DEBUG] The cached results are still valid. Skipping the rule: 
org.apache.maven.plugins.enforcer.RequireJavaVersion
[INFO] 
[INFO] --- maven-site-plugin:3.0:attach-descriptor (attach-descriptor) @ 
hadoop-common-project ---
[DEBUG] Configuring mojo 
org.apache.maven.plugins:maven-site-plugin:3.0:attach-descriptor from plugin 
realm ClassRealm[plugin>org.apache.maven.plugins:maven-site-plugin:3.0, parent: 
sun.misc.Launcher$AppClassLoader@126b249]
[DEBUG] Configuring mojo 
'org.apache.maven.plugins:maven-site-plugin:3.0:attach-descriptor' with basic 
configurator -->
[DEBUG]   (f) basedir = 

[DEBUG]   (f) inputEncoding = UTF-8
[DEBUG]   (f) localRepository =id: local
  url: file:///home/jenkins/.m2/repository/
   layout: none

[DEBUG]   (f) outputEncoding = UTF-8
[DEBUG]   (f) pomPackagingOnly = true
[DEBUG]   (f) project = MavenProject: 
org.apache.hadoop:hadoop-common-project:3.0.0-SNAPSHOT @ 

[DEBUG]   (f) reactorProjects = [MavenProject: 
org.apache.hadoop:hadoop-annotations:3.0.0-SNAPSHOT @ 

[jira] [Created] (HADOOP-8310) FileContext#checkPath should handle URIs with no port

[Aaron T. Myers (JIRA)]

Aaron T. Myers created HADOOP-8310:
--

 Summary: FileContext#checkPath should handle URIs with no port
 Key: HADOOP-8310
 URL: https://issues.apache.org/jira/browse/HADOOP-8310
 Project: Hadoop Common
  Issue Type: Bug
  Components: fs
Affects Versions: 2.0.0
Reporter: Aaron T. Myers
Assignee: Aaron T. Myers


AbstractFileSystem#checkPath is used to verify that a given path is for the 
same file system as represented by the AbstractFileSystem instance.

The original intent of the code was to allow for no port to be provided in the 
checked path, if the default port was being used by the AbstractFileSystem 
instance. However, before performing port handling, AFS#checkPath compares the 
full URI authorities for equality. Since the URI authority includes the port, 
the port handling code is never reached, and thus valid paths may be 
erroneously considered invalid.

--
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