[jira] [Commented] (AMBARI-16417) More information for Standby sync alert
[
https://issues.apache.org/jira/browse/AMBARI-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280854#comment-15280854
]
jun aoki commented on AMBARI-16417:
---
Committed to trunk
b9ed455d5df1c5cec968234e0e6c7019413b68c8
> More information for Standby sync alert
> ---
>
> Key: AMBARI-16417
> URL: https://issues.apache.org/jira/browse/AMBARI-16417
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: jun aoki
>Assignee: jun aoki
>Priority: Minor
> Attachments: AMBARI-16417-trunk.v1.patch,
> AMBARI-16417-trunk.v2.patch, AMBARI-16417-trunk.v3.patch
>
>
> When Standby master is down (actually I removed it through API, and it got
> deleted but somehow the configuration has the old IP) the hawq alert pops
> up(, which is good) but only saying "HAWQSTANDBY is not in sync with
> HAWQMASTER".
> If you take a close look at gp_master_mirroring table, it has more detailed
> information. (in this case, connection issue)
> {code}
> [gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from
> gp_master_mirroring;"
> summary_state | detail_state |log_time|
>error_message
> --+--++--
> Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error
> received sending data to standby master: server closed the connection
> unexpectedly
> : This
> probably means the server terminated abnormally
> :
> before or while processing the request.
> :
> (1 row)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16417) More information for Standby sync alert
[
https://issues.apache.org/jira/browse/AMBARI-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jun aoki updated AMBARI-16417:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> More information for Standby sync alert
> ---
>
> Key: AMBARI-16417
> URL: https://issues.apache.org/jira/browse/AMBARI-16417
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: jun aoki
>Assignee: jun aoki
>Priority: Minor
> Attachments: AMBARI-16417-trunk.v1.patch,
> AMBARI-16417-trunk.v2.patch, AMBARI-16417-trunk.v3.patch
>
>
> When Standby master is down (actually I removed it through API, and it got
> deleted but somehow the configuration has the old IP) the hawq alert pops
> up(, which is good) but only saying "HAWQSTANDBY is not in sync with
> HAWQMASTER".
> If you take a close look at gp_master_mirroring table, it has more detailed
> information. (in this case, connection issue)
> {code}
> [gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from
> gp_master_mirroring;"
> summary_state | detail_state |log_time|
>error_message
> --+--++--
> Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error
> received sending data to standby master: server closed the connection
> unexpectedly
> : This
> probably means the server terminated abnormally
> :
> before or while processing the request.
> :
> (1 row)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16417) More information for Standby sync alert
[
https://issues.apache.org/jira/browse/AMBARI-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jun aoki updated AMBARI-16417:
--
Status: Patch Available (was: Open)
> More information for Standby sync alert
> ---
>
> Key: AMBARI-16417
> URL: https://issues.apache.org/jira/browse/AMBARI-16417
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: jun aoki
>Assignee: jun aoki
>Priority: Minor
> Attachments: AMBARI-16417-trunk.v1.patch,
> AMBARI-16417-trunk.v2.patch, AMBARI-16417-trunk.v3.patch
>
>
> When Standby master is down (actually I removed it through API, and it got
> deleted but somehow the configuration has the old IP) the hawq alert pops
> up(, which is good) but only saying "HAWQSTANDBY is not in sync with
> HAWQMASTER".
> If you take a close look at gp_master_mirroring table, it has more detailed
> information. (in this case, connection issue)
> {code}
> [gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from
> gp_master_mirroring;"
> summary_state | detail_state |log_time|
>error_message
> --+--++--
> Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error
> received sending data to standby master: server closed the connection
> unexpectedly
> : This
> probably means the server terminated abnormally
> :
> before or while processing the request.
> :
> (1 row)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16417) More information for Standby sync alert
[
https://issues.apache.org/jira/browse/AMBARI-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jun aoki updated AMBARI-16417:
--
Attachment: AMBARI-16417-trunk.v3.patch
> More information for Standby sync alert
> ---
>
> Key: AMBARI-16417
> URL: https://issues.apache.org/jira/browse/AMBARI-16417
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: jun aoki
>Assignee: jun aoki
>Priority: Minor
> Attachments: AMBARI-16417-trunk.v1.patch,
> AMBARI-16417-trunk.v2.patch, AMBARI-16417-trunk.v3.patch
>
>
> When Standby master is down (actually I removed it through API, and it got
> deleted but somehow the configuration has the old IP) the hawq alert pops
> up(, which is good) but only saying "HAWQSTANDBY is not in sync with
> HAWQMASTER".
> If you take a close look at gp_master_mirroring table, it has more detailed
> information. (in this case, connection issue)
> {code}
> [gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from
> gp_master_mirroring;"
> summary_state | detail_state |log_time|
>error_message
> --+--++--
> Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error
> received sending data to standby master: server closed the connection
> unexpectedly
> : This
> probably means the server terminated abnormally
> :
> before or while processing the request.
> :
> (1 row)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16417) More information for Standby sync alert
[
https://issues.apache.org/jira/browse/AMBARI-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jun aoki updated AMBARI-16417:
--
Attachment: AMBARI-16417-trunk.v2.patch
> More information for Standby sync alert
> ---
>
> Key: AMBARI-16417
> URL: https://issues.apache.org/jira/browse/AMBARI-16417
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: jun aoki
>Assignee: jun aoki
>Priority: Minor
> Attachments: AMBARI-16417-trunk.v1.patch, AMBARI-16417-trunk.v2.patch
>
>
> When Standby master is down (actually I removed it through API, and it got
> deleted but somehow the configuration has the old IP) the hawq alert pops
> up(, which is good) but only saying "HAWQSTANDBY is not in sync with
> HAWQMASTER".
> If you take a close look at gp_master_mirroring table, it has more detailed
> information. (in this case, connection issue)
> {code}
> [gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from
> gp_master_mirroring;"
> summary_state | detail_state |log_time|
>error_message
> --+--++--
> Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error
> received sending data to standby master: server closed the connection
> unexpectedly
> : This
> probably means the server terminated abnormally
> :
> before or while processing the request.
> :
> (1 row)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16417) More information for Standby sync alert
[
https://issues.apache.org/jira/browse/AMBARI-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jun aoki updated AMBARI-16417:
--
Description:
When Standby master is down (actually I removed it through API, and it got
deleted but somehow the configuration has the old IP) the hawq alert pops up(,
which is good) but only saying "HAWQSTANDBY is not in sync with HAWQMASTER".
If you take a close look at gp_master_mirroring table, it has more detailed
information. (in this case, connection issue)
{code}
[gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from
gp_master_mirroring;"
summary_state | detail_state |log_time|
error_message
--+--++--
Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error received
sending data to standby master: server closed the connection unexpectedly
: This
probably means the server terminated abnormally
: before
or while processing the request.
:
(1 row)
{code}
was:
This is a good-to-have.
When Standby master is down (actually I removed it through API, and it got
deleted but somehow the configuration has the old IP) the hawq alert pops up(,
which is good) but only saying "HAWQSTANDBY is not in sync with HAWQMASTER".
If you take a close look at gp_master_mirroring table, it has more detailed
information. (in this case, connection issue)
{code}
[gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from
gp_master_mirroring;"
summary_state | detail_state |log_time|
error_message
--+--++--
Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error received
sending data to standby master: server closed the connection unexpectedly
: This
probably means the server terminated abnormally
: before
or while processing the request.
:
(1 row)
{code}
> More information for Standby sync alert
> ---
>
> Key: AMBARI-16417
> URL: https://issues.apache.org/jira/browse/AMBARI-16417
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: jun aoki
>Assignee: jun aoki
>Priority: Minor
> Attachments: AMBARI-16417-trunk.v1.patch
>
>
> When Standby master is down (actually I removed it through API, and it got
> deleted but somehow the configuration has the old IP) the hawq alert pops
> up(, which is good) but only saying "HAWQSTANDBY is not in sync with
> HAWQMASTER".
> If you take a close look at gp_master_mirroring table, it has more detailed
> information. (in this case, connection issue)
> {code}
> [gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from
> gp_master_mirroring;"
> summary_state | detail_state |log_time|
>error_message
> --+--++--
> Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error
> received sending data to standby master: server closed the connection
> unexpectedly
> : This
> probably means the server terminated abnormally
> :
> before or while processing the request.
> :
> (1 row)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16417) More information for Standby sync alert
[
https://issues.apache.org/jira/browse/AMBARI-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jun aoki updated AMBARI-16417:
--
Attachment: AMBARI-16417-trunk.v1.patch
> More information for Standby sync alert
> ---
>
> Key: AMBARI-16417
> URL: https://issues.apache.org/jira/browse/AMBARI-16417
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: jun aoki
>Assignee: jun aoki
>Priority: Minor
> Attachments: AMBARI-16417-trunk.v1.patch
>
>
> This is a good-to-have.
> When Standby master is down (actually I removed it through API, and it got
> deleted but somehow the configuration has the old IP) the hawq alert pops
> up(, which is good) but only saying "HAWQSTANDBY is not in sync with
> HAWQMASTER".
> If you take a close look at gp_master_mirroring table, it has more detailed
> information. (in this case, connection issue)
> {code}
> [gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from
> gp_master_mirroring;"
> summary_state | detail_state |log_time|
>error_message
> --+--++--
> Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error
> received sending data to standby master: server closed the connection
> unexpectedly
> : This
> probably means the server terminated abnormally
> :
> before or while processing the request.
> :
> (1 row)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-16417) More information for Standby sync alert
jun aoki created AMBARI-16417: - Summary: More information for Standby sync alert Key: AMBARI-16417 URL: https://issues.apache.org/jira/browse/AMBARI-16417 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: jun aoki Assignee: jun aoki Priority: Minor This is a good-to-have. When Standby master is down (actually I removed it through API, and it got deleted but somehow the configuration has the old IP) the hawq alert pops up(, which is good) but only saying "HAWQSTANDBY is not in sync with HAWQMASTER". If you take a close look at gp_master_mirroring table, it has more detailed information. (in this case, connection issue) ``` [gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from gp_master_mirroring;" summary_state | detail_state |log_time| error_message --+--++-- Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error received sending data to standby master: server closed the connection unexpectedly : This probably means the server terminated abnormally : before or while processing the request. : (1 row) ``` -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16417) More information for Standby sync alert
[
https://issues.apache.org/jira/browse/AMBARI-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jun aoki updated AMBARI-16417:
--
Description:
This is a good-to-have.
When Standby master is down (actually I removed it through API, and it got
deleted but somehow the configuration has the old IP) the hawq alert pops up(,
which is good) but only saying "HAWQSTANDBY is not in sync with HAWQMASTER".
If you take a close look at gp_master_mirroring table, it has more detailed
information. (in this case, connection issue)
{code}
[gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from
gp_master_mirroring;"
summary_state | detail_state |log_time|
error_message
--+--++--
Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error received
sending data to standby master: server closed the connection unexpectedly
: This
probably means the server terminated abnormally
: before
or while processing the request.
:
(1 row)
{code}
was:
This is a good-to-have.
When Standby master is down (actually I removed it through API, and it got
deleted but somehow the configuration has the old IP) the hawq alert pops up(,
which is good) but only saying "HAWQSTANDBY is not in sync with HAWQMASTER".
If you take a close look at gp_master_mirroring table, it has more detailed
information. (in this case, connection issue)
```
[gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from
gp_master_mirroring;"
summary_state | detail_state |log_time|
error_message
--+--++--
Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error received
sending data to standby master: server closed the connection unexpectedly
: This
probably means the server terminated abnormally
: before
or while processing the request.
:
(1 row)
```
> More information for Standby sync alert
> ---
>
> Key: AMBARI-16417
> URL: https://issues.apache.org/jira/browse/AMBARI-16417
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: jun aoki
>Assignee: jun aoki
>Priority: Minor
>
> This is a good-to-have.
> When Standby master is down (actually I removed it through API, and it got
> deleted but somehow the configuration has the old IP) the hawq alert pops
> up(, which is good) but only saying "HAWQSTANDBY is not in sync with
> HAWQMASTER".
> If you take a close look at gp_master_mirroring table, it has more detailed
> information. (in this case, connection issue)
> {code}
> [gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from
> gp_master_mirroring;"
> summary_state | detail_state |log_time|
>error_message
> --+--++--
> Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error
> received sending data to standby master: server closed the connection
> unexpectedly
> : This
> probably means the server terminated abnormally
> :
> before or while processing the request.
> :
> (1 row)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16237) PXF alert: change the message to make it more meaningful when both namenodes are down on Secured HA cluster.
[ https://issues.apache.org/jira/browse/AMBARI-16237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272795#comment-15272795 ] jun aoki commented on AMBARI-16237: --- Committed to trunk be7f69625e354123facf0df369a29a3da85462ec > PXF alert: change the message to make it more meaningful when both namenodes > are down on Secured HA cluster. > -- > > Key: AMBARI-16237 > URL: https://issues.apache.org/jira/browse/AMBARI-16237 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-16237-trunk.v1.patch, AMBARI-16237-trunk.v2.patch > > > PXF alerts shows "Configuration parameter 'fs_root' was not found in > configurations dictionary!" when both namnodes are down on secured NN HA > environment, which the error message is not too clear. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16237) PXF alert: change the message to make it more meaningful when both namenodes are down on Secured HA cluster.
[ https://issues.apache.org/jira/browse/AMBARI-16237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-16237: -- Fix Version/s: trunk > PXF alert: change the message to make it more meaningful when both namenodes > are down on Secured HA cluster. > -- > > Key: AMBARI-16237 > URL: https://issues.apache.org/jira/browse/AMBARI-16237 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-16237-trunk.v1.patch, AMBARI-16237-trunk.v2.patch > > > PXF alerts shows "Configuration parameter 'fs_root' was not found in > configurations dictionary!" when both namnodes are down on secured NN HA > environment, which the error message is not too clear. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16237) PXF alert: change the message to make it more meaningful when both namenodes are down on Secured HA cluster.
[ https://issues.apache.org/jira/browse/AMBARI-16237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-16237: -- Attachment: AMBARI-16237-trunk.v2.patch > PXF alert: change the message to make it more meaningful when both namenodes > are down on Secured HA cluster. > -- > > Key: AMBARI-16237 > URL: https://issues.apache.org/jira/browse/AMBARI-16237 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Attachments: AMBARI-16237-trunk.v1.patch, AMBARI-16237-trunk.v2.patch > > > PXF alerts shows "Configuration parameter 'fs_root' was not found in > configurations dictionary!" when both namnodes are down on secured NN HA > environment, which the error message is not too clear. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16237) PXF alert: change the message to make it more meaningful when both namenodes are down on Secured HA cluster.
[ https://issues.apache.org/jira/browse/AMBARI-16237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-16237: -- Status: Patch Available (was: Open) > PXF alert: change the message to make it more meaningful when both namenodes > are down on Secured HA cluster. > -- > > Key: AMBARI-16237 > URL: https://issues.apache.org/jira/browse/AMBARI-16237 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Attachments: AMBARI-16237-trunk.v1.patch > > > PXF alerts shows "Configuration parameter 'fs_root' was not found in > configurations dictionary!" when both namnodes are down on secured NN HA > environment, which the error message is not too clear. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16237) PXF alert: change the message to make it more meaningful when both namenodes are down on Secured HA cluster.
[ https://issues.apache.org/jira/browse/AMBARI-16237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-16237: -- Attachment: AMBARI-16237-trunk.v1.patch > PXF alert: change the message to make it more meaningful when both namenodes > are down on Secured HA cluster. > -- > > Key: AMBARI-16237 > URL: https://issues.apache.org/jira/browse/AMBARI-16237 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Attachments: AMBARI-16237-trunk.v1.patch > > > PXF alerts shows "Configuration parameter 'fs_root' was not found in > configurations dictionary!" when both namnodes are down on secured NN HA > environment, which the error message is not too clear. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16237) PXF alert: change the message to make it more meaningful when both namenodes are down on Secured HA cluster.
jun aoki created AMBARI-16237: - Summary: PXF alert: change the message to make it more meaningful when both namenodes are down on Secured HA cluster. Key: AMBARI-16237 URL: https://issues.apache.org/jira/browse/AMBARI-16237 Project: Ambari Issue Type: Bug Reporter: jun aoki Assignee: jun aoki Priority: Minor Attachments: AMBARI-16237-trunk.v1.patch PXF alerts shows "Configuration parameter 'fs_root' was not found in configurations dictionary!" when both namnodes are down on secured NN HA environment, which the error message is not too clear. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16232) Enabling Kerberos wizard want fill the readonly REALM field on step4
[ https://issues.apache.org/jira/browse/AMBARI-16232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-16232: -- Attachment: realm-is-not-filled.png > Enabling Kerberos wizard want fill the readonly REALM field on step4 > > > Key: AMBARI-16232 > URL: https://issues.apache.org/jira/browse/AMBARI-16232 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: jun aoki > Attachments: realm-is-not-filled.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16232) Enabling Kerberos wizard want fill the readonly REALM field on step4
jun aoki created AMBARI-16232: - Summary: Enabling Kerberos wizard want fill the readonly REALM field on step4 Key: AMBARI-16232 URL: https://issues.apache.org/jira/browse/AMBARI-16232 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: jun aoki Attachments: realm-is-not-filled.png -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16174) Move RM wizard should update HAWQ related parameters
[ https://issues.apache.org/jira/browse/AMBARI-16174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269217#comment-15269217 ] jun aoki commented on AMBARI-16174: --- Got a +1 on reviewboard. Committed to trunk 7d0d33a49cfd4b8fb832ad6f0aa5f7e4b48ea048 > Move RM wizard should update HAWQ related parameters > > > Key: AMBARI-16174 > URL: https://issues.apache.org/jira/browse/AMBARI-16174 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Attachments: AMBARI-16174-trunk.v1.patch, > AMBARI-16174-trunk.v2.patch, AMBARI-16174-trunk.v3.patch > > > when RM HA is not enabled, following properties should be updated in > hawq-site.xml should be updated. > hawq_rm_yarn_address > hawq_rm_yarn_scheduler_address > When RM HA Is enabled and then a RM is moved, following properties in > yarn-client.xml should be updated > yarn.resourcemanager.ha > yarn.resourcemanager.scheduler.ha -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16174) Move RM wizard should update HAWQ related parameters
[ https://issues.apache.org/jira/browse/AMBARI-16174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-16174: -- Attachment: AMBARI-16174-trunk.v3.patch > Move RM wizard should update HAWQ related parameters > > > Key: AMBARI-16174 > URL: https://issues.apache.org/jira/browse/AMBARI-16174 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Attachments: AMBARI-16174-trunk.v1.patch, > AMBARI-16174-trunk.v2.patch, AMBARI-16174-trunk.v3.patch > > > when RM HA is not enabled, following properties should be updated in > hawq-site.xml should be updated. > hawq_rm_yarn_address > hawq_rm_yarn_scheduler_address > When RM HA Is enabled and then a RM is moved, following properties in > yarn-client.xml should be updated > yarn.resourcemanager.ha > yarn.resourcemanager.scheduler.ha -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16174) Move RM wizard should update HAWQ related parameters
[ https://issues.apache.org/jira/browse/AMBARI-16174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-16174: -- Attachment: AMBARI-16174-trunk.v2.patch > Move RM wizard should update HAWQ related parameters > > > Key: AMBARI-16174 > URL: https://issues.apache.org/jira/browse/AMBARI-16174 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Attachments: AMBARI-16174-trunk.v1.patch, AMBARI-16174-trunk.v2.patch > > > when RM HA is not enabled, following properties should be updated in > hawq-site.xml should be updated. > hawq_rm_yarn_address > hawq_rm_yarn_scheduler_address > When RM HA Is enabled and then a RM is moved, following properties in > yarn-client.xml should be updated > yarn.resourcemanager.ha > yarn.resourcemanager.scheduler.ha -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16174) Move RM wizard should update HAWQ related parameters
[ https://issues.apache.org/jira/browse/AMBARI-16174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-16174: -- Status: Patch Available (was: Open) > Move RM wizard should update HAWQ related parameters > > > Key: AMBARI-16174 > URL: https://issues.apache.org/jira/browse/AMBARI-16174 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Attachments: AMBARI-16174-trunk.v1.patch > > > when RM HA is not enabled, following properties should be updated in > hawq-site.xml should be updated. > hawq_rm_yarn_address > hawq_rm_yarn_scheduler_address > When RM HA Is enabled and then a RM is moved, following properties in > yarn-client.xml should be updated > yarn.resourcemanager.ha > yarn.resourcemanager.scheduler.ha -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16174) Move RM wizard should update HAWQ related parameters
[ https://issues.apache.org/jira/browse/AMBARI-16174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-16174: -- Attachment: AMBARI-16174-trunk.v1.patch > Move RM wizard should update HAWQ related parameters > > > Key: AMBARI-16174 > URL: https://issues.apache.org/jira/browse/AMBARI-16174 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Attachments: AMBARI-16174-trunk.v1.patch > > > when RM HA is not enabled, following properties should be updated in > hawq-site.xml should be updated. > hawq_rm_yarn_address > hawq_rm_yarn_scheduler_address > When RM HA Is enabled and then a RM is moved, following properties in > yarn-client.xml should be updated > yarn.resourcemanager.ha > yarn.resourcemanager.scheduler.ha -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16176) Move Master Wizard for RM does not allow any of host.
[ https://issues.apache.org/jira/browse/AMBARI-16176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-16176: -- Attachment: screenshot-1.png > Move Master Wizard for RM does not allow any of host. > - > > Key: AMBARI-16176 > URL: https://issues.apache.org/jira/browse/AMBARI-16176 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: jun aoki > Attachments: screenshot-1.png > > > Move Master Wizard (confirmed for RM) won't let you choose any hosts. > Next button is kept disabled no matter what host you choose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16176) Move Master Wizard for RM does not allow any of host.
[ https://issues.apache.org/jira/browse/AMBARI-16176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-16176: -- Affects Version/s: trunk > Move Master Wizard for RM does not allow any of host. > - > > Key: AMBARI-16176 > URL: https://issues.apache.org/jira/browse/AMBARI-16176 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: jun aoki > Attachments: screenshot-1.png > > > Move Master Wizard (confirmed for RM) won't let you choose any hosts. > Next button is kept disabled no matter what host you choose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16176) Move Master Wizard for RM does not allow any of host.
jun aoki created AMBARI-16176: - Summary: Move Master Wizard for RM does not allow any of host. Key: AMBARI-16176 URL: https://issues.apache.org/jira/browse/AMBARI-16176 Project: Ambari Issue Type: Bug Reporter: jun aoki Move Master Wizard (confirmed for RM) won't let you choose any hosts. Next button is kept disabled no matter what host you choose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16174) Move RM wizard should update HAWQ related parameters
jun aoki created AMBARI-16174: - Summary: Move RM wizard should update HAWQ related parameters Key: AMBARI-16174 URL: https://issues.apache.org/jira/browse/AMBARI-16174 Project: Ambari Issue Type: Bug Reporter: jun aoki Assignee: jun aoki Priority: Minor when RM HA is not enabled, following properties should be updated in hawq-site.xml should be updated. hawq_rm_yarn_address hawq_rm_yarn_scheduler_address When RM HA Is enabled and then a RM is moved, following properties in yarn-client.xml should be updated yarn.resourcemanager.ha yarn.resourcemanager.scheduler.ha -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252616#comment-15252616 ] jun aoki commented on AMBARI-16024: --- [~bhuvnesh2703], I might be missing some background context but have a question. In general, changing topology (in this case removing standby) and followed by performing a service check is a right thing to do. The problem occurs when HDFS HA, but is Remove Standby wizard OK when HDFS non-HA? I'd rather keep Service Check running on Remove Standby wizard, but fix a wizard to enable HDFS HA to update "the old filespace"? Just my 2 cents > Remove performing service check during "Remove Standby Wizard" > -- > > Key: AMBARI-16024 > URL: https://issues.apache.org/jira/browse/AMBARI-16024 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.3.0 > > Attachments: AMBARI-16024.patch > > > Users will need to remove the HAWQ Standby Master using "Remove Standby > Wizard" after enabling HDFS HA. > So the service check may fail during the wizard as the HAWQ catalog might be > still pointing to the old filespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15926) HAWQ activate standby wizard fails after port number change but before restart.
[ https://issues.apache.org/jira/browse/AMBARI-15926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15248386#comment-15248386 ] jun aoki commented on AMBARI-15926: --- Committed to trunk 9ed03583b8bdce6be57f482cb88db62d185dd027 > HAWQ activate standby wizard fails after port number change but before > restart. > --- > > Key: AMBARI-15926 > URL: https://issues.apache.org/jira/browse/AMBARI-15926 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: 2.2.2 > > Attachments: AMBARI-15926-branch-2.2.v1.patch, > AMBARI-15926-trunk.v1.patch > > > Precondition: > Install HAWQ with master and standby master (HA) > Steps: > 1. Go to HAWQ's config and change master port number and standby port number. > 2. Do not restart HAWQ service > 3. Run Activate Standby wizard > Expected: > Succeeded. > Actual: > It fails due to probably "hawq activate standby" command transition the > standby master to master with an old port without Ambari knowing it. > And the following actions (stop) fails because the port number is different. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15926) HAWQ activate standby wizard fails after port number change but before restart.
[ https://issues.apache.org/jira/browse/AMBARI-15926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15926: -- Resolution: Fixed Status: Resolved (was: Patch Available) > HAWQ activate standby wizard fails after port number change but before > restart. > --- > > Key: AMBARI-15926 > URL: https://issues.apache.org/jira/browse/AMBARI-15926 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: 2.2.2 > > Attachments: AMBARI-15926-branch-2.2.v1.patch, > AMBARI-15926-trunk.v1.patch > > > Precondition: > Install HAWQ with master and standby master (HA) > Steps: > 1. Go to HAWQ's config and change master port number and standby port number. > 2. Do not restart HAWQ service > 3. Run Activate Standby wizard > Expected: > Succeeded. > Actual: > It fails due to probably "hawq activate standby" command transition the > standby master to master with an old port without Ambari knowing it. > And the following actions (stop) fails because the port number is different. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15926) HAWQ activate standby wizard fails after port number change but before restart.
[ https://issues.apache.org/jira/browse/AMBARI-15926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15926: -- Attachment: AMBARI-15926-trunk.v1.patch > HAWQ activate standby wizard fails after port number change but before > restart. > --- > > Key: AMBARI-15926 > URL: https://issues.apache.org/jira/browse/AMBARI-15926 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: 2.2.2 > > Attachments: AMBARI-15926-branch-2.2.v1.patch, > AMBARI-15926-trunk.v1.patch > > > Precondition: > Install HAWQ with master and standby master (HA) > Steps: > 1. Go to HAWQ's config and change master port number and standby port number. > 2. Do not restart HAWQ service > 3. Run Activate Standby wizard > Expected: > Succeeded. > Actual: > It fails due to probably "hawq activate standby" command transition the > standby master to master with an old port without Ambari knowing it. > And the following actions (stop) fails because the port number is different. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15926) HAWQ activate standby wizard fails after port number change but before restart.
[ https://issues.apache.org/jira/browse/AMBARI-15926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15926: -- Status: Patch Available (was: Open) > HAWQ activate standby wizard fails after port number change but before > restart. > --- > > Key: AMBARI-15926 > URL: https://issues.apache.org/jira/browse/AMBARI-15926 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: 2.2.2 > > Attachments: AMBARI-15926-branch-2.2.v1.patch, > AMBARI-15926-trunk.v1.patch > > > Precondition: > Install HAWQ with master and standby master (HA) > Steps: > 1. Go to HAWQ's config and change master port number and standby port number. > 2. Do not restart HAWQ service > 3. Run Activate Standby wizard > Expected: > Succeeded. > Actual: > It fails due to probably "hawq activate standby" command transition the > standby master to master with an old port without Ambari knowing it. > And the following actions (stop) fails because the port number is different. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15926) HAWQ activate standby wizard fails after port number change but before restart.
[ https://issues.apache.org/jira/browse/AMBARI-15926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246520#comment-15246520 ] jun aoki commented on AMBARI-15926: --- Committed to branch-2.2.2 add3a20cabc77902de947b05b172c1b9eb832162 Committed to branc-2.2 980a4d94686446be1bd04ec67cf74f9ec88762bb > HAWQ activate standby wizard fails after port number change but before > restart. > --- > > Key: AMBARI-15926 > URL: https://issues.apache.org/jira/browse/AMBARI-15926 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: 2.2.2 > > Attachments: AMBARI-15926-branch-2.2.v1.patch > > > Precondition: > Install HAWQ with master and standby master (HA) > Steps: > 1. Go to HAWQ's config and change master port number and standby port number. > 2. Do not restart HAWQ service > 3. Run Activate Standby wizard > Expected: > Succeeded. > Actual: > It fails due to probably "hawq activate standby" command transition the > standby master to master with an old port without Ambari knowing it. > And the following actions (stop) fails because the port number is different. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15926) HAWQ activate standby wizard fails after port number change but before restart.
[ https://issues.apache.org/jira/browse/AMBARI-15926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15926: -- Attachment: AMBARI-15926-branch-2.2.v1.patch > HAWQ activate standby wizard fails after port number change but before > restart. > --- > > Key: AMBARI-15926 > URL: https://issues.apache.org/jira/browse/AMBARI-15926 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: 2.2.2 > > Attachments: AMBARI-15926-branch-2.2.v1.patch > > > Precondition: > Install HAWQ with master and standby master (HA) > Steps: > 1. Go to HAWQ's config and change master port number and standby port number. > 2. Do not restart HAWQ service > 3. Run Activate Standby wizard > Expected: > Succeeded. > Actual: > It fails due to probably "hawq activate standby" command transition the > standby master to master with an old port without Ambari knowing it. > And the following actions (stop) fails because the port number is different. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15852) Changing HAWQ Ports through Ambari prevents HAWQ service from restarting
[ https://issues.apache.org/jira/browse/AMBARI-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243907#comment-15243907 ] jun aoki commented on AMBARI-15852: --- Committed to trunk d13aa508569c2ee8afce4a746560e7a1d2b0e1a8 > Changing HAWQ Ports through Ambari prevents HAWQ service from restarting > > > Key: AMBARI-15852 > URL: https://issues.apache.org/jira/browse/AMBARI-15852 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.2 >Reporter: Matt >Assignee: jun aoki >Priority: Blocker > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15852-branch-2.2.patch, > AMBARI-15852-branch-2.2.v2.patch, AMBARI-15852-branch-2.2.v3.patch, > AMBARI-15852-branch-2.2.v4.patch, AMBARI-15852-trunk.v1.patch > > > Steps to reproduce: > - The initial HAWQ masters port is set to 5432. > - Change port to 10432, and restart HAWQ service. > HAWQMASTER failed to start because it skipped stopping the process (it > attempted to stop process on 10432, while the process was actually running on > 5432). > Removing the only_if condition might fix this issue: > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py#L3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15852) Changing HAWQ Ports through Ambari prevents HAWQ service from restarting
[ https://issues.apache.org/jira/browse/AMBARI-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15852: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Changing HAWQ Ports through Ambari prevents HAWQ service from restarting > > > Key: AMBARI-15852 > URL: https://issues.apache.org/jira/browse/AMBARI-15852 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.2 >Reporter: Matt >Assignee: jun aoki >Priority: Blocker > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15852-branch-2.2.patch, > AMBARI-15852-branch-2.2.v2.patch, AMBARI-15852-branch-2.2.v3.patch, > AMBARI-15852-branch-2.2.v4.patch, AMBARI-15852-trunk.v1.patch > > > Steps to reproduce: > - The initial HAWQ masters port is set to 5432. > - Change port to 10432, and restart HAWQ service. > HAWQMASTER failed to start because it skipped stopping the process (it > attempted to stop process on 10432, while the process was actually running on > 5432). > Removing the only_if condition might fix this issue: > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py#L3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15852) Changing HAWQ Ports through Ambari prevents HAWQ service from restarting
[ https://issues.apache.org/jira/browse/AMBARI-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243686#comment-15243686 ] jun aoki commented on AMBARI-15852: --- Tested on trunk as well. Will commit to trunk > Changing HAWQ Ports through Ambari prevents HAWQ service from restarting > > > Key: AMBARI-15852 > URL: https://issues.apache.org/jira/browse/AMBARI-15852 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.2 >Reporter: Matt >Assignee: jun aoki >Priority: Blocker > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15852-branch-2.2.patch, > AMBARI-15852-branch-2.2.v2.patch, AMBARI-15852-branch-2.2.v3.patch, > AMBARI-15852-branch-2.2.v4.patch, AMBARI-15852-trunk.v1.patch > > > Steps to reproduce: > - The initial HAWQ masters port is set to 5432. > - Change port to 10432, and restart HAWQ service. > HAWQMASTER failed to start because it skipped stopping the process (it > attempted to stop process on 10432, while the process was actually running on > 5432). > Removing the only_if condition might fix this issue: > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py#L3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-15926) HAWQ activate standby wizard fails after port number change but before restart.
[ https://issues.apache.org/jira/browse/AMBARI-15926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki reassigned AMBARI-15926: - Assignee: jun aoki > HAWQ activate standby wizard fails after port number change but before > restart. > --- > > Key: AMBARI-15926 > URL: https://issues.apache.org/jira/browse/AMBARI-15926 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: 2.2.2 > > > Precondition: > Install HAWQ with master and standby master (HA) > Steps: > 1. Go to HAWQ's config and change master port number and standby port number. > 2. Do not restart HAWQ service > 3. Run Activate Standby wizard > Expected: > Succeeded. > Actual: > It fails due to probably "hawq activate standby" command transition the > standby master to master with an old port without Ambari knowing it. > And the following actions (stop) fails because the port number is different. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15852) Changing HAWQ Ports through Ambari prevents HAWQ service from restarting
[ https://issues.apache.org/jira/browse/AMBARI-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15852: -- Attachment: AMBARI-15852-trunk.v1.patch > Changing HAWQ Ports through Ambari prevents HAWQ service from restarting > > > Key: AMBARI-15852 > URL: https://issues.apache.org/jira/browse/AMBARI-15852 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.2 >Reporter: Matt >Assignee: jun aoki >Priority: Blocker > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15852-branch-2.2.patch, > AMBARI-15852-branch-2.2.v2.patch, AMBARI-15852-branch-2.2.v3.patch, > AMBARI-15852-branch-2.2.v4.patch, AMBARI-15852-trunk.v1.patch > > > Steps to reproduce: > - The initial HAWQ masters port is set to 5432. > - Change port to 10432, and restart HAWQ service. > HAWQMASTER failed to start because it skipped stopping the process (it > attempted to stop process on 10432, while the process was actually running on > 5432). > Removing the only_if condition might fix this issue: > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py#L3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15852) Changing HAWQ Ports through Ambari prevents HAWQ service from restarting
[ https://issues.apache.org/jira/browse/AMBARI-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243377#comment-15243377 ] jun aoki commented on AMBARI-15852: --- Committed to branch-2.2.2 209ade07b42b606188d8257955f47bc79eb8f4c1 Committed to branch-2.2 96e6fcec3cd8808bca3cd170e49c0ec5ae81dacf > Changing HAWQ Ports through Ambari prevents HAWQ service from restarting > > > Key: AMBARI-15852 > URL: https://issues.apache.org/jira/browse/AMBARI-15852 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.2 >Reporter: Matt >Assignee: jun aoki >Priority: Blocker > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15852-branch-2.2.patch, > AMBARI-15852-branch-2.2.v2.patch, AMBARI-15852-branch-2.2.v3.patch, > AMBARI-15852-branch-2.2.v4.patch > > > Steps to reproduce: > - The initial HAWQ masters port is set to 5432. > - Change port to 10432, and restart HAWQ service. > HAWQMASTER failed to start because it skipped stopping the process (it > attempted to stop process on 10432, while the process was actually running on > 5432). > Removing the only_if condition might fix this issue: > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py#L3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15926) HAWQ activate standby wizard fails after port number change but before restart.
jun aoki created AMBARI-15926: - Summary: HAWQ activate standby wizard fails after port number change but before restart. Key: AMBARI-15926 URL: https://issues.apache.org/jira/browse/AMBARI-15926 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.2.2 Reporter: jun aoki Priority: Minor Fix For: 2.2.2 Precondition: Install HAWQ with master and standby master (HA) Steps: 1. Go to HAWQ's config and change master port number and standby port number. 2. Do not restart HAWQ service 3. Run Activate Standby wizard Expected: Succeeded. Actual: It fails due to probably "hawq activate standby" command transition the standby master to master with an old port without Ambari knowing it. And the following actions (stop) fails because the port number is different. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15852) Changing HAWQ Ports through Ambari prevents HAWQ service from restarting
[ https://issues.apache.org/jira/browse/AMBARI-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15852: -- Attachment: AMBARI-15852-branch-2.2.v4.patch > Changing HAWQ Ports through Ambari prevents HAWQ service from restarting > > > Key: AMBARI-15852 > URL: https://issues.apache.org/jira/browse/AMBARI-15852 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.2 >Reporter: Matt >Assignee: jun aoki > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15852-branch-2.2.patch, > AMBARI-15852-branch-2.2.v2.patch, AMBARI-15852-branch-2.2.v3.patch, > AMBARI-15852-branch-2.2.v4.patch > > > Steps to reproduce: > - The initial HAWQ masters port is set to 5432. > - Change port to 10432, and restart HAWQ service. > HAWQMASTER failed to start because it skipped stopping the process (it > attempted to stop process on 10432, while the process was actually running on > 5432). > Removing the only_if condition might fix this issue: > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py#L3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15852) Changing HAWQ Ports through Ambari prevents HAWQ service from restarting
[ https://issues.apache.org/jira/browse/AMBARI-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15852: -- Attachment: AMBARI-15852-branch-2.2.v3.patch > Changing HAWQ Ports through Ambari prevents HAWQ service from restarting > > > Key: AMBARI-15852 > URL: https://issues.apache.org/jira/browse/AMBARI-15852 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.2 >Reporter: Matt >Assignee: jun aoki > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15852-branch-2.2.patch, > AMBARI-15852-branch-2.2.v2.patch, AMBARI-15852-branch-2.2.v3.patch > > > Steps to reproduce: > - The initial HAWQ masters port is set to 5432. > - Change port to 10432, and restart HAWQ service. > HAWQMASTER failed to start because it skipped stopping the process (it > attempted to stop process on 10432, while the process was actually running on > 5432). > Removing the only_if condition might fix this issue: > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py#L3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15852) Changing HAWQ Ports through Ambari prevents HAWQ service from restarting
[ https://issues.apache.org/jira/browse/AMBARI-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15852: -- Fix Version/s: (was: 2.2.0) > Changing HAWQ Ports through Ambari prevents HAWQ service from restarting > > > Key: AMBARI-15852 > URL: https://issues.apache.org/jira/browse/AMBARI-15852 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.2 >Reporter: Matt >Assignee: jun aoki > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15852-branch-2.2.patch, > AMBARI-15852-branch-2.2.v2.patch > > > Steps to reproduce: > - The initial HAWQ masters port is set to 5432. > - Change port to 10432, and restart HAWQ service. > HAWQMASTER failed to start because it skipped stopping the process (it > attempted to stop process on 10432, while the process was actually running on > 5432). > Removing the only_if condition might fix this issue: > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py#L3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15852) Changing HAWQ Ports through Ambari prevents HAWQ service from restarting
[ https://issues.apache.org/jira/browse/AMBARI-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15852: -- Fix Version/s: 2.2.0 > Changing HAWQ Ports through Ambari prevents HAWQ service from restarting > > > Key: AMBARI-15852 > URL: https://issues.apache.org/jira/browse/AMBARI-15852 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.2 >Reporter: Matt >Assignee: jun aoki > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15852-branch-2.2.patch, > AMBARI-15852-branch-2.2.v2.patch > > > Steps to reproduce: > - The initial HAWQ masters port is set to 5432. > - Change port to 10432, and restart HAWQ service. > HAWQMASTER failed to start because it skipped stopping the process (it > attempted to stop process on 10432, while the process was actually running on > 5432). > Removing the only_if condition might fix this issue: > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py#L3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15852) Changing HAWQ Ports through Ambari prevents HAWQ service from restarting
[ https://issues.apache.org/jira/browse/AMBARI-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15852: -- Attachment: AMBARI-15852-branch-2.2.v2.patch > Changing HAWQ Ports through Ambari prevents HAWQ service from restarting > > > Key: AMBARI-15852 > URL: https://issues.apache.org/jira/browse/AMBARI-15852 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.2 >Reporter: Matt >Assignee: jun aoki > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15852-branch-2.2.patch, > AMBARI-15852-branch-2.2.v2.patch > > > Steps to reproduce: > - The initial HAWQ masters port is set to 5432. > - Change port to 10432, and restart HAWQ service. > HAWQMASTER failed to start because it skipped stopping the process (it > attempted to stop process on 10432, while the process was actually running on > 5432). > Removing the only_if condition might fix this issue: > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py#L3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15852) Changing HAWQ Ports through Ambari prevents HAWQ service from restarting
[ https://issues.apache.org/jira/browse/AMBARI-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15852: -- Attachment: (was: AMBARI-15852-branch-2.2.v2.patch) > Changing HAWQ Ports through Ambari prevents HAWQ service from restarting > > > Key: AMBARI-15852 > URL: https://issues.apache.org/jira/browse/AMBARI-15852 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.2 >Reporter: Matt >Assignee: jun aoki > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15852-branch-2.2.patch > > > Steps to reproduce: > - The initial HAWQ masters port is set to 5432. > - Change port to 10432, and restart HAWQ service. > HAWQMASTER failed to start because it skipped stopping the process (it > attempted to stop process on 10432, while the process was actually running on > 5432). > Removing the only_if condition might fix this issue: > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py#L3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15852) Changing HAWQ Ports through Ambari prevents HAWQ service from restarting
[ https://issues.apache.org/jira/browse/AMBARI-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15852: -- Attachment: AMBARI-15852-branch-2.2.v2.patch > Changing HAWQ Ports through Ambari prevents HAWQ service from restarting > > > Key: AMBARI-15852 > URL: https://issues.apache.org/jira/browse/AMBARI-15852 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.2 >Reporter: Matt >Assignee: jun aoki > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15852-branch-2.2.patch, > AMBARI-15852-branch-2.2.v2.patch > > > Steps to reproduce: > - The initial HAWQ masters port is set to 5432. > - Change port to 10432, and restart HAWQ service. > HAWQMASTER failed to start because it skipped stopping the process (it > attempted to stop process on 10432, while the process was actually running on > 5432). > Removing the only_if condition might fix this issue: > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py#L3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15852) Changing HAWQ Ports through Ambari prevents HAWQ service from restarting
[ https://issues.apache.org/jira/browse/AMBARI-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15852: -- Attachment: AMBARI-15852-branch-2.2.patch > Changing HAWQ Ports through Ambari prevents HAWQ service from restarting > > > Key: AMBARI-15852 > URL: https://issues.apache.org/jira/browse/AMBARI-15852 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.2 >Reporter: Matt >Assignee: jun aoki > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15852-branch-2.2.patch > > > Steps to reproduce: > - The initial HAWQ masters port is set to 5432. > - Change port to 10432, and restart HAWQ service. > HAWQMASTER failed to start because it skipped stopping the process (it > attempted to stop process on 10432, while the process was actually running on > 5432). > Removing the only_if condition might fix this issue: > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py#L3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15852) Changing HAWQ Ports through Ambari prevents HAWQ service from restarting
[ https://issues.apache.org/jira/browse/AMBARI-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15852: -- Status: Patch Available (was: Open) > Changing HAWQ Ports through Ambari prevents HAWQ service from restarting > > > Key: AMBARI-15852 > URL: https://issues.apache.org/jira/browse/AMBARI-15852 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.2 >Reporter: Matt >Assignee: jun aoki > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15852-branch-2.2.patch > > > Steps to reproduce: > - The initial HAWQ masters port is set to 5432. > - Change port to 10432, and restart HAWQ service. > HAWQMASTER failed to start because it skipped stopping the process (it > attempted to stop process on 10432, while the process was actually running on > 5432). > Removing the only_if condition might fix this issue: > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py#L3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15475) Editing tmp dir from single to multiple dir doesn't trigger the backend change
[ https://issues.apache.org/jira/browse/AMBARI-15475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15475: -- Attachment: AMBARI-15475.branch-2.2.v2.patch > Editing tmp dir from single to multiple dir doesn't trigger the backend change > -- > > Key: AMBARI-15475 > URL: https://issues.apache.org/jira/browse/AMBARI-15475 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Attachments: AMBARI-15475.branch-2.2.patch, > AMBARI-15475.branch-2.2.v2.patch > > > Modified "HAWQ Segment Temp Directory” from one [/d1/tmp/hawqsegment] to > many > [/d1/tmp/hawqsegment,/d2/tmp/hawqsegment,/d3/tmp/hawqsegment,/d4/tmp/hawqsegment,/d5/tmp/hawqsegment] > and the change is not propagated to segments and the folders are not created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15475) Editing tmp dir from single to multiple dir doesn't trigger the backend change
[ https://issues.apache.org/jira/browse/AMBARI-15475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15475: -- Attachment: AMBARI-15475.branch-2.2.patch > Editing tmp dir from single to multiple dir doesn't trigger the backend change > -- > > Key: AMBARI-15475 > URL: https://issues.apache.org/jira/browse/AMBARI-15475 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Attachments: AMBARI-15475.branch-2.2.patch > > > Modified "HAWQ Segment Temp Directory” from one [/d1/tmp/hawqsegment] to > many > [/d1/tmp/hawqsegment,/d2/tmp/hawqsegment,/d3/tmp/hawqsegment,/d4/tmp/hawqsegment,/d5/tmp/hawqsegment] > and the change is not propagated to segments and the folders are not created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15475) Editing tmp dir from single to multiple dir doesn't trigger the backend change
[ https://issues.apache.org/jira/browse/AMBARI-15475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202458#comment-15202458 ] jun aoki commented on AMBARI-15475: --- Committed to branch-2.2 e4899550fc1f8f1fbfb17228175e15aa4cd8a18c > Editing tmp dir from single to multiple dir doesn't trigger the backend change > -- > > Key: AMBARI-15475 > URL: https://issues.apache.org/jira/browse/AMBARI-15475 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15475.branch-2.2.patch, > AMBARI-15475.branch-2.2.v2.patch, AMBARI-15475.branch-2.2.v3.patch > > > Modified "HAWQ Segment Temp Directory” from one [/d1/tmp/hawqsegment] to > many > [/d1/tmp/hawqsegment,/d2/tmp/hawqsegment,/d3/tmp/hawqsegment,/d4/tmp/hawqsegment,/d5/tmp/hawqsegment] > and the change is not propagated to segments and the folders are not created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15435) Update Hawq GUCS: Refactor resource related GUC
[
https://issues.apache.org/jira/browse/AMBARI-15435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200583#comment-15200583
]
jun aoki commented on AMBARI-15435:
---
For some reason, v2 patch fails
{code}
OK
--
Failed tests:
ERROR: test_recommendHAWQConfigurations
(test_stack_advisor.TestHDP23StackAdvisor)
--
Traceback (most recent call last):
File
"/home/jaoki/coding/ambari/ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py",
line 1486, in test_recommendHAWQConfigurations
self.assertEquals(configurations["hawq-site"]["properties"]["default_hash_table_bucket_number"],
str(3 * 6))
KeyError: 'default_hash_table_bucket_number'
--
{code}
Will look into it.
> Update Hawq GUCS: Refactor resource related GUC
> ---
>
> Key: AMBARI-15435
> URL: https://issues.apache.org/jira/browse/AMBARI-15435
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server, ambari-web
>Affects Versions: trunk, 2.2.2
>Reporter: Goutam Tadi
>Assignee: Goutam Tadi
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15435-trunk-v1.patch,
> AMBARI-15435-trunk-v2.patch, AMBARI-15435-trunk.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15475) Editing tmp dir from single to multiple dir doesn't trigger the backend change
jun aoki created AMBARI-15475: - Summary: Editing tmp dir from single to multiple dir doesn't trigger the backend change Key: AMBARI-15475 URL: https://issues.apache.org/jira/browse/AMBARI-15475 Project: Ambari Issue Type: Bug Reporter: jun aoki Assignee: jun aoki Priority: Minor Modified "HAWQ Segment Temp Directory” from one [/d1/tmp/hawqsegment] to many [/d1/tmp/hawqsegment,/d2/tmp/hawqsegment,/d3/tmp/hawqsegment,/d4/tmp/hawqsegment,/d5/tmp/hawqsegment] and the change is not propagated to segments and the folders are not created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15435) Update Hawq GUCS: Refactor resource related GUC
[ https://issues.apache.org/jira/browse/AMBARI-15435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200593#comment-15200593 ] jun aoki commented on AMBARI-15435: --- sorry. My bad. My branch was not clean. > Update Hawq GUCS: Refactor resource related GUC > --- > > Key: AMBARI-15435 > URL: https://issues.apache.org/jira/browse/AMBARI-15435 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, ambari-web >Affects Versions: trunk, 2.2.2 >Reporter: Goutam Tadi >Assignee: Goutam Tadi >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15435-trunk-v1.patch, > AMBARI-15435-trunk-v2.patch, AMBARI-15435-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15475) Editing tmp dir from single to multiple dir doesn't trigger the backend change
[ https://issues.apache.org/jira/browse/AMBARI-15475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15475: -- Status: Patch Available (was: In Progress) > Editing tmp dir from single to multiple dir doesn't trigger the backend change > -- > > Key: AMBARI-15475 > URL: https://issues.apache.org/jira/browse/AMBARI-15475 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Attachments: AMBARI-15475.branch-2.2.patch, > AMBARI-15475.branch-2.2.v2.patch > > > Modified "HAWQ Segment Temp Directory” from one [/d1/tmp/hawqsegment] to > many > [/d1/tmp/hawqsegment,/d2/tmp/hawqsegment,/d3/tmp/hawqsegment,/d4/tmp/hawqsegment,/d5/tmp/hawqsegment] > and the change is not propagated to segments and the folders are not created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15475) Editing tmp dir from single to multiple dir doesn't trigger the backend change
[ https://issues.apache.org/jira/browse/AMBARI-15475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202650#comment-15202650 ] jun aoki commented on AMBARI-15475: --- Committed to trunk b65b7c2ddbe6e11d8c0514346f2c00da3feceaae > Editing tmp dir from single to multiple dir doesn't trigger the backend change > -- > > Key: AMBARI-15475 > URL: https://issues.apache.org/jira/browse/AMBARI-15475 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15475.branch-2.2.patch, > AMBARI-15475.branch-2.2.v2.patch, AMBARI-15475.branch-2.2.v3.patch, > AMBARI-15475.trunk.patch, AMBARI-15475.trunk.v2.patch > > > Modified "HAWQ Segment Temp Directory” from one [/d1/tmp/hawqsegment] to > many > [/d1/tmp/hawqsegment,/d2/tmp/hawqsegment,/d3/tmp/hawqsegment,/d4/tmp/hawqsegment,/d5/tmp/hawqsegment] > and the change is not propagated to segments and the folders are not created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15475) Editing tmp dir from single to multiple dir doesn't trigger the backend change
[ https://issues.apache.org/jira/browse/AMBARI-15475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15475: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Editing tmp dir from single to multiple dir doesn't trigger the backend change > -- > > Key: AMBARI-15475 > URL: https://issues.apache.org/jira/browse/AMBARI-15475 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15475.branch-2.2.patch, > AMBARI-15475.branch-2.2.v2.patch, AMBARI-15475.branch-2.2.v3.patch, > AMBARI-15475.trunk.patch, AMBARI-15475.trunk.v2.patch > > > Modified "HAWQ Segment Temp Directory” from one [/d1/tmp/hawqsegment] to > many > [/d1/tmp/hawqsegment,/d2/tmp/hawqsegment,/d3/tmp/hawqsegment,/d4/tmp/hawqsegment,/d5/tmp/hawqsegment] > and the change is not propagated to segments and the folders are not created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15475) Editing tmp dir from single to multiple dir doesn't trigger the backend change
[ https://issues.apache.org/jira/browse/AMBARI-15475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15475: -- Attachment: AMBARI-15475.trunk.v2.patch > Editing tmp dir from single to multiple dir doesn't trigger the backend change > -- > > Key: AMBARI-15475 > URL: https://issues.apache.org/jira/browse/AMBARI-15475 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15475.branch-2.2.patch, > AMBARI-15475.branch-2.2.v2.patch, AMBARI-15475.branch-2.2.v3.patch, > AMBARI-15475.trunk.patch, AMBARI-15475.trunk.v2.patch > > > Modified "HAWQ Segment Temp Directory” from one [/d1/tmp/hawqsegment] to > many > [/d1/tmp/hawqsegment,/d2/tmp/hawqsegment,/d3/tmp/hawqsegment,/d4/tmp/hawqsegment,/d5/tmp/hawqsegment] > and the change is not propagated to segments and the folders are not created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15475) Editing tmp dir from single to multiple dir doesn't trigger the backend change
[ https://issues.apache.org/jira/browse/AMBARI-15475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15475: -- Attachment: AMBARI-15475.trunk.patch > Editing tmp dir from single to multiple dir doesn't trigger the backend change > -- > > Key: AMBARI-15475 > URL: https://issues.apache.org/jira/browse/AMBARI-15475 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15475.branch-2.2.patch, > AMBARI-15475.branch-2.2.v2.patch, AMBARI-15475.branch-2.2.v3.patch, > AMBARI-15475.trunk.patch > > > Modified "HAWQ Segment Temp Directory” from one [/d1/tmp/hawqsegment] to > many > [/d1/tmp/hawqsegment,/d2/tmp/hawqsegment,/d3/tmp/hawqsegment,/d4/tmp/hawqsegment,/d5/tmp/hawqsegment] > and the change is not propagated to segments and the folders are not created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15435) Update Hawq GUCS: Refactor resource related GUC
[ https://issues.apache.org/jira/browse/AMBARI-15435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200632#comment-15200632 ] jun aoki commented on AMBARI-15435: --- Committed to trunk b663dbe1be5291d8d32de7ec2b4434612d0861c0 Committed to branch-2.2 e3a673f747bd274ec16535b4aa11302634ce39d4 > Update Hawq GUCS: Refactor resource related GUC > --- > > Key: AMBARI-15435 > URL: https://issues.apache.org/jira/browse/AMBARI-15435 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, ambari-web >Affects Versions: trunk, 2.2.2 >Reporter: Goutam Tadi >Assignee: Goutam Tadi >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15435-trunk-v1.patch, > AMBARI-15435-trunk-v2.patch, AMBARI-15435-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15435) Update Hawq GUCS: Refactor resource related GUC
[ https://issues.apache.org/jira/browse/AMBARI-15435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15435: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Update Hawq GUCS: Refactor resource related GUC > --- > > Key: AMBARI-15435 > URL: https://issues.apache.org/jira/browse/AMBARI-15435 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, ambari-web >Affects Versions: trunk, 2.2.2 >Reporter: Goutam Tadi >Assignee: Goutam Tadi >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15435-trunk-v1.patch, > AMBARI-15435-trunk-v2.patch, AMBARI-15435-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15475) Editing tmp dir from single to multiple dir doesn't trigger the backend change
[ https://issues.apache.org/jira/browse/AMBARI-15475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15475: -- Fix Version/s: 2.2.2 trunk > Editing tmp dir from single to multiple dir doesn't trigger the backend change > -- > > Key: AMBARI-15475 > URL: https://issues.apache.org/jira/browse/AMBARI-15475 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15475.branch-2.2.patch, > AMBARI-15475.branch-2.2.v2.patch > > > Modified "HAWQ Segment Temp Directory” from one [/d1/tmp/hawqsegment] to > many > [/d1/tmp/hawqsegment,/d2/tmp/hawqsegment,/d3/tmp/hawqsegment,/d4/tmp/hawqsegment,/d5/tmp/hawqsegment] > and the change is not propagated to segments and the folders are not created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15475) Editing tmp dir from single to multiple dir doesn't trigger the backend change
[ https://issues.apache.org/jira/browse/AMBARI-15475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15475: -- Attachment: AMBARI-15475.branch-2.2.v3.patch > Editing tmp dir from single to multiple dir doesn't trigger the backend change > -- > > Key: AMBARI-15475 > URL: https://issues.apache.org/jira/browse/AMBARI-15475 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15475.branch-2.2.patch, > AMBARI-15475.branch-2.2.v2.patch, AMBARI-15475.branch-2.2.v3.patch > > > Modified "HAWQ Segment Temp Directory” from one [/d1/tmp/hawqsegment] to > many > [/d1/tmp/hawqsegment,/d2/tmp/hawqsegment,/d3/tmp/hawqsegment,/d4/tmp/hawqsegment,/d5/tmp/hawqsegment] > and the change is not propagated to segments and the folders are not created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15417) Blueprint should have a flag to allow configuring use of RCO vs Retry method
[ https://issues.apache.org/jira/browse/AMBARI-15417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194671#comment-15194671 ] jun aoki commented on AMBARI-15417: --- I don't have a background knowledge of why RCO is only honored through Wizard, but would like to chip in my idea. The service dependencies (RCO) should be always honored regardless of user input type (Through Wizard, or Blueprint, or even some other means in future) because it should be simply a part of stack definition. So I'd like to downvote to introduce a flag to control whether or not RCO is used. > Blueprint should have a flag to allow configuring use of RCO vs Retry method > > > Key: AMBARI-15417 > URL: https://issues.apache.org/jira/browse/AMBARI-15417 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: trunk >Reporter: bhuvnesh chaudhary > > With Blueprint deploy's, role command oder (RCO) is not honored. > Currently, in order to mitigate failure for a service start due to > dependencies on other services, blueprint deploy uses retry mechanism to > ensure that the services are started and their prerequisite are met. > However, retry mechanism in some cases can cause the install / start time to > take long and might need additional logic on component specific installation > to handle retries. > In order to provide with flexibility, we should put up a flag in blueprints > which drive the required behavior. (Use RCO vs Use Retry) > Say: The flag name is use_rco (Change what seems better)) > By default, the value of use_rco can be false and if someone wan't to > override it they can specify it as true in the blueprint. > Note: Keeping it as false by default as it has been already there since > Ambari 2.1.0. Hopefully, even if we set this to true by default, it should > not impact customers except a few. But we can make this decision based on > communities opinion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15339) Align PXF Alert description with other services.
[ https://issues.apache.org/jira/browse/AMBARI-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15339: -- Attachment: AMBARI-15339-branch-2.2.v2.patch > Align PXF Alert description with other services. > > > Key: AMBARI-15339 > URL: https://issues.apache.org/jira/browse/AMBARI-15339 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15339-branch-2.2.patch, > AMBARI-15339-branch-2.2.v2.patch, datanode alert.png > > > Something similar to datanode (screenshot attached) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15339) Align PXF Alert description with other services.
[ https://issues.apache.org/jira/browse/AMBARI-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186006#comment-15186006 ] jun aoki commented on AMBARI-15339: --- the patch applies to trunk as well. > Align PXF Alert description with other services. > > > Key: AMBARI-15339 > URL: https://issues.apache.org/jira/browse/AMBARI-15339 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15339-branch-2.2.patch, datanode alert.png > > > Something similar to datanode (screenshot attached) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15339) Align PXF Alert description with other services.
[ https://issues.apache.org/jira/browse/AMBARI-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15339: -- Status: Patch Available (was: Open) > Align PXF Alert description with other services. > > > Key: AMBARI-15339 > URL: https://issues.apache.org/jira/browse/AMBARI-15339 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15339-branch-2.2.patch, datanode alert.png > > > Something similar to datanode (screenshot attached) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15339) Align PXF Alert description with other services.
[ https://issues.apache.org/jira/browse/AMBARI-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15339: -- Description: Something similar to datanode (screenshot attached) > Align PXF Alert description with other services. > > > Key: AMBARI-15339 > URL: https://issues.apache.org/jira/browse/AMBARI-15339 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15339-branch-2.2.patch, datanode alert.png > > > Something similar to datanode (screenshot attached) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15339) Align PXF Alert description with other services.
[ https://issues.apache.org/jira/browse/AMBARI-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15339: -- Attachment: AMBARI-15339-branch-2.2.patch > Align PXF Alert description with other services. > > > Key: AMBARI-15339 > URL: https://issues.apache.org/jira/browse/AMBARI-15339 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15339-branch-2.2.patch, datanode alert.png > > > Something similar to datanode (screenshot attached) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15339) Align PXF Alert description with other services.
jun aoki created AMBARI-15339: - Summary: Align PXF Alert description with other services. Key: AMBARI-15339 URL: https://issues.apache.org/jira/browse/AMBARI-15339 Project: Ambari Issue Type: Bug Reporter: jun aoki Assignee: jun aoki Priority: Minor Attachments: datanode alert.png -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15339) Align PXF Alert description with other services.
[ https://issues.apache.org/jira/browse/AMBARI-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15339: -- Fix Version/s: 2.2.2 trunk > Align PXF Alert description with other services. > > > Key: AMBARI-15339 > URL: https://issues.apache.org/jira/browse/AMBARI-15339 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: datanode alert.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15339) Align PXF Alert description with other services.
[ https://issues.apache.org/jira/browse/AMBARI-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun aoki updated AMBARI-15339: -- Attachment: datanode alert.png > Align PXF Alert description with other services. > > > Key: AMBARI-15339 > URL: https://issues.apache.org/jira/browse/AMBARI-15339 > Project: Ambari > Issue Type: Bug >Reporter: jun aoki >Assignee: jun aoki >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: datanode alert.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
