Skip to content

Conversation

@jdye64
Copy link
Contributor

@jdye64 jdye64 commented Apr 22, 2016

Expose BackPressureObjectThreshold and BackPressureDataSizeThreshold to
ConnectionStatus

Expose BackPressureObjectThreshold and BackPressureDataSizeThreshold to
ConnectionStatus
@aperepel
Copy link
Contributor

I wonder if, upon crossing a threshold, we should raise a bulletin maybe?

@jdye64
Copy link
Contributor Author

jdye64 commented Apr 22, 2016

@aperepel that isn't a bad idea. That takes a little more discussion around how often we continue to post that bulletin if the threshold is constantly exceeded, what severity, etc

@jdye64
Copy link
Contributor Author

jdye64 commented Apr 22, 2016

It might make more sense to leave those sort of operations to a ReportingTask however? Does anyone have any thoughts around that?

@apiri
Copy link
Member

apiri commented Apr 23, 2016

I like the ReportingTask path.

@markap14
Copy link
Contributor

We have talked before about having some sort of icon on a connection that indicates that back pressure is configured and then some sort of indicator that back pressure is applied. Perhaps an icon on the connection that is grey when configured but the threshold is not met, and then it would turn red or something if backpressure is actively being applied. The only issue with this approach is that we always have more & more things that we want to show and we have to balance what to show vs. how much screen real estate should be used. I am hoping that the UI redesign going on for 1.0 will make this work much better.

@aperepel
Copy link
Contributor

aperepel commented Apr 28, 2016

@markap14 don't show more, change how things are shown. in case of a connection and backpressure a simple gradient change in color (or a binary ok/throttled color) of the block is all it takes, IMO.

@apiri
Copy link
Member

apiri commented Jun 19, 2016

@jdye64 Apologies for delays. These changes look fine and everything builds fine. As far as the other commentary on this thread, I will leave that to folks to generate other issues to track, but these changes should certainly help as a means for any of those enhancements.

@asfgit asfgit closed this in 406d8a1 Jun 19, 2016
asfgit pushed a commit that referenced this pull request Jun 19, 2016
Expose BackPressureObjectThreshold and BackPressureDataSizeThreshold to
ConnectionStatus

This closes #377.

Signed-off-by: Aldrin Piri <aldrin@apache.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants