You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@kafka.apache.org by Peter Davis <da...@gmail.com> on 2016/05/13 00:01:20 UTC

Connect MemoryOffsetBackingStore creates a non-daemon thread, prevents clean shutdown

I'm having an issue running a Connect source worker running as a standalone
herder embedded in a webapp.  The webapp hangs on shutdown.

MemoryOffsetBackingStore creates an executor but doesn't call
ExecutorService.shutdown() on stop().

I'd like to contribute a pull request.  Question in the meantime: has
anyone else encountered this or know of a workaround?  My Source,
incidentally, does not use offsets, but there doesn't appear to be a way to
disable committing offsets.

-Peter

Re: Connect MemoryOffsetBackingStore creates a non-daemon thread, prevents clean shutdown

Posted by Peter Davis <da...@gmail.com>.
Created https://issues.apache.org/jira/browse/KAFKA-3710

Regards,

Peter Davis
(206) 713-7352
davispw@gmail.com



On Fri, May 13, 2016 at 7:02 AM, Peter Davis <da...@gmail.com> wrote:

> I tried. JIRA is locked down.
>
> -Peter
>
>
> > On May 12, 2016, at 18:14, Liquan Pei <li...@gmail.com> wrote:
> >
> > Hi Peter,
> >
> > That seems to be an issue. Do you want to file a JIRA on this?
> >
> > Thanks,
> > Liquan
> >
> >> On Thu, May 12, 2016 at 5:01 PM, Peter Davis <da...@gmail.com> wrote:
> >>
> >> I'm having an issue running a Connect source worker running as a
> standalone
> >> herder embedded in a webapp.  The webapp hangs on shutdown.
> >>
> >> MemoryOffsetBackingStore creates an executor but doesn't call
> >> ExecutorService.shutdown() on stop().
> >>
> >> I'd like to contribute a pull request.  Question in the meantime: has
> >> anyone else encountered this or know of a workaround?  My Source,
> >> incidentally, does not use offsets, but there doesn't appear to be a
> way to
> >> disable committing offsets.
> >>
> >> -Peter
> >
> >
> >
> > --
> > Liquan Pei
> > Software Engineer, Confluent Inc
>

Re: Connect MemoryOffsetBackingStore creates a non-daemon thread, prevents clean shutdown

Posted by Peter Davis <da...@gmail.com>.
I tried. JIRA is locked down. 

-Peter


> On May 12, 2016, at 18:14, Liquan Pei <li...@gmail.com> wrote:
> 
> Hi Peter,
> 
> That seems to be an issue. Do you want to file a JIRA on this?
> 
> Thanks,
> Liquan
> 
>> On Thu, May 12, 2016 at 5:01 PM, Peter Davis <da...@gmail.com> wrote:
>> 
>> I'm having an issue running a Connect source worker running as a standalone
>> herder embedded in a webapp.  The webapp hangs on shutdown.
>> 
>> MemoryOffsetBackingStore creates an executor but doesn't call
>> ExecutorService.shutdown() on stop().
>> 
>> I'd like to contribute a pull request.  Question in the meantime: has
>> anyone else encountered this or know of a workaround?  My Source,
>> incidentally, does not use offsets, but there doesn't appear to be a way to
>> disable committing offsets.
>> 
>> -Peter
> 
> 
> 
> -- 
> Liquan Pei
> Software Engineer, Confluent Inc

Re: Connect MemoryOffsetBackingStore creates a non-daemon thread, prevents clean shutdown

Posted by Liquan Pei <li...@gmail.com>.
Hi Peter,

That seems to be an issue. Do you want to file a JIRA on this?

Thanks,
Liquan

On Thu, May 12, 2016 at 5:01 PM, Peter Davis <da...@gmail.com> wrote:

> I'm having an issue running a Connect source worker running as a standalone
> herder embedded in a webapp.  The webapp hangs on shutdown.
>
> MemoryOffsetBackingStore creates an executor but doesn't call
> ExecutorService.shutdown() on stop().
>
> I'd like to contribute a pull request.  Question in the meantime: has
> anyone else encountered this or know of a workaround?  My Source,
> incidentally, does not use offsets, but there doesn't appear to be a way to
> disable committing offsets.
>
> -Peter
>



-- 
Liquan Pei
Software Engineer, Confluent Inc