-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sparklint UI does not come up #66
Comments
I have a spark streaming job with 10 sec micro batch. My sparkling UI does not show up. Logs show that connection is accepted still no response. Do I have to put additional config for streaming job? |
Hi, I am also facing the same issue as sparkuser3. The SparkLint UI does not comes up even when the job is running, but I can see the below message in the logs. Am I missing any configuration here? INFO nio1.NIO1SocketServerGroup: Service bound to address /0:0:0:0:0:0:0:0:23763 Thanks |
What platform are you running the application on? |
Thanks Max for getting back. I am using it on a cloudera hadoop platform (cdh 15.5). Regards |
Hi! We used it on a hortonworks hadoop platform and to view the UI we had to port forward the required port. This could be a similar issue you are facing |
Hi Max, This is on a single server, so I am not sure port forwarding is required here. Did you make any other configuration changes or anything in setup? tcp6 0 0 :::23763 :::* LISTEN 61356/java |
Hi ,
Tried the instruction provided in https://github.com/groupon/sparklint . When I do a spark submit I do see the logs which says the below . But when I hit the driver IP with port I cannot see the UI. Could you please help me . Are there any additional configs to be applied ?
Logs
17/08/17 14:30:16 INFO nio1.NIO1SocketServerGroup: Service bound to address /0:0:0:0:0:0:0:0:23763
17/08/17 14:30:16 INFO sparklint.Sparklint: Server started on 23763
17/08/17 14:30:16 INFO spark.SparkContext: Registered listener com.groupon.sparklint.SparklintListener
The text was updated successfully, but these errors were encountered: