Mailing-List: contact user-help@flink.apache.org; run by ezmlm
Precedence: bulk
Subject: Re: Question about jobmanager.web.upload.dir
To: user@flink.apache.org
References: <d350e533-88ae-1f2e-f7b1-14e31bbce137@radicalbit.io>
From: Timo Walther <twalthr@apache.org>
Cc: chesnay@apache.org
Message-ID: <1c78b17a-5360-c00c-ed32-ada051ced2b7@apache.org>
Date: Wed, 17 May 2017 15:52:02 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0)
 Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <d350e533-88ae-1f2e-f7b1-14e31bbce137@radicalbit.io>
Content-Type: text/plain; charset=iso-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Wed, 17 May 2017 13:52:08 -0000

Hey Mauro,

I'm not aware of any reason for that. I loop in Chesnay, maybe he knows 
why. @Chesnay wouldn't it be helpful to also archive the jars using the 
HistoryServer?

Timo


Am 17.05.17 um 12:31 schrieb Mauro Cortellazzi:
> Hi Flink comunity,
>
> is there a particular reason to delete the jobmanager.web.upload.dir 
> content when the JobManager restart? Could it be interesting have the 
> jar previously uploaded when JM restart? Could the jars be saved to 
> HDFS for HA mode?
>
> Thank you for your support.
>
> Mauro