Fabian, Thank you for the prompt responses. I was able to find the output in the job manager logs. There were no task manager logs generated
Sent from my iPhone > On Aug 30, 2017, at 8:24 AM, Fabian Hueske <fhue...@gmail.com> wrote: > > print() writes to the standard output of the TaskManager process. > The TM stdout is usually redirected to an out file in the ./log folder. > > 2017-08-30 17:20 GMT+02:00 Krishnanand Khambadkone <kkhambadk...@yahoo.com>: >> I am running this standalone, not under yarn, on a single instance setup. >> I believe you are referring to the flink log files >> >> Sent from my iPhone >> >>> On Aug 30, 2017, at 12:56 AM, Fabian Hueske <fhue...@gmail.com> wrote: >>> >>> Fabian Hueske (fhue...@gmail.com) is not on your Guest List | Approve >>> sender | Approve domain >>> Hi, >>> >>> print() writes the data to the out files of the TaskManagers. So you need >>> to go to the machine that runs the TM and check its out file which is >>> located in the log folder. >>> >>> Best, Fabian >>> >>> 2017-08-29 23:53 GMT+02:00 Krishnanand Khambadkone <kkhambadk...@yahoo.com>: >>>> I am trying to run the basic twitter example, it does deploy correctly >>>> and show as RUNNING both in the command line and in the UI. However I see >>>> no output. I am able to verify that my credentials are correct with >>>> another small client I have built that does connect to twitter and prints >>>> out tweets. >>>> >>>> >>>> streamSource = env.addSource(new TwitterSource(props)); >>>> streamSource.print(); >>>> >>>> >>>> >>>> >>>> *************** TWITTER INPUTS ************* >>>> qzenHPFVPNb7GaEypSvp3yV3s : >>>> XQuQHpOklVnUHEUTmtEbePU7O80Vaj5mwWnvNMrGyBiSsML9dA : >>>> 78358289-rjJ44rtlFr5BlTMyNPzDjQq6daOMT7PnQVvkGgwgO : >>>> IAr1eoCbBuJRkaERcKFxv5mFAOu6KPr7Q2EmAZYRXmedl >>>> ********************* FOUND PROPERTIES ***************** >>>> Submitting job with JobID: de6024b484fc1d163b4190011595e4f0. Waiting for >>>> job completion. >>>> Connected to JobManager at >>>> Actor[akka.tcp://flink@localhost:6123/user/jobmanager#1901137740] with >>>> leader session id 00000000-0000-0000-0000-000000000000. >>>> 08/29/2017 14:25:32 Job execution switched to status RUNNING. >>>> 08/29/2017 14:25:32 Source: Custom Source -> Sink: Unnamed(1/1) >>>> switched to SCHEDULED >>>> 08/29/2017 14:25:32 Source: Custom Source -> Sink: Unnamed(1/1) >>>> switched to DEPLOYING >>>> 08/29/2017 14:25:32 Source: Custom Source -> Sink: Unnamed(1/1) >>>> switched to RUNNING >>>> >>> >
