[jira] [Created] (HADOOP-16247) NPE in FsUrlConnection

2019-04-10 Thread Karthik Palanisamy (JIRA) 
Karthik Palanisamy created HADOOP-16247:
---

 Summary: NPE in FsUrlConnection
 Key: HADOOP-16247
 URL: https://issues.apache.org/jira/browse/HADOOP-16247
 Project: Hadoop Common
  Issue Type: Bug
  Components: hdfs-client
Affects Versions: 3.1.2
Reporter: Karthik Palanisamy
Assignee: Karthik Palanisamy


FsUrlConnection doesn't handle relativePath correctly after the change 
[HADOOP-15217|https://issues.apache.org/jira/browse/HADOOP-15217]

{code}

Exception in thread "main" java.lang.NullPointerException
 at org.apache.hadoop.fs.Path.isUriPathAbsolute(Path.java:385)
 at org.apache.hadoop.fs.Path.isAbsolute(Path.java:395)
 at 
org.apache.hadoop.fs.RawLocalFileSystem.pathToFile(RawLocalFileSystem.java:87)
 at 
org.apache.hadoop.fs.RawLocalFileSystem.deprecatedGetFileStatus(RawLocalFileSystem.java:636)
 at 
org.apache.hadoop.fs.RawLocalFileSystem.getFileLinkStatusInternal(RawLocalFileSystem.java:930)
 at 
org.apache.hadoop.fs.RawLocalFileSystem.getFileStatus(RawLocalFileSystem.java:631)
 at 
org.apache.hadoop.fs.FilterFileSystem.getFileStatus(FilterFileSystem.java:454)
 at 
org.apache.hadoop.fs.ChecksumFileSystem$ChecksumFSInputChecker.(ChecksumFileSystem.java:146)
 at org.apache.hadoop.fs.ChecksumFileSystem.open(ChecksumFileSystem.java:347)
 at org.apache.hadoop.fs.FileSystem.open(FileSystem.java:899)
 at org.apache.hadoop.fs.FsUrlConnection.connect(FsUrlConnection.java:62)
 at org.apache.hadoop.fs.FsUrlConnection.getInputStream(FsUrlConnection.java:71)
 at java.net.URL.openStream(URL.java:1045)
 at UrlProblem.testRelativePath(UrlProblem.java:33)
 at UrlProblem.main(UrlProblem.java:19)

{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

[jira] [Created] (HADOOP-15449) Frequent Namenode Flipover affecting user Jobs.

2018-05-07 Thread Karthik Palanisamy (JIRA) 
Karthik Palanisamy created HADOOP-15449:
---

 Summary: Frequent Namenode Flipover affecting user Jobs.
 Key: HADOOP-15449
 URL: https://issues.apache.org/jira/browse/HADOOP-15449
 Project: Hadoop Common
  Issue Type: Wish
  Components: common
Affects Versions: 2.7.4
Reporter: Karthik Palanisamy


We observed from several users regarding Namenode flip-over is due to either 
zookeeper disk slowness (higher fsync cost) or network issue. We would need to 
avoid flip-over issue to some extent by increasing HA session timeout, 
ha.zookeeper.session-timeout.ms.

Default value 5000 ms, seems very low in any production environment.  I would 
suggest 1 ms as default session timeout.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

[jira] [Created] (HADOOP-13468) In HA, Namenode is failed to start If any of the Quorum hostname is unresolved

2016-08-04 Thread Karthik Palanisamy (JIRA) 
Karthik Palanisamy created HADOOP-13468:
---

 Summary: In HA, Namenode is failed to start If any of the Quorum 
hostname is unresolved
 Key: HADOOP-13468
 URL: https://issues.apache.org/jira/browse/HADOOP-13468
 Project: Hadoop Common
  Issue Type: Bug
Affects Versions: 2.7.0, 2.8.0
 Environment: HDP-2.4.0
Reporter: Karthik Palanisamy


2016-08-03 02:53:53,760 ERROR namenode.NameNode (NameNode.java:main(1712)) - 
Failed to start namenode.
java.lang.IllegalArgumentException: Unable to construct journal, 
qjournal://1:8485;2:8485;3:8485/shva
at 
org.apache.hadoop.hdfs.server.namenode.FSEditLog.createJournal(FSEditLog.java:1637)
at 
org.apache.hadoop.hdfs.server.namenode.FSEditLog.initJournals(FSEditLog.java:282)
at 
org.apache.hadoop.hdfs.server.namenode.FSEditLog.initSharedJournalsForRead(FSEditLog.java:260)
at 
org.apache.hadoop.hdfs.server.namenode.FSImage.initEditLog(FSImage.java:789)
at 
org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:634)
at 
org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:294)
at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:983)
at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:688)
at 
org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:662)
at 
org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:726)
at 
org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:951)
at 
org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:935)
at 
org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1641)
at 
org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1707)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at 
org.apache.hadoop.hdfs.server.namenode.FSEditLog.createJournal(FSEditLog.java:1635)
... 13 more
Caused by: java.lang.NullPointerException
at 
org.apache.hadoop.hdfs.qjournal.client.IPCLoggerChannelMetrics.getName(IPCLoggerChannelMetrics.java:107)
at 
org.apache.hadoop.hdfs.qjournal.client.IPCLoggerChannelMetrics.create(IPCLoggerChannelMetrics.java:91)
at 
org.apache.hadoop.hdfs.qjournal.client.IPCLoggerChannel.(IPCLoggerChannel.java:178)
at 
org.apache.hadoop.hdfs.qjournal.client.IPCLoggerChannel$1.createLogger(IPCLoggerChannel.java:156)
at 
org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager.createLoggers(QuorumJournalManager.java:367)
at 
org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager.createLoggers(QuorumJournalManager.java:149)
at 
org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager.(QuorumJournalManager.java:116)
at 
org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager.(QuorumJournalManager.java:105)
... 18 more
2016-08-03 02:53:53,765 INFO  util.ExitUtil (ExitUtil.java:terminate(124)) - 
Exiting with status 1
2016-08-03 02:53:53,768 INFO  namenode.NameNode (LogAdapter.java:info(47)) - 
SHUTDOWN_MSG:

*and the failover is not successful*

I have attached the patch, It allows the Namenode to start if the majority of 
the Quorums are resolvable.
throws warning if the quorum is unresolvable.
throws Unknown host exception if the majority of the journals are unresolvable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org