Uploaded image for project: 'Samza'
  1. Samza
  2. SAMZA-1636

Disallow setting job.container.thread.pool.size value to 1

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      Setting job.container.thread.pool.size to 1 should make SamzaContainer ignore it and default to 0 instead. With a single processing thread, the extra latency of the message handoff is unnecessary overhead. 

      Configuration reference should also be updated to clarify the new behavior. We should also remove the following statement: "Note that the thread pool is not applicable to [sic] AsyncStremTask.processAsync(). ", since the thread pool size can still allow window/commit to proceed in parallel for AsyncStreamTask.

      xinyu, do you know of any use case where thread.pool.size == 1 is better than sync processing?

       

      Attachments

        Activity

          People

            xinyu Xinyu Liu
            pmaheshwari Prateek Maheshwari
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: