Re: [build system] UPS failure in Soda Hall took down jenkins' reverse proxy

...and we're back! On Wed, Dec 20, 2017 at 7:51 PM, shane knapp wrote: > the build system is up, but you can't reach it through normal channels ( > amplab.cs.berkeley.edu/jenkins or rise.cs.berkeley.edu/jenkins) as the > machine hosting the reverse proxy is down due to a

[build system] UPS failure in Soda Hall took down jenkins' reverse proxy

the build system is up, but you can't reach it through normal channels ( amplab.cs.berkeley.edu/jenkins or rise.cs.berkeley.edu/jenkins) as the machine hosting the reverse proxy is down due to a UPS fault during normal maintenance... machines are coming up now, and we should have network

Re: Timeline for Spark 2.3

+1 I think the earlier we cut a branch the better. From: Michael Armbrust Sent: Tuesday, December 19, 2017 4:41:44 PM To: Holden Karau Cc: Sameer Agarwal; Erik Erlandson; dev Subject: Re: Timeline for Spark 2.3 Do people really need to be

ERROR executor.CoarseGrainedExecutorBackend: RECEIVED SIGNAL TERM

Hi All, please help me with this error 17/12/20 11:07:16 INFO executor.CoarseGrainedExecutorBackend: Started daemon with process name: 19581@ddh-dev-dataproc-sw-hdgx 17/12/20 11:07:16 INFO util.SignalUtils: Registered signal handler for TERM 17/12/20 11:07:16 INFO util.SignalUtils: Registered

Re: Rolling policy in Spark event logs for long living streaming applications

I reported the issue as SPARK-22783. Hope this will be resolved soon. Regards Omkar On Fri, Dec 1, 2017 at 10:55 PM, Marcelo Vanzin wrote: > There's really no current solution to this. There's a brief discussion > about it on SPARK-12140. > > Here we recommend people