Member since
08-19-2017
13
Posts
1
Kudos Received
0
Solutions
05-08-2019
06:42 PM
1 Kudo
Running over a public IP may not be a good idea if it is open to the internet. Consider using a VPC? That said, you can point HBase Master and RegionServer to use the address from a specific interface name (eth0, eth1, etc.) and/or a specific DNS resolver (IP or name that can answer to a dns:// resolving call) via advanced config properties: hbase.master.dns.interface hbase.master.dns.nameserver hbase.regionserver.dns.interface hbase.regionserver.dns.nameserver By default the services will use whatever is the host's default name and resolving address: getent hosts $(hostname -f) and publish this to clients.
... View more
03-17-2019
04:18 AM
I submitted KNOX-1828 for this issue and have created a pull request for a patch that appears to work.
... View more
10-18-2018
03:22 PM
@Charles Bernard's suggestion solved it for me.
... View more
09-28-2018
03:28 PM
The article is very general and doe not provide concrete and specific backup & recovery tools.
... View more
02-10-2019
08:57 PM
I had the same problem happen more than once on different clusters from different sites and networks configurations (with or without proxy/gateway/knox, company network, wifi router, home ISP, public wifi...). With various results It concerned the display of the notes themselves and the welcome page also (sometimes only the notes, the welcome page was ok) Some browser settings block websockets for security reasons. So be aware of that. Sometimes, it can be a firewall issue. Last occurence happened to require a clearing of the outputs of the notes. I was working on a note including a spark job that took ages and the progress bar froze. I restarted zeppelin, Spark, Yarn, nothing seemed to fix it. The note seemed "lost", undisplayable, desperately blank. My fix (after a couple of hours trying to figure what the hell was causing that) was to Hover over the note in the welcome page, and click the rubber, "clear output"... and voila,I was able to open my note again. Note That this has to be done after a restart of the Zeppelin service. Just for note (no pun intented) when I explored the browser prior the fix the websocket kept trying to load content from the server but nothing came out.
... View more