[jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
[
https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921522#comment-13921522
]
Hadoop QA commented on HDFS-5653:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626744/HDFS-5653.006.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common:
org.apache.hadoop.cli.TestHDFSCLI
org.apache.hadoop.cli.TestAclCLI
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/6311//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6311//console
This message is automatically generated.
Log namenode hostname in various exceptions being thrown in a HA setup
--
Key: HDFS-5653
URL: https://issues.apache.org/jira/browse/HDFS-5653
Project: Hadoop HDFS
Issue Type: Improvement
Components: ha
Affects Versions: 2.2.0
Reporter: Arpit Gupta
Assignee: Haohui Mai
Priority: Minor
Attachments: HDFS-5653.000.patch, HDFS-5653.001.patch,
HDFS-5653.002.patch, HDFS-5653.003.patch, HDFS-5653.004.patch,
HDFS-5653.005.patch, HDFS-5653.006.patch
In a HA setup any time we see an exception such as safemode or namenode in
standby etc we dont know which namenode it came from. The user has to go to
the logs of the namenode and determine which one was active and/or standby
around the same time.
I think it would help with debugging if any such exceptions could include the
namenode hostname so the user could know exactly which namenode served the
request.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
[ https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921565#comment-13921565 ] Jing Zhao commented on HDFS-5653: - +1 the new Patch looks good to me. Log namenode hostname in various exceptions being thrown in a HA setup -- Key: HDFS-5653 URL: https://issues.apache.org/jira/browse/HDFS-5653 Project: Hadoop HDFS Issue Type: Improvement Components: ha Affects Versions: 2.2.0 Reporter: Arpit Gupta Assignee: Haohui Mai Priority: Minor Attachments: HDFS-5653.000.patch, HDFS-5653.001.patch, HDFS-5653.002.patch, HDFS-5653.003.patch, HDFS-5653.004.patch, HDFS-5653.005.patch, HDFS-5653.006.patch In a HA setup any time we see an exception such as safemode or namenode in standby etc we dont know which namenode it came from. The user has to go to the logs of the namenode and determine which one was active and/or standby around the same time. I think it would help with debugging if any such exceptions could include the namenode hostname so the user could know exactly which namenode served the request. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
[
https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889895#comment-13889895
]
Hadoop QA commented on HDFS-5653:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626711/HDFS-5653.005.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common:
org.apache.hadoop.ipc.TestIPC
org.apache.hadoop.fs.shell.TestHdfsTextCommand
org.apache.hadoop.hdfs.server.namenode.snapshot.TestSnapshotFileLength
org.apache.hadoop.hdfs.server.namenode.TestNameNodeJspHelper
org.apache.hadoop.hdfs.TestClose
org.apache.hadoop.hdfs.TestShortCircuitLocalRead
org.apache.hadoop.hdfs.web.TestFSMainOperationsWebHdfs
org.apache.hadoop.hdfs.server.namenode.TestStorageRestore
org.apache.hadoop.hdfs.TestFSInputChecker
org.apache.hadoop.hdfs.server.namenode.TestBackupNode
org.apache.hadoop.hdfs.TestDataTransferProtocol
org.apache.hadoop.hdfs.server.namenode.TestHDFSConcat
org.apache.hadoop.hdfs.server.namenode.TestNamenodeCapacityReport
org.apache.hadoop.hdfs.server.balancer.TestBalancerWithMultipleNameNodes
org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.TestInterDatanodeProtocol
org.apache.hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting
org.apache.hadoop.hdfs.server.namenode.TestFSNamesystemMBean
org.apache.hadoop.hdfs.TestDFSClientFailover
org.apache.hadoop.hdfs.server.namenode.ha.TestStandbyIsHot
org.apache.hadoop.hdfs.server.blockmanagement.TestBlockTokenWithDFS
org.apache.hadoop.tools.TestJMXGet
org.apache.hadoop.hdfs.TestDFSShell
org.apache.hadoop.hdfs.security.TestDelegationToken
org.apache.hadoop.hdfs.server.namenode.TestSecondaryNameNodeUpgrade
org.apache.hadoop.hdfs.server.namenode.ha.TestDNFencingWithReplication
org.apache.hadoop.fs.permission.TestStickyBit
org.apache.hadoop.hdfs.server.namenode.TestNNStorageRetentionFunctional
org.apache.hadoop.hdfs.TestFileConcurrentReader
org.apache.hadoop.hdfs.server.datanode.TestCachingStrategy
org.apache.hadoop.hdfs.server.namenode.snapshot.TestCheckpointsWithSnapshots
org.apache.hadoop.hdfs.server.blockmanagement.TestComputeInvalidateWork
org.apache.hadoop.hdfs.server.namenode.TestListCorruptFileBlocks
org.apache.hadoop.fs.TestFcHdfsCreateMkdir
org.apache.hadoop.hdfs.TestCrcCorruption
org.apache.hadoop.hdfs.TestAppendDifferentChecksum
org.apache.hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureToleration
org.apache.hadoop.fs.viewfs.TestViewFileSystemHdfs
org.apache.hadoop.hdfs.server.namenode.TestParallelImageWrite
org.apache.hadoop.hdfs.security.TestDelegationTokenForProxyUser
org.apache.hadoop.hdfs.server.namenode.TestSequentialBlockId
org.apache.hadoop.hdfs.server.namenode.snapshot.TestSnapshotBlocksMap
org.apache.hadoop.hdfs.tools.TestGetGroups
org.apache.hadoop.hdfs.TestDFSPermission
org.apache.hadoop.hdfs.server.namenode.snapshot.TestDisallowModifyROSnapshot
org.apache.hadoop.hdfs.TestDFSUpgradeFromImage
org.apache.hadoop.hdfs.TestListFilesInFileContext
org.apache.hadoop.hdfs.server.namenode.TestNameNodeResourceChecker
org.apache.hadoop.hdfs.server.balancer.TestBalancerWithHANameNodes
[jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
[
https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890212#comment-13890212
]
Hadoop QA commented on HDFS-5653:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626744/HDFS-5653.006.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common:
org.apache.hadoop.hdfs.server.namenode.TestNameNodeHttpServer
org.apache.hadoop.hdfs.server.namenode.TestCacheDirectives
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/6013//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6013//console
This message is automatically generated.
Log namenode hostname in various exceptions being thrown in a HA setup
--
Key: HDFS-5653
URL: https://issues.apache.org/jira/browse/HDFS-5653
Project: Hadoop HDFS
Issue Type: Improvement
Components: ha
Affects Versions: 2.2.0
Reporter: Arpit Gupta
Assignee: Haohui Mai
Priority: Minor
Attachments: HDFS-5653.000.patch, HDFS-5653.001.patch,
HDFS-5653.002.patch, HDFS-5653.003.patch, HDFS-5653.004.patch,
HDFS-5653.005.patch, HDFS-5653.006.patch
In a HA setup any time we see an exception such as safemode or namenode in
standby etc we dont know which namenode it came from. The user has to go to
the logs of the namenode and determine which one was active and/or standby
around the same time.
I think it would help with debugging if any such exceptions could include the
namenode hostname so the user could know exactly which namenode served the
request.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
[
https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890341#comment-13890341
]
Hadoop QA commented on HDFS-5653:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626744/HDFS-5653.006.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common:
org.apache.hadoop.hdfs.server.namenode.TestCacheDirectives
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/6017//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6017//console
This message is automatically generated.
Log namenode hostname in various exceptions being thrown in a HA setup
--
Key: HDFS-5653
URL: https://issues.apache.org/jira/browse/HDFS-5653
Project: Hadoop HDFS
Issue Type: Improvement
Components: ha
Affects Versions: 2.2.0
Reporter: Arpit Gupta
Assignee: Haohui Mai
Priority: Minor
Attachments: HDFS-5653.000.patch, HDFS-5653.001.patch,
HDFS-5653.002.patch, HDFS-5653.003.patch, HDFS-5653.004.patch,
HDFS-5653.005.patch, HDFS-5653.006.patch
In a HA setup any time we see an exception such as safemode or namenode in
standby etc we dont know which namenode it came from. The user has to go to
the logs of the namenode and determine which one was active and/or standby
around the same time.
I think it would help with debugging if any such exceptions could include the
namenode hostname so the user could know exactly which namenode served the
request.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
[ https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887371#comment-13887371 ] Haohui Mai commented on HDFS-5653: -- The v4 patch addresses Jing's comments. Log namenode hostname in various exceptions being thrown in a HA setup -- Key: HDFS-5653 URL: https://issues.apache.org/jira/browse/HDFS-5653 Project: Hadoop HDFS Issue Type: Improvement Components: ha Affects Versions: 2.2.0 Reporter: Arpit Gupta Assignee: Haohui Mai Priority: Minor Attachments: HDFS-5653.000.patch, HDFS-5653.001.patch, HDFS-5653.002.patch, HDFS-5653.003.patch, HDFS-5653.004.patch In a HA setup any time we see an exception such as safemode or namenode in standby etc we dont know which namenode it came from. The user has to go to the logs of the namenode and determine which one was active and/or standby around the same time. I think it would help with debugging if any such exceptions could include the namenode hostname so the user could know exactly which namenode served the request. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
[
https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887427#comment-13887427
]
Hadoop QA commented on HDFS-5653:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12626241/HDFS-5653.004.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common:
org.apache.hadoop.ipc.TestIPC
org.apache.hadoop.io.retry.TestFailoverProxy
org.apache.hadoop.hdfs.server.namenode.TestMetaSave
org.apache.hadoop.hdfs.server.namenode.snapshot.TestSnapshotFileLength
org.apache.hadoop.fs.TestFcHdfsCreateMkdir
org.apache.hadoop.hdfs.TestSetTimes
org.apache.hadoop.hdfs.server.blockmanagement.TestBlocksWithNotEnoughRacks
org.apache.hadoop.hdfs.server.blockmanagement.TestOverReplicatedBlocks
org.apache.hadoop.hdfs.TestDFSStartupVersions
org.apache.hadoop.fs.TestUrlStreamHandler
org.apache.hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting
org.apache.hadoop.hdfs.server.namenode.ha.TestEditLogTailer
org.apache.hadoop.hdfs.server.namenode.TestSnapshotPathINodes
org.apache.hadoop.hdfs.server.namenode.snapshot.TestSnapshottableDirListing
org.apache.hadoop.hdfs.server.namenode.snapshot.TestSnapshotDeletion
org.apache.hadoop.fs.TestSymlinkHdfsDisable
org.apache.hadoop.hdfs.tools.TestDFSHAAdminMiniCluster
org.apache.hadoop.hdfs.server.namenode.TestNameNodeMXBean
org.apache.hadoop.fs.TestGlobPaths
org.apache.hadoop.hdfs.server.blockmanagement.TestPendingReplication
org.apache.hadoop.hdfs.server.datanode.TestMultipleNNDataBlockScanner
org.apache.hadoop.hdfs.server.namenode.TestINodeFile
org.apache.hadoop.hdfs.server.namenode.TestListCorruptFileBlocks
org.apache.hadoop.hdfs.TestDFSShellGenericOptions
org.apache.hadoop.hdfs.server.namenode.ha.TestHAMetrics
org.apache.hadoop.hdfs.TestDatanodeDeath
org.apache.hadoop.hdfs.TestFileAppend2
org.apache.hadoop.hdfs.server.namenode.TestCheckPointForSecurityTokens
org.apache.hadoop.hdfs.TestDFSPermission
org.apache.hadoop.hdfs.TestFileAppendRestart
org.apache.hadoop.hdfs.TestDataTransferProtocol
org.apache.hadoop.hdfs.TestInjectionForSimulatedStorage
org.apache.hadoop.hdfs.server.namenode.TestFileLimit
org.apache.hadoop.fs.TestSymlinkHdfsFileContext
org.apache.hadoop.hdfs.server.datanode.TestDeleteBlockPool
org.apache.hadoop.hdfs.web.TestFSMainOperationsWebHdfs
org.apache.hadoop.fs.TestEnhancedByteBufferAccess
org.apache.hadoop.hdfs.TestDFSUpgrade
org.apache.hadoop.hdfs.server.namenode.ha.TestGetGroupsWithHA
org.apache.hadoop.hdfs.TestIsMethodSupported
org.apache.hadoop.fs.TestHDFSFileContextMainOperations
org.apache.hadoop.hdfs.server.namenode.TestNameNodeRecovery
org.apache.hadoop.hdfs.server.datanode.TestBlockReport
org.apache.hadoop.hdfs.TestParallelUnixDomainRead
org.apache.hadoop.hdfs.TestHDFSServerPorts
org.apache.hadoop.hdfs.server.namenode.snapshot.TestSnapshotListing
org.apache.hadoop.hdfs.server.namenode.ha.TestInitializeSharedEdits
org.apache.hadoop.hdfs.server.namenode.TestParallelImageWrite
org.apache.hadoop.hdfs.server.namenode.TestCheckpoint
org.apache.hadoop.hdfs.web.TestHttpsFileSystem
[jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
[ https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866118#comment-13866118 ] Jing Zhao commented on HDFS-5653: - For the current patch, since getCurrentProxyInfo and getProxy are called in different places, is it possible that a failover happened in the middle (triggered by another RPC call, e.g.)? I think another possible solution is to let getProxy return (Proxy + extra tag) where the tag can be used to indicate the NN. Log namenode hostname in various exceptions being thrown in a HA setup -- Key: HDFS-5653 URL: https://issues.apache.org/jira/browse/HDFS-5653 Project: Hadoop HDFS Issue Type: Improvement Components: ha Affects Versions: 2.2.0 Reporter: Arpit Gupta Assignee: Haohui Mai Priority: Minor Attachments: HDFS-5653.000.patch, HDFS-5653.001.patch, HDFS-5653.002.patch, HDFS-5653.003.patch In a HA setup any time we see an exception such as safemode or namenode in standby etc we dont know which namenode it came from. The user has to go to the logs of the namenode and determine which one was active and/or standby around the same time. I think it would help with debugging if any such exceptions could include the namenode hostname so the user could know exactly which namenode served the request. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
[ https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863375#comment-13863375 ] Suresh Srinivas commented on HDFS-5653: --- [~wheat9], can you please add description of the changes done in the patch? Log namenode hostname in various exceptions being thrown in a HA setup -- Key: HDFS-5653 URL: https://issues.apache.org/jira/browse/HDFS-5653 Project: Hadoop HDFS Issue Type: Improvement Components: ha Affects Versions: 2.2.0 Reporter: Arpit Gupta Assignee: Haohui Mai Priority: Minor Attachments: HDFS-5653.000.patch, HDFS-5653.001.patch, HDFS-5653.002.patch, HDFS-5653.003.patch In a HA setup any time we see an exception such as safemode or namenode in standby etc we dont know which namenode it came from. The user has to go to the logs of the namenode and determine which one was active and/or standby around the same time. I think it would help with debugging if any such exceptions could include the namenode hostname so the user could know exactly which namenode served the request. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
[ https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863445#comment-13863445 ] Haohui Mai commented on HDFS-5653: -- This patch is to add a new interface FailoverProxyProvider#getCurrentProxyInfo() on the client side to allow the implementation to provide the address of the current NN. It prints out a debug message with the address when failovers happen. Log namenode hostname in various exceptions being thrown in a HA setup -- Key: HDFS-5653 URL: https://issues.apache.org/jira/browse/HDFS-5653 Project: Hadoop HDFS Issue Type: Improvement Components: ha Affects Versions: 2.2.0 Reporter: Arpit Gupta Assignee: Haohui Mai Priority: Minor Attachments: HDFS-5653.000.patch, HDFS-5653.001.patch, HDFS-5653.002.patch, HDFS-5653.003.patch In a HA setup any time we see an exception such as safemode or namenode in standby etc we dont know which namenode it came from. The user has to go to the logs of the namenode and determine which one was active and/or standby around the same time. I think it would help with debugging if any such exceptions could include the namenode hostname so the user could know exactly which namenode served the request. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
[
https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863461#comment-13863461
]
Suresh Srinivas commented on HDFS-5653:
---
[~arpitgupta], is this what you were looking for?
The issues I see with this approach are:
# Debug logs are generally not enabled. Hence this information will not be
available for debugging.
# Logging on the client side means that along with the exception, one must
access client logs to determine the namenode.
Adding host information to the exception on the server side is the ideal
solution. But that could be a huge amount of change. Would adding this
information only to {{SafemodeException}} be sufficient? [~arpitgupta],
comments?
Log namenode hostname in various exceptions being thrown in a HA setup
--
Key: HDFS-5653
URL: https://issues.apache.org/jira/browse/HDFS-5653
Project: Hadoop HDFS
Issue Type: Improvement
Components: ha
Affects Versions: 2.2.0
Reporter: Arpit Gupta
Assignee: Haohui Mai
Priority: Minor
Attachments: HDFS-5653.000.patch, HDFS-5653.001.patch,
HDFS-5653.002.patch, HDFS-5653.003.patch
In a HA setup any time we see an exception such as safemode or namenode in
standby etc we dont know which namenode it came from. The user has to go to
the logs of the namenode and determine which one was active and/or standby
around the same time.
I think it would help with debugging if any such exceptions could include the
namenode hostname so the user could know exactly which namenode served the
request.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
[
https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851112#comment-13851112
]
Hadoop QA commented on HDFS-5653:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12619165/HDFS-5653.000.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/5746//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HDFS-Build/5746//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5746//console
This message is automatically generated.
Log namenode hostname in various exceptions being thrown in a HA setup
--
Key: HDFS-5653
URL: https://issues.apache.org/jira/browse/HDFS-5653
Project: Hadoop HDFS
Issue Type: Improvement
Components: ha
Affects Versions: 2.2.0
Reporter: Arpit Gupta
Priority: Minor
Attachments: HDFS-5653.000.patch
In a HA setup any time we see an exception such as safemode or namenode in
standby etc we dont know which namenode it came from. The user has to go to
the logs of the namenode and determine which one was active and/or standby
around the same time.
I think it would help with debugging if any such exceptions could include the
namenode hostname so the user could know exactly which namenode served the
request.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
[
https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851127#comment-13851127
]
Hadoop QA commented on HDFS-5653:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12619197/HDFS-5653.001.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5748//console
This message is automatically generated.
Log namenode hostname in various exceptions being thrown in a HA setup
--
Key: HDFS-5653
URL: https://issues.apache.org/jira/browse/HDFS-5653
Project: Hadoop HDFS
Issue Type: Improvement
Components: ha
Affects Versions: 2.2.0
Reporter: Arpit Gupta
Priority: Minor
Attachments: HDFS-5653.000.patch, HDFS-5653.001.patch
In a HA setup any time we see an exception such as safemode or namenode in
standby etc we dont know which namenode it came from. The user has to go to
the logs of the namenode and determine which one was active and/or standby
around the same time.
I think it would help with debugging if any such exceptions could include the
namenode hostname so the user could know exactly which namenode served the
request.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
[
https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851220#comment-13851220
]
Hadoop QA commented on HDFS-5653:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12619218/HDFS-5653.002.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5751//console
This message is automatically generated.
Log namenode hostname in various exceptions being thrown in a HA setup
--
Key: HDFS-5653
URL: https://issues.apache.org/jira/browse/HDFS-5653
Project: Hadoop HDFS
Issue Type: Improvement
Components: ha
Affects Versions: 2.2.0
Reporter: Arpit Gupta
Assignee: Haohui Mai
Priority: Minor
Attachments: HDFS-5653.000.patch, HDFS-5653.001.patch,
HDFS-5653.002.patch
In a HA setup any time we see an exception such as safemode or namenode in
standby etc we dont know which namenode it came from. The user has to go to
the logs of the namenode and determine which one was active and/or standby
around the same time.
I think it would help with debugging if any such exceptions could include the
namenode hostname so the user could know exactly which namenode served the
request.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Commented] (HDFS-5653) Log namenode hostname in various exceptions being thrown in a HA setup
[
https://issues.apache.org/jira/browse/HDFS-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851362#comment-13851362
]
Hadoop QA commented on HDFS-5653:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12619224/HDFS-5653.003.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/5753//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5753//console
This message is automatically generated.
Log namenode hostname in various exceptions being thrown in a HA setup
--
Key: HDFS-5653
URL: https://issues.apache.org/jira/browse/HDFS-5653
Project: Hadoop HDFS
Issue Type: Improvement
Components: ha
Affects Versions: 2.2.0
Reporter: Arpit Gupta
Assignee: Haohui Mai
Priority: Minor
Attachments: HDFS-5653.000.patch, HDFS-5653.001.patch,
HDFS-5653.002.patch, HDFS-5653.003.patch
In a HA setup any time we see an exception such as safemode or namenode in
standby etc we dont know which namenode it came from. The user has to go to
the logs of the namenode and determine which one was active and/or standby
around the same time.
I think it would help with debugging if any such exceptions could include the
namenode hostname so the user could know exactly which namenode served the
request.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
