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/
Client connects to server after too long time interval (1 minute)
Hello. I need some advice. I have 1 client and 1 server. Ignite client connection to server take ~1 minute. And I don't understand why. In server log I see next entry: 2018-11-09 16:34:16,471 [tcp-disco-client-message-worker-#16] DEBUG o.a.i.s.d.tcp.TcpDiscoverySpi - Redirecting message to client [sock=Socket[addr=/10.37.92.222,port=48843,localport=47500], locNodeId=c86fe162-0a55-4aaa-a2cd-f2ea1c644b5f, rmtNodeId=f4856174-de1d-4eae-ad85-80681f783955, msg=TcpDiscoveryNodeAddFinishedMessage [nodeId=f4856174-de1d-4eae-ad85-80681f783955, super=TcpDiscoveryAbstractMessage [sndNodeId=c86fe162-0a55-4aaa-a2cd-f2ea1c644b5f, id=a79abb8f661-c86fe162-0a55-4aaa-a2cd-f2ea1c644b5f, verifierNodeId=c86fe162-0a55-4aaa-a2cd-f2ea1c644b5f, topVer=7, pendingIdx=0, failedNodes=null, isClient=false]]] Client log: 2018-11-09 16:35:06.585 DEBUG 10 --- [-sock-reader-#3] o.a.i.spi.discovery.tcp.TcpDiscoverySpi : Message has been received: TcpDiscoveryNodeAddFinishedMessage [nodeId=f4856174-de1d-4eae-ad85-80681f783955, super=TcpDiscoveryAbstractMessage [sndNodeId=c86fe162-0a55-4aaa-a2cd-f2ea1c644b5f, id=a79abb8f661-c86fe162-0a55-4aaa-a2cd-f2ea1c644b5f, verifierNodeId=c86fe162-0a55-4aaa-a2cd-f2ea1c644b5f, topVer=7, pendingIdx=0, failedNodes=null, isClient=false]] Difference is 50 seconds. Wireshark log entries on client and server with TcpDiscoveryNodeAddFinishedMessage in packet bytes: On server (10.48.14.1): 1648 16:34:16.473071 10.48.14.1 10.37.92.222 35780 TCP [TCP Window Full] 47500 → 48843 [ACK] Seq=180330 Ack=30711 Win=99584 Len=35712 TSval=3529221982 TSecr=2842678176 On client (10.37.92.222): 131 16:34:16.473103 10.48.14.1 10.37.92.222 35780 TCP [TCP Window Full] 47500 → 48843 [ACK] Seq=180330 Ack=30711 Win=99584 Len=35712 TSval=3529221982 TSecr=2842678176 I cann't understand that delay. Thank you. PS. This is kubernetes.
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: Events question
Hi Mikael, In order to use event storage you should configure EventStorageSpi. By default an event storage is not enabled. Which fits your case. You can find more details about event storage in [1]. [1] https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/eventstorage/memory/MemoryEventStorageSpi.html пт, 9 нояб. 2018 г. в 15:11, Mikael : > Hi! > > The event documentation say you can query events, so they are stored > locally, how long does it store them ? can I control this in any way ? > say I just want to use event listeners and not interested in query them, > so no use to keep them around once they have been caught by the > listener, is that possible ? > > It sounds like keeping lots of events around after they have been > triggered would be wasting memory, or maybe it would not make any > difference ? > > Mikael > > > -- Best regards, Ivan Pavlukhin
Re: How does Ignite provides load balancing?
Dear Denis, How does Ignite provides load balancing between nodes? Is it hash-based? Is it dynamically allocated? Is it something else? Thanks, On Thu, Nov 8, 2018 at 1:14 AM Denis Magda wrote: > > Hi, > > In general, the load is balanced because the data is distributed evenly > across a cluster of machines. For instance, if you utilize key-value calls > then each request goes to a specific node. If you're on SQL then a query > might be broadcasted or sent to a specific node as well. > > Overall, yes, Ignite is the right solution if you need to scale and > accelerate performance. > > -- > Denis > > On Tue, Nov 6, 2018 at 6:55 AM Alejandro Santos wrote: >> >> Hi all, >> >> I've been reading the Ignite documentation and have some technical >> questions. I need to evaluate massive storage systems for some >> specific application and I would like to understand how ignite works. >> >> My application needs a buffering space that write arbitrary values, >> but then reads on average half of the values at most once. This is a >> random process, and we can't really predict which keys will be read. >> >> Is ignite the right tool for this application? Do you need more information? >> >> Thank you, >> >> -- >> Alejandro Santos -- Alejandro Santos
Re: Sql long running queries
Hi, Can you run EXPLAIN for these queries so we can see the indexes that were used? Evgenii чт, 8 нояб. 2018 г. в 21:23, Ranjit Sahu : > Hi guys, > > I have the following query which is slow. Below is the explain plan. Any > clue whats going wrong ? > > > > [WARNING][client-connector-#62][IgniteH2Indexing] *Query execution is too > long [time=9649 ms*, sql='SELECT > 2018-10-31T17:09:25.071Z __Z0.ACCOUNTNUMBER __C0_0, > 2018-10-31T17:09:25.071Z __Z0.COMPANYID __C0_1, > 2018-10-31T17:09:25.071Z __Z1.SUBSNUMBER __C0_2, > 2018-10-31T17:09:25.071Z __Z1.APPLICATIONID __C0_3, > 2018-10-31T17:09:25.071Z __Z1.TYPE __C0_4, > 2018-10-31T17:09:25.071Z __Z1.STARTDATE __C0_5, > 2018-10-31T17:09:25.071Z __Z1.ENDDATE __C0_6, > 2018-10-31T17:09:25.071Z __Z1.MLANUMBER __C0_7, > 2018-10-31T17:09:25.071Z __Z1.TRIALOFFER __C0_8, > 2018-10-31T17:09:25.071Z __Z2.MATERIALNUMBER __C0_9, > 2018-10-31T17:09:25.071Z __Z2.TYPE __C0_10, > 2018-10-31T17:09:25.071Z __Z2.DESCRIPTION __C0_11, > 2018-10-31T17:09:25.071Z __Z2.INTERNALDESC __C0_12, > 2018-10-31T17:09:25.071Z __Z3.MATERIALNUMBER __C0_13, > 2018-10-31T17:09:25.071Z __Z3.CLASSIFICATIONID __C0_14, > 2018-10-31T17:09:25.071Z __Z3.CLASSIFICATIONNAME __C0_15, > 2018-10-31T17:09:25.071Z __Z3.CLASSIFICATIONDESC __C0_16, > 2018-10-31T17:09:25.071Z __Z3.CLASSIFICATIONTYPE __C0_17, > 2018-10-31T17:09:25.071Z __Z4.LINENUMBER __C0_18, > 2018-10-31T17:09:25.071Z __Z4.STARTDATE __C0_19, > 2018-10-31T17:09:25.071Z __Z4.ENDDATE __C0_20, > 2018-10-31T17:09:25.071Z __Z4.QUANTITY __C0_21, > 2018-10-31T17:09:25.071Z __Z5.BANDLOW __C0_22, > 2018-10-31T17:09:25.071Z __Z5.BANDHIGH __C0_23, > 2018-10-31T17:09:25.071Z __Z5.BASECOUNT __C0_24, > 2018-10-31T17:09:25.071Z __Z5.USERCAP __C0_25, > 2018-10-31T17:09:25.071Z __Z5.USERAVAILABLE __C0_26, > 2018-10-31T17:09:25.071Z __Z5.USERCOUNT __C0_27 > 2018-10-31T17:09:25.071Z FROM PUBLIC.ACCOUNT __Z0 > 2018-10-31T17:09:25.071Z LEFT OUTER JOIN PUBLIC.SUBSCRIPTION __Z1 > 2018-10-31T17:09:25.071Z ON __Z0.ACCOUNTNUMBER = __Z1.ACCOUNTNUMBER > 2018-10-31T17:09:25.071Z LEFT OUTER JOIN PUBLIC.MATERIALS __Z2 > 2018-10-31T17:09:25.071Z ON __Z1.MATERIALNUMBER = __Z2.MATERIALNUMBER > 2018-10-31T17:09:25.071Z LEFT OUTER JOIN PUBLIC.CLASSIFICATIONS __Z3 > 2018-10-31T17:09:25.071Z ON __Z2.MATERIALNUMBER = __Z3.MATERIALNUMBER > 2018-10-31T17:09:25.071Z LEFT OUTER JOIN PUBLIC.SUBSCRIPTIONLINES __Z4 > 2018-10-31T17:09:25.071Z ON __Z1.SUBSNUMBER = __Z4.SUBSNUMBER > 2018-10-31T17:09:25.071Z LEFT OUTER JOIN PUBLIC.BANDRANGE __Z5 > 2018-10-31T17:09:25.071Z ON __Z1.SUBSNUMBER = __Z5.SUBSNUMBER > 2018-10-31T17:09:25.071Z WHERE __Z0.ACCOUNTNUMBER = 'da'', plan= > 2018-10-31T17:09:25.071Z SELECT > 2018-10-31T17:09:25.071Z __Z0.ACCOUNTNUMBER AS __C0_0, > 2018-10-31T17:09:25.071Z __Z0.COMPANYID AS __C0_1, > 2018-10-31T17:09:25.071Z __Z1.SUBSNUMBER AS __C0_2, > 2018-10-31T17:09:25.071Z __Z1.APPLICATIONID AS __C0_3, > 2018-10-31T17:09:25.071Z __Z1.TYPE AS __C0_4, > 2018-10-31T17:09:25.071Z __Z1.STARTDATE AS __C0_5, > 2018-10-31T17:09:25.071Z __Z1.ENDDATE AS __C0_6, > 2018-10-31T17:09:25.071Z __Z1.MLANUMBER AS __C0_7, > 2018-10-31T17:09:25.071Z __Z1.TRIALOFFER AS __C0_8, > 2018-10-31T17:09:25.071Z __Z2.MATERIALNUMBER AS __C0_9, > 2018-10-31T17:09:25.071Z __Z2.TYPE AS __C0_10, > 2018-10-31T17:09:25.071Z __Z2.DESCRIPTION AS __C0_11, > 2018-10-31T17:09:25.071Z __Z2.INTERNALDESC AS __C0_12, > 2018-10-31T17:09:25.071Z __Z3.MATERIALNUMBER AS __C0_13, > 2018-10-31T17:09:25.071Z __Z3.CLASSIFICATIONID AS __C0_14, > 2018-10-31T17:09:25.071Z __Z3.CLASSIFICATIONNAME AS __C0_15, > 2018-10-31T17:09:25.071Z __Z3.CLASSIFICATIONDESC AS __C0_16, > 2018-10-31T17:09:25.071Z __Z3.CLASSIFICATIONTYPE AS __C0_17, > 2018-10-31T17:09:25.071Z __Z4.LINENUMBER AS __C0_18, > 2018-10-31T17:09:25.071Z __Z4.STARTDATE AS __C0_19, > 2018-10-31T17:09:25.071Z __Z4.ENDDATE AS __C0_20, > 2018-10-31T17:09:25.071Z __Z4.QUANTITY AS __C0_21, > 2018-10-31T17:09:25.071Z __Z5.BANDLOW AS __C0_22, > 2018-10-31T17:09:25.071Z __Z5.BANDHIGH AS __C0_23, > 2018-10-31T17:09:25.071Z __Z5.BASECOUNT AS __C0_24, > 2018-10-31T17:09:25.071Z __Z5.USERCAP AS __C0_25, > 2018-10-31T17:09:25.071Z __Z5.USERAVAILABLE AS __C0_26, > 2018-10-31T17:09:25.072Z __Z5.USERCOUNT AS __C0_27 > 2018-10-31T17:09:25.072Z FROM PUBLIC.ACCOUNT __Z0 > 2018-10-31T17:09:25.072Z /* PUBLIC."_key_PK_proxy": ACCOUNTNUMBER = > 'da' */ > 2018-10-31T17:09:25.072Z /* WHERE __Z0.ACCOUNTNUMBER = 'da' > 2018-10-31T17:09:25.072Z */ > 2018-10-31T17:09:25.072Z LEFT OUTER JOIN PUBLIC.SUBSCRIPTION __Z1 > 2018-10-31T17:09:25.072Z /* PUBLIC.SUBSCRIPTION_ACCOUNTNUMBER_IDX: > ACCOUNTNUMBER = __Z0.ACCOUNTNUMBER */ > 2018-10-31T17:09:25.072Z ON __Z0.ACCOUNTNUMBER = __Z1.ACCOUNTNUMBER > 2018-10-31T17:09:25.072Z LEFT OUTER JOIN PUBLIC.MATERIALS __Z2 > 2018-10-31T17:09:25.072Z /* PUBLIC."_key_PK_proxy": MATERIALNUMBER = > __Z1.MATERIALNUMBER */ > 2018-10-31T17:09:25.072Z ON __Z1.MATERIALNUMBER = __Z2.MATERIALNUMBER > 2018-10-31T17:09:25.072Z LEFT OUTER JOIN PUBLIC.CLASSIF
Re: Ways to improve cluster activation time
We can ignore this as there was already another ticket on the same issue -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Events question
Hi! The event documentation say you can query events, so they are stored locally, how long does it store them ? can I control this in any way ? say I just want to use event listeners and not interested in query them, so no use to keep them around once they have been caught by the listener, is that possible ? It sounds like keeping lots of events around after they have been triggered would be wasting memory, or maybe it would not make any difference ? Mikael
Re: How to add a new cache type to a existing cache?
from the command line there is a error messasge Error: CREATE TABLE can only be executed on PUBLIC schema. (state=5,code=0) just want to know is there anyway to add the new type/table to my existing schema? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: How to add a new cache type to a existing cache?
from the command line there is a error messasge Error: CREATE TABLE can only be executed on PUBLIC schema. (state=5,code=0) just want to know is there anyway to add the new type/table to my existing schema? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
How to add a new cache type to a existing cache?
my cache is created via (cache name is 'abc') == igniteSpringBean.getOrCreateCache(cfg) == and the indexedType is [Long.class, Person.class, Long.class, Student.class] keep the server node running, and issue command from `sqlline.sh` CREATE TABLE IF NOT EXISTS Person ( id int, city_id int, name varchar, age int, company varchar, PRIMARY KEY (id, city_id) ) WITH "template=partitioned,backups=1,cache_name=abc, key_type=PersonKey, value_type=MyPerson"; after the command executed, I can not see the new table 'PERSON' in schema 'abc', if I remove `cache_name=abc ` then I can see a new table `PERSON` is created in `PUBLIC` schema. is there any way to add new new key/value cache to a existing cache? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Can't add new key/value pair to existing cache via sql command
my cache is created via (cache name is 'abc')*igniteSpringBean.getOrCreateCache(cfg);*and the indexedType is [Long.class, Person.class]keep the server node running, and issue command via 'sqlline.sh'CREATE TABLE IF NOT EXISTS Person ( id int, city_id int, name varchar, age int, company varchar, PRIMARY KEY (id, city_id)) WITH "template=partitioned,backups=1,cache_name=abc, key_type=PersonKey, value_type=MyPerson";after the command executed, I can not see any the new table 'PERSON' in schema 'abc',if I remove `cache_name=abc ` then I can see a new table `PERSON` is created in `PUBLIC` schema.did i make a mistake?is there any way to add new new key/value cache to a existing cache? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
