Is there a way to reload a log4j.properties file without stopping and starting the job server?
Any guidance on troubleshooting error Error: No KvStateLocation found for KvState instance with name X when trying to make a queryable state call in Flink 1.2.0? I do know the server is receiving the call made from the remote client. (query.server.enable = true on the server in
andalone cluster and configure 6123 as the port. I'm pretty surethat the config has not been updated.But everything should work as you say when you point it to the correctjobmanager address and port. Could you please post the completestacktrace you get instead of the message you log?On Mon, Apr 24, 2017
state instance with the respective name in the case of parallelism >1?Expected output is something like this: "Key value state registeredfor job ${msg.getJobId} under name ${msg.getRegistrationName}."– UfukOn Wed, Apr 26, 2017 at 3:06 PM, Chet Masterson<chet.master...@yandex.com> w
I moved up from running queryable state on a standalone Flink instance to a several node cluster. My queries don't seem to be responding when I execute them on the cluster. A few questions: 1. The error I am getting:WARN [ReliableDeliverySupervisor] Association with remote system
Any insight here? I've got a situation where a key value state on a task manager is being registered with the job manager, but when I try to query it, the job manager responds it doesn't know the location of the key value state... 26.04.2017, 12:11, "Chet Masterson" <chet.master.
to aJM.– UfukOn Tue, May 2, 2017 at 2:53 PM, Chet Masterson<chet.master...@yandex.com> wrote: Can do. Any advice on where the trace prints should go in the task manager source code? BTW - How do I know I have a correctly configured cluster? Is there a set of messages in the job / task manager
ask manager side?– UfukOn Fri, Apr 28, 2017 at 2:20 PM, Chet Masterson<chet.master...@yandex.com> wrote: Any insight here? I've got a situation where a key value state on a task manager is being registered with the job manager, but when I try to query it, the job manager responds it doe
