[jira] [Created] (ZEPPELIN-5245) Zeppelin doesn't propagate interpreter setting in cluster mode

["Ruslan Fialkovsky (Jira)" <ji...@apache.org>]

Ruslan Fialkovsky created ZEPPELIN-5245:
-------------------------------------------

             Summary: Zeppelin doesn't propagate interpreter setting in cluster mode
                 Key: ZEPPELIN-5245
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5245
             Project: Zeppelin
          Issue Type: Bug
          Components: Core, interpreter-setting, zeppelin-server
    Affects Versions: 0.9.0
            Reporter: Ruslan Fialkovsky


Hello. I'm trying to configure zeppelin in cluster mode. 

When I change interpreter setting they implement only on local node and  I get  error on remote node:
(\{netty-messaging-event-epoll-client-3} NettyMessagingService.java[lambda$null$20]:531) - An error occurred in a message handler: {} │
java.lang.ClassCastException: com.google.gson.internal.LinkedTreeMap cannot be cast to java.util.HashMap │
 at org.apache.zeppelin.interpreter.InterpreterSettingManager.onClusterEvent(InterpreterSettingManager.java:1215) │
 at org.apache.zeppelin.cluster.ClusterManagerServer.lambda$new$5(ClusterManagerServer.java:370) │
 at io.atomix.cluster.messaging.impl.NettyMessagingService.lambda$null$20(NettyMessagingService.java:529) │
 at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:399) │
 at io.atomix.cluster.messaging.impl.NettyMessagingService.lambda$registerHandler$21(NettyMessagingService.java:525) │
 at io.atomix.cluster.messaging.impl.NettyMessagingService$RemoteServerConnection.dispatch(NettyMessagingService.java:1122) │
 at io.atomix.cluster.messaging.impl.NettyMessagingService$RemoteServerConnection.access$800(NettyMessagingService.java:1100) │
 at io.atomix.cluster.messaging.impl.NettyMessagingService$InboundMessageDispatcher.channelRead0(NettyMessagingService.java:754) │
 at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105) │
 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) │
 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) │
 at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) │
 at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310) │
 at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284) │
 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) │
 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) │
 at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) │
 at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434) │
 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) │
 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) │
 at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965) │
 at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:808) │
 at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:417) │
 at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:317) │
 at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884) │
 at java.lang.Thread.run(Thread.java:748)

 

Also what interesting, I tried 0.9.0 preview2 and everything have worked fine. The problem appeared in release version 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)