flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7040) Flip-6 client-cluster communication
Date Tue, 22 Aug 2017 15:14:00 GMT

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

ASF GitHub Bot commented on FLINK-7040:
---------------------------------------

Github user zentol commented on a diff in the pull request:

    https://github.com/apache/flink/pull/4569#discussion_r134512163
  
    --- Diff: flink-runtime/src/main/java/org/apache/flink/runtime/rest/RestClientEndpoint.java
---
    @@ -0,0 +1,263 @@
    +/*
    + * Licensed to the Apache Software Foundation (ASF) under one
    + * or more contributor license agreements.  See the NOTICE file
    + * distributed with this work for additional information
    + * regarding copyright ownership.  The ASF licenses this file
    + * to you under the Apache License, Version 2.0 (the
    + * "License"); you may not use this file except in compliance
    + * with the License.  You may obtain a copy of the License at
    + *
    + *     http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +
    +package org.apache.flink.runtime.rest;
    +
    +import org.apache.flink.configuration.ConfigConstants;
    +import org.apache.flink.runtime.concurrent.Executors;
    +import org.apache.flink.runtime.concurrent.FutureUtils;
    +import org.apache.flink.runtime.rest.handler.PipelineErrorHandler;
    +import org.apache.flink.runtime.rest.messages.ErrorResponseBody;
    +import org.apache.flink.runtime.rest.messages.MessageHeaders;
    +import org.apache.flink.runtime.rest.messages.ParameterMapper;
    +import org.apache.flink.runtime.rest.messages.RequestBody;
    +import org.apache.flink.runtime.rest.messages.ResponseBody;
    +import org.apache.flink.runtime.rest.util.RestMapperUtils;
    +import org.apache.flink.util.Preconditions;
    +
    +import org.apache.flink.shaded.netty4.io.netty.bootstrap.Bootstrap;
    +import org.apache.flink.shaded.netty4.io.netty.buffer.ByteBuf;
    +import org.apache.flink.shaded.netty4.io.netty.buffer.ByteBufInputStream;
    +import org.apache.flink.shaded.netty4.io.netty.buffer.Unpooled;
    +import org.apache.flink.shaded.netty4.io.netty.channel.Channel;
    +import org.apache.flink.shaded.netty4.io.netty.channel.ChannelHandler;
    +import org.apache.flink.shaded.netty4.io.netty.channel.ChannelHandlerContext;
    +import org.apache.flink.shaded.netty4.io.netty.channel.ChannelInitializer;
    +import org.apache.flink.shaded.netty4.io.netty.channel.SimpleChannelInboundHandler;
    +import org.apache.flink.shaded.netty4.io.netty.channel.nio.NioEventLoopGroup;
    +import org.apache.flink.shaded.netty4.io.netty.channel.socket.SocketChannel;
    +import org.apache.flink.shaded.netty4.io.netty.channel.socket.nio.NioSocketChannel;
    +import org.apache.flink.shaded.netty4.io.netty.handler.codec.http.DefaultFullHttpRequest;
    +import org.apache.flink.shaded.netty4.io.netty.handler.codec.http.FullHttpRequest;
    +import org.apache.flink.shaded.netty4.io.netty.handler.codec.http.FullHttpResponse;
    +import org.apache.flink.shaded.netty4.io.netty.handler.codec.http.HttpClientCodec;
    +import org.apache.flink.shaded.netty4.io.netty.handler.codec.http.HttpHeaders;
    +import org.apache.flink.shaded.netty4.io.netty.handler.codec.http.HttpObjectAggregator;
    +import org.apache.flink.shaded.netty4.io.netty.handler.codec.http.HttpVersion;
    +import org.apache.flink.shaded.netty4.io.netty.handler.ssl.SslHandler;
    +
    +import com.fasterxml.jackson.core.JsonParseException;
    +import com.fasterxml.jackson.core.JsonProcessingException;
    +import com.fasterxml.jackson.databind.JsonMappingException;
    +import com.fasterxml.jackson.databind.JsonNode;
    +import com.fasterxml.jackson.databind.ObjectMapper;
    +import org.slf4j.Logger;
    +import org.slf4j.LoggerFactory;
    +
    +import javax.net.ssl.SSLEngine;
    +
    +import java.io.IOException;
    +import java.io.InputStream;
    +import java.io.StringWriter;
    +import java.util.concurrent.CompletableFuture;
    +import java.util.concurrent.Executor;
    +
    +/**
    + * This client is the counter-part to the {@link RestServerEndpoint}.
    + */
    +public class RestClientEndpoint {
    +	private static final Logger LOG = LoggerFactory.getLogger(RestClientEndpoint.class);
    +
    +	private static final ObjectMapper objectMapper = RestMapperUtils.getStrictObjectMapper();
    +
    +	private final String configuredTargetAddress;
    +	private final int configuredTargetPort;
    +	private final SSLEngine sslEngine;
    +
    +	private Bootstrap bootstrap;
    +
    +	private final ClientHandler handler = new ClientHandler();
    +
    +	private CompletableFuture<?> lastFuture = CompletableFuture.completedFuture(null);
    +
    +	private final Executor directExecutor = Executors.directExecutor();
    +
    +	public RestClientEndpoint(RestClientEndpointConfiguration configuration) {
    +		this.configuredTargetAddress = configuration.getTargetRestEndpointAddress();
    +		this.configuredTargetPort = configuration.getTargetRestEndpointPort();
    +		this.sslEngine = configuration.getSslEngine();
    +	}
    +
    +	public void start() {
    +		ChannelInitializer<SocketChannel> initializer = new ChannelInitializer<SocketChannel>()
{
    +
    +			@Override
    +			protected void initChannel(SocketChannel ch) {
    +
    +				// SSL should be the first handler in the pipeline
    +				if (sslEngine != null) {
    +					ch.pipeline().addLast("ssl", new SslHandler(sslEngine));
    +				}
    +
    +				ch.pipeline()
    +					.addLast(new HttpClientCodec())
    +					.addLast(new HttpObjectAggregator(1024 * 1024))
    +					.addLast(handler)
    +					.addLast(new PipelineErrorHandler(LOG));
    +			}
    +		};
    +
    +		NioEventLoopGroup group = new NioEventLoopGroup(1);
    +
    +		bootstrap = new Bootstrap();
    +		bootstrap
    +			.group(group)
    +			.channel(NioSocketChannel.class)
    +			.handler(initializer);
    +
    +		LOG.info("Rest client endpoint started.");
    --- End diff --
    
    its not strictly _necessary_ for the server since the `RestServerEndpoint` constructor
could accept the list of handlers.


> Flip-6 client-cluster communication
> -----------------------------------
>
>                 Key: FLINK-7040
>                 URL: https://issues.apache.org/jira/browse/FLINK-7040
>             Project: Flink
>          Issue Type: New Feature
>          Components: Cluster Management, Mesos
>            Reporter: Till Rohrmann
>            Assignee: Chesnay Schepler
>            Priority: Critical
>              Labels: flip-6
>
> With the new Flip-6 architecture, the client will communicate with the cluster in a RESTful
manner.
> The cluster shall support the following REST calls:
> * List jobs (GET): Get list of all running jobs on the cluster
> * Submit job (POST): Submit a job to the cluster (only supported in session mode)
> * Lookup job leader (GET): Gets the JM leader for the given job
> * Get job status (GET): Get the status of an executed job (and maybe the JobExecutionResult)
> * Cancel job (PUT): Cancel the given job
> * Stop job (PUT): Stops the given job
> * Take savepoint (POST): Take savepoint for given job (How to return the savepoint under
which the savepoint was stored? Maybe always having to specify a path)
> * Get KV state (GET): Gets the KV state for the given job and key (Queryable state)
> * Poll/subscribe to notifications for job (GET, WebSocket): Polls new notifications from
the execution of the given job/Opens WebSocket to receive notifications
> The first four REST calls will be served by the REST endpoint running in the application
master/cluster entrypoint. The other calls will be served by a REST endpoint running along
side to the JobManager.
> Detailed information about different implementations and their pros and cons can be found
in this document:
> https://docs.google.com/document/d/1eIX6FS9stwraRdSUgRSuLXC1sL7NAmxtuqIXe_jSi-k/edit?usp=sharing
> The implementation will most likely be Netty based.



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

Mime
View raw message