[jira] [Resolved] (HADOOP-11836) Update release note in index.md.vm
[ https://issues.apache.org/jira/browse/HADOOP-11836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Andreina resolved HADOOP-11836. - Resolution: Implemented This issue has been already fixed . Hence resolving the same. > Update release note in index.md.vm > -- > > Key: HADOOP-11836 > URL: https://issues.apache.org/jira/browse/HADOOP-11836 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 2.6.0, 2.7.0 >Reporter: Akira AJISAKA >Assignee: J.Andreina > > http://hadoop.apache.org/docs/current/ still shows the new features of Hadoop > 2.5. The document should be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HADOOP-12410) Fix failures in TestLazyPersistReplicaPlacement
J.Andreina created HADOOP-12410:
---
Summary: Fix failures in TestLazyPersistReplicaPlacement
Key: HADOOP-12410
URL: https://issues.apache.org/jira/browse/HADOOP-12410
Project: Hadoop Common
Issue Type: Bug
Reporter: J.Andreina
Assignee: J.Andreina
Testcases TestLazyPersistReplicaPlacement#testSynchronousEviction,
TestLazyPersistReplicaPlacement#testFallbackToDiskFull fails with below
excepiton
{noformat}
java.lang.AssertionError: expected:<1> but was:<0>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at
org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.LazyPersistTestCase.verifyRamDiskJMXMetric(LazyPersistTestCase.java:483)
at
org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.TestLazyPersistReplicaPlacement.testSynchronousEviction(TestLazyPersistReplicaPlacement.java:92)
{noformat}
{noformat}
java.lang.AssertionError: expected:<1> but was:<0>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at
org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.LazyPersistTestCase.verifyRamDiskJMXMetric(LazyPersistTestCase.java:483)
at
org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.TestLazyPersistReplicaPlacement.testFallbackToDiskFull(TestLazyPersistReplicaPlacement.java:107)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HADOOP-12105) Avoid returning 0 , while fetching the status of a process ,which is not running.
J.Andreina created HADOOP-12105:
---
Summary: Avoid returning 0 , while fetching the status of a
process ,which is not running.
Key: HADOOP-12105
URL: https://issues.apache.org/jira/browse/HADOOP-12105
Project: Hadoop Common
Issue Type: Improvement
Reporter: J.Andreina
Assignee: J.Andreina
If the process(Namenode) is crashed there will be stale pid file .
Any other JVM process might get allocated with the same pid as that of the
content of stale pid file.
As per current implementation for fetching the status :
we check if any process is running with pid (fetched from
corresponding process pid file) then returns 0.
{code}
if ps -p ${pid} /dev/null 21; then
return 0
fi
{code}
*So while fetching the status of namenode return code will be 0 , even if the
namenode process is not running (because some other process is assigned with
same pid ).*
Can we check status of process as below
{code}
if ps -fp pid | grep process_classname /dev/null 21; then
return 0
fi
{code}
Please provide your feedback.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HADOOP-11865) Incorrect path mentioned in document for accessing script files
J.Andreina created HADOOP-11865: --- Summary: Incorrect path mentioned in document for accessing script files Key: HADOOP-11865 URL: https://issues.apache.org/jira/browse/HADOOP-11865 Project: Hadoop Common Issue Type: Bug Components: documentation Reporter: J.Andreina Assignee: J.Andreina Instead of sbin it is mentioned as bin in path to access script files. 1. http://hadoop.apache.org/docs/current/hadoop-kms/index.html To start/stop KMS use KMS's *bin/kms.sh* script. For example: 2.http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/HdfsUserGuide.html Run the new version with -upgrade option *(bin/start-dfs.sh -upgrade).* 3. start the cluster with rollback option. *(bin/start-dfs.sh -rollback).* 4.http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/Federation.html */bin/hadoop-daemon.sh* --config $HADOOP_CONF_DIR --script $bin/hdfs start balancer [-policy policy] 5.*bin/distributed-exclude.sh* exclude_file 6.*bin/refresh-namenodes.sh* Need to check for any other occurrences and fix the same -- This message was sent by Atlassian JIRA (v6.3.4#6332)
