[
https://issues.apache.org/jira/browse/HBASE-28489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17834767#comment-17834767
]
Istvan Toth commented on HBASE-28489:
-------------------------------------
For SPENGO (which is the performance critical case), the best solution would be
to use Jetty's ConfigurableSpnegoLoginService.
However it seems that we are currently using Hadoop's Kerberos implementation
which relies on the standard Servlet API.
> Implement HTTP session support in REST server and client
> --------------------------------------------------------
>
> Key: HBASE-28489
> URL: https://issues.apache.org/jira/browse/HBASE-28489
> Project: HBase
> Issue Type: Improvement
> Components: REST
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> The REST server (and java client) currently does not implement sessions.
> While is not necessary for the REST API to work, implementing sessions would
> be a big improvement in throughput and resource usage.
> * It would make load balancing with sticky sessions possible
> * It would save the overhead of performing authentication for each request
> The gains are particularly big when using SPENGO:
> * The full SPENGO handshake can be skipped for subsequent requests
> * When Knox performs SPENGO authentication for the proxied client, it access
> the identity store each time. When the session is set, this step is only
> perfomed on the initial request.
> The same change has resulted in spectacular performance improvements for
> Phoenix Query Server when implemented in Avatica.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
