[jira] [Updated] (AMBARI-25955) ambari-agent的data目录未清理
[ https://issues.apache.org/jira/browse/AMBARI-25955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-25955: - Attachment: 清理前.png > ambari-agent的data目录未清理 > -- > > Key: AMBARI-25955 > URL: https://issues.apache.org/jira/browse/AMBARI-25955 > Project: Ambari > Issue Type: Improvement >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Attachments: 清理前.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25955) ambari-agent的data目录未清理
zhangxiaolu created AMBARI-25955: Summary: ambari-agent的data目录未清理 Key: AMBARI-25955 URL: https://issues.apache.org/jira/browse/AMBARI-25955 Project: Ambari Issue Type: Improvement Reporter: zhangxiaolu Assignee: zhangxiaolu -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25154) can't delete kerberos when user exits step 4 in enabling kerbeors wizard
[ https://issues.apache.org/jira/browse/AMBARI-25154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-25154: - Attachment: AMBARI-25154.patch > can't delete kerberos when user exits step 4 in enabling kerbeors wizard > > > Key: AMBARI-25154 > URL: https://issues.apache.org/jira/browse/AMBARI-25154 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.8.0, 2.7.4 >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-25154.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25154) can't delete kerberos when user exits step 4 in enabling kerbeors wizard
[ https://issues.apache.org/jira/browse/AMBARI-25154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-25154: - Labels: ambari-web (was: ) > can't delete kerberos when user exits step 4 in enabling kerbeors wizard > > > Key: AMBARI-25154 > URL: https://issues.apache.org/jira/browse/AMBARI-25154 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.8.0, 2.7.4 >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Minor > Labels: ambari-web > Fix For: trunk > > Attachments: AMBARI-25154.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25154) can't delete kerberos when user exits step 4 in enabling kerbeors wizard
[ https://issues.apache.org/jira/browse/AMBARI-25154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-25154: - Fix Version/s: trunk Affects Version/s: 2.7.4 2.8.0 Status: Patch Available (was: In Progress) > can't delete kerberos when user exits step 4 in enabling kerbeors wizard > > > Key: AMBARI-25154 > URL: https://issues.apache.org/jira/browse/AMBARI-25154 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.8.0, 2.7.4 >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Minor > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-25154) can't delete kerberos when user exits step 4 in enabling kerbeors wizard
[ https://issues.apache.org/jira/browse/AMBARI-25154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771082#comment-16771082 ] zhangxiaolu commented on AMBARI-25154: -- Hi [~afernandez],[~nc...@hortonworks.com],[~BuzhorDenys] could you be so kind as to review the patch for me please? Thanks in advance > can't delete kerberos when user exits step 4 in enabling kerbeors wizard > > > Key: AMBARI-25154 > URL: https://issues.apache.org/jira/browse/AMBARI-25154 > Project: Ambari > Issue Type: Improvement >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25154) can't delete kerberos when user exits step 4 in enabling kerbeors wizard
[ https://issues.apache.org/jira/browse/AMBARI-25154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-25154: - Priority: Minor (was: Major) > can't delete kerberos when user exits step 4 in enabling kerbeors wizard > > > Key: AMBARI-25154 > URL: https://issues.apache.org/jira/browse/AMBARI-25154 > Project: Ambari > Issue Type: Improvement >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25154) can't delete kerberos when user exits step 4 in enabling kerbeors wizard
zhangxiaolu created AMBARI-25154: Summary: can't delete kerberos when user exits step 4 in enabling kerbeors wizard Key: AMBARI-25154 URL: https://issues.apache.org/jira/browse/AMBARI-25154 Project: Ambari Issue Type: Improvement Reporter: zhangxiaolu Assignee: zhangxiaolu -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23558) Tip issue when turn on or off maintainance and there is no host in such status
[ https://issues.apache.org/jira/browse/AMBARI-23558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-23558: - Status: Patch Available (was: Open) > Tip issue when turn on or off maintainance and there is no host in such status > -- > > Key: AMBARI-23558 > URL: https://issues.apache.org/jira/browse/AMBARI-23558 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > Attachments: AMBARI-23558.patch, screenshot-1.png, screenshot-2.png, > screenshot-3.png > > > when all hosts are not in Maintenance Mode, excuting turn off Maintenance > Mode, and the tip is like this. > Better to give right tip. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23558) Tip issue when turn on or off maintainance and there is no host in such status
[ https://issues.apache.org/jira/browse/AMBARI-23558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-23558: - Attachment: AMBARI-23558.patch > Tip issue when turn on or off maintainance and there is no host in such status > -- > > Key: AMBARI-23558 > URL: https://issues.apache.org/jira/browse/AMBARI-23558 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > Attachments: AMBARI-23558.patch, screenshot-1.png, screenshot-2.png, > screenshot-3.png > > > when all hosts are not in Maintenance Mode, excuting turn off Maintenance > Mode, and the tip is like this. > Better to give right tip. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23558) Tip issue when turn on or off maintainance and there is no host in such status
[ https://issues.apache.org/jira/browse/AMBARI-23558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-23558: - Description: when all hosts are not in Maintenance Mode, excuting turn off Maintenance Mode, and the tip is like this. Better to give right tip. > Tip issue when turn on or off maintainance and there is no host in such status > -- > > Key: AMBARI-23558 > URL: https://issues.apache.org/jira/browse/AMBARI-23558 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > > when all hosts are not in Maintenance Mode, excuting turn off Maintenance > Mode, and the tip is like this. > Better to give right tip. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23558) Tip issue when turn on or off maintainance and there is no host in such status
[ https://issues.apache.org/jira/browse/AMBARI-23558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-23558: - Attachment: screenshot-3.png > Tip issue when turn on or off maintainance and there is no host in such status > -- > > Key: AMBARI-23558 > URL: https://issues.apache.org/jira/browse/AMBARI-23558 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23558) Tip issue when turn on or off maintainance and there is no host in such status
[ https://issues.apache.org/jira/browse/AMBARI-23558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-23558: - Attachment: screenshot-2.png > Tip issue when turn on or off maintainance and there is no host in such status > -- > > Key: AMBARI-23558 > URL: https://issues.apache.org/jira/browse/AMBARI-23558 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > Attachments: screenshot-1.png, screenshot-2.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23558) Tip issue when turn on or off maintainance and there is no host in such status
[ https://issues.apache.org/jira/browse/AMBARI-23558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-23558: - Attachment: screenshot-1.png > Tip issue when turn on or off maintainance and there is no host in such status > -- > > Key: AMBARI-23558 > URL: https://issues.apache.org/jira/browse/AMBARI-23558 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23558) Tip issue when turn on or off maintainance and there is no host in such status
zhangxiaolu created AMBARI-23558: Summary: Tip issue when turn on or off maintainance and there is no host in such status Key: AMBARI-23558 URL: https://issues.apache.org/jira/browse/AMBARI-23558 Project: Ambari Issue Type: Improvement Affects Versions: trunk Reporter: zhangxiaolu Assignee: zhangxiaolu Fix For: trunk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23524) There is no alerts for logfeeder
[ https://issues.apache.org/jira/browse/AMBARI-23524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-23524: - Labels: patch (was: ) > There is no alerts for logfeeder > > > Key: AMBARI-23524 > URL: https://issues.apache.org/jira/browse/AMBARI-23524 > Project: Ambari > Issue Type: Bug > Components: logsearch >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Labels: patch > Fix For: trunk > > Attachments: AMBARI-23524.patch, screenshot-1.png, screenshot-2.png > > > h1. There is no alerts for logfeeder. > when one logfeeder is down,there is no alert. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23524) There is no alerts for logfeeder
[ https://issues.apache.org/jira/browse/AMBARI-23524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-23524: - Attachment: screenshot-2.png > There is no alerts for logfeeder > > > Key: AMBARI-23524 > URL: https://issues.apache.org/jira/browse/AMBARI-23524 > Project: Ambari > Issue Type: Bug > Components: logsearch >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > Attachments: AMBARI-23524.patch, screenshot-1.png, screenshot-2.png > > > h1. There is no alerts for logfeeder. > when one logfeeder is down,there is no alert. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23524) There is no alerts for logfeeder
[ https://issues.apache.org/jira/browse/AMBARI-23524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-23524: - Status: Patch Available (was: Open) > There is no alerts for logfeeder > > > Key: AMBARI-23524 > URL: https://issues.apache.org/jira/browse/AMBARI-23524 > Project: Ambari > Issue Type: Bug > Components: logsearch >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > Attachments: AMBARI-23524.patch, screenshot-1.png, screenshot-2.png > > > h1. There is no alerts for logfeeder. > when one logfeeder is down,there is no alert. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23524) There is no alerts for logfeeder
[ https://issues.apache.org/jira/browse/AMBARI-23524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-23524: - Attachment: AMBARI-23524.patch > There is no alerts for logfeeder > > > Key: AMBARI-23524 > URL: https://issues.apache.org/jira/browse/AMBARI-23524 > Project: Ambari > Issue Type: Bug > Components: logsearch >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > Attachments: AMBARI-23524.patch, screenshot-1.png, screenshot-2.png > > > h1. There is no alerts for logfeeder. > when one logfeeder is down,there is no alert. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23524) There is no alerts for logfeeder
[ https://issues.apache.org/jira/browse/AMBARI-23524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-23524: - Attachment: screenshot-1.png > There is no alerts for logfeeder > > > Key: AMBARI-23524 > URL: https://issues.apache.org/jira/browse/AMBARI-23524 > Project: Ambari > Issue Type: Bug > Components: logsearch >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > Attachments: screenshot-1.png > > > h1. There is no alerts for logfeeder. > when one logfeeder is down,there is no alert. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23524) There is no alerts for logfeeder
[ https://issues.apache.org/jira/browse/AMBARI-23524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-23524: - Description: h1. There is no alerts for logfeeder. when one logfeeder is down,there is no alert. > There is no alerts for logfeeder > > > Key: AMBARI-23524 > URL: https://issues.apache.org/jira/browse/AMBARI-23524 > Project: Ambari > Issue Type: Bug > Components: logsearch >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > > h1. There is no alerts for logfeeder. > when one logfeeder is down,there is no alert. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23524) There is no alerts for logfeeder
zhangxiaolu created AMBARI-23524: Summary: There is no alerts for logfeeder Key: AMBARI-23524 URL: https://issues.apache.org/jira/browse/AMBARI-23524 Project: Ambari Issue Type: Bug Components: logsearch Affects Versions: trunk Reporter: zhangxiaolu Assignee: zhangxiaolu Fix For: trunk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22894) Install zk error when cluster just only installed zk.
[
https://issues.apache.org/jira/browse/AMBARI-22894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-22894:
-
Resolution: Resolved
Status: Resolved (was: Patch Available)
[https://github.com/apache/ambari/blob/79504f74e83164a9c70713ea54cfc2f257d5be04/ambari-server/src/main/resources/stack-hooks/before-START/scripts/params.py#L336-L337]
and
[https://github.com/apache/ambari/blob/2019a5c0d824c73167535ac7091fc1af765c4826/ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py#L330-L331]
> Install zk error when cluster just only installed zk.
> -
>
> Key: AMBARI-22894
> URL: https://issues.apache.org/jira/browse/AMBARI-22894
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: cluster with only the service of zookeeper
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
>Priority: Major
> Labels: pull-request-available, trunk
> Fix For: trunk
>
> Attachments: AMBARI-22894.patch, screenshot-1.png
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> cluster with only the service of zookeeper.
>
> when start zk, error is like this:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 40, in
> BeforeStartHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 314, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 28, in hook
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py",
> line 320, in
> if namenode_rpc:
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'core-site'
> was not found in configurations dictionary!
> Error: Error: Unable to run the custom hook script ['/usr/bin/python',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py',
> 'START', '/var/lib/ambari-agent/data/command-31.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START',
> '/var/lib/ambari-agent/data/structured-out-31.json', 'INFO',
> '/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1']
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22894) Install zk error when cluster just only installed zk.
[
https://issues.apache.org/jira/browse/AMBARI-22894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-22894:
-
Component/s: ambari-server
> Install zk error when cluster just only installed zk.
> -
>
> Key: AMBARI-22894
> URL: https://issues.apache.org/jira/browse/AMBARI-22894
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: cluster with only the service of zookeeper
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
>Priority: Major
> Labels: trunk
> Fix For: trunk
>
> Attachments: AMBARI-22894.patch, screenshot-1.png
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> cluster with only the service of zookeeper.
>
> when start zk, error is like this:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 40, in
> BeforeStartHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 314, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 28, in hook
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py",
> line 320, in
> if namenode_rpc:
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'core-site'
> was not found in configurations dictionary!
> Error: Error: Unable to run the custom hook script ['/usr/bin/python',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py',
> 'START', '/var/lib/ambari-agent/data/command-31.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START',
> '/var/lib/ambari-agent/data/structured-out-31.json', 'INFO',
> '/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1']
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22894) Install zk error when cluster just only installed zk.
[
https://issues.apache.org/jira/browse/AMBARI-22894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-22894:
-
Labels: trunk (was: pull-request-available)
> Install zk error when cluster just only installed zk.
> -
>
> Key: AMBARI-22894
> URL: https://issues.apache.org/jira/browse/AMBARI-22894
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: cluster with only the service of zookeeper
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
>Priority: Major
> Labels: trunk
> Fix For: trunk
>
> Attachments: AMBARI-22894.patch, screenshot-1.png
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> cluster with only the service of zookeeper.
>
> when start zk, error is like this:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 40, in
> BeforeStartHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 314, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 28, in hook
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py",
> line 320, in
> if namenode_rpc:
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'core-site'
> was not found in configurations dictionary!
> Error: Error: Unable to run the custom hook script ['/usr/bin/python',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py',
> 'START', '/var/lib/ambari-agent/data/command-31.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START',
> '/var/lib/ambari-agent/data/structured-out-31.json', 'INFO',
> '/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1']
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22894) Install zk error when cluster just only installed zk.
[
https://issues.apache.org/jira/browse/AMBARI-22894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-22894:
-
Description:
cluster with only the service of zookeeper.
when start zk, error is like this:
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
line 40, in
BeforeStartHook().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 314, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
line 28, in hook
import params
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py",
line 320, in
if namenode_rpc:
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found in
configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter 'core-site'
was not found in configurations dictionary!
Error: Error: Unable to run the custom hook script ['/usr/bin/python',
'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py',
'START', '/var/lib/ambari-agent/data/command-31.json',
'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START',
'/var/lib/ambari-agent/data/structured-out-31.json', 'INFO',
'/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1']
was:
cluster with only the service of zookeeper.
when start zk, error is like this
> Install zk error when cluster just only installed zk.
> -
>
> Key: AMBARI-22894
> URL: https://issues.apache.org/jira/browse/AMBARI-22894
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
> Environment: cluster with only the service of zookeeper
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
>Priority: Major
> Fix For: trunk
>
> Attachments: AMBARI-22894.patch, screenshot-1.png
>
>
> cluster with only the service of zookeeper.
>
> when start zk, error is like this:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 40, in
> BeforeStartHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 314, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 28, in hook
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py",
> line 320, in
> if namenode_rpc:
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'core-site'
> was not found in configurations dictionary!
> Error: Error: Unable to run the custom hook script ['/usr/bin/python',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py',
> 'START', '/var/lib/ambari-agent/data/command-31.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START',
> '/var/lib/ambari-agent/data/structured-out-31.json', 'INFO',
> '/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1']
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22894) Install zk error when cluster just only installed zk.
[
https://issues.apache.org/jira/browse/AMBARI-22894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-22894:
-
Status: Patch Available (was: Open)
> Install zk error when cluster just only installed zk.
> -
>
> Key: AMBARI-22894
> URL: https://issues.apache.org/jira/browse/AMBARI-22894
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
> Environment: cluster with only the service of zookeeper
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
>Priority: Major
> Fix For: trunk
>
> Attachments: AMBARI-22894.patch, screenshot-1.png
>
>
> cluster with only the service of zookeeper.
>
> when start zk, error is like this:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 40, in
> BeforeStartHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 314, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 28, in hook
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py",
> line 320, in
> if namenode_rpc:
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'core-site'
> was not found in configurations dictionary!
> Error: Error: Unable to run the custom hook script ['/usr/bin/python',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py',
> 'START', '/var/lib/ambari-agent/data/command-31.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START',
> '/var/lib/ambari-agent/data/structured-out-31.json', 'INFO',
> '/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1']
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22894) Install zk error when cluster just only installed zk.
[ https://issues.apache.org/jira/browse/AMBARI-22894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22894: - Attachment: screenshot-1.png > Install zk error when cluster just only installed zk. > - > > Key: AMBARI-22894 > URL: https://issues.apache.org/jira/browse/AMBARI-22894 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk > Environment: cluster with only the service of zookeeper >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > Attachments: AMBARI-22894.patch, screenshot-1.png > > > cluster with only the service of zookeeper. > > when start zk, error is like this -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22894) Install zk error when cluster just only installed zk.
[ https://issues.apache.org/jira/browse/AMBARI-22894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22894: - Attachment: AMBARI-22894.patch > Install zk error when cluster just only installed zk. > - > > Key: AMBARI-22894 > URL: https://issues.apache.org/jira/browse/AMBARI-22894 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk > Environment: cluster with only the service of zookeeper >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > Attachments: AMBARI-22894.patch > > > cluster with only the service of zookeeper. > > when start zk, error is like this -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22894) Install zk error when cluster just only installed zk.
[ https://issues.apache.org/jira/browse/AMBARI-22894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22894: - Description: cluster with only the service of zookeeper. when start zk, error is like this > Install zk error when cluster just only installed zk. > - > > Key: AMBARI-22894 > URL: https://issues.apache.org/jira/browse/AMBARI-22894 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk > Environment: cluster with only the service of zookeeper >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > > cluster with only the service of zookeeper. > > when start zk, error is like this -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22894) Install zk error when cluster just only installed zk.
zhangxiaolu created AMBARI-22894: Summary: Install zk error when cluster just only installed zk. Key: AMBARI-22894 URL: https://issues.apache.org/jira/browse/AMBARI-22894 Project: Ambari Issue Type: Bug Affects Versions: trunk Environment: cluster with only the service of zookeeper Reporter: zhangxiaolu Assignee: zhangxiaolu Fix For: trunk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22436) zookeeper service issue
[ https://issues.apache.org/jira/browse/AMBARI-22436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22436: - Attachment: AMBARI-22436_1.patch > zookeeper service issue > --- > > Key: AMBARI-22436 > URL: https://issues.apache.org/jira/browse/AMBARI-22436 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-22436.patch, AMBARI-22436_1.patch, > screenshot-1.png > > > amabri-qa has not permission to write zookeeper'.log in the dir of > /var/log/zookeeper for permission is 0755. > so should set permission is 0777 when executing service check. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22557) when stoppd hdfs, zkfc's alerts show issue
[ https://issues.apache.org/jira/browse/AMBARI-22557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22557: - Attachment: AMBARI-22557.patch > when stoppd hdfs, zkfc's alerts show issue > -- > > Key: AMBARI-22557 > URL: https://issues.apache.org/jira/browse/AMBARI-22557 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.3 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-22557.patch, before.png > > > (1)when zkfc is down, page shows no alerts; -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22557) when stoppd hdfs, zkfc's alerts show issue
[ https://issues.apache.org/jira/browse/AMBARI-22557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22557: - Attachment: (was: AMBARI-22557.patch) > when stoppd hdfs, zkfc's alerts show issue > -- > > Key: AMBARI-22557 > URL: https://issues.apache.org/jira/browse/AMBARI-22557 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.3 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-22557.patch, before.png > > > (1)when zkfc is down, page shows no alerts; -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22557) when stoppd hdfs, zkfc's alerts show issue
[ https://issues.apache.org/jira/browse/AMBARI-22557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22557: - Description: (1)when zkfc is down, page shows no alerts; > when stoppd hdfs, zkfc's alerts show issue > -- > > Key: AMBARI-22557 > URL: https://issues.apache.org/jira/browse/AMBARI-22557 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.3 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-22557.patch, before.png > > > (1)when zkfc is down, page shows no alerts; -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22557) when stoppd hdfs, zkfc's alerts show issue
[ https://issues.apache.org/jira/browse/AMBARI-22557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22557: - Affects Version/s: 2.5.3 > when stoppd hdfs, zkfc's alerts show issue > -- > > Key: AMBARI-22557 > URL: https://issues.apache.org/jira/browse/AMBARI-22557 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.3 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-22557.patch, before.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22557) when stoppd hdfs, zkfc's alerts show issue
[ https://issues.apache.org/jira/browse/AMBARI-22557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22557: - Status: Patch Available (was: Open) > when stoppd hdfs, zkfc's alerts show issue > -- > > Key: AMBARI-22557 > URL: https://issues.apache.org/jira/browse/AMBARI-22557 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-22557.patch, before.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22557) when stoppd hdfs, zkfc's alerts show issue
[ https://issues.apache.org/jira/browse/AMBARI-22557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22557: - Attachment: before.png AMBARI-22557.patch > when stoppd hdfs, zkfc's alerts show issue > -- > > Key: AMBARI-22557 > URL: https://issues.apache.org/jira/browse/AMBARI-22557 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-22557.patch, before.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22557) when stoppd hdfs, zkfc's alerts show issue
zhangxiaolu created AMBARI-22557: Summary: when stoppd hdfs, zkfc's alerts show issue Key: AMBARI-22557 URL: https://issues.apache.org/jira/browse/AMBARI-22557 Project: Ambari Issue Type: Bug Affects Versions: trunk Reporter: zhangxiaolu Assignee: zhangxiaolu Fix For: trunk -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22436) zookeeper service issue
[ https://issues.apache.org/jira/browse/AMBARI-22436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22436: - Description: amabri-qa has not permission to write zookeeper'.log in the dir of /var/log/zookeeper for permission is 0755. so should set permission is 0777 when executing service check. was: amabri-qa has not permission to write zookeeper'.log in /var/log/zookeeper for permission is 0755. so should set permission is 0777 when executing service check. > zookeeper service issue > --- > > Key: AMBARI-22436 > URL: https://issues.apache.org/jira/browse/AMBARI-22436 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-22436.patch, screenshot-1.png > > > amabri-qa has not permission to write zookeeper'.log in the dir of > /var/log/zookeeper for permission is 0755. > so should set permission is 0777 when executing service check. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22436) zookeeper service issue
[ https://issues.apache.org/jira/browse/AMBARI-22436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22436: - Status: Patch Available (was: Open) > zookeeper service issue > --- > > Key: AMBARI-22436 > URL: https://issues.apache.org/jira/browse/AMBARI-22436 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-22436.patch, screenshot-1.png > > > amabri-qa has not permission to write zookeeper'.log in the dir of > /var/log/zookeeper for permission is 0755. > so should set permission is 0777 when executing service check. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22436) zookeeper service issue
[ https://issues.apache.org/jira/browse/AMBARI-22436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22436: - Attachment: AMBARI-22436.patch > zookeeper service issue > --- > > Key: AMBARI-22436 > URL: https://issues.apache.org/jira/browse/AMBARI-22436 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-22436.patch, screenshot-1.png > > > amabri-qa has not permission to write zookeeper'.log in /var/log/zookeeper > for permission is 0755. > so should set permission is 0777 when executing service check. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22436) zookeeper service issue
[ https://issues.apache.org/jira/browse/AMBARI-22436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22436: - Description: amabri-qa has not permission to write zookeeper'.log in /var/log/zookeeper for permission is 0755. so should set permission is 0777 when executing service check. > zookeeper service issue > --- > > Key: AMBARI-22436 > URL: https://issues.apache.org/jira/browse/AMBARI-22436 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: screenshot-1.png > > > amabri-qa has not permission to write zookeeper'.log in /var/log/zookeeper > for permission is 0755. > so should set permission is 0777 when executing service check. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22436) zookeeper service issue
[ https://issues.apache.org/jira/browse/AMBARI-22436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22436: - Attachment: screenshot-1.png > zookeeper service issue > --- > > Key: AMBARI-22436 > URL: https://issues.apache.org/jira/browse/AMBARI-22436 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22436) zookeeper service issue
zhangxiaolu created AMBARI-22436: Summary: zookeeper service issue Key: AMBARI-22436 URL: https://issues.apache.org/jira/browse/AMBARI-22436 Project: Ambari Issue Type: Improvement Affects Versions: trunk Reporter: zhangxiaolu Assignee: zhangxiaolu Fix For: trunk -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22078) The configs of HBase and Kafka issue
[ https://issues.apache.org/jira/browse/AMBARI-22078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196393#comment-16196393 ] zhangxiaolu commented on AMBARI-22078: -- Hi [~ncole], Thank you so much for reviewing my patch on reviewboard, and could you be so kind as to commit the patch for me please? Thanks in advance > The configs of HBase and Kafka issue > > > Key: AMBARI-22078 > URL: https://issues.apache.org/jira/browse/AMBARI-22078 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk > Environment: When the cluster is kerberoed, the config's group is > root,Maybe should be user.group be better. >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-22078.patch, screenshot-1.png, screenshot-2.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22078) The configs of HBase and Kafka issue
[ https://issues.apache.org/jira/browse/AMBARI-22078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22078: - Status: Patch Available (was: Open) > The configs of HBase and Kafka issue > > > Key: AMBARI-22078 > URL: https://issues.apache.org/jira/browse/AMBARI-22078 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk > Environment: When the cluster is kerberoed, the config's group is > root,Maybe should be user.group be better. >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-22078.patch, screenshot-1.png, screenshot-2.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22078) The configs of HBase and Kafka issue
[ https://issues.apache.org/jira/browse/AMBARI-22078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22078: - Attachment: AMBARI-22078.patch > The configs of HBase and Kafka issue > > > Key: AMBARI-22078 > URL: https://issues.apache.org/jira/browse/AMBARI-22078 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk > Environment: When the cluster is kerberoed, the config's group is > root,Maybe should be user.group be better. >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-22078.patch, screenshot-1.png, screenshot-2.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22078) The configs of HBase and Kafka issue
[ https://issues.apache.org/jira/browse/AMBARI-22078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22078: - Attachment: screenshot-2.png > The configs of HBase and Kafka issue > > > Key: AMBARI-22078 > URL: https://issues.apache.org/jira/browse/AMBARI-22078 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk > Environment: When the cluster is kerberoed, the config's group is > root,Maybe should be user.group be better. >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: screenshot-1.png, screenshot-2.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22078) The configs of HBase and Kafka issue
[ https://issues.apache.org/jira/browse/AMBARI-22078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22078: - Attachment: screenshot-1.png > The configs of HBase and Kafka issue > > > Key: AMBARI-22078 > URL: https://issues.apache.org/jira/browse/AMBARI-22078 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk > Environment: When the cluster is kerberoed, the config's group is > root,Maybe should be user.group be better. >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: screenshot-1.png, screenshot-2.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22078) The configs of HBase and Kafka issue
zhangxiaolu created AMBARI-22078: Summary: The configs of HBase and Kafka issue Key: AMBARI-22078 URL: https://issues.apache.org/jira/browse/AMBARI-22078 Project: Ambari Issue Type: Improvement Affects Versions: trunk Environment: When the cluster is kerberoed, the config's group is root,Maybe should be user.group be better. Reporter: zhangxiaolu Assignee: zhangxiaolu Fix For: trunk -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-20437) HDFS Bytes Written and HDFS Bytes Read maybe not correct
[
https://issues.apache.org/jira/browse/AMBARI-20437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180023#comment-16180023
]
zhangxiaolu commented on AMBARI-20437:
--
[~dsen]
ok.
Thank you
> HDFS Bytes Written and HDFS Bytes Read maybe not correct
>
>
> Key: AMBARI-20437
> URL: https://issues.apache.org/jira/browse/AMBARI-20437
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0, 2.4.2
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-20437_1.patch, AMBARI-20437.patch
>
>
> As the description of "HDFS Bytes Written" : dfs.datanode.BytesRead and
> properties's display_unit is MB
> So in heatmap's page,values should be ${dfs.datanode.BytesRead._rate/1024} MB
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-20437) HDFS Bytes Written and HDFS Bytes Read maybe not correct
[
https://issues.apache.org/jira/browse/AMBARI-20437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-20437:
-
Attachment: AMBARI-20437_1.patch
> HDFS Bytes Written and HDFS Bytes Read maybe not correct
>
>
> Key: AMBARI-20437
> URL: https://issues.apache.org/jira/browse/AMBARI-20437
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0, 2.4.2
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-20437_1.patch, AMBARI-20437.patch
>
>
> As the description of "HDFS Bytes Written" : dfs.datanode.BytesRead and
> properties's display_unit is MB
> So in heatmap's page,values should be ${dfs.datanode.BytesRead._rate/1024} MB
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-20437) HDFS Bytes Written and HDFS Bytes Read maybe not correct
[
https://issues.apache.org/jira/browse/AMBARI-20437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167253#comment-16167253
]
zhangxiaolu commented on AMBARI-20437:
--
Hi [~dsen] and [~nc...@hortonworks.com] Thank you so much for reviewing my
patch on reviewboard, and could you be so kind as to commit the patch for me
please? Thanks in advance
> HDFS Bytes Written and HDFS Bytes Read maybe not correct
>
>
> Key: AMBARI-20437
> URL: https://issues.apache.org/jira/browse/AMBARI-20437
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0, 2.4.2
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-20437.patch
>
>
> As the description of "HDFS Bytes Written" : dfs.datanode.BytesRead and
> properties's display_unit is MB
> So in heatmap's page,values should be ${dfs.datanode.BytesRead._rate/1024} MB
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21305) Hivesevers's status shows issue for the thrift's port conflict, when hiveservers and spark thrift server installed in the same host.
[ https://issues.apache.org/jira/browse/AMBARI-21305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-21305: - Attachment: AMBARI-21305_1.patch > Hivesevers's status shows issue for the thrift's port conflict, when > hiveservers and spark thrift server installed in the same host. > > > Key: AMBARI-21305 > URL: https://issues.apache.org/jira/browse/AMBARI-21305 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.5.0 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-21305_1.patch, AMBARI-21305.patch > > > Hivesevers's status shows issue for the thrift's port conflict, when > hiveservers and spark thrift server installed in the same host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21305) Hivesevers's status shows issue for the thrift's port conflict, when hiveservers and spark thrift server installed in the same host.
[ https://issues.apache.org/jira/browse/AMBARI-21305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-21305: - Attachment: BCHCON-21305.patch > Hivesevers's status shows issue for the thrift's port conflict, when > hiveservers and spark thrift server installed in the same host. > > > Key: AMBARI-21305 > URL: https://issues.apache.org/jira/browse/AMBARI-21305 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.5.0 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-21305.patch > > > Hivesevers's status shows issue for the thrift's port conflict, when > hiveservers and spark thrift server installed in the same host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21305) Hivesevers's status shows issue for the thrift's port conflict, when hiveservers and spark thrift server installed in the same host.
[ https://issues.apache.org/jira/browse/AMBARI-21305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-21305: - Attachment: (was: BCHCON-21305.patch) > Hivesevers's status shows issue for the thrift's port conflict, when > hiveservers and spark thrift server installed in the same host. > > > Key: AMBARI-21305 > URL: https://issues.apache.org/jira/browse/AMBARI-21305 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.5.0 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-21305.patch > > > Hivesevers's status shows issue for the thrift's port conflict, when > hiveservers and spark thrift server installed in the same host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21305) Hivesevers's status shows issue for the thrift's port conflict, when hiveservers and spark thrift server installed in the same host.
[ https://issues.apache.org/jira/browse/AMBARI-21305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-21305: - Attachment: AMBARI-21305.patch > Hivesevers's status shows issue for the thrift's port conflict, when > hiveservers and spark thrift server installed in the same host. > > > Key: AMBARI-21305 > URL: https://issues.apache.org/jira/browse/AMBARI-21305 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.5.0 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-21305.patch > > > Hivesevers's status shows issue for the thrift's port conflict, when > hiveservers and spark thrift server installed in the same host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21305) Hivesevers's status shows issue for the thrift's port conflict, when hiveservers and spark thrift server installed in the same host.
[ https://issues.apache.org/jira/browse/AMBARI-21305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-21305: - Status: Patch Available (was: Open) > Hivesevers's status shows issue for the thrift's port conflict, when > hiveservers and spark thrift server installed in the same host. > > > Key: AMBARI-21305 > URL: https://issues.apache.org/jira/browse/AMBARI-21305 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.5.0 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-21305.patch > > > Hivesevers's status shows issue for the thrift's port conflict, when > hiveservers and spark thrift server installed in the same host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21305) Hivesevers's status shows issue for the thrift's port conflict, when hiveservers and spark thrift server installed in the same host.
zhangxiaolu created AMBARI-21305: Summary: Hivesevers's status shows issue for the thrift's port conflict, when hiveservers and spark thrift server installed in the same host. Key: AMBARI-21305 URL: https://issues.apache.org/jira/browse/AMBARI-21305 Project: Ambari Issue Type: Bug Components: ambari-sever Affects Versions: 2.5.0 Reporter: zhangxiaolu Assignee: zhangxiaolu Fix For: trunk Hivesevers's status shows issue for the thrift's port conflict, when hiveservers and spark thrift server installed in the same host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21019) host's onLoadRangerConfigs description issue
[ https://issues.apache.org/jira/browse/AMBARI-21019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-21019: - Component/s: ambari-web > host's onLoadRangerConfigs description issue > > > Key: AMBARI-21019 > URL: https://issues.apache.org/jira/browse/AMBARI-21019 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-21019.patch > > > delete RangerKmsServer‘s description issue -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21019) host's onLoadRangerConfigs description issue
[ https://issues.apache.org/jira/browse/AMBARI-21019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-21019: - Status: Patch Available (was: Open) > host's onLoadRangerConfigs description issue > > > Key: AMBARI-21019 > URL: https://issues.apache.org/jira/browse/AMBARI-21019 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-21019.patch > > > delete RangerKmsServer‘s description issue -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21019) host's onLoadRangerConfigs description issue
[ https://issues.apache.org/jira/browse/AMBARI-21019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-21019: - Attachment: AMBARI-21019.patch > host's onLoadRangerConfigs description issue > > > Key: AMBARI-21019 > URL: https://issues.apache.org/jira/browse/AMBARI-21019 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-21019.patch > > > delete RangerKmsServer‘s description issue -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21019) host's onLoadRangerConfigs description issue
zhangxiaolu created AMBARI-21019: Summary: host's onLoadRangerConfigs description issue Key: AMBARI-21019 URL: https://issues.apache.org/jira/browse/AMBARI-21019 Project: Ambari Issue Type: Improvement Affects Versions: 2.5.2 Reporter: zhangxiaolu Assignee: zhangxiaolu Fix For: trunk delete RangerKmsServer‘s description issue -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20977) Journalnode should support batch restart in hosts' page likeing datanode or region
[ https://issues.apache.org/jira/browse/AMBARI-20977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20977: - Fix Version/s: 2.5.1 trunk > Journalnode should support batch restart in hosts' page likeing datanode or > region > -- > > Key: AMBARI-20977 > URL: https://issues.apache.org/jira/browse/AMBARI-20977 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20977.patch > > > Journalnode should support batch restart in hosts' page likeing datanode or > region. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20977) Journalnode should support batch restart in hosts' page likeing datanode or region
[ https://issues.apache.org/jira/browse/AMBARI-20977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20977: - Affects Version/s: (was: 2.5.2) (was: 2.5.1) (was: 2.5.0) > Journalnode should support batch restart in hosts' page likeing datanode or > region > -- > > Key: AMBARI-20977 > URL: https://issues.apache.org/jira/browse/AMBARI-20977 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20977.patch > > > Journalnode should support batch restart in hosts' page likeing datanode or > region. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20977) Journalnode should support batch restart in hosts' page likeing datanode or region
[ https://issues.apache.org/jira/browse/AMBARI-20977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005730#comment-16005730 ] zhangxiaolu commented on AMBARI-20977: -- Hi [~afernandez] , Thank you so much for reviewing my patch on reviewboard, and could you be so kind as to commit the patch for me please? Thanks in advance > Journalnode should support batch restart in hosts' page likeing datanode or > region > -- > > Key: AMBARI-20977 > URL: https://issues.apache.org/jira/browse/AMBARI-20977 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk, 2.5.0, 2.5.1, 2.5.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Attachments: AMBARI-20977.patch > > > Journalnode should support batch restart in hosts' page likeing datanode or > region. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20977) Journalnode should support batch restart in hosts' page likeing datanode or region
[ https://issues.apache.org/jira/browse/AMBARI-20977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20977: - Attachment: AMBARI-20977.patch > Journalnode should support batch restart in hosts' page likeing datanode or > region > -- > > Key: AMBARI-20977 > URL: https://issues.apache.org/jira/browse/AMBARI-20977 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk, 2.5.0, 2.5.1, 2.5.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Attachments: AMBARI-20977.patch > > > Journalnode should support batch restart in hosts' page likeing datanode or > region. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20977) Journalnode should support batch restart in hosts' page likeing datanode or region
[ https://issues.apache.org/jira/browse/AMBARI-20977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20977: - Status: Patch Available (was: Open) > Journalnode should support batch restart in hosts' page likeing datanode or > region > -- > > Key: AMBARI-20977 > URL: https://issues.apache.org/jira/browse/AMBARI-20977 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk, 2.5.0, 2.5.1, 2.5.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > > Journalnode should support batch restart in hosts' page likeing datanode or > region. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20977) Journalnode should support batch restart in hosts' page likeing datanode or region
zhangxiaolu created AMBARI-20977: Summary: Journalnode should support batch restart in hosts' page likeing datanode or region Key: AMBARI-20977 URL: https://issues.apache.org/jira/browse/AMBARI-20977 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: trunk, 2.5.0, 2.5.1, 2.5.2 Reporter: zhangxiaolu Assignee: zhangxiaolu Journalnode should support batch restart in hosts' page likeing datanode or region. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19952) NFSGateways's shown issue
[
https://issues.apache.org/jira/browse/AMBARI-19952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-19952:
-
Status: Open (was: Patch Available)
> NFSGateways's shown issue
> -
>
> Key: AMBARI-19952
> URL: https://issues.apache.org/jira/browse/AMBARI-19952
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk, 3.0.0
>Reporter: zhangxiaolu
> Attachments: AMBARI-19952.patch, screenshot-1.png
>
>
> if the cluster hasn't installed the nfsgatesays, the web shown like this.
> maybe this method is better.
> isNfsInStack: function () {
> return //App.StackServiceComponent.find().someProperty('componentName',
> 'NFS_GATEWAY');
> App.HostComponent.find().filterProperty('componentName',
> 'NFS_GATEWAY').length >0 ? true : false ;
> }.property(),
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-19952) NFSGateways's shown issue
[
https://issues.apache.org/jira/browse/AMBARI-19952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu resolved AMBARI-19952.
--
Resolution: Not A Problem
> NFSGateways's shown issue
> -
>
> Key: AMBARI-19952
> URL: https://issues.apache.org/jira/browse/AMBARI-19952
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk, 3.0.0
>Reporter: zhangxiaolu
> Attachments: AMBARI-19952.patch, screenshot-1.png
>
>
> if the cluster hasn't installed the nfsgatesays, the web shown like this.
> maybe this method is better.
> isNfsInStack: function () {
> return //App.StackServiceComponent.find().someProperty('componentName',
> 'NFS_GATEWAY');
> App.HostComponent.find().filterProperty('componentName',
> 'NFS_GATEWAY').length >0 ? true : false ;
> }.property(),
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20710) hive maybe not rely on slider
[ https://issues.apache.org/jira/browse/AMBARI-20710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20710: - Resolution: Not A Problem Status: Resolved (was: Patch Available) > hive maybe not rely on slider > - > > Key: AMBARI-20710 > URL: https://issues.apache.org/jira/browse/AMBARI-20710 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20710.patch > > > when adding the hive, the dialog tips that > " > You did not select Slider, but it is needed by other services you selected. > We will automatically add Slider. Is this OK? > " > There is no dependency relationship between hive and slider,so maybe we > should remove requiceservice slider in hive's metainfo.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Description: the problem is that the installing of hbase-client is before hdfs-client, and the hdfs-client installed failed because the hadoop-conf-dir didn't exist. so there are two ways to solve this problem. the first method is that create the hadoop-conf-dir in hbase.py the second method is that setting the orders in role_command_order.json. I think that we can take the first method. Maybe there is no necessary to deal with hdfs-site about hadoop_conf_dir in hbase.py. was: the problem is that the installing of hbase-client is before hdfs-client, and the hdfs-client installed failed because the hadoop-conf-dir didn't exist. so there are two ways to solve this problem. the first method is that create the hadoop-conf-dir in hbase.py the second method is that setting the orders in role_command_order.json. I think that we can take the first method. > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: 2.5.0, 2.4.2, 2.5.1 > > Attachments: AMBARI-20368-1.patch, AMBARI-20368.patch, > screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. > Maybe > there is no necessary to deal with hdfs-site about hadoop_conf_dir in > hbase.py. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Fix Version/s: 2.5.1 2.5.0 > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: 2.5.0, 2.4.2, 2.5.1 > > Attachments: AMBARI-20368-1.patch, AMBARI-20368.patch, > screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Attachment: AMBARI-20368-1.patch there is no necessary to deal with hdfs-site in hbase.py > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: 2.4.2 > > Attachments: AMBARI-20368-1.patch, AMBARI-20368.patch, > screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Fix Version/s: (was: trunk) 2.4.2 > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: 2.4.2 > > Attachments: AMBARI-20368-1.patch, AMBARI-20368.patch, > screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Affects Version/s: (was: 2.5.0) (was: 2.4.1) (was: trunk) > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu reopened AMBARI-20368: -- > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Status: Patch Available (was: Reopened) > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Status: Open (was: Patch Available) > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu resolved AMBARI-20368. -- Resolution: Implemented > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962540#comment-15962540 ] zhangxiaolu commented on AMBARI-20368: -- [~afernandez]. Thank you for following the issue. I had added some tests and all relative tests had passed, could you review again? Thank you advanced. > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Attachment: (was: AMBARI-20368.patch) > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Attachment: AMBARI-20368.patch > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, AMBARI-20368.patch, > screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Attachment: AMBARI-20368.patch > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Attachment: (was: AMBARI-20368.patch) > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20710) hive maybe not rely on slider
[ https://issues.apache.org/jira/browse/AMBARI-20710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20710: - Attachment: AMBARI-20710.patch > hive maybe not rely on slider > - > > Key: AMBARI-20710 > URL: https://issues.apache.org/jira/browse/AMBARI-20710 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20710.patch > > > when adding the hive, the dialog tips that > " > You did not select Slider, but it is needed by other services you selected. > We will automatically add Slider. Is this OK? > " > There is no dependency relationship between hive and slider,so maybe we > should remove requiceservice slider in hive's metainfo.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20710) hive maybe not rely on slider
zhangxiaolu created AMBARI-20710: Summary: hive maybe not rely on slider Key: AMBARI-20710 URL: https://issues.apache.org/jira/browse/AMBARI-20710 Project: Ambari Issue Type: Bug Components: HiveServer2, Metastore, and Client Heap Sizes to Smart Configs Affects Versions: trunk Reporter: zhangxiaolu Assignee: zhangxiaolu Fix For: trunk Attachments: AMBARI-20710.patch when adding the hive, the dialog tips that " You did not select Slider, but it is needed by other services you selected. We will automatically add Slider. Is this OK? " There is no dependency relationship between hive and slider,so maybe we should remove requiceservice slider in hive's metainfo.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20710) hive maybe not rely on slider
[ https://issues.apache.org/jira/browse/AMBARI-20710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20710: - Status: Patch Available (was: Open) > hive maybe not rely on slider > - > > Key: AMBARI-20710 > URL: https://issues.apache.org/jira/browse/AMBARI-20710 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20710.patch > > > when adding the hive, the dialog tips that > " > You did not select Slider, but it is needed by other services you selected. > We will automatically add Slider. Is this OK? > " > There is no dependency relationship between hive and slider,so maybe we > should remove requiceservice slider in hive's metainfo.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Attachment: (was: AMBARI-20368.patch) > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Attachment: AMBARI-20368.patch > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20108) the item of "reblance hdfs" should be hidden in NameNode menu
[ https://issues.apache.org/jira/browse/AMBARI-20108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20108: - Status: Patch Available (was: Open) > the item of "reblance hdfs" should be hidden in NameNode menu > - > > Key: AMBARI-20108 > URL: https://issues.apache.org/jira/browse/AMBARI-20108 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20108.patch, screenshot-1.png > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py", > line 420, in > NameNode().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 280, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py", > line 282, in rebalancehdfs > name_node_parameters = json.loads( params.name_node_params ) > File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line > 307, in loads > return _default_decoder.decode(s) > File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line > 335, in decode > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > TypeError: expected string or buffer -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20108) the item of "reblance hdfs" should be hidden in NameNode menu
[ https://issues.apache.org/jira/browse/AMBARI-20108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20108: - Attachment: (was: AMBARI-20108.patch) > the item of "reblance hdfs" should be hidden in NameNode menu > - > > Key: AMBARI-20108 > URL: https://issues.apache.org/jira/browse/AMBARI-20108 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20108.patch, screenshot-1.png > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py", > line 420, in > NameNode().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 280, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py", > line 282, in rebalancehdfs > name_node_parameters = json.loads( params.name_node_params ) > File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line > 307, in loads > return _default_decoder.decode(s) > File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line > 335, in decode > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > TypeError: expected string or buffer -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20108) the item of "reblance hdfs" should be hidden in NameNode menu
[ https://issues.apache.org/jira/browse/AMBARI-20108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20108: - Attachment: AMBARI-20108.patch > the item of "reblance hdfs" should be hidden in NameNode menu > - > > Key: AMBARI-20108 > URL: https://issues.apache.org/jira/browse/AMBARI-20108 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20108.patch, screenshot-1.png > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py", > line 420, in > NameNode().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 280, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py", > line 282, in rebalancehdfs > name_node_parameters = json.loads( params.name_node_params ) > File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line > 307, in loads > return _default_decoder.decode(s) > File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line > 335, in decode > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > TypeError: expected string or buffer -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20108) the item of "reblance hdfs" should be hidden in NameNode menu
[ https://issues.apache.org/jira/browse/AMBARI-20108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20108: - Assignee: zhangxiaolu Status: Open (was: Patch Available) > the item of "reblance hdfs" should be hidden in NameNode menu > - > > Key: AMBARI-20108 > URL: https://issues.apache.org/jira/browse/AMBARI-20108 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20108.patch, screenshot-1.png > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py", > line 420, in > NameNode().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 280, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py", > line 282, in rebalancehdfs > name_node_parameters = json.loads( params.name_node_params ) > File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line > 307, in loads > return _default_decoder.decode(s) > File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line > 335, in decode > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > TypeError: expected string or buffer -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Attachment: AMBARI-20368.patch > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Attachment: (was: AMBARI-20368.patch) > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20675) Repetitive operation in hdfs.py
[ https://issues.apache.org/jira/browse/AMBARI-20675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20675: - Resolution: Not A Bug Status: Resolved (was: Patch Available) > Repetitive operation in hdfs.py > --- > > Key: AMBARI-20675 > URL: https://issues.apache.org/jira/browse/AMBARI-20675 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20675.patch, screenshot-1.png > > > the method of install_snappy in hdfs.py is as follows: > def install_snappy(): > import params > Directory([params.so_target_dir_x86, params.so_target_dir_x64], > create_parents = True, > ) > Link(params.so_target_x86, >to=params.so_src_x86, > ) > Link(params.so_target_x64, >to=params.so_src_x64, > ) > is repetitived. > so it's better remove one -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20675) Repetitive operation in hdfs.py
[ https://issues.apache.org/jira/browse/AMBARI-20675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20675: - Attachment: screenshot-1.png > Repetitive operation in hdfs.py > --- > > Key: AMBARI-20675 > URL: https://issues.apache.org/jira/browse/AMBARI-20675 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20675.patch, screenshot-1.png > > > the method of install_snappy in hdfs.py is as follows: > def install_snappy(): > import params > Directory([params.so_target_dir_x86, params.so_target_dir_x64], > create_parents = True, > ) > Link(params.so_target_x86, >to=params.so_src_x86, > ) > Link(params.so_target_x64, >to=params.so_src_x64, > ) > is repetitived. > so it's better remove one -- This message was sent by Atlassian JIRA (v6.3.15#6346)
