+1
Many thanks to Allen and Andrew for driving this.
-Varun
On 7/3/15, 10:25 AM, "Vinayakumar B" wrote:
>+1 for the auto generation.
>
>bq. Besides, after a release R1 is out, someone may (accidentally or
>intentionally) modify the JIRA summary.
>Is there any possibility that, we can restric
+1 for the auto generation.
bq. Besides, after a release R1 is out, someone may (accidentally or
intentionally) modify the JIRA summary.
Is there any possibility that, we can restrict someone from editing the
issue in jira once its marked as "closed" after release?
Regards,
Vinay
On Fri, Jul 3,
Huge +1
On Thursday, July 2, 2015, Chris Nauroth wrote:
> +1
>
> Thank you to Allen for the script, and thank you to Andrew for
> volunteering to drive the conversion.
>
> --Chris Nauroth
>
>
>
>
> On 7/2/15, 2:01 PM, "Andrew Wang" >
> wrote:
>
> >Hi all,
> >
> >I want to revive the discussion o
+1
Thank you to Allen for the script, and thank you to Andrew for
volunteering to drive the conversion.
--Chris Nauroth
On 7/2/15, 2:01 PM, "Andrew Wang" wrote:
>Hi all,
>
>I want to revive the discussion on this thread, since the overhead of
>CHANGES.txt came up again in the context of bac
Hi all,
I want to revive the discussion on this thread, since the overhead of
CHANGES.txt came up again in the context of backporting fixes for
maintenance releases.
Allen's automatic generation script (HADOOP-11731) went into trunk but not
branch-2, so we're still maintaining CHANGES.txt everywh
Chandan Biswas created HDFS-8714:
Summary: Folder ModificationTime in Millis Changed When NameNode
is restarted
Key: HDFS-8714
URL: https://issues.apache.org/jira/browse/HDFS-8714
Project: Hadoop HDFS
Andrew Wang created HDFS-8713:
-
Summary: Convert DatanodeDescriptor to use SLF4J logging
Key: HDFS-8713
URL: https://issues.apache.org/jira/browse/HDFS-8713
Project: Hadoop HDFS
Issue Type: Impro
Lei (Eddy) Xu created HDFS-8712:
---
Summary: Remove "public" and "abstract" modifiers in FsVolumeSpi
and FsDatasetSpi
Key: HDFS-8712
URL: https://issues.apache.org/jira/browse/HDFS-8712
Project: Hadoop HD
Not really Dmitry, QJM with automatic failover is being used in very large
production clusters. So its hardly a cutting edge feature by now and if
configured correctly you can failover in matter of seconds without major
hiccups to the clients.
--
Cloudera, Inc.
On Thu, Jul 2, 2015 at 8:25 AM, D
Hi, Esteban.
Thanks for your reply. Thus, QJM automatic failover option is a cut-edge
thing. Am I right?
I think that it's a good idea to have truly equal NNs doing their work
in parallel, as Konstantin Shvachko mentioned.
On 07/02/2015 04:49 PM, Esteban Gutierrez wrote:
Hi Dmitry,
Have y
Hi Dmitry,
Have you looked into the QJM automatic failover mode using the
ZKFailoverController?
https://hadoop.apache.org/docs/r2.6.0/hadoop-project-dist/hadoop-hdfs/HDFSHighAvailabilityWithQJM.html#Automatic_Failover
This is the most commonly used HA mode in production environments. Also
there is
Sure, I did. It's actually not what I'm looking for. I don't want to
spend time to make dead NN alive by my hands. There should be a solution
for NN-SPOF problem.
On 07/02/2015 04:36 PM, Vinayakumar B wrote:
Hi..
Did you look at the HDFS Namenode high availability?
-Vinay
On Jul 2, 2015 11:50
Hi..
Did you look at the HDFS Namenode high availability?
-Vinay
On Jul 2, 2015 11:50 AM, "Dmitry Salychev" wrote:
> Hello, HDFS Developers.
>
> I know that NN is a single point of failure of an entire HDFS cluster. If
> it fails, the cluster will be unavailable no matter how many DN there. I
>
+1 (non-binding)
+ verified mds of source and binary tarball
+ built from source tarball
+ deployed binary tarball to 4 nodes cluster and run some
hadoop-mapreduce-examples jobs
Thanks,
Masatake Iwasaki
On 6/29/15 17:45, Vinod Kumar Vavilapalli wrote:
Hi all,
I've created a release candida
+1 (non-binding)
+ Downloaded and built source+ Installed on one-node cluster+ Ran simple manual
tests+ spot-checked unit tests
Thanks, Vinod, for managing this release!-Eric Payne
From: Vinod Kumar Vavilapalli
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
yarn-...@hadoo
Surendra Singh Lilhore created HDFS-8711:
Summary: setSpaceQuota command should print the available storage
type when input storage type is wrong
Key: HDFS-8711
URL: https://issues.apache.org/jira/browse/H
Xinwei Qin created HDFS-8710:
-
Summary: Always read DU value from the cached "dfsUsed" file on
datanode startup
Key: HDFS-8710
URL: https://issues.apache.org/jira/browse/HDFS-8710
Project: Hadoop HDFS
17 matches
Mail list logo
