I installed Spark and able to run Spark jobs.
however I can't access the spark history server.
when I start it, I can see the service is running:
services running
but after few seconds the service is gone.
trying to access the web ui in port 18080 returning "site can't be reached"
Related
I have to restart a deployed app when one node in the cluster(2 nodes Active/Passive) goes down, how do I handle a node failure and then restart the app?
I'm using mod_cluster for hot_standby and load balancing.
You cannot restart the application server from the balancer if that is what you are trying to do?
If your App has crashed or become undeployed you could have a crontask that runs on the server and checks the status of the App
If you are hosting in a cloud environment (eg. AWS) you could use the EC2 API's to reboot any instances that have become unresponsive from the balancer
The error I am getting after running kubectl cluster-info
Kubernetes master is running at https://xxx-xxx-aks-yyyy.hcp.westeurope.azmk8s.io:443
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
Unable to connect to the server: net/http: TLS handshake timeout
Rifats-MacBook-Pro:~ rifaterdemsahin$ kubectl cluster-info
There is some issue on Azure Server. Please refer to this similar issue.
I suggest you could try again, if it still does not work, you could open a ticket or give feedback to Azure.
The solution to this one for me was to scale the nodes in my Cluster from the Azure Kubernetes service blade web console (NOT your local terminal since you can't connect with kubectl).
After scaling up by one (and back down to save costs) I am back working again.
Workaround / Solution
Log into the Azure Console — Kubernetes Service blade.
Scale your cluster up by 1 node.
Wait for scale to complete and attempt to connect (you should be able to).
Scale your cluster back down to the normal size to avoid cost increases.
Total time it took me ~2 mins.
More Background Info on the Issue
Added this to the full ticket description write up that I posted over here (if you want more info have a read):
'Unable to connect Net/http: TLS handshake timeout' — Why can't Kubectl connect to Azure AKS server?
Looking to interact with the traditional Spark Web GUI on default clusters in Dataproc.
This can be done by creating a SSH tunnel to the Dataproc master node. By using a SOCKS proxy you can then access all the applications running on YARN including your Spark sessions.
This guide will walk you through in detail:
Dataproc Cluster web interfaces
Does anyone know why we are experiencing on our kubernetes master node some system load peaks. I thought that the master node is not doing anything except monitoring our agent nodes.
Each time we have a system load peak of 1.8-2 on our dual-core machine, I see in the kube-controller-manager log that the master tries to start 3 things:
controllermanager.go:373] Attempting to start disruption controller
controllermanager.go:385] Attempting to start petset
controllermanager.go:460] Attempting to start certificates
Our kubernetes version is 1.4.6 and is created via the azure portal. The system peaks can we see via datadog monitoring.
I've installed SQL 2012 in Sharepoint Integrated Mode and have Sharepoint 2010 installed on a different server. In Central Administration I have added a SQL Server Reporting Services Service Application and proxy. This all appears to have worked (the RS databases were created).
The problem is I cannot finish the configuration as I need the report server URL. Upon researching I found that this would be "http://myspserver/_vti_bin/reportserver" however this does not connect. I have looked at the rsreportserver.config file and where the URL should be is just
<ReportServerUrl>
</ReportServerUrl>
Upon looking at the at the service applications list I have noticed that the SQL Server Reporting Services Service Application is stopped. This might be why I can't connect to the URL so I tried stopping and restarting the SQL Server Reporting Services Service and although this was successful it made no difference to the state of the service application.
How to get this setup sorted out?