[jira] [Updated] (AMBARI-16028) Namenode marked as INITIAL standby could potentially never start if other namenode is down

2016-08-17 Thread Jayush Luniya (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-16028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayush Luniya updated AMBARI-16028:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Namenode marked as INITIAL standby could potentially never start if other 
> namenode is down
> --
>
> Key: AMBARI-16028
> URL: https://issues.apache.org/jira/browse/AMBARI-16028
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.2-next
>
> Attachments: AMBARI-16028-trunk.patch
>
>
> *Issue:*
> # During Namenode HA blueprint deployment, we configure the name nodes to 
> start in active/standby mode based on the following properties
> {code}
>  {
> "hadoop-env": {
>   "properties" : {
> "dfs_ha_initial_namenode_active" : "host1",
> "dfs_ha_initial_namenode_standby" : "host2”
>   }
> }
>   }
> {code}
> # The current logic is to always bootstrap the name node marked as standby. 
> # This will lead to the Namenode marked as Standby to never start under the 
> following situation
> - Cluster is deployed successfully
> - Both name nodes are stopped
> - Start the name node marked as standby. Namenode will never start.
> - This is because the standby name node will try to bootstrap again. 
> - However to bootstrap a name node an active name node is required. Based on 
> the HDFS logic the first step done when bootstrapping is to connect to the 
> Active Namenode. 
> - Also there is no need to bootstrap here as the name node should already be 
> bootstrapped and should come back up as “Active"



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

[jira] [Updated] (AMBARI-16028) Namenode marked as INITIAL standby could potentially never start if other namenode is down

2016-04-26 Thread Sumit Mohanty (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-16028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated AMBARI-16028:
---
Fix Version/s: (was: 2.4.0)
   2.2-next

> Namenode marked as INITIAL standby could potentially never start if other 
> namenode is down
> --
>
> Key: AMBARI-16028
> URL: https://issues.apache.org/jira/browse/AMBARI-16028
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.2-next
>
> Attachments: AMBARI-16028-trunk.patch
>
>
> *Issue:*
> # During Namenode HA blueprint deployment, we configure the name nodes to 
> start in active/standby mode based on the following properties
> {code}
>  {
> "hadoop-env": {
>   "properties" : {
> "dfs_ha_initial_namenode_active" : "host1",
> "dfs_ha_initial_namenode_standby" : "host2”
>   }
> }
>   }
> {code}
> # The current logic is to always bootstrap the name node marked as standby. 
> # This will lead to the Namenode marked as Standby to never start under the 
> following situation
> - Cluster is deployed successfully
> - Both name nodes are stopped
> - Start the name node marked as standby. Namenode will never start.
> - This is because the standby name node will try to bootstrap again. 
> - However to bootstrap a name node an active name node is required. Based on 
> the HDFS logic the first step done when bootstrapping is to connect to the 
> Active Namenode. 
> - Also there is no need to bootstrap here as the name node should already be 
> bootstrapped and should come back up as “Active"



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

[jira] [Updated] (AMBARI-16028) Namenode marked as INITIAL standby could potentially never start if other namenode is down

2016-04-21 Thread Jayush Luniya (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-16028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayush Luniya updated AMBARI-16028:
---
Description: 
*Issue:*
# During Namenode HA blueprint deployment, we configure the name nodes to start 
in active/standby mode based on the following properties
{code}
 {
"hadoop-env": {
  "properties" : {
"dfs_ha_initial_namenode_active" : "host1",
"dfs_ha_initial_namenode_standby" : "host2”
  }
}
  }
{code}
# The current logic is to always bootstrap the name node marked as standby. 
# This will lead to the Namenode marked as Standby to never start under the 
following situation
- Cluster is deployed successfully
- Both name nodes are stopped
- Start the name node marked as standby. Namenode will never start.
- This is because the standby name node will try to bootstrap again. 
- However to bootstrap a name node an active name node is required. Based on 
the HDFS logic the first step done when bootstrapping is to connect to the 
Active Namenode. 
- Also there is no need to bootstrap here as the name node should already be 
bootstrapped and should come back up as “Active"

  was:
*Issue:*
# During Namenode HA blueprint deployment, we configure the name nodes to start 
in active/standby mode based on the following properties
{code}
 {
"hadoop-env": {
  "properties" : {
"dfs_ha_initial_namenode_active" : 
"jay-msft-1.c.pramod-thangali.internal",
"dfs_ha_initial_namenode_standby" : 
"jay-msft-2.c.pramod-thangali.internal”
  }
}
  }
{code}
# The current logic is to always bootstrap the name node marked as standby. 
# This will lead to the Namenode marked as Standby to never start under the 
following situation
- Cluster is deployed successfully
- Both name nodes are stopped
- Start the name node marked as standby. Namenode will never start.
- This is because the standby name node will try to bootstrap again. 
- However to bootstrap a name node an active name node is required. Based on 
the HDFS logic the first step done when bootstrapping is to connect to the 
Active Namenode. 
- Also there is no need to bootstrap here as the name node should already be 
bootstrapped and should come back up as “Active"


> Namenode marked as INITIAL standby could potentially never start if other 
> namenode is down
> --
>
> Key: AMBARI-16028
> URL: https://issues.apache.org/jira/browse/AMBARI-16028
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16028-trunk.patch
>
>
> *Issue:*
> # During Namenode HA blueprint deployment, we configure the name nodes to 
> start in active/standby mode based on the following properties
> {code}
>  {
> "hadoop-env": {
>   "properties" : {
> "dfs_ha_initial_namenode_active" : "host1",
> "dfs_ha_initial_namenode_standby" : "host2”
>   }
> }
>   }
> {code}
> # The current logic is to always bootstrap the name node marked as standby. 
> # This will lead to the Namenode marked as Standby to never start under the 
> following situation
> - Cluster is deployed successfully
> - Both name nodes are stopped
> - Start the name node marked as standby. Namenode will never start.
> - This is because the standby name node will try to bootstrap again. 
> - However to bootstrap a name node an active name node is required. Based on 
> the HDFS logic the first step done when bootstrapping is to connect to the 
> Active Namenode. 
> - Also there is no need to bootstrap here as the name node should already be 
> bootstrapped and should come back up as “Active"



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

[jira] [Updated] (AMBARI-16028) Namenode marked as INITIAL standby could potentially never start if other namenode is down

2016-04-21 Thread Jayush Luniya (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-16028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayush Luniya updated AMBARI-16028:
---
Attachment: AMBARI-16028-trunk.patch

> Namenode marked as INITIAL standby could potentially never start if other 
> namenode is down
> --
>
> Key: AMBARI-16028
> URL: https://issues.apache.org/jira/browse/AMBARI-16028
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16028-trunk.patch
>
>
> *Issue:*
> # During Namenode HA blueprint deployment, we configure the name nodes to 
> start in active/standby mode based on the following properties
> {code}
>  {
> "hadoop-env": {
>   "properties" : {
> "dfs_ha_initial_namenode_active" : 
> "jay-msft-1.c.pramod-thangali.internal",
> "dfs_ha_initial_namenode_standby" : 
> "jay-msft-2.c.pramod-thangali.internal”
>   }
> }
>   }
> {code}
> # The current logic is to always bootstrap the name node marked as standby. 
> # This will lead to the Namenode marked as Standby to never start under the 
> following situation
> - Cluster is deployed successfully
> - Both name nodes are stopped
> - Start the name node marked as standby. Namenode will never start.
> - This is because the standby name node will try to bootstrap again. 
> - However to bootstrap a name node an active name node is required. Based on 
> the HDFS logic the first step done when bootstrapping is to connect to the 
> Active Namenode. 
> - Also there is no need to bootstrap here as the name node should already be 
> bootstrapped and should come back up as “Active"



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

[jira] [Updated] (AMBARI-16028) Namenode marked as INITIAL standby could potentially never start if other namenode is down

2016-04-21 Thread Jayush Luniya (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-16028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayush Luniya updated AMBARI-16028:
---
Status: Patch Available  (was: In Progress)

> Namenode marked as INITIAL standby could potentially never start if other 
> namenode is down
> --
>
> Key: AMBARI-16028
> URL: https://issues.apache.org/jira/browse/AMBARI-16028
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16028-trunk.patch
>
>
> *Issue:*
> # During Namenode HA blueprint deployment, we configure the name nodes to 
> start in active/standby mode based on the following properties
> {code}
>  {
> "hadoop-env": {
>   "properties" : {
> "dfs_ha_initial_namenode_active" : 
> "jay-msft-1.c.pramod-thangali.internal",
> "dfs_ha_initial_namenode_standby" : 
> "jay-msft-2.c.pramod-thangali.internal”
>   }
> }
>   }
> {code}
> # The current logic is to always bootstrap the name node marked as standby. 
> # This will lead to the Namenode marked as Standby to never start under the 
> following situation
> - Cluster is deployed successfully
> - Both name nodes are stopped
> - Start the name node marked as standby. Namenode will never start.
> - This is because the standby name node will try to bootstrap again. 
> - However to bootstrap a name node an active name node is required. Based on 
> the HDFS logic the first step done when bootstrapping is to connect to the 
> Active Namenode. 
> - Also there is no need to bootstrap here as the name node should already be 
> bootstrapped and should come back up as “Active"



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