not really Kerberos issues.
> > Yes, we do understand that making Kerberos work *in a right way* is
> always
> > an uphill task (I'm a long time Kerberos+Hadoop Support Engineer) but
> that
> > shouldn't be the reason to replace it.
> >
> > Hint: CVE-2020-9492
.
regards,
Eric
On Thu, May 21, 2020 at 9:22 AM Steve Loughran
wrote:
> On Wed, 6 May 2020 at 23:32, Eric Yang wrote:
>
> > Hi all,
> >
> >
> > 4. Passing different form of tokens does not work well with cloud
> provider
> > security mechanism. For examp
See my comments inline:
On Wed, May 20, 2020 at 4:50 PM Rajive Chittajallu wrote:
> On Wed, May 20, 2020 at 1:47 PM Eric Yang wrote:
> >
> >> > Kerberos was developed decade before web development becomes popular.
> >> > There are some Kerberos limitations whi
DC
> and that way operating costs will be reduced.
>
> Regards,
> Akira
>
> On Thu, May 7, 2020 at 7:32 AM Eric Yang wrote:
>
>> Hi all,
>>
>> Kerberos was developed decade before web development becomes popular.
>> There are some Kerberos limitations which does
ProtobufHelper should not be a public API. Hadoop uses protobuf
serialization to expertise RPC performance with many drawbacks. The
generalized object usually require another indirection to map to usable
Java object, this is making Hadoop code messy, and that is topic for
another day. The main
If I recall this problem correctly, the root cause is the default zstd
compression block size is 256kb, and Hadoop Zstd compression will attempt
to use the OS platform default compression size, if it is available. The
recommended output size is slightly bigger than input size to account for
Hi all,
Kerberos was developed decade before web development becomes popular.
There are some Kerberos limitations which does not work well in Hadoop. A
few examples of corner cases:
1. Kerberos principal doesn't encode port number, it is difficult to know
if the principal is coming from an
[
https://issues.apache.org/jira/browse/HADOOP-16590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved HADOOP-16590.
Fix Version/s: 3.3.0
Resolution: Fixed
[~nmarion] Thanks for the patch. I merged pull
[
https://issues.apache.org/jira/browse/HADOOP-16614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved HADOOP-16614.
Fix Version/s: 3.3.0
Resolution: Fixed
Thank you [~seanlau] for the patch.
+1 merged
Eric Yang created HADOOP-16463:
--
Summary: Migrate away from jsr305 jar
Key: HADOOP-16463
URL: https://issues.apache.org/jira/browse/HADOOP-16463
Project: Hadoop Common
Issue Type: Bug
Eric Yang created HADOOP-16457:
--
Summary: Hadoop does not work without Kerberos for simple security
Key: HADOOP-16457
URL: https://issues.apache.org/jira/browse/HADOOP-16457
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-16095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved HADOOP-16095.
Resolution: Fixed
All related tasks have been closed, mark this as resolved.
Thank you
[
https://issues.apache.org/jira/browse/HADOOP-16356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved HADOOP-16356.
Resolution: Duplicate
> Distcp with webhdfs is not working with ProxyUserAuthenticationFil
[
https://issues.apache.org/jira/browse/HADOOP-16095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang reopened HADOOP-16095:
Found an issue with distcp backward compatibility, opened HADOOP-16356 to track
required changes
Eric Yang created HADOOP-16356:
--
Summary: Distcp with webhdfs is not working with
ProxyUserAuthenticationFilter or AuthenticationFilter
Key: HADOOP-16356
URL: https://issues.apache.org/jira/browse/HADOOP-16356
[
https://issues.apache.org/jira/browse/HADOOP-16095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved HADOOP-16095.
Resolution: Fixed
Fix Version/s: 3.3.0
The current implementation is based on option 1
Eric Yang created HADOOP-16325:
--
Summary: Add ability to run pytthon test and build docker in
docker in start-build-env.sh
Key: HADOOP-16325
URL: https://issues.apache.org/jira/browse/HADOOP-16325
Eric Yang created HADOOP-16314:
--
Summary: Make sure all end point URL is covered by the same
AuthenticationFilter
Key: HADOOP-16314
URL: https://issues.apache.org/jira/browse/HADOOP-16314
Project
ockerfile would be
> adjusted).
>
> Marton
>
> ps: for the development (non published images) I am convinced that the
> optional docker profile can be an easier way to create images. Will
> create a similar plugin execution for this Dockerfile:
>
> https://github.com/apache/hadoop/t
+1
On 4/29/19, 9:05 PM, "Ajay Kumar" wrote:
Hi All,
We have created the third release candidate (RC2) for Apache Hadoop Ozone
0.4.0-alpha.
This release contains security payload for Ozone. Below are some important
features in it:
Eric Yang created HADOOP-16236:
--
Summary: Update C code to run with c99 standard
Key: HADOOP-16236
URL: https://issues.apache.org/jira/browse/HADOOP-16236
Project: Hadoop Common
Issue Type
The flexibility of date appended release number is equivalent to maven snapshot
or Docker latest image convention, machine can apply timestamp better than
human. By using the Jenkins release process, this can be done with little
effort. For official release, it is best to use Docker image
IBM JDK is one of the Java that default ticket cache to different than
/tmp/krb5* path. If I recall correctly, most logic had been implemented in UGI
by passing ticketCachePath parameter in 2012-13 time frame. The new addition
will follow the MIT Kerberos lookup order, this is a good
,
Eric
From: Jonathan Eagles
Date: Tuesday, March 19, 2019 at 11:48 AM
To: Eric Yang
Cc: "Elek, Marton" , Hadoop Common
, "yarn-...@hadoop.apache.org"
, Hdfs-dev , Eric
Badger , Eric Payne ,
Jim Brennan
Subject: Re: [DISCUSS] Docker build process
This email discussion
terms or share a link to the description?
> I will make adjustment accordingly unless 7 more people comes
> out and say otherwise.
What adjustment is this?
Thanks,
Arpit
> On Mar 19, 2019, at 10:19 AM, Eric Yang wrote:
>
> Hi Ma
jdk8/jdk11). In Hadoop, profiles are used to introduce optional
steps. I think it's fine as the maven lifecycle/phase model is very
static (compare it with the tree based approach in Gradle).
Marton
[1]: https://issues.apache.org/jira/browse/HADOOP-16091
On 3/13/19 11:
Loughran
Date: Monday, March 18, 2019 at 3:36 AM
To: Eric Yang
Cc: Hadoop Common , "yarn-...@hadoop.apache.org"
, Hdfs-dev , Eric
Badger , Eric Payne ,
Jonathan Eagles , Jim Brennan
, "Elek, Marton"
Subject: Re: [DISCUSS] Docker build process
I'm not enthusiastic about mak
Hi Hadoop developers,
In the recent months, there were various discussions on creating docker build
process for Hadoop. There was convergence to make docker build process inline
in the mailing list last month when Ozone team is planning new repository for
Hadoop/ozone docker images. New
[
https://issues.apache.org/jira/browse/HADOOP-16106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved HADOOP-16106.
Resolution: Duplicate
This is a duplicate of HADOOP-16098.
> hadoop-aws project javadoc d
Eric Yang created HADOOP-16106:
--
Summary: hadoop-aws project javadoc does not compile
Key: HADOOP-16106
URL: https://issues.apache.org/jira/browse/HADOOP-16106
Project: Hadoop Common
Issue Type
Eric Yang created HADOOP-16094:
--
Summary: AuthenticationFilter can trigger NullPointerException in
KerberosName class
Key: HADOOP-16094
URL: https://issues.apache.org/jira/browse/HADOOP-16094
Project
AM
To: Eric Yang
Cc: Weiwei Yang , Xun Liu , Hadoop
Common , "yarn-...@hadoop.apache.org"
, Hdfs-dev ,
"mapreduce-...@hadoop.apache.org"
Subject: Re: [DISCUSS] Making submarine to different release model like Ozone
Thanks everyone for sharing thoughts!
Eric, appreci
Submarine is an application built for YARN framework, but it does not have
strong dependency on YARN development. For this kind of projects, it would be
best to enter Apache Incubator cycles to create a new community. Apache
commons is the only project other than Incubator that has
Thanks a lot,
Marton
On 1/30/19 6:50 PM, Eric Yang wrote:
> Hi Marton,
>
> Hi Marton,
>
> Flagging automated build on dockerhub seems conflicts with Apache release
policy. The vote and release process are manual processes of Apache Way.
T
a Apache account?
>
>
> Thanks
> Anu
>
>
> On 1/29/19, 4:54 PM, "Eric Yang" wrote:
>
> By separating Hadoop docker related build into a separate git
repository have some slippery slope. It is harder to synchronize the change
By separating Hadoop docker related build into a separate git repository have
some slippery slope. It is harder to synchronize the changes between two
separate source trees. There is multi-steps process to build jar, tarball, and
docker images. This might be problematic to reproduce.
It
[
https://issues.apache.org/jira/browse/HADOOP-15959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved HADOOP-15959.
Resolution: Fixed
The failed registry DNS unit test has been addressed in HADOOP-16031. Hence
Eric Yang created HADOOP-15996:
--
Summary: Plugin interface to support more complex usernames in
Hadoop
Key: HADOOP-15996
URL: https://issues.apache.org/jira/browse/HADOOP-15996
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-15922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang reopened HADOOP-15922:
> DelegationTokenAuthenticationFilter get wrong doAsUser since it does not
> deco
Eric Yang created HADOOP-15896:
--
Summary: Refine Kerberos based AuthenticationHandler to check
proxyuser ACL
Key: HADOOP-15896
URL: https://issues.apache.org/jira/browse/HADOOP-15896
Project: Hadoop
[
https://issues.apache.org/jira/browse/HADOOP-15821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang reopened HADOOP-15821:
> Move Hadoop YARN Registry to Hadoop Regis
[
https://issues.apache.org/jira/browse/HADOOP-15670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved HADOOP-15670.
Resolution: Not A Problem
> UserGroupInformation TGT renewer thread doesn't use monotonica
Most of code coverage tools can instrument java classes without make any
source code changes, but tracing distributed system is more involved because
code execution via network interactions are not easy to match up.
All interactions between sender and receiver have some form of session id
or
Hi Sunil,
For YARN service and docker related work, I like to propose the following
features to be merged:
YARN-7129 Application Catalog for YARN applications
YARN-7512 Support service upgrade via YARN Service API and CLI
YARN-8220 Running Tensorflow on YARN with GPU and Docker - Examples
Eric Yang created HADOOP-15601:
--
Summary: Change yarn.admin.acl setting to be more restricted
Key: HADOOP-15601
URL: https://issues.apache.org/jira/browse/HADOOP-15601
Project: Hadoop Common
Eric Yang created HADOOP-15600:
--
Summary: Set default proxy user settings to non-routable IP
addresses and default users group
Key: HADOOP-15600
URL: https://issues.apache.org/jira/browse/HADOOP-15600
[
https://issues.apache.org/jira/browse/HADOOP-15597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved HADOOP-15597.
Resolution: Duplicate
> UserGroupInformation class throws NPE when Kerberos TGT expi
Eric Yang created HADOOP-15597:
--
Summary: UserGroupInformation class throws NPE when Kerberos TGT
expired
Key: HADOOP-15597
URL: https://issues.apache.org/jira/browse/HADOOP-15597
Project: Hadoop Common
Eric Yang created HADOOP-15588:
--
Summary: Add proxy acl check for AuthenticationFilter
Key: HADOOP-15588
URL: https://issues.apache.org/jira/browse/HADOOP-15588
Project: Hadoop Common
Issue
Eric Yang created HADOOP-15587:
--
Summary: Securing ASF Hadoop releases out of the box
Key: HADOOP-15587
URL: https://issues.apache.org/jira/browse/HADOOP-15587
Project: Hadoop Common
Issue Type
+1 on Non-routable IP idea. My preference is to start in Hadoop-common to
minimize the scope and incrementally improve. However, this will be
incompatible change for initial user experience on public cloud. What would be
the right release vehicle for this work (3.2+ or 4.x)?
Regards,
Eric
+1
On 7/5/18, 2:44 PM, "Giovanni Matteo Fumarola"
wrote:
+1
On Thu, Jul 5, 2018 at 2:41 PM, Wangda Tan wrote:
> +1
>
> On Thu, Jul 5, 2018 at 2:37 PM Subru Krishnan wrote:
>
> > Folks,
> >
> > There was a merge commit accidentally pushed to
Hadoop default configuration aimed for user friendliness to increase adoption,
and security can be enabled one by one. This approach is most problematic to
security because system can be compromised before all security features are
turned on.
Larry's proposal will add some safety to remind
Eric Yang created HADOOP-15284:
--
Summary: Could not determine real path of mount
Key: HADOOP-15284
URL: https://issues.apache.org/jira/browse/HADOOP-15284
Project: Hadoop Common
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HADOOP-14077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang reopened HADOOP-14077:
> Improve the patch of HADOOP-13119
> -
>
>
Eric Yang created HADOOP-15222:
--
Summary: Refine proxy user authorization to support multiple ACL
list
Key: HADOOP-15222
URL: https://issues.apache.org/jira/browse/HADOOP-15222
Project: Hadoop Common
gt; - What if someone is already using 3.0.0 and has changed
>> all the scripts to 9820? Just let them fail?
>> - Compared to 2.x, 3.0.0 has many incompatible changes. Are
>> we going to have other incompatible changes in the future minor and dot
&
, 2018 at 7:36 PM
To: Eric Yang <ey...@hortonworks.com>
Cc: "Aaron T. Myers" <a...@apache.org>, Daryn Sharp <da...@oath.com>, Hadoop
Common <common-dev@hadoop.apache.org>, larry mccay <lmc...@apache.org>
Subject: Re: When are incompatible changes acceptable
ary 10, 2018 at 10:53 AM
To: Daryn Sharp <da...@oath.com>
Cc: "Aaron T. Myers" <a...@apache.org>, Eric Yang <ey...@hortonworks.com>,
Chris Douglas <cdoug...@apache.org>, Hadoop Common
<common-dev@hadoop.apache.org>
Subject: Re: When are incompatible changes
[
https://issues.apache.org/jira/browse/HADOOP-15162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved HADOOP-15162.
Resolution: Not A Problem
Close this as not a problem. Bad assumption for SIMPLE security mode
See comments inline.
Regards,
Eric
From: <a...@cloudera.com> on behalf of "Aaron T. Myers" <a...@apache.org>
Date: Wednesday, January 10, 2018 at 9:21 AM
To: Eric Yang <ey...@hortonworks.com>
Cc: Chris Douglas <cdoug...@apache.org>, larry mccay <lmc...@ap
..@apache.org>
Date: Tuesday, January 9, 2018 at 9:22 PM
To: Eric Yang <ey...@hortonworks.com>
Cc: Chris Douglas <cdoug...@apache.org>, larry mccay <lmc...@apache.org>,
Hadoop Common <common-dev@hadoop.apache.org>
Subject: Re: When are incompatible changes acceptable (HDF
While I agree the original port change was unnecessary, I don’t think Hadoop NN
port change is a bad thing.
I worked for a Hadoop distro that NN RPC port was default to port 9000. When
we migrate from BigInsights to IOP and now to HDP, we have to move customer
Hive metadata to new NN RPC
Eric Yang created HADOOP-15162:
--
Summary: UserGroupInformation.createRmoteUser hardcode
authentication method to SIMPLE
Key: HADOOP-15162
URL: https://issues.apache.org/jira/browse/HADOOP-15162
Project
[
https://issues.apache.org/jira/browse/HADOOP-10054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang reopened HADOOP-10054:
This patch broke trunk development. Please run unit test:
{code}
mvn clean test -Dtest
Friday, December 15, 2017 at 11:06 AM
To: Eric Yang <ey...@hortonworks.com>
Cc: Chris Douglas <cdoug...@apache.org>, Eric Yang <ey...@apache.org>, Arun
Suresh <asur...@apache.org>, Sunil G <sun...@apache.org>, Hadoop Common
<common-dev@hadoop.apache.org>
Subj
+1 for merge –no-ff for feature merge.
Do we all agree on this optimization for going forward?
Regards,
Eric
On 12/15/17, 10:34 AM, "Chris Douglas" <cdoug...@apache.org> wrote:
On Thu, Dec 14, 2017 at 9:40 PM, Eric Yang <ey...@apache.org> wrote:
> I am looking
On Thu, Dec 14, 2017 at 6:52 PM, Chris Douglas <cdoug...@apache.org> wrote:
> Eric-
>
> What problem are you trying to solve? Most of us understand how git works,
> you can omit that. -C
>
> On Thu, Dec 14, 2017 at 6:31 PM Eric Yang <ey...@hortonworks.com> wrote:
>
On Thu, Dec 14, 2017 at 2:31 PM Eric Yang <ey...@hortonworks.com> wrote:
> When details are rebased, the number of entries to test through the linear
> history is much more than a merge point to isolate where the error might
> have occurred. It is similar to trav
it so it's clear the branch was developed
outside the mainline. -C
On Thu, Dec 14, 2017 at 1:18 PM, Eric Yang <ey...@hortonworks.com> wrote:
> +1 on squash merge to keep history compressed. The rebase + merge
contains good deals, but it is easy to get confused for people
he.org> wrote:
Another option - atleast for feature branches is to maybe squash merge -
this way we see it as a single commit ? Although we will loose the feature
branch history (I am ok with that though)
Cheers
-Arun
On Thu, Dec 14, 2017 at 11:32 AM, Eric Yang <ey
the root cause of trunk failure was due to merge or some recent commits.
Regards,
Eric
From: Sunil G <sun...@apache.org>
Date: Thursday, December 14, 2017 at 11:11 AM
To: Eric Yang <ey...@hortonworks.com>
Cc: Hadoop Common <common-dev@hadoop.apache.org>
Subject: Re: Missing some tr
Hi all,
While troubleshooting a trunk build failure, I notice the commit history for
trunk between Nov 30th to Dec 6th are squashed or disappeared for no reason.
This seems to have taken place in the last 24 hours. I can see the commit logs
from github UI. When doing a new clone from Apache
- YARN-6419[4]. UI support for native-services on the new YARN UI
> > All these new services are optional and are sitting outside of the
> > existing system, and have no impact on existing system if disabled.
> >
> > Special thanks to a team of folks who worked
Looks good and +1 for markdown documentations to provide per release
specific information.
On Sat, Oct 21, 2017 at 8:47 AM, larry mccay wrote:
> New Revision...
>
> This revision acknowledges the reality that we often have multiple phases
> of feature lifecycle and that we
The check list looks good. Some more items to add:
Kerberos
TGT renewal
SPNEGO support
Delegation token
Proxy User ACL
CVE tracking list
We might want to start a security section for Hadoop wiki for each of the
services and components.
This helps to track what has been completed.
How
Eric Yang created HADOOP-14967:
--
Summary: Use jetty CORS filter for web interface
Key: HADOOP-14967
URL: https://issues.apache.org/jira/browse/HADOOP-14967
Project: Hadoop Common
Issue Type
Hi Allen,
What if the commands are:
yarn application -deploy –f spec.json
yarn application -stop
yarn application -restart
yarn application -remove
and
yarn application –list will display both application list from RM as well as
docker services?
I think the development team was concerned
On Mon, Oct 2, 2017 at 2:12 PM, Eric Yang <ey...@hortonworks.com> wrote:
> Mock provides tool chains to run simulation for a piece of code. It
helps to prevent null pointer exception, and reduce unexpected runtime
exceptions. When a piece of code is finished with
n <ste...@hortonworks.com>
Date: Sunday, October 1, 2017 at 12:36 PM
To: Eric Yang <ey...@hortonworks.com>
Cc: Andrew Wang <andrew.w...@cloudera.com>, Chris Douglas
<cdoug...@apache.org>, "common-dev@hadoop.apache.org"
<common-dev@hadoop.apache.org>
Subjec
to
rethink the improvement that Powermock can bring to the table. Thank you for
your considation.
Regards,
Eric
From: Andrew Wang <andrew.w...@cloudera.com>
Date: Friday, September 29, 2017 at 1:55 PM
To: Chris Douglas <cdoug...@apache.org>
Cc: Eric Yang <ey...@hortonworks.co
Hi Hadoop-dev,
Long time ago, Hadoop community decided to put Powermock on hold for unit
tests. Both mockito and powermock has evolved a lot in the past 5 years.
There are mature versions of both software, and there are compatibility charts
to indicate which versions can work together.
[
https://issues.apache.org/jira/browse/HADOOP-9122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang reopened HADOOP-9122:
---
Assignee: Eric Yang (was: Radim Kolar)
Reopening this old issue. Powermockito is great
[
https://issues.apache.org/jira/browse/HADOOP-13119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang reopened HADOOP-13119:
> Web UI authorization error accessing /logs/ when Kerbe
Hi Gregorio,
${BASH_SOURCE-$0} is not a bug. That is a short hand notation for locating
the script's directory. There are some legacy reasons for this arrangement.
$bin in hadoop-daemon[s].sh are designed to run in both development and
binary deployment environment. Where $bin is hadoop
Hi Andrew,
Many Apache projects already have Github integration. Chukwa also has
Github integration. Pull request can be integrated into JIRA, i.e.
https://issues.apache.org/jira/browse/CHUKWA-783
This allows code review process to happen at per line level on Github, or
comment on JIRA for
[
https://issues.apache.org/jira/browse/HADOOP-12110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved HADOOP-12110.
Resolution: Invalid
Opened for the wrong project. Sorry, close as invalid.
Consolidate usage
Eric Yang created HADOOP-12110:
--
Summary: Consolidate usage of JSON libraries
Key: HADOOP-12110
URL: https://issues.apache.org/jira/browse/HADOOP-12110
Project: Hadoop Common
Issue Type: Bug
Some lesson learn during 2.x. WebHDFS, HDFS ACL, QJM HA, rolling upgrade
are great features. Mapreduce 1.x uses resources more efficiently,
containers have rigid constraint, and applications get killed prematurely.
When a node has a lot of containers, YARN takes significant amount of
system
[
https://issues.apache.org/jira/browse/HADOOP-10759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved HADOOP-10759.
Resolution: Fixed
Allen, this JIRA is filed for Hadoop Common, YARN problems can be addressed
Single node developer build may be supported independently from
package installed builds. There are multiple ways to achieve this.
The current method is using shell script to support different
deployment conditions. This is a awkward and inefficient way to
maintain compatibility to support
[
https://issues.apache.org/jira/browse/HADOOP-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved HADOOP-7751.
---
Resolution: Won't Fix
For maven, the number number includes -SNAPSHOT for on going builds
Components: build
Affects Versions: 0.20.205.0
Environment: Java, ant
Reporter: Eric Yang
Assignee: Eric Yang
Fix For: 0.20.205.1
When packaging is invoked as ant clean tar deb. The system creates both
system layout and tarball layout in the same build
Components: scripts
Affects Versions: 0.20.205.0
Environment: Linux RHEL6
Reporter: Eric Yang
Assignee: Eric Yang
Priority: Minor
kinit location is in /usr/kerberos/bin in RHEL5, and switched to /usr/bin in
RHEL6. Hence, it may be better to support
+1 (non-binding)
Exercised Hadoop 0.20.205 with HBase 0.90.4+, Pig 0.9.1+, Chukwa trunk on 20
nodes clusters, works fine.
regards,
Eric
On Oct 13, 2011, at 5:46 PM, Aaron T. Myers wrote:
+1 (non-binding)
I downloaded the tar ball and deployed on a 6 node cluster with security
disabled. I
[
https://issues.apache.org/jira/browse/HADOOP-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved HADOOP-7731.
---
Resolution: Duplicate
Fix Version/s: 0.20.205.0
Assignee: Eric Yang
This is fixed
: Bug
Components: scripts
Affects Versions: 0.20.205.0, 0.23.0
Environment: Java, Linux
Reporter: Eric Yang
Assignee: Eric Yang
Fix For: 0.20.205.0, 0.23.0
The current set of init.d scripts can start/stop process for:
namenode
datanode
Components: build
Affects Versions: 0.20.205.0
Reporter: Eric Yang
Assignee: Eric Yang
Fix For: 0.20.205.0
205 build of tar is fine, but rpm failed with:
{noformat}
[rpm] Processing files: hadoop-0.20.205.0-1
[rpm] warning: File listed twice: /usr
Components: scripts
Affects Versions: 0.20.205.0
Environment: Java, Linux
Reporter: Eric Yang
Assignee: Eric Yang
Fix For: 0.20.205.0
Quote email from Ashutosh Chauhan:
bq. There is a bug in hadoop-env.sh which prevents hcatalog server to start
increase/reduce the
risk of dead code and how they make more-difficult/easier the
packagedeployment.
Would you please explain this?
Thanks.
Alejandro
On Tue, Sep 6, 2011 at 6:38 PM, Eric Yang eric...@gmail.com wrote:
Option #2 proposed by Amareshwari, seems like a better proposal. We don't
1 - 100 of 120 matches
Mail list logo