ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21629) Update Include and Exclude Files for [HDFS]/Refreshnodes is called even if manage.include.files is set to false
Date Mon, 07 Aug 2017 15:37:00 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-21629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116761#comment-16116761
] 

Hadoop QA commented on AMBARI-21629:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12880661/AMBARI-21629.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level [trunk compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/11945//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11945//console

This message is automatically generated.

> Update Include and Exclude Files for [HDFS]/Refreshnodes is called even if manage.include.files
is set to false
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21629
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21629
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-admin
>    Affects Versions: 2.5.2
>            Reporter: Dhanya Balasundaran
>            Assignee: Dmytro Sen
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-21629.patch
>
>
> - Deploy a cluster
> - manage.include.files property in Advanced hdfs-site is set to false by default
> - Stop and Delete datanode from one of the hosts
> - Check bgops to make sure we see Delete Datanode as the Operation
> - But it shows "Update Include and Exclude Files for HDFS"
> - As user chose not to manage this file by setting property to false, this operation
should not have been shown. From logs of this operation looks like it called refreshnodes
too



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message