streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Ebanks <ryaneba...@gmail.com>
Subject Re: Bug in StreamsPersistWriterTask and StreamsProcessorTask. BREAKS LOCAL RUNTIME
Date Thu, 15 May 2014 15:19:19 GMT
Actually it should not be, !this.inQueue.isEmpty().  It should be, datum !=
null


On Wed, May 14, 2014 at 5:19 PM, Ryan Ebanks <ryanebanks@gmail.com> wrote:

> I can't seem to log into Jira at the moment create the bug ticket.  But
> this bug breaks the local runtime.
>
> A recent commit seems to have introduced this.  Its a simple fix, but the
> while statement on line 70 of StreamsProviderTask should read
> while(this.keepRunning.get() || !this.inQueue.isEmpty()) {
>
> And line 75 in StreamsPersist writer task should read
> while(this.keepRunning.get() || !this.inQueue.isEmpty()) {
>
>
> Both lines are missing the !this.inQueue.isEmpty() statement.  This causes
> tasks to be shutdown before data is processed and data is orphaned in the
> stream.  In the worst case only the provider runs.
>
> -Ryan Ebanks
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message