Hi Chesnay If REST API (i.e. the web server) is mandatory for submitting jobs then why is there an option to set rest.port to -1? I think it should be mandatory to set some valid port for rest.port and make sure flink job manager does not come up if valid port is not set for rest.port? Or else there must be some way to submit jobs even if REST API (i.e. the web server) is not instantiated.
If jobmanger.rpc.address is not required for flink client then why is it still looking for that property in flink-conf.yaml? Isn't it not a bug? Because if we comment out the jobmanger.rpc.address and jobmanger.rpc.port then flink client will not be able to submit the job. On Tue, Jun 19, 2018 at 5:49 PM, Chesnay Schepler <ches...@apache.org> wrote: > In 1.5 we reworked the job-submission to go through the REST API instead > of akka. > > I believe the jobmanager rpc port shouldn't be necessary anymore, the rpc > address is still *required *due to some technical implementations; it may > be that you can set this to some arbitrary value however. > > As a result the REST API (i.e. the web server) must be running in order to > submit jobs. > > > On 19.06.2018 14:12, Sampath Bhat wrote: > > Hello > > I'm using Flink 1.5.0 version and Flink CLI to submit jar to flink cluster. > > In flink 1.4.2 only job manager rpc address and job manager rpc port were > sufficient for flink client to connect to job manager and submit the job. > > But in flink 1.5.0 the flink client additionally requires the rest.address > and rest.port for submitting the job to job manager. What is the advantage > of this new method over the 1.4.2 method of submitting job? > > Moreover if we make rest.port = -1 the web server will not be instantiated > then how should we submit the job? > > Regards > Sampath > > >
