You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Sriram Subramanian (JIRA)" <ji...@apache.org> on 2013/08/27 23:53:51 UTC

[jira] [Commented] (SAMZA-24) Support throttling in Samza

    [ https://issues.apache.org/jira/browse/SAMZA-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751770#comment-13751770 ] 

Sriram Subramanian commented on SAMZA-24:
-----------------------------------------

Here is my thought on this. We have a mechanism to schedule messages using the MessageChooser. It makes sense to implement throttling as one form of scheduling. This can be done either by using the Throttler instance that the ThrottleMessageChooser uses to throttle each stream partition or by using the metrics value. I see the benefit of using the metrics approach to throttle arbitrary parameters but it is safer to not expose that feature now without understanding how it would behave for different parameters. In the future, if we really need to support arbitrary throttling, we could make the metric type a config value that is used when the Picker is a ThrottleMessageChooser. 
                
> Support throttling in Samza
> ---------------------------
>
>                 Key: SAMZA-24
>                 URL: https://issues.apache.org/jira/browse/SAMZA-24
>             Project: Samza
>          Issue Type: Bug
>          Components: container
>    Affects Versions: 0.6.0
>            Reporter: Chris Riccomini
>
> We used to have Throttling in Samza, but we removed it in favor of CGroups and MessageChooser (SAMZA-2). There is still a demand for this feature, though.
> I've put up a design proposal at:
> https://wiki.apache.org/samza/Throttling
> Looking for thoughts and feedback.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira