You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Yi Pan (Data Infrastructure) (JIRA)" <ji...@apache.org> on 2015/07/29 01:52:04 UTC

[jira] [Created] (SAMZA-744) Samza shutdown sequence throws exception

Yi Pan (Data Infrastructure) created SAMZA-744:
--------------------------------------------------

             Summary: Samza shutdown sequence throws exception
                 Key: SAMZA-744
                 URL: https://issues.apache.org/jira/browse/SAMZA-744
             Project: Samza
          Issue Type: Bug
    Affects Versions: 0.10.0, 0.9.1
            Reporter: Yi Pan (Data Infrastructure)


The current shutdown sequence has a problematic sequence for changelog attached stores:

{code}
    } finally {
      info("Shutting down.")

      shutdownConsumers
      shutdownTask
      shutdownProducers
      shutdownStores
      shutdownLocalityManager
      shutdownOffsetManager
      shutdownMetrics

      info("Shutdown complete.")
    }
{code}

If the KV-stores has pending writes in cache and a changelog attached, shutdownStores will try to flush the store, which results in invoking producer.send(). However, the producers are already shutdown according to the above sequence. We need to move the shutdownProducers later than any shutdown procedure that would possibly flushing out pending writes to the system streams.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)