Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Sat, 16 Aug 2014 00:32:18 +0000 (UTC)
From: "Zhijie Shen (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12721734.1403023507255.12889.1408149138827@arcas>
In-Reply-To: <JIRA.12721734.1403023507255@arcas>
References: <JIRA.12721734.1403023507255@arcas>
Subject: [jira] [Updated] (YARN-2174) Enabling HTTPs for the writer REST API
 of TimelineServer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhijie Shen updated YARN-2174:
------------------------------

    Attachment: YARN-2174.1.patch

This patch makes TimelineClient be able to post the entities via HTTPS:

1. I've added a test case to verify the communication via HTTPS.
2. I tested POST method over HTTPS in both insecure and secure cluster, and it turned out to work.

> Enabling HTTPs for the writer REST API of TimelineServer
> --------------------------------------------------------
>
>                 Key: YARN-2174
>                 URL: https://issues.apache.org/jira/browse/YARN-2174
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>         Attachments: YARN-2174.1.patch
>
>
> Since we'd like to allow the application to put the timeline data at the client, the AM and even the containers, we need to provide the way to distribute the keystore.


--
This message was sent by Atlassian JIRA
(v6.2#6252)