Member since
09-15-2021
2
Posts
0
Kudos Received
0
Solutions
01-06-2022
05:51 AM
This appears to be the cause. Switching to MS Edge avoided the HSTS feature in Chrome. Will look at enabling HTTPS on all UIs though since that is the correct solution in the longterm (spark.ssl.historyServer.enabled option is currently set to false ).
... View more
01-06-2022
03:51 AM
Accessing the URL on port 18088 returns a ERR_SSL_PROTOCOL_ERROR error in Chrome. history server logs have the following: 11:25:29.130 AM WARN HttpParser
Illegal character 0x16 in state=START for buffer HeapByteBuffer@1af6bd16[p=1,l=517,c=8192,r=516]={\x16<<< ...}
11:25:29.130 AM WARN HttpParser
Illegal character 0x16 in state=START for buffer HeapByteBuffer@21158554[p=1,l=517,c=8192,r=516]={\x16<<< ...}
11:25:29.130 AM WARN HttpParser
bad HTTP parsed: 400 Illegal character 0x16 for HttpChannelOverHttp@2390a367{r=0,c=false,a=IDLE,uri=null}
11:25:29.131 AM WARN HttpParser
bad HTTP parsed: 400 Illegal character 0x16 for HttpChannelOverHttp@7843db5f{r=0,c=false,a=IDLE,uri=null} Note: some lines truncated to avoid exposing data. There was a similar post regarding Schema Registry UI in Ambari but the solution doesn't appear to be applicable here (though I suspect the issue is similar). Any thoughts?
... View more
Labels:
- Labels:
-
Apache Spark