[
https://issues.apache.org/jira/browse/HBASE-26953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534283#comment-17534283
]
Bryan Beaudreault commented on HBASE-26953:
-------------------------------------------
[~ayeshasilvia] sorry for the confusion. Yes, the exception includes the port
for us as well. In terms of hours to reproduce, you could potentially deploy
hbase with your own implementation of the pluggable RPC queue which always
calls call.drop(). Otherwise I think it would only happen if using the codel
queue, and only under high saturation.
I’m out of office not, so can’t give better suggestion until next week
> CallDroppedException message says "server 0.0.0.0 is overloaded"
> ----------------------------------------------------------------
>
> Key: HBASE-26953
> URL: https://issues.apache.org/jira/browse/HBASE-26953
> Project: HBase
> Issue Type: Bug
> Reporter: Bryan Beaudreault
> Assignee: Ayesha Mosaddeque
> Priority: Trivial
> Labels: newbie
>
> This is not a super useful error when seen on the client side. Maybe we can
> have it pull in the ServerName instead, or at the very least resolve to the
> hostname.
>
> https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/CallRunner.java#L213
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
