[
https://issues.apache.org/jira/browse/KNOX-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Kumar M resolved KNOX-3507.
--------------------------------
Resolution: Fixed
PR has merged sucessfully
[https://github.com/apache/knox/pull/1443]
> Wire LivyHaDispatch for LIVYSERVER, LIVY_FOR_SPARK3, and LIVY_FOR_SPARK4
> ------------------------------------------------------------------------
>
> Key: KNOX-3507
> URL: https://issues.apache.org/jira/browse/KNOX-3507
> Project: Apache Knox
> Issue Type: Task
> Reporter: Arun Kumar M
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Summary
> -------
> Add baseline Livy HA dispatch wiring for LIVYSERVER, LIVY_FOR_SPARK3, and
> LIVY_FOR_SPARK4.
> This is a follow-up to KNOX-3472 / apache/knox#1411 and KNOX-3473 /
> apache/knox#1412, which introduced the Livy for Spark 3 and Livy for Spark 4
> service definitions. Those changes left the Livy services on
> LivyDispatch-only wiring and did not connect the Knox HA dispatch path for
> Livy roles.
> Problem
> -------
> The LIVYSERVER, LIVY_FOR_SPARK3, and LIVY_FOR_SPARK4 service descriptors
> reference org.apache.knox.gateway.livy.LivyDispatch without ha-classname
> wiring to org.apache.knox.gateway.ha.dispatch.LivyHaDispatch.
> For deployments that enable Knox HA for Livy, that gap means Livy-specific HA
> behavior is not consistently applied (including Livy batch/session POST
> handling via LivyHttpServletRequest and Livy HA failover handling such as
> HTTP 307), compared to the established HA dispatch pattern used for Livy
> elsewhere in Knox.
> Scope / proposed fix
> --------------------
> - Introduce baseline LivyHaDispatch (HA dispatch + Livy-specific request
> handling hooks).
> - Extract LivyHttpServletRequest for reuse from both LivyDispatch and
> LivyHaDispatch.
> - Add gateway-service-livy as a dependency of gateway-provider-ha where
> required for compilation/wiring.
> - Set ha-classname on:
> - services/livy/0.4.0/service.xml (LIVYSERVER)
> - services/livy_for_spark3/0.6.0/service.xml (LIVY_FOR_SPARK3)
> - services/livy_for_spark4/1.0.0/service.xml (LIVY_FOR_SPARK4)
> Relationship to KNOX-3479
> -------------------------
> This work is prerequisite baseline wiring for per-instance HA routing tracked
> under KNOX-3479 / apache/knox#1420. Keep per-instance routing / homepage
> “?host=” behavior out of this change.
> Out of scope
> ------------
> - Per-instance HA routing, sticky cookies, Referer-based routing (KNOX-3479)
> - Knox Homepage tile JavaScript changes (KNOX-3479)
> - New service definition versions beyond what is required for ha-classname
> wiring
> Acceptance criteria
> -----------------
> - LivyHaDispatch exists with baseline Livy HA behavior expected from
> ConfigurableHADispatch + Livy-specific overrides (including HTTP 307 handling
> path consistent with existing Knox HA patterns).
> - LivyHttpServletRequest is shared by LivyDispatch and LivyHaDispatch.
> - ha-classname is set for all three Livy roles listed above.
> - mvn -pl
> gateway-service-livy,gateway-provider-ha,gateway-service-definitions -am test
> -DskipITs passes.
> Implementation
> --------------
> GitHub: apache/knox#1443
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
