Re: Display ackers executors

[Alessio Pagliari]

Thank you Ethan, I totally missed that button. 

Is there also a way to retrieve information about ‘__acker’ through REST APIs, 
like any other component of the topology? Calling 
http://localhost:8080/api/v1/topology/my-topology-id/component/__acker 
 
doesn’t give me the same output as other components.

Cheers,

Alessio


> On 19 Jul 2018, at 18:20, Ethan Li  wrote:
> 
> At the bottom of the topology page, you can find “Show System Stats” button. 
> Click on it and you will see __acker.
> 
> Best,
> Ethan
> 
>> On Jul 19, 2018, at 11:04 AM, Alessio Pagliari  wrote:
>> 
>> Hello everybody,
>> 
>> I cannot find a way to show in the UI or retrieve through REST APIs the 
>> placement of the acker executors. Is there a way to get this information? I 
>> remember that in some topologies in the past I was able to see them in the 
>> UI with the name ‘__acker’, but now I can’t understand how to display them 
>> again.
>> 
>> Thank you,
>> 
>> Alessio
>> 
> 

Re: Display ackers executors

[Ethan Li]

At the bottom of the topology page, you can find “Show System Stats” button. 
Click on it and you will see __acker.

Best,
Ethan

> On Jul 19, 2018, at 11:04 AM, Alessio Pagliari  wrote:
> 
> Hello everybody,
> 
> I cannot find a way to show in the UI or retrieve through REST APIs the 
> placement of the acker executors. Is there a way to get this information? I 
> remember that in some topologies in the past I was able to see them in the UI 
> with the name ‘__acker’, but now I can’t understand how to display them again.
> 
> Thank you,
> 
> Alessio
> 

Display ackers executors

[Alessio Pagliari]

Hello everybody,

I cannot find a way to show in the UI or retrieve through REST APIs the 
placement of the acker executors. Is there a way to get this information? I 
remember that in some topologies in the past I was able to see them in the UI 
with the name ‘__acker’, but now I can’t understand how to display them again.

Thank you,

Alessio

Rest api hangs when one of HA Nimbus nodes is down

[Łukasz Gebel]

Hi Storm users,

I encountered strange behavior of my storm cluster. When one of Nimbuses is
down (the second one is working correctly) the healthy Nimbus seems to work
ok (getting leadership if it was a follower etc.) however Rest API and
probably Nimbus doesn't work correctly. Getting response from Rest API
takes a couple of seconds (e.g. http://localhost:8080/api/v1/nimbus/summary
).

Nimbus logs looks ok, however ui log is like that (this logs appears in
loop until the second Nimbus machine is up):

A lot of: 018-07-19 13:13:55.580
o.a.s.u.StormBoundedExponentialBackoffRetry [WARN] WILL SLEEP FOR 2001ms
(NOT MAX)

and:

2018-07-19 13:13:55.620 o.a.s.u.NimbusClient [WARN] Ignoring exception
while trying to get leader nimbus info from 10.0.5.2. will retry with a
different seed host.
java.lang.RuntimeException: java.lang.RuntimeException:
org.apache.storm.thrift.transport.TTransportException:
java.net.ConnectException: Connection refused (Connection refused)
at
org.apache.storm.security.auth.ThriftClient.reconnect(ThriftClient.java:112)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.security.auth.ThriftClient.(ThriftClient.java:73)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.utils.NimbusClient.(NimbusClient.java:136)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.utils.NimbusClient.getConfiguredClientAs(NimbusClient.java:92)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.utils.NimbusClient.getConfiguredClientAs(NimbusClient.java:66)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.ui.core$all_topologies_summary.invoke(core.clj:509)
~[storm-core-1.2.2.jar:1.2.2]
at org.apache.storm.ui.core$fn__8445.invoke(core.clj:1144)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.compojure.core$make_route$fn__3195.invoke(core.clj:100)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.compojure.core$if_route$fn__3183.invoke(core.clj:46)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.compojure.core$if_method$fn__3176.invoke(core.clj:31)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.compojure.core$routing$fn__3201.invoke(core.clj:113)
~[storm-core-1.2.2.jar:1.2.2]
at clojure.core$some.invoke(core.clj:2570) ~[clojure-1.7.0.jar:?]
at
org.apache.storm.shade.compojure.core$routing.doInvoke(core.clj:113)
~[storm-core-1.2.2.jar:1.2.2]
at clojure.lang.RestFn.applyTo(RestFn.java:139)
~[clojure-1.7.0.jar:?]
at clojure.core$apply.invoke(core.clj:632) ~[clojure-1.7.0.jar:?]
at
org.apache.storm.shade.compojure.core$routes$fn__3205.invoke(core.clj:118)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.ring.middleware.cors$wrap_cors$fn__7765.invoke(cors.clj:149)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.ring.middleware.json$wrap_json_params$fn__7712.invoke(json.clj:56)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.ring.middleware.multipart_params$wrap_multipart_params$fn__4416.invoke(multipart_params.clj:118)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.ring.middleware.reload$wrap_reload$fn__7241.invoke(reload.clj:22)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.ui.helpers$requests_middleware$fn__4669.invoke(helpers.clj:52)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.ui.core$catch_errors$fn__8632.invoke(core.clj:1428)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.ring.middleware.keyword_params$wrap_keyword_params$fn__4336.invoke(keyword_params.clj:35)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.ring.middleware.nested_params$wrap_nested_params$fn__4379.invoke(nested_params.clj:84)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.ring.middleware.params$wrap_params$fn__4308.invoke(params.clj:64)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.ring.middleware.multipart_params$wrap_multipart_params$fn__4416.invoke(multipart_params.clj:118)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.ring.middleware.flash$wrap_flash$fn__4631.invoke(flash.clj:35)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.ring.middleware.session$wrap_session$fn__4617.invoke(session.clj:98)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.ring.middleware.session$wrap_session$fn__4617.invoke(session.clj:98)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.ring.util.servlet$make_service_method$fn__4166.invoke(servlet.clj:127)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.ring.util.servlet$servlet$fn__4170.invoke(servlet.clj:136)
~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.ring.util.servlet.proxy$javax.servlet.http.HttpServlet$ff19274a.service(Unknown
Source) ~[storm-core-1.2.2.jar:1.2.2]
at
org.apache.storm.shade.org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:654)
~[storm-core-1.2.2.jar:1.2.2]
at

UNSUBSCRIBE

[Sidhant Goyal]