Running the executables from Flink distribution of the source build

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Running the executables from Flink distribution of the source build

kedar mhaswade
Flink gurus!

I have built Flink from source. I find that the executables are all at:

<workspace>/flink-dist/target/flink-1.6-SNAPSHOT-bin/flink-1.6-SNAPSHOT.

However, when I try to run start-scala-shell.sh local from the bin subfolder of this folder, it does not seem to run the simple wordcount example. Am I doing it right? How else do people test out the distribution of the Flink sources that the have just built?

Regards,
Kedar

PS- A tentative thread dump on JobManager shows that many threads are just waiting on some condition variable. Appears like a livelock. The task manager has one main thread which is also waiting.
Reply | Threaded
Open this post in threaded view
|

Re: Running the executables from Flink distribution of the source build

flinkuser101
Can you try to look into log folder for error? May be some clue.



--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: Running the executables from Flink distribution of the source build

Chesnay Schepler
In reply to this post by kedar mhaswade
The scala-shell does not currently work out-of-the-box in 1.5-SNAPSHOT/1.6-SNAPSHOT.

As a workaround please add "mode: old" to conf/flink-conf.yaml.
 
See also: https://issues.apache.org/jira/browse/FLINK-8795

On 12.03.2018 02:19, kedar mhaswade wrote:
Flink gurus!

I have built Flink from source. I find that the executables are all at:

<workspace>/flink-dist/target/flink-1.6-SNAPSHOT-bin/flink-1.6-SNAPSHOT.

However, when I try to run start-scala-shell.sh local from the bin subfolder of this folder, it does not seem to run the simple wordcount example. Am I doing it right? How else do people test out the distribution of the Flink sources that the have just built?

Regards,
Kedar

PS- A tentative thread dump on JobManager shows that many threads are just waiting on some condition variable. Appears like a livelock. The task manager has one main thread which is also waiting.