Did you add the `flink-queryable-state-runtime` jar as a dependency to your project? You can check the log whether a queryable state proxy and server have been started.
Cheers, Till On Fri, Jan 5, 2018 at 5:19 PM, Boris Lublinsky < boris.lublin...@lightbend.com> wrote: > I also tried to comment out > > // config.setInteger(ConfigConstants.LOCAL_NUMBER_TASK_MANAGER, 2); > > Still no luck. > Do you guys have a working example for queryable state for 1.4 somewhere? > > Boris Lublinsky > FDP Architect > boris.lublin...@lightbend.com > https://www.lightbend.com/ > > On Jan 5, 2018, at 6:33 AM, Till Rohrmann <trohrm...@apache.org> wrote: > > Hi Boris, > > if you start 2 TaskManagers on the same host, then you have to define a > port range for the KvState server and the proxy. Otherwise the Flink > cluster should not be able to start. > > Cheers, > Till > > On Thu, Jan 4, 2018 at 11:19 PM, Boris Lublinsky < > boris.lublin...@lightbend.com> wrote: > >> It appears, that queryable state access significantly changed in 1.4 >> compared to 1.3. >> >> Documentation on the queryable state client https://ci.apache.org/p >> rojects/flink/flink-docs-release-1.4/dev/stream/state/querya >> ble_state.html#example >> States that the client needs to connect to a proxy port. >> My implementation, which I used for 1.3 is enclosed >> >> >> Here I am setting both server port and proxy port. >> When I am running it on a localhost and try to do lsof -i:9069 and lsof >> -i:9067 It does not show anything using this port. >> >> Am I missing something? >> >> As a result my query implementation >> >> >> Return an error - connection refused >> >> My state is defined in the following class >> >> >> Boris Lublinsky >> FDP Architect >> boris.lublin...@lightbend.com >> https://www.lightbend.com/ >> >> >> > >
