[jira] [Created] (HDFS-3464) Deleting currentLedger and leaving 'inprogress_x' on exceptions can throw BKNoSuchLedgerExistsException later.
Uma Maheswara Rao G created HDFS-3464:
-
Summary: Deleting currentLedger and leaving 'inprogress_x' on
exceptions can throw BKNoSuchLedgerExistsException later.
Key: HDFS-3464
URL: https://issues.apache.org/jira/browse/HDFS-3464
Project: Hadoop HDFS
Issue Type: Sub-task
Affects Versions: 2.0.1-alpha, 3.0.0
Reporter: Uma Maheswara Rao G
Assignee: Uma Maheswara Rao G
HDFS-3058 will clean currentLedgers on exception.
In BookKeeperJournalManager, startLogSegment() is deleting the corresponding
'inprogress_ledger' ledger on exception. Here leaving the 'inprogress_x' ledger
metadata in ZooKeeper. When the other node becomes active, he will see the
'inprogress_x' znode and tries to recoverLastTxId() it would throw exception,
since there is no 'inprogress_ledger' exists.
{noformat}
Caused by:
org.apache.bookkeeper.client.BKException$BKNoSuchLedgerExistsException
at
org.apache.bookkeeper.client.BookKeeper.openLedger(BookKeeper.java:393)
at
org.apache.hadoop.contrib.bkjournal.BookKeeperJournalManager.recoverLastTxId(BookKeeperJournalManager.java:493)
{noformat}
As per the discussion in HDFS-3058, we will handle the coment as part of this
JIRA.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-3465) 2NN doesn't start with fs.defaultFS set to a viewfs URI unless service RPC address is also set
Eli Collins created HDFS-3465:
-
Summary: 2NN doesn't start with fs.defaultFS set to a viewfs URI
unless service RPC address is also set
Key: HDFS-3465
URL: https://issues.apache.org/jira/browse/HDFS-3465
Project: Hadoop HDFS
Issue Type: Bug
Components: name-node
Affects Versions: 2.0.0-alpha
Reporter: Eli Collins
Looks like the 2NN first tries servicerpc-address then falls back on
fs.defaultFS, which won't work in the case of federation since fs.defaultFS
doesn't refer to an RPC address. Instead, the 2NN should first check
servicerpc-address, then rpc-address, then fall back on fs.defaultFS.
{noformat}
Exception in thread "main" java.lang.IllegalArgumentException: Invalid
URI for NameNode address (check fs.defaultFS): viewfs:/// has no
authority.
at
org.apache.hadoop.hdfs.server.namenode.NameNode.getAddress(NameNode.java:315)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.getAddress(NameNode.java:303)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.getServiceAddress(NameNode.java:296)
at
org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.initialize(SecondaryNameNode.java:214)
at
org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.(SecondaryNameNode.java:178)
at
org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.main(SecondaryNameNode.java:582)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file
Owen O'Malley created HDFS-3466: --- Summary: The SPNEGO filter for the NameNode should come out of the web keytab file Key: HDFS-3466 URL: https://issues.apache.org/jira/browse/HDFS-3466 Project: Hadoop HDFS Issue Type: Bug Components: name-node, security Affects Versions: 2.0.0-alpha, 1.1.0 Reporter: Owen O'Malley Assignee: Owen O'Malley Currently, the spnego filter uses the DFS_NAMENODE_KEYTAB_FILE_KEY to find the keytab. It should use the DFS_WEB_AUTHENTICATION_KERBEROS_KEYTAB_KEY to do it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-3467) NN is getting shutdown by throwing IllegalArgumentException
Brahma Reddy Battula created HDFS-3467:
--
Summary: NN is getting shutdown by throwing
IllegalArgumentException
Key: HDFS-3467
URL: https://issues.apache.org/jira/browse/HDFS-3467
Project: Hadoop HDFS
Issue Type: Bug
Components: name-node
Affects Versions: 2.0.0-alpha, 2.0.1-alpha
Reporter: Brahma Reddy Battula
Scenario:
=
Configure fs.default.name
Format Namenode
Start NameNode.
Here it is getting shutdown ..like following..
{noformat}
2012-05-25 21:09:30,810 ERROR org.apache.hadoop.hdfs.server.namenode.NameNode:
Exception in namenode join
java.lang.IllegalArgumentException: Invalid URI for NameNode address (check
fs.defaultFS): file:/// has no authority.
at
org.apache.hadoop.hdfs.server.namenode.NameNode.getAddress(NameNode.java:295)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.getAddress(NameNode.java:283)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.getRpcServerAddress(NameNode.java:336)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.loginAsNameNodeUser(NameNode.java:388)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:400)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:570)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:551)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1114)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1170)
2012-05-25 21:09:30,812 INFO org.apache.hadoop.hdfs.server.namenode.NameNode:
SHUTDOWN_MSG:
{noformat}
This is happening in hadoop-2.0.1 But it's not like that in trunk.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-3468) Make BKJM-ZK session timeout configurable.
Uma Maheswara Rao G created HDFS-3468: - Summary: Make BKJM-ZK session timeout configurable. Key: HDFS-3468 URL: https://issues.apache.org/jira/browse/HDFS-3468 Project: Hadoop HDFS Issue Type: Sub-task Affects Versions: 2.0.0-alpha Reporter: Uma Maheswara Rao G Assignee: Uma Maheswara Rao G Currently BKJM-ZK session timeout has been hardcoded to 3000ms. Considering ZKFC timeouts configurable, we should make this also configurable. Unfortunale we can not compare both the values at runtime, because they both are different processes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
