[
https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969204#comment-15969204
]
Rajeshbabu Chintaguntla edited comment on PHOENIX-3360 at 4/14/17 4:05 PM:
---------------------------------------------------------------------------
Yes [~jamestaylor] we have observed index updates and meta updates are going
with higher priority in case of RS->RS.
||Count||Queue||Priority||Method||Server||
|8000|Delegate|0|ExecService|1|
|4|Delegate|0|GetRegionInfo|1|
|1000|Delegate|0|Multi|1|
|1|Delegate|0|OpenRegion|1|
|2|Delegate|0|Scan|1|
|1|Delegate|200|Scan|1|
|5000|Index|1000|Multi|1|
|7006|Delegate|0|ExecService|2|
|6|Delegate|0|GetRegionInfo|2|
|1000|Delegate|0|Multi|2|
|2|Delegate|0|OpenRegion|2|
|46|Delegate|0|Scan|2|
|22|Delegate|200|Multi|2|
|74|Delegate|200|Scan|2|
|5000|Index|1000|Multi|2|
|5|Metadata|2000|ExecService|2|
|5|Metadata|2000|Multi|2|
|5|Metadata|2000|Scan|2|
|6000|Delegate|0|ExecService|3|
|7|Delegate|0|GetRegionInfo|3|
|1000|Delegate|0|Multi|3|
|1|Delegate|0|OpenRegion|3|
|2|Delegate|0|Scan|3|
|2|Delegate|200|Get|3|
|1|Delegate|200|Scan|3|
|6000|Index|1000|Multi|3|
These are the numbers in handy right now. Credit to [~elserj] for collecting
the same.
was (Author: rajeshbabu):
Yes [~jamestaylor] we have observed index updates and meta updates are going
with higher priority in case of RS->RS.
||Count||Queue||Priority||Method||Server||
|8000|Delegate|0|ExecService|1|
|4|Delegate|0|GetRegionInfo|1|
|1000|Delegate|0|Multi|1|
|1|Delegate|0|OpenRegion|1|
|2|Delegate|0|Scan|1|
|1|Delegate|200|Scan|1|
|5000|Index|1000|Multi|1|
|7006|Delegate|0|ExecService|2|
|6|Delegate|0|GetRegionInfo|2|
|1000|Delegate|0|Multi|2|
|2|Delegate|0|OpenRegion|2|
|46|Delegate|0|Scan|2|
|22|Delegate|200|Multi|2|
|74|Delegate|200|Scan|2|
|5000|Index|1000|Multi|2|
|5|Metadata|2000|ExecService|2|
|5|Metadata|2000|Multi|2|
|5|Metadata|2000|Scan|2|
|6000|Delegate|0|ExecService|3|
|7|Delegate|0|GetRegionInfo|3|
|1000|Delegate|0|Multi|3|
|1|Delegate|0|OpenRegion|3|
|2|Delegate|0|Scan|3|
|2|Delegate|200|Get|3|
|1|Delegate|200|Scan|3|
|6000|Index|1000|Multi|3|
Credit to [~elserj] which are in handy with me right now.
> Secondary index configuration is wrong
> --------------------------------------
>
> Key: PHOENIX-3360
> URL: https://issues.apache.org/jira/browse/PHOENIX-3360
> Project: Phoenix
> Issue Type: Bug
> Reporter: Enis Soztutar
> Assignee: William Yang
> Priority: Critical
> Fix For: 4.10.0
>
> Attachments: ConfCP.java, indexlogging.patch, PHOENIX-3360.patch,
> PHOENIX-3360-v2.PATCH, PHOENIX-3360-v3.PATCH, PHOENIX-3360-v4.PATCH
>
>
> IndexRpcScheduler allocates some handler threads and uses a higher priority
> for RPCs. The corresponding IndexRpcController is not used by default as it
> is, but used through ServerRpcControllerFactory that we configure from Ambari
> by default which sets the priority of the outgoing RPCs to either metadata
> priority, or the index priority.
> However, after reading code of IndexRpcController / ServerRpcController it
> seems that the IndexRPCController DOES NOT look at whether the outgoing RPC
> is for an Index table or not. It just sets ALL rpc priorities to be the index
> priority. The intention seems to be the case that ONLY on servers, we
> configure ServerRpcControllerFactory, and with clients we NEVER configure
> ServerRpcControllerFactory, but instead use ClientRpcControllerFactory. We
> configure ServerRpcControllerFactory from Ambari, which in affect makes it so
> that ALL rpcs from Phoenix are only handled by the index handlers by default.
> It means all deadlock cases are still there.
> The documentation in https://phoenix.apache.org/secondary_indexing.html is
> also wrong in this sense. It does not talk about server side / client side.
> Plus this way of configuring different values is not how HBase configuration
> is deployed. We cannot have the configuration show the
> ServerRpcControllerFactory even only for server nodes, because the clients
> running on those nodes will also see the wrong values.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
