Re: graceful shutdown in external data sources

ndle this issue, including shutdown hooks and a ref counted cache. - Dan On Wed, Mar 16, 2016 at 4:04 PM, Dan Burkert wrote: > Thanks for the replies, responses inline: > > On Wed, Mar 16, 2016 at 3:36 PM, Reynold Xin wrote: > >> There is no way to really know that, because users

Re: graceful shutdown in external data sources

shell shutdown. - Dan On Wed, Mar 16, 2016 at 2:40 PM, Reynold Xin wrote: > Maybe just add a watch dog thread and closed the connection upon some > timeout? > > > On Wednesday, March 16, 2016, Dan Burkert wrote: > >> Hi all, >> >> I'm working on the Spar

Re: graceful shutdown in external data sources

ghran wrote: > > On 16 Mar 2016, at 23:43, Dan Burkert wrote: > > After further thought, I think following both of your suggestions- adding > a shutdown hook and making the threads non-daemon- may have the result I'm > looking for. I'll check and see if there are

Re: graceful shutdown in external data sources

nning. You can test this with the following input to the shell: new Thread(new Runnable { override def run() = { while (true) { println("running"); Thread.sleep(1) } } }).start() Runtime.getRuntime.addShutdownHook(new Thread(new Runnable { override def run() = println("shutdown

graceful shutdown in external data sources

Hi all, I'm working on the Spark connector for Apache Kudu, and I've run into an issue that is a bit beyond my Spark knowledge. The Kudu connector internally holds an open connection to the Kudu cluster