Is this the list of metrics reported by storm in JMX?

Hi, I know there are plans to revamp the current metrics system. But until then, I just wanted to confirm the metrics I have got through JMX and if that is expected. I added the following to *worker.options*: -Dcom.sun.management.jmxremote \ -Dcom.sun.management.jmxremote.port=1%ID% \

Re: Does one port in supervisor.slots.ports translate to one physical JVM?

Thanks. Somehow this was slightly unclear in the docs. On Thu, Oct 13, 2016 at 3:49 PM, P. Taylor Goetz wrote: > Answered there as well, but yes, one port == one slot == one JVM. > > -Taylor > > > On Oct 13, 2016, at 6:17 PM, Tech Id wrote: > > > >

[GitHub] storm issue #1702: Update Eventhub-Client jar dependency to 1.0.1

Github user srdo commented on the issue: https://github.com/apache/storm/pull/1702 No, this seems fine. +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so,

Re: Does one port in supervisor.slots.ports translate to one physical JVM?

Answered there as well, but yes, one port == one slot == one JVM. -Taylor > On Oct 13, 2016, at 6:17 PM, Tech Id wrote: > > Hi, > > Does anyone know the answer to this question? >

Does one port in supervisor.slots.ports translate to one physical JVM?

Hi, Does anyone know the answer to this question? http://stackoverflow.com/questions/40031917/does-a-port-in-supervisor-slots-ports-translate-to-one-physical-jvm Thanks TI

[GitHub] storm pull request #1687: Apache master storm 1694 top storm 2097

Github user harshach commented on a diff in the pull request: https://github.com/apache/storm/pull/1687#discussion_r83286131 --- Diff: examples/storm-starter/src/jvm/org/apache/storm/starter/trident/TridentKafkaClientWordCountNamedTopics.java --- @@ -0,0 +1,122 @@ +/* + *

[GitHub] storm pull request #1687: Apache master storm 1694 top storm 2097

Github user harshach commented on a diff in the pull request: https://github.com/apache/storm/pull/1687#discussion_r83312306 --- Diff: external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/trident/KafkaTridentSpoutEmitter.java --- @@ -0,0 +1,187 @@ +/* +

[GitHub] storm pull request #1687: Apache master storm 1694 top storm 2097

Github user harshach commented on a diff in the pull request: https://github.com/apache/storm/pull/1687#discussion_r83285410 --- Diff: examples/storm-starter/src/jvm/org/apache/storm/starter/trident/DebugMemoryMapState.java --- @@ -0,0 +1,73 @@ +/* + * Licensed to the

[GitHub] storm pull request #1687: Apache master storm 1694 top storm 2097

Github user harshach commented on a diff in the pull request: https://github.com/apache/storm/pull/1687#discussion_r83312172 --- Diff: external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/trident/KafkaTridentSpoutBatchMetadata.java --- @@ -0,0 +1,83 @@ +/*

[GitHub] storm pull request #1687: Apache master storm 1694 top storm 2097

Github user harshach commented on a diff in the pull request: https://github.com/apache/storm/pull/1687#discussion_r83289318 --- Diff: examples/storm-starter/src/jvm/org/apache/storm/starter/trident/TridentKafkaClientWordCountNamedTopics.java --- @@ -0,0 +1,122 @@ +/* + *

[GitHub] storm pull request #1687: Apache master storm 1694 top storm 2097

Github user harshach commented on a diff in the pull request: https://github.com/apache/storm/pull/1687#discussion_r83290282 --- Diff: external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/trident/KafkaTridentSpoutEmitter.java --- @@ -0,0 +1,187 @@ +/* +

[GitHub] storm issue #1702: Update Eventhub-Client jar dependency to 1.0.1

Github user harshach commented on the issue: https://github.com/apache/storm/pull/1702 +1. @srdo do you have any further comments pending. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have

[GitHub] storm issue #1717: Update eventhub client dependency. Move Storm-Eventhubs d...

Github user harshach commented on the issue: https://github.com/apache/storm/pull/1717 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] storm pull request #1735: STORM-203 Adding paths to default java library pat...

GitHub user picadoh opened a pull request: https://github.com/apache/storm/pull/1735 STORM-203 Adding paths to default java library path Adding /usr/lib64 and /usr/lib/x86_64-linux-gnu to default java library path You can merge this pull request into a Git repository by running:

[GitHub] storm pull request #1733: [STORM-2134] - improving the current scheduling st...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1733 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] storm pull request #1687: Apache master storm 1694 top storm 2097

Github user harshach commented on a diff in the pull request: https://github.com/apache/storm/pull/1687#discussion_r83280245 --- Diff: examples/storm-starter/src/jvm/org/apache/storm/starter/trident/TridentKafkaClientWordCountWildcardTopics.java --- @@ -0,0 +1,51 @@ +/* +

Different way used to create file path in hdfs state

Hi, I was looking HdfsState class where createOutputFile api present at line 182 is as follows Path path = new Path(this.fileNameFormat.getPath(), this.fileNameFormat.getName(this.rotation, System.currentTimeMillis())); whereas there is another createOutputFile at line 272 line Path p = new

Re: Internal server error , "NimbusLeaderNotFoundException"

Did you run Nimbus process, or checked it's dead? You may want to check Nimbus's log and see what's happening. UI log can also give you the error information, like which Nimbus it tried to connect. - Jungtaek Lim (HeartSaVioR) 2016년 10월 13일 (목) 오후 8:18, Htet Myo Myint 님이

Re: Should nimbus.seeds always be refreshed in storm.yaml?

Storm finds leader Nimbus via connecting to known Nimbus and query, so it's safe unless all of Nimbus in nimbus.seeds are dead. But, AFAIK, runtime update of Nimbus seeds (via discovery) doesn't happen. (Anyone please correct me if I'm wrong.) Might be better to have it for H/A (run discovery for

Internal server error , "NimbusLeaderNotFoundException"

I got Internal server error , "NimbusLeaderNotFoundException" to be exact, when ":8080" is accessed. At first, I set up storm local mode by using tar and it worked well. After that, I build Storm from source , start processes and accessed UI, above error occurred. I revert some steps for local

Re: Should nimbus.seeds always be refreshed in storm.yaml?

Which version of Storm are you using? If you are using 1.x then you can use nimbus HA by configuring respective nimbus.hosts. Thanks, Satish. On Thu, Oct 13, 2016 at 11:56 AM, S G wrote: > Hi, > > We are setting up a storm cluster where a nimbus node would be >

Should nimbus.seeds always be refreshed in storm.yaml?

Hi, We are setting up a storm cluster where a nimbus node would be automatically added to the nimbus cluster if any nimbus machine fails. In such a scenario, the new nimbus node will have a different host-name/IP address. If that happens, is it absolutely mandatory for all the