[jira] [Created] (FLINK-9937) Kubernetes(Minikube) Flink : cannot submit job in Flink UI with FLink 1.5.1

2018-07-24 Thread Aleksandr Filichkin (JIRA)
Aleksandr Filichkin created FLINK-9937:
--

 Summary: Kubernetes(Minikube) Flink : cannot submit job in Flink 
UI with FLink 1.5.1
 Key: FLINK-9937
 URL: https://issues.apache.org/jira/browse/FLINK-9937
 Project: Flink
  Issue Type: Wish
Reporter: Aleksandr Filichkin


Hi,
I cannot submit Flink 1,5,1 job from UI on Kubernetes(minikube).
But it works perfect with Flink 1.4.2

I've created Flink artifacts like this:
kubectl create -f jobmanager-deployment.yaml
kubectl create -f taskmanager-deployment.yaml
kubectl create -f jobmanager-service.yaml

>From 
>https://ci.apache.org/projects/flink/flink-docs-release-1.2/setup/kubernetes.html
The make kubctl port-frowasr  8081




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9893) Cannot run Flink job in IDE when we have more than 1 taskslot

2018-07-19 Thread Aleksandr Filichkin (JIRA)
Aleksandr Filichkin created FLINK-9893:
--

 Summary: Cannot run Flink job in IDE when we have more than 1 
taskslot
 Key: FLINK-9893
 URL: https://issues.apache.org/jira/browse/FLINK-9893
 Project: Flink
  Issue Type: Wish
  Components: Streaming
Affects Versions: 1.5.1
Reporter: Aleksandr Filichkin


The problem is I cannot run it in IDE when I have more than 1 taskslot in my 
job.

public class StreamingJob {

public static void main(String[] args) throws Exception {
// set up the streaming execution environment
final StreamExecutionEnvironment env = 
StreamExecutionEnvironment.getExecutionEnvironment();

Properties kafkaProperties = new Properties();
kafkaProperties.setProperty("bootstrap.servers", "localhost:9092");
kafkaProperties.setProperty("group.id", "test");
env.setParallelism(1);

DataStream kafkaSource = env.addSource(new 
FlinkKafkaConsumer010<>("flink-source", new SimpleStringSchema(), 
kafkaProperties)).name("Kafka-Source").slotSharingGroup("Kafka-Source");

kafkaSource.print().slotSharingGroup("Print");

env.execute("Flink Streaming Java API Skeleton");
}
}

I know that job need 2 slot for this job and I can have two taskmanagers in 
Flink cluster, but how can I run it locally in IDE.

Currently I have to specify the same slotSharingGroup name for all operator 
locally to have one slot. But it's not flexible.

How do you handle it?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-8829) Flink in EMR(YARN) is down due to Akka communication issue

2018-03-01 Thread Aleksandr Filichkin (JIRA)
Aleksandr Filichkin created FLINK-8829:
--

 Summary: Flink in EMR(YARN) is down due to Akka communication issue
 Key: FLINK-8829
 URL: https://issues.apache.org/jira/browse/FLINK-8829
 Project: Flink
  Issue Type: Bug
  Components: YARN
Affects Versions: 1.3.2
Reporter: Aleksandr Filichkin


Hi,

We have running Flink 1.3.2 app in Amazon EMR. Every week our Flink job is down 
due to:

_2018-02-16 19:00:04,595 WARN akka.remote.ReliableDeliverySupervisor - 
Association with remote system 
[akka.tcp://[fl...@ip-10-97-34-209.tr-fr-nonprod.aws-int.thomsonreuters.com:42177]|mailto:fl...@ip-10-97-34-209.tr-fr-nonprod.aws-int.thomsonreuters.com:42177]]
 has failed, address is now gated for [5000] ms. Reason: [Association failed 
with 
[akka.tcp://[fl...@ip-10-97-34-209.tr-fr-nonprod.aws-int.thomsonreuters.com:42177]]|mailto:fl...@ip-10-97-34-209.tr-fr-nonprod.aws-int.thomsonreuters.com:42177]]]
 Caused by: [Connection refused: 
ip-10-97-34-209.tr-fr-nonprod.aws-int.thomsonreuters.com/10.97.34.209:42177] 
2018-02-16 19:00:05,593 WARN akka.remote.RemoteWatcher - Detected unreachable: 
[akka.tcp://[fl...@ip-10-97-34-209.tr-fr-nonprod.aws-int.thomsonreuters.com:42177]|mailto:fl...@ip-10-97-34-209.tr-fr-nonprod.aws-int.thomsonreuters.com:42177]]
 2018-02-16 19:00:05,596 INFO 
org.apache.flink.runtime.client.JobSubmissionClientActor - Lost connection to 
JobManager 
akka.tcp://[fl...@ip-10-97-34-209.tr-fr-nonprod.aws-int.thomsonreuters.com:42177/user/jobmanager|mailto:fl...@ip-10-97-34-209.tr-fr-nonprod.aws-int.thomsonreuters.com:42177/user/jobmanager].
 Triggering connection timeout._

Do you have any ideas how to troubleshoot it?

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)