For enabling JMX when starting Flink from your IDE, you need to do the
following:
Configuration configuration = new Configuration();
configuration.setString("metrics.reporters", "my_jmx_reporter");
configuration.setString("metrics.reporter.my_jmx_reporter.class",
"org.apache.flink.metrics.jmx.JMXReporter");
configuration.setString("metrics.reporter.my_jmx_reporter.port",
"9020-9040");
StreamExecutionEnvironment see =
StreamExecutionEnvironment.createLocalEnvironment(1, configuration);
On Mon, Dec 5, 2016 at 11:56 AM, vinay patil <vinay18.pa...@gmail.com>
wrote:
> Yes I had configured it as given in the documentation.
> I can see this line in Job Manager Logs : Started JMX server on port 9020
> (but this was on EMR )
>
> How to do this locally ? can we check these metrics while running the
> pipeline from IDE ? If yes what is teh default JMX port to connect ? or do
> we need to do some configuration locally ?
>
> Regards,
> Vinay Patil
>
> On Mon, Dec 5, 2016 at 4:14 PM, rmetzger0 [via Apache Flink User Mailing
> List archive.] <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=10445&i=0>> wrote:
>
>> Hi Vinay,
>>
>> the JMX port depends on the port you've configured for the JMX metrics
>> reporter.
>> Did you configure it?
>>
>> Regards,
>> Robert
>>
>>
>> On Fri, Dec 2, 2016 at 11:14 AM, vinay patil <[hidden email]
>> <http:///user/SendEmail.jtp?type=node&node=10442&i=0>> wrote:
>>
>>> Hi Robert,
>>>
>>> I had resolved this issue earlier as I had not set the Kafka source
>>> parallelism to number of partitions, so I was getting the issue of window
>>> not getting triggered.
>>>
>>> Now I am facing the same issue, I tried to check the watermark value by
>>> using visualVM locally but I am not seeing that value there, I have
>>> attached
>>> the snapahot of visualVM
>>> <http://apache-flink-user-mailing-list-archive.2336050.n4.na
>>> bble.com/file/n10412/jVisualVMMetrics.png>
>>>
>>> Just to verify , JMX port runs on 9010 by default , right ?, because
>>> when I
>>> tried to connect to it locally, I could not connect
>>>
>>>
>>>
>>> --
>>> View this message in context: http://apache-flink-user-maili
>>> ng-list-archive.2336050.n4.nabble.com/Dealing-with-Multiple-
>>> sinks-in-Flink-tp8643p10412.html
>>> Sent from the Apache Flink User Mailing List archive. mailing list
>>> archive at Nabble.com.
>>>
>>
>>
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://apache-flink-user-mailing-list-archive.2336050.n4.
>> nabble.com/Dealing-with-Multiple-sinks-in-Flink-tp8643p10442.html
>> To start a new topic under Apache Flink User Mailing List archive., email
>> [hidden
>> email] <http:///user/SendEmail.jtp?type=node&node=10445&i=1>
>> To unsubscribe from Apache Flink User Mailing List archive., click here.
>> NAML
>> <http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>
> ------------------------------
> View this message in context: Re: Dealing with Multiple sinks in Flink
> <http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Dealing-with-Multiple-sinks-in-Flink-tp8643p10445.html>
> Sent from the Apache Flink User Mailing List archive. mailing list archive
> <http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/> at
> Nabble.com.
>
