Thank you Chesnay. I found the logs being printed in the standalone session
when I used CLI to submit the job. However this only deepens the mystery of
the configuration file on the other thread - I see from the logs that the
configuration values are being read correctly, but when these values are
I see, thanks for that clarification - I incorrectly assumed both methods
of submission produce logs in the same place. I will have an update
tomorrow!
On Wed, Oct 21, 2020 at 6:12 PM Chesnay Schepler wrote:
> Hold on, let us clarify how you submit the job.
>
> Do you upload the jar via the WebU
Hold on, let us clarify how you submit the job.
Do you upload the jar via the WebUI, or with the CLI (e.g., ./bin/flink
run ...)?
If it is the former, then it show up in the JM logs.
If it is the latter, then it should appear in the logs of the client
(i.e., log/flink-???-client-???.log).
O
Hi Chesnay,
I checked the JobManager logs - it's not there either.
On Wed, Oct 21, 2020 at 3:51 PM Chesnay Schepler wrote:
> The main method is executed in the JobManager process and never reaches
> the TaskExecutors (only the individual functions do).
> As such you have to take a peek into the
The main method is executed in the JobManager process and never reaches
the TaskExecutors (only the individual functions do).
As such you have to take a peek into the JobManager logs.
On 10/21/2020 11:37 AM, Manas Kale wrote:
Hi,
I have the following pattern:
public static void main(String[] a
Hi,
I have the following pattern:
public static void main(String[] args) {
// Get the exec environment. This could be a cluster or a
mini-cluster used for local development.
StreamExecutionEnvironment env =
StreamExecutionEnvironment.getExecutionEnvironment();
// Make the Flink
