Re: Storm using Kafka Spout gives error: IllegalStateException

2018-12-12 Thread saurabh mimani
Hey Stig, Thanks for looking into this and providing a fix. We have build the storm-kafka-client jar from your branch and it is working fine on that. We are still testing it and will let you know if there are any issues we fix. I see for STORM-3301

UNSUBSCRIBE

2018-12-12 Thread Ramiro Rivera

Re: UNSUBSCRIBE

2018-12-12 Thread Obaid UrRehman
Unsubscribe On Wed, Dec 12, 2018, 21:53 niloofar zarif wrote: > UNSUBSCRIBE > > On Thu, 13 Dec 2018, 00:16 Thomas Chang, wrote: > >> UNSUBSCRIBE >> >> On Sun, Dec 9, 2018 at 5:07 AM Xiang Wang wrote: >> >>> -- Regards, Obaid Ur Rehman

unsubscribe

2018-12-12 Thread Narayanan P S
-- *Regards,* *Narayanan PS* *SDE2 | Search | Ingestion*

unsubscribe

2018-12-12 Thread Shubham Gupta
unsubscribe

unsubscribe

2018-12-12 Thread Michaël Melchiore
unsubscribe

Re: UNSUBSCRIBE

2018-12-12 Thread niloofar zarif
UNSUBSCRIBE On Thu, 13 Dec 2018, 00:16 Thomas Chang, wrote: > UNSUBSCRIBE > > On Sun, Dec 9, 2018 at 5:07 AM Xiang Wang wrote: > >>

UNSUBSCRIBE

2018-12-12 Thread Nithin Uppalapati

Re: UNSUBSCRIBE

2018-12-12 Thread Thomas Chang
UNSUBSCRIBE On Sun, Dec 9, 2018 at 5:07 AM Xiang Wang wrote: >

Re: Disruptor Queue flush behaviour

2018-12-12 Thread Roshan Naik
 There is a detailed diagram of both the 1.x and 2.x messaging internals ...  starting at slide  11 over here:  https://www.slideshare.net/Hadoop_Summit/next-generation-execution-for-apache-storm The flusher threads shown in 1.x there should be in a thread pool .. as Bobby described earlier.

Unsubscribe messages?

2018-12-12 Thread Steve Miller
It’d be really nice if whatever mailing-list maintenance software this list is using would look for messages with a single-word body of un-subscribing (deliberately not spelling that correctly so I don’t trip people’s mail filters) and toss them. I know support for this has existed since

Storm UI Assigned Mem

2018-12-12 Thread Jonas Krauss
Hi all, we are currently using storm 1.2.2 together with zookeeper 3.4.11. The value for assigned mem per topology in the storm ui under topology summary always displays 65, even though we assign xmx4096m by default through the storm.yaml. The workers are correctly started with -xmx4096m though.

Re: Disruptor Queue flush behaviour

2018-12-12 Thread Thomas Cooper (PGR)
Bobby, Thank you for such a detailed reply. It was really useful. I was wondering if you could confirm a few final details for me? (This is for Storm version 1.2.2) 1) My first question is about the worker process local transfer function (defined in

unsubscribe

2018-12-12 Thread Akshay Madhuranath
unsubscribe Thanks, Akshay

unsubscribe

2018-12-12 Thread Rahul Jeevanandam
unsubscribe Regards, Rahul 'This e-mail may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it permanently.'