Github user aniketalhat commented on the issue:
https://github.com/apache/storm/pull/2066
@liu-zhaokun how did you manage to solve this? Currently new
storm-kafka-client isn't very stable and doesn't support the transactional
spout. I've to connect to Kafka (0.11.0.2) via. Kerberos
Github user liu-zhaokun commented on the issue:
https://github.com/apache/storm/pull/2066
@aniketalhat
You can look through my PRï¼and my intention was to export
java.security.auth.login.config=the path to your keytab,and it works.You can
try it.
---
Github user asfgit closed the pull request at:
https://github.com/apache/storm-site/pull/5
---
Github user srdo commented on the issue:
https://github.com/apache/storm-site/pull/5
Thanks for the reviews, I'll merge and push this to the site.
@erikdw I probably should have thought to include a screenshot, thanks :)
---
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/2674
---
GitHub user srdo opened a pull request:
https://github.com/apache/storm/pull/2676
STORM-3073: Uncap pendingEmits for bolt executors, and prevent LoadSpout
from overflowing pendingEmits in spout executors
https://issues.apache.org/jira/browse/STORM-3073
The first commit
Github user aniketalhat commented on the issue:
https://github.com/apache/storm/pull/2066
Hello Liu,
Thanks for your quick reply, my one concern is that your PR is for
storm-kafka-client(new consumer) where as I'm looking for storm-kafka(old
consumer) solution, what do
Github user srdo commented on a diff in the pull request:
https://github.com/apache/storm/pull/2669#discussion_r188377925
--- Diff: storm-client/src/jvm/org/apache/storm/messaging/IContext.java ---
@@ -38,6 +38,7 @@
/**
* This method establishes a server
Github user srdo commented on the issue:
https://github.com/apache/storm/pull/2669
As far as I can tell all connections are still being shut down with this
change. The connections cached by WorkerState are closed during worker shutdown
in
Github user pczb commented on a diff in the pull request:
https://github.com/apache/storm/pull/2669#discussion_r188355473
--- Diff: storm-client/src/jvm/org/apache/storm/messaging/netty/Client.java
---
@@ -451,7 +451,6 @@ public int getPort() {
public void close() {
Github user pczb commented on the issue:
https://github.com/apache/storm/pull/2669
@srdo add doc specification, i was wonder if we need remove synchronized
when bind port
@revans2 just as srdo says the connection will be closed by the worker
before worker shutdown.
i will
Github user Ethanlm commented on the issue:
https://github.com/apache/storm/pull/2677
There might be a bug in the code:
https://github.com/apache/storm/blob/master/storm-server/src/main/java/org/apache/storm/daemon/nimbus/Nimbus.java#L490-L497
```
if (leaderElector ==
Github user srdo commented on the issue:
https://github.com/apache/storm/pull/2673
Okay, pretty sure I've seen this break now. Ran the TVL topology and got
occasional worker crashes, e.g.
```
2018-05-15 16:36:01.018 o.a.s.m.n.StormClientHandler client-worker-1 [INFO]
Github user agresch commented on the issue:
https://github.com/apache/storm/pull/2677
@Ethanlm - I see tc being null whenever I start nimbus (at least with no
topologies).
---
GitHub user agresch opened a pull request:
https://github.com/apache/storm/pull/2677
STORM-3075 fix NPE
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agresch/storm agresch_storm-3075
Alternatively you can review and apply
Github user Ethanlm commented on the issue:
https://github.com/apache/storm/pull/2677
It looks reasonable. But would like to understand more about it. Could you
elaborate on in which case tc will be null?
---
Github user agresch commented on the issue:
https://github.com/apache/storm/pull/2677
@Ethanlm - nice catch. Will fix the source of the problem instead
---
Github user agresch commented on the issue:
https://github.com/apache/storm/pull/2677
@Ethanlm - please take a look. Thanks.
---
18 matches
Mail list logo
