Known Issues in Apache Knox

Known issues and technical limitations for Apache Knox are addressed in Cloudera Runtime 7.3.3.

Known Issues identified in Cloudera Runtime 7.3.3

CDPD-126571: JDBCTokenStateService fails to initialize on PostgreSQL when multiple Knox instances start at the same time
7.3.3
In a Knox high availability deployment that uses PostgreSQL, JDBCTokenStateService can fail to initialize when multiple Knox Gateway instances start at the same time against an empty database. Startup fails with an error similar to the following:
PSQLException: ERROR: duplicate key value violates unique constraint "pg_type_typname_nsp_index"
Detail: Key (typname, typnamespace)=(knox_tokens, 2200) already exists.
Restart the Knox service on the host where startup failed. The KNOX_TOKENS and KNOX_TOKEN_METADATA tables already exist, so the service starts normally. To avoid the issue on the first startup, start Knox on one host at a time, or create the KNOX_TOKENS and KNOX_TOKEN_METADATA tables before you start Knox.
Apache JIRA: KNOX-3536

Known Issues identified before Cloudera Runtime 7.3.3

Known issues identified before Cloudera Runtime 7.3.3 include only unresolved issues from previous releases that continue to affect the Cloudera Runtime 7.3.3 base release.

CDPD-104007: Tokens on Knox Token Management page might intermittently fail to display
7.3.3, 7.3.2.100 CHF 1 and higher
Tokens created under the Knox Token Management page might intermittently fail to display. The issue occurs randomly upon refreshing the page, where the underlying API call to retrieve user tokens is not triggered, causing the page to appear empty.
Refresh the page again until the tokens are displayed.
CDPD-71305: Concurrent impala shell connection failure
7.3.3, 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and CHFs, 7.1.9 SP1 and its CHFs
If a user makes a concurrent impala-shell connection through Knox, then the connection fails.
Use only one Knox role.
CDPD-64652: During CDH + OS rolling upgrade knox admin api access fails with 403 ACL authorization failures
7.3.3, 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and CHFs, 7.2.18 and its Service Packs
During OS upgrades, attempts to access Knox on the host being upgraded may produce occasional 403 HTTP responses.
Since the cause is the unavailability of underlying OS service(s), wait and retry the failed request(s).
CDPD-60376: Cloud loadbalancer takes 20-30 secs to failover to the next available knox host
7.3.3, 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and CHFs, 7.2.18 and its Service Packs
If Knox is in HA and one of the Knox server is down, then accessing of service via Control plane endpoint url(i.e. via cloud loadbalancer) will take ~ 30secs to failover the request to available knox instance.
Retry the request after 30 seconds.
CDPD-3125: Logging out of Atlas does not manage the external authentication
7.3.3, 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and CHFs, 7.2.18, 7.1.9
At this time, Atlas does not communicate a log-out event with the external authentication management, Apache Knox. When you log out of Atlas, you can still open the instance of Atlas from the same web browser without re-authentication.
To prevent additional access to Atlas, close all browser windows and exit the browser.
CDPD-84236: Token generated by one Knox host fails with Unknown token error on another Knox host in Data Engineering High Availability clusters
7.3.3, 7.3.2 and its SPs and CHFs, 7.3.1.400 through 7.3.1.700
In Data Engineering High Availability clusters, a token generated by one Knox host may fail with an Unknown token error when accessed through another Knox host. This issue occurs due to a race condition in the PostgreSQL database, which prevents one of the Knox instances from properly initializing its configured token state service.
Restart Knox on all hosts.