+1 (binding)
On Thu, Jun 3, 2021 at 1:14 AM Akira Ajisaka wrote:
> Dear Hadoop developers,
>
> Given the feedback from the discussion thread [1], I'd like to start
> an official vote
> thread for the community to vote and start the 3.1 EOL process.
>
> What this entails:
>
> (1) an official
+1 for the 100 char limit.
But I would have liked 132 columns more. :)
Kihwal
On Mon, May 24, 2021 at 1:46 PM Sean Busbey
wrote:
> Hi folks!
>
> The consensus seems pretty strongly in favor of increasing the line length
> limit. Do folks still want to see a formal VOTE thread?
>
>
> > On May
Gabor,
If you want to release asap, you can simply revert HDFS-14941 in the
release branch for now. It is causing the issue and was committed after
3.1.3. This causes failure of the automated upgrade process and namenode
memory leak.
Kihwal
On Tue, Jun 23, 2020 at 8:47 AM Akira Ajisaka wrote:
+1
Kihwal
On Tue, Aug 20, 2019 at 10:03 PM Wangda Tan wrote:
> Hi all,
>
> This is a vote thread to mark any versions smaller than 2.7 (inclusive),
> and 3.0 EOL. This is based on discussions of [1]
>
> This discussion runs for 7 days and will conclude on Aug 28 Wed.
>
> Please feel free to
Kihwal Lee created MAPREDUCE-7177:
-
Summary: Disable speculative execution in TestDFSIO
Key: MAPREDUCE-7177
URL: https://issues.apache.org/jira/browse/MAPREDUCE-7177
Project: Hadoop Map/Reduce
+1 (binding)
- Built from source
- Brought up a single node cluster
- Checked basic HDFS functions and checked the UIs
- Ran several simple jobs.
On Mon, Sep 10, 2018 at 7:01 AM 俊平堵 wrote:
> Hi all,
>
> I've created the first release candidate (RC0) for Apache
> Hadoop 2.8.5. This is our
HADOOP-14060 is a blocker. Daryn will add more detail to the jira or to
this thread.
On Thu, Feb 8, 2018 at 7:01 AM, Brahma Reddy Battula
wrote:
> Hi Eddy,
>
> HDFS-12990 got committed to 3.0.1,can we have RC for 3.0.1 (only YARN-5742
> blocker is open ) ?
>
>
> On Sat,
Thanks for driving the next 2.8 release, Junping. While I was committing a
blocker for 2.7.4, I noticed some of the jiras are back-ported to 2.7, but
missing in branch-2.8.2. Perhaps it is safer and easier to simply rebranch
2.8.2.
Thanks,Kihwal
On Thursday, July 20, 2017, 3:32:16 PM CDT,
Kihwal Lee created MAPREDUCE-6767:
-
Summary: TestSlive fails after a common change
Key: MAPREDUCE-6767
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6767
Project: Hadoop Map/Reduce
You might want the snapshot bug fix done in HDFS-7056. This bug creates
snapshot filediffs even if you never use snapshot. For 2.6, we will have to do
it in a separate jira to pick up the fix only. Related to this, HDFS-9696 might
be of interest too.
Kihwal
From: Chris Trezzo
Just reverted HDFS-8791 from branch-2.7.Eulogy: Although it has ascended to a
better version, it did caught an upgrade bug while in branch-2.7.
Kihwal
From: Vinod Kumar Vavilapalli
To: yarn-...@hadoop.apache.org
Cc: Hadoop Common ;
Moving Hadoop 3 forward sounds fine. If EC is one of the main motivations, are
we getting rid of branch-2.8?
Kihwal
From: Andrew Wang
To: "common-...@hadoop.apache.org"
Cc: "yarn-...@hadoop.apache.org"
+1 (binding)Checked out the source and built.Ran basic hdfs and mapred tests on
a single node cluster
Kihwal
From: Vinod Kumar Vavilapalli
To: Hadoop Common ; hdfs-...@hadoop.apache.org;
yarn-...@hadoop.apache.org;
+1 (binding)- Verified the signature/digest.
- I've built the dist tree with the native support from the source.- Brought up
a single node cluster and ran a set of basic tests.
From: Vinod Kumar Vavilapalli
To: Hadoop Common ;
We found HDFS-9426. The rolling upgrade finalization is not backward
compatible.I.e. 2.7.1 or 2.6.x datanodes will ignore finalization.
So -1.
Kihwal
From: Vinod Kumar Vavilapalli
To: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
I will try to get them in or bug Daryn. HDFS-8498 doesn't seem a new bug, so I
kicked it out to 2.7.3.
Kihwal
From: Vinod Vavilapalli <vino...@hortonworks.com>
To: "common-...@hadoop.apache.org" <common-...@hadoop.apache.org>; Kihwal Lee
<kih...@
I think we need HDFS-8950 and HDFS-7725 in 2.7.2.It should be easy to
backport/cherry-pick HDFS-7725. For HDFS-8950, it will be nice if Ming can
chime in.
Kihwal
From: Tsuyoshi Ozawa
To: "common-...@hadoop.apache.org"
Cc: Chris Nauroth
sun.security.krb5.KrbApReq was creating a static MD5 digest object and not
synchronizing access.
This has been fixed in jdk8u60.
http://hg.openjdk.java.net/jdk8u/jdk8u60/jdk/rev/02d6b1096e89
One of the visible symptom is RPC reader thread getting
ArrayIndexOutOfBoundsException from
+1 (binding)Built the source from the tag and ran basic test on pseudo
distributed cluster.
Kihwal
From: Vinod Kumar Vavilapalli vino...@apache.org
To: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
yarn-...@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
Cc:
Ever since build #8430 in 8/29, test results are not showing up. I see there
was build config changes around that time. Anyone with the right permission
care to take a look?
Thanks,Kihwal
+1 (binding)
Kihwal
On 8/8/14, 9:57 PM, Karthik Kambatla ka...@cloudera.com wrote:
I have put together this proposal based on recent discussion on this
topic.
Please vote on the proposal. The vote runs for 7 days.
1. Migrate from subversion to git for version control.
2. Force-push to
Now builds are failing because of this. Please make sure build works with
-Pnative.
[exec] CMake Error at
/usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108
(message):
[exec] Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
[exec] Call Stack (most recent
+1 (binding)
Kihwal
On 6/24/14, 3:53 AM, Arun C Murthy a...@hortonworks.com wrote:
Folks,
As discussed, I'd like to call a vote on changing our by-laws to change
release votes from 7 days to 5.
I've attached the change to by-laws I'm proposing.
Please vote, the vote will the usual period
Kihwal Lee created MAPREDUCE-5939:
-
Summary: StartTime showing up as the epoch time in JHS UI after
upgrade
Key: MAPREDUCE-5939
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5939
Project
If we ever respin 2.4.1, I strongly suggest HDFS-6527 be included.
Kihwal
On 6/19/14, 4:56 PM, Akira AJISAKA ajisa...@oss.nttdata.co.jp wrote:
I think we should include this issue in 2.4.1, so I uploaded a patch to
fix it. I'll appreciate your review.
Thanks,
Akira
(2014/06/18 12:13), Vinod
Checked out the source, built and started a single node cluster.
Ran a couple of sample jobs.
+1 (binding)
Kihwal
On 6/19/14, 10:14 AM, Thomas Graves tgra...@yahoo-inc.com.INVALID
wrote:
Hey Everyone,
There have been various bug fixes that have went into
branch-0.23 since the 0.23.10 release.
for the feedback Vinod, Akira Kihwal.
I'll re-spin rc1 with MAPREDUCE-5830 HDFS-6527.
@Kihwal - Can you, please, merge HDFS-6527 to branch-2.4 and
branch-2.4.1?
thanks,
Arun
On Jun 20, 2014, at 7:32 AM, Kihwal Lee kih...@yahoo-inc.com.INVALID
wrote:
If we ever respin 2.4.1, I strongly suggest
The most common mistake is making incorrect assumptions on test/component
run-time. We often forget how slower/faster things can be on different
platforms and how the load on the machine at the time of test execution
affect the run time. If not sure, leave it to surefire. If things run
generally
I've built the tag and ran some basic tests on a single node cluster.
+1 (binding)
Kihwal
On Tuesday, December 3, 2013 12:24 AM, Thomas Graves tgra...@yahoo-inc.com
wrote:
Hey Everyone,
There have been lots of improvements and bug fixes that have went into
branch-0.23 since the 0.23.9
+1 Ran a set of tests against a single node cluster.
Kihwal
On Monday, October 7, 2013 2:02 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
It's your call, Arun. I.e. as long you believe rc2 meets the expectations and
objectives of 2.1.0-beta.
Kihwal
From: Arun Murthy a...@hortonworks.com
To: common-...@hadoop.apache.org common-...@hadoop.apache.org
Cc: Kihwal Lee kih...@yahoo-inc.com; mapreduce
I've changed the target version of HADOOP-9880 to 2.1.1. Please change it
back, if you feel that it needs to be in 2.1.0-beta.
Kihwal
From: Kihwal Lee kih...@yahoo-inc.com
To: Arun Murthy a...@hortonworks.com; common-...@hadoop.apache.org
common
Another blocker, HADOOP-9850, has been committed.
Kihwal
From: Arun C Murthy a...@hortonworks.com
To: Daryn Sharp da...@yahoo-inc.com
Cc: hdfs-...@hadoop.apache.org hdfs-...@hadoop.apache.org;
mapreduce-dev@hadoop.apache.org mapreduce-dev@hadoop.apache.org;
Sorry to hijack the thread but, I also wanted to mention Avro. See HADOOP-9672.
The version we are using has memory leak and inefficiency issues. We've seen
users running into it.
Kihwal
From: Tsuyoshi OZAWA ozawa.tsuyo...@gmail.com
To:
[
https://issues.apache.org/jira/browse/MAPREDUCE-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee resolved MAPREDUCE-3894.
---
Resolution: Fixed
0.23 and trunk MR builds fail intermittently
+1 Downloaded it and ran several sample tests in a pseudo-distributed
cluster.
Kihwal
On 7/1/13 12:20 PM, Thomas Graves tgra...@yahoo-inc.com wrote:
I've created a release candidate (RC0) for hadoop-0.23.9 that I would like
to release.
The RC is available at:
+1
Built from source and ran a couple of jobs in a pseudo-distributed cluster.
Kihwal
On 6/3/13 2:51 PM, Konstantin Boudnik c...@apache.org wrote:
I have rolled out release candidate (rc2) for hadoop-2.0.5-alpha.
The difference between rc1 and rc2 is the optimistic release date is
set for
+1
Verified checksums. Built from source, deployed and ran a couple of jobs.
Kihwal
On 2/6/13 9:59 PM, Arun C Murthy a...@hortonworks.com wrote:
Folks,
I've created a release candidate (rc0) for hadoop-2.0.3-alpha that I
would like to release.
This release contains several major
Ted,
I couldn't reproduce it by just running the test case. When you reproduce
it, look at the stderr/stdout file somewhere under
target/org.apache.hadoop.mapred.MiniMRCluster. Look for the one under the
directory whose name containing the app id.
I did run into a similar problem and the stderr
Kihwal Lee created MAPREDUCE-4470:
-
Summary: Fix TestCombineFileInputFormat.testForEmptyFile
Key: MAPREDUCE-4470
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4470
Project: Hadoop Map/Reduce
Kihwal Lee created MAPREDUCE-4471:
-
Summary: TestClientRMService.testGetQueueInfo failing after MR-4427
Key: MAPREDUCE-4471
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4471
Project: Hadoop
[
https://issues.apache.org/jira/browse/MAPREDUCE-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee resolved MAPREDUCE-4471.
---
Resolution: Invalid
TestClientRMService.testGetQueueInfo failing after MR-4427
Kihwal Lee created MAPREDUCE-4416:
-
Summary: Some tests run twice or fail if Clover is enabled
Key: MAPREDUCE-4416
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4416
Project: Hadoop Map/Reduce
Kihwal Lee created MAPREDUCE-4387:
-
Summary: RM gets fatal error and exits during TestRM
Key: MAPREDUCE-4387
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4387
Project: Hadoop Map/Reduce
Kihwal Lee created MAPREDUCE-4384:
-
Summary: Race conditions in IndexCache
Key: MAPREDUCE-4384
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4384
Project: Hadoop Map/Reduce
Issue Type
Kihwal Lee created MAPREDUCE-4308:
-
Summary: Remove excessive split log messages
Key: MAPREDUCE-4308
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4308
Project: Hadoop Map/Reduce
Kihwal Lee created MAPREDUCE-4207:
-
Summary: Remove System.out.println() in FileInputFormat
Key: MAPREDUCE-4207
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4207
Project: Hadoop Map/Reduce
Components: build
Affects Versions: 0.24.0, 0.23.2
Reporter: Kihwal Lee
The commit builds occasionally report ABORTED or FAILURE, which is not caused
by the new code change included in the builds. We are not sure since when it
has been broken this way, but Bobby's guess
: Bug
Components: tasktracker
Affects Versions: 1.0.0
Reporter: Kihwal Lee
Fix For: 1.1.0, 1.0.1
MAPREDUCE-2529 added the useful failure detection mechanism. In this jira, I
propose we add a periodic check inside TT and configurable action to
self-destruct
Hi James,
It means that the jvm's crashed. 134-128=6, which is SIGABRT. This is not the
cause, but what the jvm is sending to itself to exit after handling the crash
condition (e.g. seg fault). To find the real cause, you need to examine the
crash dump. You can specify the dump location with
Components: build
Affects Versions: 0.23.1, 0.24.0
Reporter: Kihwal Lee
Fix For: 0.23.1, 0.24.0
{code:xml}
dependency
groupIdorg.apache.hadoop/groupId
artifactIdhadoop-mapreduce-client-hs/artifactId
scopeprovided/scope
/dependency
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: nodemanager
Affects Versions: 0.23.0, 0.24.0
Reporter: Kihwal Lee
Assignee: Kihwal Lee
Priority: Critical
As seen in MAPREDUCE-2915, java.library.path is not being passed when
://issues.apache.org/jira/browse/MAPREDUCE-2915
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: task-controller
Affects Versions: 0.20.205.0
Reporter: Kihwal Lee
Assignee: Kihwal Lee
Fix For: 0.20.205.0
When a job
53 matches
Mail list logo