g of
> topics,
> but it's definitely on the todo list for the Kafka connector and won't be
> too hard to implement once querying in the consumer is resolved (perhaps
> Robert can clarify this a bit more).
>
> Best,
> Gordon
>
>
>
> --
> View this message in co
context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/API-request-to-submit-job-takes-over-1hr-tp7319p7558.html
Sent from the Apache Flink User Mailing List archive. mailing list archive at
Nabble.com.
t;>
Date: Thursday, June 2, 2016 at 4:19 AM
To: "user@flink.apache.org<mailto:user@flink.apache.org>"
mailto:user@flink.apache.org>>
Subject: Re: API request to submit job takes over 1hr
Hi Shannon,
thank you for further investigating the issue.
Its fine to keep the disc
y.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)
> at
> io.netty.util.concurrent.Default
ead.java:745)
From: Shannon Carey mailto:shannon.ca...@orbitz.com>>
on behalf of Shannon Carey mailto:sca...@expedia.com>>
Date: Wednesday, June 1, 2016 at 12:54 PM
To: "user@flink.apache.org<mailto:user@flink.apache.org>"
mailto:user@flink.apache.org>>
Subject: API
Hi folks,
I have deployed a Flink cluster on top of YARN in an AWS EMR cluster in my test
environment, and everything is working fine. However, I am unable to submit
jobs to the prod cluster.
Uploading the JAR containing a Flink job succeeds. However, the request to run
the job (UI makes API
