[jira] [Created] (AMBARI-19416) Ambari agents remain in heartbeat lost state after ambari server restart
Sebastian Toader created AMBARI-19416:
-
Summary: Ambari agents remain in heartbeat lost state after ambari
server restart
Key: AMBARI-19416
URL: https://issues.apache.org/jira/browse/AMBARI-19416
Project: Ambari
Issue Type: Bug
Reporter: Sebastian Toader
Assignee: Sebastian Toader
Priority: Critical
Fix For: 3.0.0
With the implementation https://issues.apache.org/jira/browse/AMBARI-18505 the
execution of status commands is done in a separate child process. Status
commands received from the server by ambari agent are passed to the status
command executor child process via Queue ({{multiprocessing.Queue()}}. In case
the child process is killed, either manually or by the parent process the queue
may end up in bad state (see: http://bugs.python.org/issue20527) thus the
re-spawned status command executor child process may not receive new status
commands any more.
When ambari server is restarted the agent re-registers with ambari server and
upon re-registration it re-spawns the status command child process in order to
receive up to date agent configs
(https://issues.apache.org/jira/browse/AMBARI-19392). In this case the status
commands won't be received by the status command executor child process due the
queue may get stuck leading the ambari agent to stay in heatbeat lost state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19415) Network interface check returns no value if there is no `ifconfig` command
[
https://issues.apache.org/jira/browse/AMBARI-19415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19415:
-
Description:
Ambari Agent Hardware check assumes there is {{ifconfig}} command in Linux, but
some environments (e.g. CentOS 7.3 with minimal install) doens't have
{{ifconfig}} command, but {{ip}} command.
A warning like below (which is in ambari-agent.log) is because of the
assumption.
{code}
WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network interfaces
list from
{code}
It would be better to check the NIC with {{ifconfig}} and {{ip}} both for
better coverage.
was:
Ambari Agent Hardware check assumes there is {{{ifconfig}}} command in Linux,
but some environments (e.g. CentOS 7.3 with minimal install) doens't have
{{{ifconfig}} command, but {{{ip}}} command.
A warning like below (which is in ambari-agent.log) is because of the
assumption.
{{{
WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network interfaces
list from
}}}
It would be better to check the NIC with {{{ifconfig}}} and {{{ip}}} both for
better coverage.
> Network interface check returns no value if there is no `ifconfig` command
> --
>
> Key: AMBARI-19415
> URL: https://issues.apache.org/jira/browse/AMBARI-19415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
> Environment: CentOS7.3 Minimal Install
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>
> Ambari Agent Hardware check assumes there is {{ifconfig}} command in Linux,
> but some environments (e.g. CentOS 7.3 with minimal install) doens't have
> {{ifconfig}} command, but {{ip}} command.
> A warning like below (which is in ambari-agent.log) is because of the
> assumption.
> {code}
> WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network
> interfaces list from
> {code}
> It would be better to check the NIC with {{ifconfig}} and {{ip}} both for
> better coverage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19415) Network interface check returns no value if there is no `ifconfig` command
Masahiro Tanaka created AMBARI-19415:
Summary: Network interface check returns no value if there is no
`ifconfig` command
Key: AMBARI-19415
URL: https://issues.apache.org/jira/browse/AMBARI-19415
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.5.0
Environment: CentOS7.3 Minimal Install
Reporter: Masahiro Tanaka
Assignee: Masahiro Tanaka
Ambari Agent Hardware check assumes there is {{{ifconfig}}} command in Linux,
but some environments (e.g. CentOS 7.3 with minimal install) doens't have
{{{ifconfig}} command, but {{{ip}}} command.
A warning like below (which is in ambari-agent.log) is because of the
assumption.
{{{
WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network interfaces
list from
}}}
It would be better to check the NIC with {{{ifconfig}}} and {{{ip}}} both for
better coverage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19413) Support Ceph for Ambari Service
[ https://issues.apache.org/jira/browse/AMBARI-19413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated AMBARI-19413: --- Summary: Support Ceph for Ambari Service (was: ceph-ambari-service) > Support Ceph for Ambari Service > --- > > Key: AMBARI-19413 > URL: https://issues.apache.org/jira/browse/AMBARI-19413 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: 2.3.0 > Environment: CentOS 6 >Reporter: Gavin > Labels: ambari, ceph > Fix For: 2.3.0 > > > Allow Ceph to be installed via Ambari > I'm trying to do > http://www.redoop.org/OpenStorage/Ceph-service.git -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-13324) Ambari doesn't create Flume Kerberos principal + keytab
[ https://issues.apache.org/jira/browse/AMBARI-13324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15808616#comment-15808616 ] Shi Wang commented on AMBARI-13324: --- Hi [~harisekhon] and [~gss2002], I would like to contribute to this jira, Ambari uses kerberos.json to automate the keytab and principal creation process, and relevant configuration changes. It works similarly with pull the kerberos descriptor as mentioned in comment1. The patch also includes some changes in service check and params after security is enabled. > Ambari doesn't create Flume Kerberos principal + keytab > --- > > Key: AMBARI-13324 > URL: https://issues.apache.org/jira/browse/AMBARI-13324 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 > Environment: HDP 2.3 + Kerberos MIT KDC >Reporter: Hari Sekhon >Assignee: Shi Wang > Fix For: trunk > > Attachments: 0001-AMBARI-13324-createFlumeKeytab.patch, > flume_kerberos.txt > > > When deploying Kerberos via Ambari with MIT KDC, Ambari doesn't generate a > Kerberos principal and keytab for Flume. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13324) Ambari doesn't create Flume Kerberos principal + keytab
[ https://issues.apache.org/jira/browse/AMBARI-13324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shi Wang updated AMBARI-13324: -- Attachment: 0001-AMBARI-13324-createFlumeKeytab.patch > Ambari doesn't create Flume Kerberos principal + keytab > --- > > Key: AMBARI-13324 > URL: https://issues.apache.org/jira/browse/AMBARI-13324 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 > Environment: HDP 2.3 + Kerberos MIT KDC >Reporter: Hari Sekhon >Assignee: Shi Wang > Fix For: trunk > > Attachments: 0001-AMBARI-13324-createFlumeKeytab.patch, > flume_kerberos.txt > > > When deploying Kerberos via Ambari with MIT KDC, Ambari doesn't generate a > Kerberos principal and keytab for Flume. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13324) Ambari doesn't create Flume Kerberos principal + keytab
[ https://issues.apache.org/jira/browse/AMBARI-13324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shi Wang updated AMBARI-13324: -- Assignee: Shi Wang Fix Version/s: trunk Status: Patch Available (was: Open) > Ambari doesn't create Flume Kerberos principal + keytab > --- > > Key: AMBARI-13324 > URL: https://issues.apache.org/jira/browse/AMBARI-13324 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 > Environment: HDP 2.3 + Kerberos MIT KDC >Reporter: Hari Sekhon >Assignee: Shi Wang > Fix For: trunk > > Attachments: flume_kerberos.txt > > > When deploying Kerberos via Ambari with MIT KDC, Ambari doesn't generate a > Kerberos principal and keytab for Flume. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19409) Auto refresh yarn queues when capacity scheduler config is changed from hive configs page
[ https://issues.apache.org/jira/browse/AMBARI-19409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-19409: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5. > Auto refresh yarn queues when capacity scheduler config is changed from hive > configs page > - > > Key: AMBARI-19409 > URL: https://issues.apache.org/jira/browse/AMBARI-19409 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19409.v0.branch-2.5.patch, > AMBARI-19409.v0.trunk.patch > > > Current behavior: > Any change to capacity scheduler triggers a confirmation popup to refresh > yarn queues while saving the configs. > Expected behavior: > The popup should not show up and yarn queues should be refreshed > automatically upon changes to capacity scheduler config from hive configs > page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19414) Cannot install Accumulo via blueprint with default settings
[
https://issues.apache.org/jira/browse/AMBARI-19414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19414:
---
Status: Patch Available (was: Open)
> Cannot install Accumulo via blueprint with default settings
> ---
>
> Key: AMBARI-19414
> URL: https://issues.apache.org/jira/browse/AMBARI-19414
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19414.patch
>
>
> Accumulo installation via blueprint with default settings (ie. without
> including {{accumulo-env}}) fails with the following error:
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ACCUMULO/1.6.1.2.2.0/package/scripts/accumulo_gc.py",
> line 24, in
> AccumuloScript('gc').execute()
> File
> "/var/lib/ambari-agent/cache/common-services/ACCUMULO/1.6.1.2.2.0/package/scripts/accumulo_script.py",
> line 51, in __init__
> import status_params
> File
> "/var/lib/ambari-agent/cache/common-services/ACCUMULO/1.6.1.2.2.0/package/scripts/status_params.py",
> line 43, in
> pid_dir = config['configurations']['accumulo-env']['accumulo_pid_dir']
> TypeError: 'NoneType' object is unsubscriptable
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19414) Cannot install Accumulo via blueprint with default settings
[
https://issues.apache.org/jira/browse/AMBARI-19414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19414:
---
Attachment: AMBARI-19414.patch
> Cannot install Accumulo via blueprint with default settings
> ---
>
> Key: AMBARI-19414
> URL: https://issues.apache.org/jira/browse/AMBARI-19414
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19414.patch
>
>
> Accumulo installation via blueprint with default settings (ie. without
> including {{accumulo-env}}) fails with the following error:
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ACCUMULO/1.6.1.2.2.0/package/scripts/accumulo_gc.py",
> line 24, in
> AccumuloScript('gc').execute()
> File
> "/var/lib/ambari-agent/cache/common-services/ACCUMULO/1.6.1.2.2.0/package/scripts/accumulo_script.py",
> line 51, in __init__
> import status_params
> File
> "/var/lib/ambari-agent/cache/common-services/ACCUMULO/1.6.1.2.2.0/package/scripts/status_params.py",
> line 43, in
> pid_dir = config['configurations']['accumulo-env']['accumulo_pid_dir']
> TypeError: 'NoneType' object is unsubscriptable
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19414) Cannot install Accumulo via blueprint with default settings
Doroszlai, Attila created AMBARI-19414:
--
Summary: Cannot install Accumulo via blueprint with default
settings
Key: AMBARI-19414
URL: https://issues.apache.org/jira/browse/AMBARI-19414
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Fix For: 3.0.0
Accumulo installation via blueprint with default settings (ie. without
including {{accumulo-env}}) fails with the following error:
{noformat}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/ACCUMULO/1.6.1.2.2.0/package/scripts/accumulo_gc.py",
line 24, in
AccumuloScript('gc').execute()
File
"/var/lib/ambari-agent/cache/common-services/ACCUMULO/1.6.1.2.2.0/package/scripts/accumulo_script.py",
line 51, in __init__
import status_params
File
"/var/lib/ambari-agent/cache/common-services/ACCUMULO/1.6.1.2.2.0/package/scripts/status_params.py",
line 43, in
pid_dir = config['configurations']['accumulo-env']['accumulo_pid_dir']
TypeError: 'NoneType' object is unsubscriptable
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19413) ceph-ambari-service
[ https://issues.apache.org/jira/browse/AMBARI-19413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated AMBARI-19413: --- Issue Type: New Feature (was: Task) > ceph-ambari-service > --- > > Key: AMBARI-19413 > URL: https://issues.apache.org/jira/browse/AMBARI-19413 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: 2.3.0 > Environment: CentOS 6 >Reporter: Gavin > Labels: ambari, ceph > Fix For: 2.3.0 > > > Allow Ceph to be installed via Ambari > I'm trying to do > http://www.redoop.org/OpenStorage/Ceph-service.git -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19413) ceph-ambari-service
Gavin created AMBARI-19413: -- Summary: ceph-ambari-service Key: AMBARI-19413 URL: https://issues.apache.org/jira/browse/AMBARI-19413 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.3.0 Environment: CentOS 6 Reporter: Gavin Fix For: 2.3.0 Allow Ceph to be installed via Ambari I'm trying to do http://www.redoop.org/OpenStorage/Ceph-service.git -- This message was sent by Atlassian JIRA (v6.3.4#6332)
