RE: Ouch! Argument is invalid: Cache name must not be null or empty.
As I’ve said in a thread nearby, there is no such thing as “global cache settings”. Usually you’ll need to repeat the configuration paratemers for all caches. You can avoid code/config duplication in multiple ways though. If you explain your use case in detail, I can suggest a way to do that. Stan From: yangjiajun Sent: 28 декабря 2018 г. 11:11 To: user@ignite.apache.org Subject: Re: Ouch! Argument is invalid: Cache name must not be null or empty. Hello.Thanks for your reply. I want to make such settings global.Do this settings only affect specific caches? ezhuravlev wrote > As you see, the example in config has > , which means that it's > just a part of the configuration. Exceptions message says "Cache name must > not be null" and that really the problem that you faced, just define cache > name property to resolve this issue. > > Evgenii > > > чт, 27 дек. 2018 г. в 22:28, yangjiajun < > 1371549332@ >>: > >> Hello. >> >> I use ignite 2.6 as a database and try to tune data rebalancing according >> to >> following doc： >> >> https://apacheignite.readme.io/docs/rebalancing#section-rebalance-message-throttling >> But I get an exception when I set those settings. >> >> class org.apache.ignite.IgniteException: Ouch! Argument is invalid: Cache >> name must not be null or empty. >> at >> >> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:990) >> at org.apache.ignite.Ignition.start(Ignition.java:355) >> at >> >> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301) >> Caused by: class org.apache.ignite.IgniteCheckedException: Ouch! Argument >> is >> invalid: Cache name must not be null or empty. >> at >> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1133) >> at >> >> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014) >> at >> >> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723) >> at >> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151) >> at >> >> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1069) >> at >> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:955) >> at >> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:854) >> at >> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:724) >> at >> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:693) >> at org.apache.ignite.Ignition.start(Ignition.java:352) >> ... 1 more >> Caused by: java.lang.IllegalArgumentException: Ouch! Argument is invalid: >> Cache name must not be null or empty. >> at >> >> org.apache.ignite.internal.util.GridArgumentCheck.ensure(GridArgumentCheck.java:109) >> at >> >> org.apache.ignite.internal.processors.cache.GridCacheUtils.validateCacheName(GridCacheUtils.java:1590) >> at >> >> org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoin(GridCacheProcessor.java:738) >> at >> >> org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoinFromConfig(GridCacheProcessor.java:808) >> at >> >> org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:707) >> at >> >> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1739) >> at >> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:980) >> ... 10 more >> Failed to start grid: Ouch! Argument is invalid: Cache name must not be >> null >> or empty. >> >> >> Here is my config file: >> example-default2.xml >> < >> http://apache-ignite-users.70518.x6.nabble.com/file/t2059/example-default2.xml> >> >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ouch! Argument is invalid: Cache name must not be null or empty.
Hello.Thanks for your reply. I want to make such settings global.Do this settings only affect specific caches? ezhuravlev wrote > As you see, the example in config has > , which means that it's > just a part of the configuration. Exceptions message says "Cache name must > not be null" and that really the problem that you faced, just define cache > name property to resolve this issue. > > Evgenii > > > чт, 27 дек. 2018 г. в 22:28, yangjiajun < > 1371549332@ >>: > >> Hello. >> >> I use ignite 2.6 as a database and try to tune data rebalancing according >> to >> following doc： >> >> https://apacheignite.readme.io/docs/rebalancing#section-rebalance-message-throttling >> But I get an exception when I set those settings. >> >> class org.apache.ignite.IgniteException: Ouch! Argument is invalid: Cache >> name must not be null or empty. >> at >> >> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:990) >> at org.apache.ignite.Ignition.start(Ignition.java:355) >> at >> >> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301) >> Caused by: class org.apache.ignite.IgniteCheckedException: Ouch! Argument >> is >> invalid: Cache name must not be null or empty. >> at >> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1133) >> at >> >> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014) >> at >> >> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723) >> at >> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151) >> at >> >> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1069) >> at >> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:955) >> at >> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:854) >> at >> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:724) >> at >> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:693) >> at org.apache.ignite.Ignition.start(Ignition.java:352) >> ... 1 more >> Caused by: java.lang.IllegalArgumentException: Ouch! Argument is invalid: >> Cache name must not be null or empty. >> at >> >> org.apache.ignite.internal.util.GridArgumentCheck.ensure(GridArgumentCheck.java:109) >> at >> >> org.apache.ignite.internal.processors.cache.GridCacheUtils.validateCacheName(GridCacheUtils.java:1590) >> at >> >> org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoin(GridCacheProcessor.java:738) >> at >> >> org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoinFromConfig(GridCacheProcessor.java:808) >> at >> >> org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:707) >> at >> >> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1739) >> at >> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:980) >> ... 10 more >> Failed to start grid: Ouch! Argument is invalid: Cache name must not be >> null >> or empty. >> >> >> Here is my config file: >> example-default2.xml >> < >> http://apache-ignite-users.70518.x6.nabble.com/file/t2059/example-default2.xml> >> >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ouch! Argument is invalid: Cache name must not be null or empty.
As you see, the example in config has , which means that it's just a part of the configuration. Exceptions message says "Cache name must not be null" and that really the problem that you faced, just define cache name property to resolve this issue. Evgenii чт, 27 дек. 2018 г. в 22:28, yangjiajun <1371549...@qq.com>: > Hello. > > I use ignite 2.6 as a database and try to tune data rebalancing according > to > following doc： > > https://apacheignite.readme.io/docs/rebalancing#section-rebalance-message-throttling > But I get an exception when I set those settings. > > class org.apache.ignite.IgniteException: Ouch! Argument is invalid: Cache > name must not be null or empty. > at > > org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:990) > at org.apache.ignite.Ignition.start(Ignition.java:355) > at > > org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301) > Caused by: class org.apache.ignite.IgniteCheckedException: Ouch! Argument > is > invalid: Cache name must not be null or empty. > at > org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1133) > at > > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014) > at > > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723) > at > org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151) > at > > org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1069) > at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:955) > at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:854) > at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:724) > at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:693) > at org.apache.ignite.Ignition.start(Ignition.java:352) > ... 1 more > Caused by: java.lang.IllegalArgumentException: Ouch! Argument is invalid: > Cache name must not be null or empty. > at > > org.apache.ignite.internal.util.GridArgumentCheck.ensure(GridArgumentCheck.java:109) > at > > org.apache.ignite.internal.processors.cache.GridCacheUtils.validateCacheName(GridCacheUtils.java:1590) > at > > org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoin(GridCacheProcessor.java:738) > at > > org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoinFromConfig(GridCacheProcessor.java:808) > at > > org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:707) > at > > org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1739) > at > org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:980) > ... 10 more > Failed to start grid: Ouch! Argument is invalid: Cache name must not be > null > or empty. > > > Here is my config file: > example-default2.xml > < > http://apache-ignite-users.70518.x6.nabble.com/file/t2059/example-default2.xml> > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Re: Ouch! Argument is invalid: Cache name must not be null or empty.
Evgenii,
"Client node didn't even join the topology. Most possible you have incorrect
discovery configuration. Also, I'd recommend to check client logs for more
information why node can't connect to the cluster."
In Zeppelin setup for the Ignite interpreter, it uses the same configuration
for Scala connection as it does for Ignite SQL connections. I have tested
the SQL connections, and they work perfectly (both the 11211 port and the
Node Client using XML). It is odd that the Scala connection doesn't work.
As far as client logs are concerned, Zeppelin only generates the interpreter
logs, such as, zeppelin-interpreter-ignite--zeppelin-db54cc4b4-kppw2.log,
and that log only states that the job was started:
INFO [2018-11-03 09:15:41,893] ({pool-2-thread-5}
SchedulerFactory.java[jobStarted]:109) - Job 20181102-071721_1550658378
started by scheduler org.apache.zeppelin.ignite.IgniteInterpreter113609227
And then nothing after that, as the interpreter process hangs.
Do you have any idea how to turn on DEBUG level logging for the Zeppelin
Ignite interpreter?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ouch! Argument is invalid: Cache name must not be null or empty.
>1) How do I enable DEBUG logging on the Ignite cluster? It depends on the logger that you use. You have to change the config file and give to the ignite package DEBUG level. It could be JUL, log4j or log4j2 config files. > org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology Client node didn't even join the topology. Most possible you have incorrect discovery configuration. Also, I'd recommend to check client logs for more information why node can't connect to the cluster. Evgenii вс, 4 нояб. 2018 г. в 8:09, sv : > Evgenii, > > 1) How do I enable DEBUG logging on the Ignite cluster? > > 2) I used jstack to produce a thread dump of the Zeppelin Ignite > interpreter > (which runs in a separate process). I pasted it below. Does anything look > out of place to you? > > 2018-11-03 09:32:37 > Full thread dump OpenJDK 64-Bit Server VM (25.171-b11 mixed mode): > > "Attach Listener" #82 daemon prio=9 os_prio=0 tid=0x7f202c001000 > nid=0x37b waiting on condition [0x] >java.lang.Thread.State: RUNNABLE > >Locked ownable synchronizers: > - None > > "tcp-client-disco-msg-worker-#4" #81 prio=5 os_prio=0 > tid=0x7f1fd1f2a000 > nid=0x2fb waiting on condition [0x7f1fce1e6000] >java.lang.Thread.State: TIMED_WAITING (sleeping) > at java.lang.Thread.sleep(Native Method) > at > > org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology(ClientImpl.java:522) > at > > org.apache.ignite.spi.discovery.tcp.ClientImpl.access$900(ClientImpl.java:128) > at > > org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.tryJoin(ClientImpl.java:1846) > at > > org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1561) > at > org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) > >Locked ownable synchronizers: > - None > > "tcp-client-disco-sock-reader-#3" #80 prio=5 os_prio=0 > tid=0x7f1fd1f25000 nid=0x2fa in Object.wait() [0x7f1fce2e7000] >java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.lang.Object.wait(Object.java:502) > at > > org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketReader.body(ClientImpl.java:1006) > - locked <0xee2bc268> (a java.lang.Object) > at > org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) > >Locked ownable synchronizers: > - None > > "tcp-client-disco-sock-writer-#2" #79 prio=5 os_prio=0 > tid=0x7f1fd1f24800 nid=0x2f9 in Object.wait() [0x7f1fce3e8000] >java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.lang.Object.wait(Object.java:502) > at > > org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1209) > - locked <0xee2bbd88> (a java.lang.Object) > at > org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) > >Locked ownable synchronizers: > - None > > "TcpDiscoverySpi.timer" #78 prio=5 os_prio=0 tid=0x7f1fd1f20800 > nid=0x2f8 in Object.wait() [0x7f1fce4e9000] >java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.lang.Object.wait(Object.java:502) > at java.util.TimerThread.mainLoop(Timer.java:526) > - locked <0xee228468> (a java.util.TaskQueue) > at java.util.TimerThread.run(Timer.java:505) > >Locked ownable synchronizers: > - None > > "grid-data-loader-flusher-#39" #77 prio=5 os_prio=0 tid=0x7f1fd1efb000 > nid=0x2f7 waiting on condition [0x7f1fce5ea000] >java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0xedc52cc0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at > java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.DelayQueue.take(DelayQueue.java:211) > at > > org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$2.body(DataStreamProcessor.java:109) > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) > at java.lang.Thread.run(Thread.java:748) > >Locked ownable synchronizers: > - None > > "grid-nio-worker-client-listener-3-#37" #75 prio=5 os_prio=0 > tid=0x7f1fd1eea800 nid=0x2f6 runnable [0x7f1fce8eb000] >java.lang.Thread.State: RUNNABLE > at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) > at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269) > at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93) > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.j
Re: Ouch! Argument is invalid: Cache name must not be null or empty.
Evgenii, 1) How do I enable DEBUG logging on the Ignite cluster? 2) I used jstack to produce a thread dump of the Zeppelin Ignite interpreter (which runs in a separate process). I pasted it below. Does anything look out of place to you? 2018-11-03 09:32:37 Full thread dump OpenJDK 64-Bit Server VM (25.171-b11 mixed mode): "Attach Listener" #82 daemon prio=9 os_prio=0 tid=0x7f202c001000 nid=0x37b waiting on condition [0x] java.lang.Thread.State: RUNNABLE Locked ownable synchronizers: - None "tcp-client-disco-msg-worker-#4" #81 prio=5 os_prio=0 tid=0x7f1fd1f2a000 nid=0x2fb waiting on condition [0x7f1fce1e6000] java.lang.Thread.State: TIMED_WAITING (sleeping) at java.lang.Thread.sleep(Native Method) at org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology(ClientImpl.java:522) at org.apache.ignite.spi.discovery.tcp.ClientImpl.access$900(ClientImpl.java:128) at org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.tryJoin(ClientImpl.java:1846) at org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1561) at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) Locked ownable synchronizers: - None "tcp-client-disco-sock-reader-#3" #80 prio=5 os_prio=0 tid=0x7f1fd1f25000 nid=0x2fa in Object.wait() [0x7f1fce2e7000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:502) at org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketReader.body(ClientImpl.java:1006) - locked <0xee2bc268> (a java.lang.Object) at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) Locked ownable synchronizers: - None "tcp-client-disco-sock-writer-#2" #79 prio=5 os_prio=0 tid=0x7f1fd1f24800 nid=0x2f9 in Object.wait() [0x7f1fce3e8000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:502) at org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1209) - locked <0xee2bbd88> (a java.lang.Object) at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) Locked ownable synchronizers: - None "TcpDiscoverySpi.timer" #78 prio=5 os_prio=0 tid=0x7f1fd1f20800 nid=0x2f8 in Object.wait() [0x7f1fce4e9000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:502) at java.util.TimerThread.mainLoop(Timer.java:526) - locked <0xee228468> (a java.util.TaskQueue) at java.util.TimerThread.run(Timer.java:505) Locked ownable synchronizers: - None "grid-data-loader-flusher-#39" #77 prio=5 os_prio=0 tid=0x7f1fd1efb000 nid=0x2f7 waiting on condition [0x7f1fce5ea000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0xedc52cc0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) at java.util.concurrent.DelayQueue.take(DelayQueue.java:211) at org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$2.body(DataStreamProcessor.java:109) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) at java.lang.Thread.run(Thread.java:748) Locked ownable synchronizers: - None "grid-nio-worker-client-listener-3-#37" #75 prio=5 os_prio=0 tid=0x7f1fd1eea800 nid=0x2f6 runnable [0x7f1fce8eb000] java.lang.Thread.State: RUNNABLE at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269) at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93) at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86) - locked <0xedb0fdf0> (a org.apache.ignite.internal.util.nio.SelectedSelectionKeySet) - locked <0xed992ff0> (a java.util.Collections$UnmodifiableSet) - locked <0xed992ed8> (a sun.nio.ch.EPollSelectorImpl) at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97) at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2105) at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1764) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) at java.lang.Thread.run(Thread.java:748) Locked ownable synchronizers: -
Re: Ouch! Argument is invalid: Cache name must not be null or empty.
IGNITE_QUIET=false enables only INFO logging. Well, then something stuck on the Zeppelin side, still it worth to collect the thread dumps from it. Evgenii пт, 2 нояб. 2018 г. в 10:39, sv : > Actually, I already am running each Ignite node with IGNITE_QUIET=false, so > that should already have INFO and DEBUG logging enabled. But still, > nothing. I suspect that the Zeppelin Ignite interpreter is not reaching > the > Ignite cluster. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Re: Ouch! Argument is invalid: Cache name must not be null or empty.
Actually, I already am running each Ignite node with IGNITE_QUIET=false, so that should already have INFO and DEBUG logging enabled. But still, nothing. I suspect that the Zeppelin Ignite interpreter is not reaching the Ignite cluster. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ouch! Argument is invalid: Cache name must not be null or empty.
Evgenii,
I am not sure if it even gets to the Ignite cluster.
Here is what I see in Zeppelin interpreter log, when I try to execute scala
code in a notebook:
INFO [2018-11-02 07:29:38,005] ({pool-2-thread-4}
SchedulerFactory.java[jobStarted]:109) - Job 20181102-071721_1550658378
started by scheduler org.apache.zeppelin.ignite.IgniteInterpreter1313679265
After that, nothing.
There is absolutely nothing in Ignite logs.
I have not increased the log level for Ignite, as that would mean I would
have to reload the entire cluster.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ouch! Argument is invalid: Cache name must not be null or empty.
> executing scala code (using %ignite) makes the entire Ignite interpreter in Zeppelin hang, without any errors in logs. How do I debug this? When something hangs, you have to check thread dumps to understand where and why it hangs. Also, sometimes, it worth to enable another level of the logging - INFO or even DEBUG. Evgenii чт, 1 нояб. 2018 г. в 11:05, sv : > Hi, to clarify: > 1) Thin client works fine > 2) Thick client using port 11211 works fine > 3) The "Client Node" connection is the one that was not working. > > I got the Client Node connection (#3) to work by specifying the cache name > in the connection string. Now it connects, and all SQL works well. > > I thought that this was fixed already in 2.6, so that you didn't have to > specify the cache name anymore? In any case, it works. > > The next problem that I ran into: executing scala code (using %ignite) > makes the entire Ignite interpreter in Zeppelin hang, without any errors in > logs. How do I debug this? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Re: Ouch! Argument is invalid: Cache name must not be null or empty.
Hi, to clarify: 1) Thin client works fine 2) Thick client using port 11211 works fine 3) The "Client Node" connection is the one that was not working. I got the Client Node connection (#3) to work by specifying the cache name in the connection string. Now it connects, and all SQL works well. I thought that this was fixed already in 2.6, so that you didn't have to specify the cache name anymore? In any case, it works. The next problem that I ran into: executing scala code (using %ignite) makes the entire Ignite interpreter in Zeppelin hang, without any errors in logs. How do I debug this? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ouch! Argument is invalid: Cache name must not be null or empty.
Hi, Looks like you use JDBC client driver, which needs cache name to be configured(https://apacheignite-sql.readme.io/docs/jdbc-client-driver). I'd recommend using a thin JDBC driver instead - it doesn't need.( https://apacheignite-sql.readme.io/docs/jdbc-driver) Evgenii пн, 29 окт. 2018 г. в 10:48, sv : > Getting "Ouch! Argument is invalid: Cache name must not be null or empty." > error when trying to execute SQL from within Zeppelin, using the Node > Client > type of connection (jdbc:ignite:cfg:[URL]). > > Zeppelin 0.8.0, Ignite 2.6 libs. Cluster is 2.6. > > Almost seems like it wants a cache name, but I thought this bug was fixed > in > 2.6? Perhaps something else is going on. > > > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
