Hadoop QA commented on AMBARI-18630:

{color:red}-1 overall{color}.  Here are the results of testing the latest 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 

Test results: 
Console output: 

This message is automatically generated.

> For rolling upgrade of Kafka, set configs for backward compatibility
> -----------------------------------------------------------------------------
>                 Key: AMBARI-18630
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18630
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>            Priority: Critical
>             Fix For: trunk, 2.5.0, 2.4.2
>         Attachments: AMBARI-18630.patch
> In the 2.5 upgrade pack, the following properties need to be set
> {code}
> inter.broker.protocol.version=
> log.message.format.version=
> {code}
> after upgrade is done we should delete the inter.broker.protocol.version.
> Users should remove log.message.format.version once they update their clients.

This message was sent by Atlassian JIRA

Reply via email to