In-Memory Computing Essentials Webinar, March 25th - New Edition

[Denis Magda]

Hi Igniters,

I thought that some of you could benefit from joining a webinar about
in-memory computing essentials [1] on March 25th, where Ignite is used as a
reference platform for explanation/demonstration of the main topics. Some
of you might have watched the original version, that had bee recorded
almost 3 years ago [2], and the list of the top watched Ignite videos on
YouTube.

A lot has changed since the time of the recording.  The content/demos have
been revisited and rebuilt from scratch for the upcoming session. I will be
pleased to see you joining me next Wednesday; you can find the agenda by
following the link [1].

[1] https://bit.ly/3acCtEY
[2] https://www.youtube.com/watch?v=G22L2KW9gEQ

-
Denis

Re: No ignitevisorcmd.sh in Ignite 2.8

[Stephen Darlington]

Ah, apparently it doesn’t work when installed from a package. It’s in the doc 
directory somewhere. See here for a discussion from when 2.7.5 was current: 
http://apache-ignite-users.70518.x6.nabble.com/2-7-5-IGNITE-HOME-bin-ignitevisorcmd-sh-is-absent-td28629.html

Regards,
Stephen

> On 20 Mar 2020, at 20:46, João Gonçalves  wrote:
> 
> Thanks for the quick reply
> 
> I downloaded the rpm package 
> https://ignite.apache.org/download.cgi#rpm-package 
> 
> 
> Which one should I use?
> 
> 
> Stephen Darlington  > escreveu no dia sexta, 20/03/2020 
> à(s) 20:30:
> Where did you download it from? Did you download the binary or source 
> version? It’s there in my download:
> 
> ~ stephen.darlington$ cd $IGNITE_HOME
> -ignite-2.8.0-bin stephen.darlington$ ls bin/*sh
> bin/control.shbin/igniterouter.sh bin/sqlline.sh
> bin/ignite.sh bin/ignitevisorcmd.sh
> apache-ignite-2.8.0-bin stephen.darlington$ 
> 
> Regards,
> Stephen
> 
>> On 20 Mar 2020, at 19:19, joaogoncalves > > wrote:
>> 
>> Hi
>> Recently started working with Ignite on version 2.8.0
>> 
>> Can't find ignitevisorcmd.sh, was it removed? According to 
>> https://apacheignite-tools.readme.io/docs/command-line-interface 
>> 
>> > >   it
>> should be under IGNITE_HOME/bin
>> 
>> I found IGNITE_HOME/bin/include/visorcmd/ignite-visor-console-2.8.0.jar and
>> tried to run it but got: 
>> "no main manifest attribute, in ignite-visor-console-2.8.0.jar"
>> 
>> Clearly it must run somehow but I can't find any documentation on how to do
>> it.
>> 
>> 
>> 
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ 
>> 
> 
> 

RE: Ignite memory leaks in 2.8.0

[Andrey Davydov]

I found one more way for leak and understand reason:


this - value: org.apache.ignite.internal.IgniteKernal #1
 <- grid - class: org.apache.ignite.internal.GridKernalContextImpl,
value: org.apache.ignite.internal.IgniteKernal #1
  <- ctx - class:
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor, value:
org.apache.ignite.internal.GridKernalContextImpl #3
   <- this$0 - class:
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$CancelableTask,
value: org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor #1
<- stmtCleanupTask - class:
org.apache.ignite.internal.processors.query.h2.ConnectionManager, value:
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$CancelableTask
#11
 <- arg$1 - class:
org.apache.ignite.internal.processors.query.h2.ConnectionManager$$Lambda$174,
value: org.apache.ignite.internal.processors.query.h2.ConnectionManager #1
  <- recycler - class:
org.apache.ignite.internal.processors.query.h2.ThreadLocalObjectPool,
value:
org.apache.ignite.internal.processors.query.h2.ConnectionManager$$Lambda$174
#1
   <- this$0 - class:
org.apache.ignite.internal.processors.query.h2.ThreadLocalObjectPool$Reusable,
value: org.apache.ignite.internal.processors.query.h2.ThreadLocalObjectPool
#1
<- value - class: java.lang.ThreadLocal$ThreadLocalMap$Entry,
value:
org.apache.ignite.internal.processors.query.h2.ThreadLocalObjectPool$Reusable
#1
 <- [411] - class:
java.lang.ThreadLocal$ThreadLocalMap$Entry[], value:
java.lang.ThreadLocal$ThreadLocalMap$Entry #35
  <- table - class: java.lang.ThreadLocal$ThreadLocalMap,
value: java.lang.ThreadLocal$ThreadLocalMap$Entry[] #25
   <- threadLocals (thread object) - class: java.lang.Thread,
value: java.lang.ThreadLocal$ThreadLocalMap #2



Reason:


org.apache.ignite.internal.processors.query.h2.ConnectionManager has some
ThreadLocal fields, including connPool, threadConns,  threadConn,
detachedConns etc.


ConnectionManager store Lambdas it this thread local storages, so link to
ConnectionManager leaks to thread local context.


And seems that method not valid enoght

private void closeConnections() {
threadConns.values().forEach(set ->
set.keySet().forEach(U::closeQuiet));
detachedConns.keySet().forEach(U::closeQuiet);

threadConns.clear();
detachedConns.clear();
}


So when Ignition.start() and Ignition.stop()  was from different thread,
caches not cleared properly and starter thread save link to
ConnectionManager via ThreadLocal context. And we get one Ignite instance
leak every time.


Im sure you run "tens of thousands nodes during every suite run." But
majority of runs may be without Indexing, and start and stop node in same
thread.


To reproduce leak, start ignite with indexing, save lint to weak reference,
and stop it asynchroniouly in other thread, null local link, check weak ref
and see heap dump.



Andrey.



*От: *Andrey Davydov 
*Отправлено: *18 марта 2020 г. в 18:37
*Кому: *user@ignite.apache.org
*Тема: *Ignite memory leaks in 2.8.0



Hello,



There are at least two way link to IgniteKernal leaks to GC root and makes
it unavailable for GC.



   1. The first one:



this - value: org.apache.ignite.internal.IgniteKernal #1

<- grid - class: org.apache.ignite.internal.GridKernalContextImpl,
value: org.apache.ignite.internal.IgniteKernal #1

  <- ctx - class:
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing, value:
org.apache.ignite.internal.GridKernalContextImpl #2

   <- this$0 - class:
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$10, value:
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing #2

<- serializer - class: org.h2.util.JdbcUtils, value:
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$10 #1

 <- [5395] - class: java.lang.Object[], value:
org.h2.util.JdbcUtils class JdbcUtils

  <- elementData - class: java.util.Vector, value:
java.lang.Object[] #37309

   <- classes - class: sun.misc.Launcher$AppClassLoader, value:
java.util.Vector #31

<- contextClassLoader (thread object) - class:
java.lang.Thread, value: sun.misc.Launcher$AppClassLoader #1



org.h2.util.JdbcUtils has static field JavaObjectSerializer serializer, which
see IgniteKernal via IgniteH2Indexing. It make closed and stopped
IgniteKernal non collectable by GC.

If some Ignites run in same JVM, JdbcUtils will always use only one, and it
can cause some races.



   1. The second way:



this - value: org.apache.ignite.internal.IgniteKernal #2

<- grid - class: org.apache.ignite.internal.GridKernalContextImpl,
value: org.apache.ignite.internal.IgniteKernal #2

  <- ctx - class:
org.apache.ignite.internal.processors.cache.GridCacheContext, value:
org.apache.ignite.internal.GridKernalContextImpl #1

   <- cctx - class:
org.apache.ignite.internal.proce

Re: No ignitevisorcmd.sh in Ignite 2.8

[João Gonçalves]

Thanks for the quick reply

I downloaded the rpm package
https://ignite.apache.org/download.cgi#rpm-package

Which one should I use?


Stephen Darlington  escreveu no dia sexta,
20/03/2020 à(s) 20:30:

> Where did you download it from? Did you download the binary or source
> version? It’s there in my download:
>
> ~ stephen.darlington$ cd $IGNITE_HOME
> -ignite-2.8.0-bin stephen.darlington$ ls bin/*sh
> bin/control.sh bin/igniterouter.sh bin/sqlline.sh
> bin/ignite.sh bin/ignitevisorcmd.sh
> apache-ignite-2.8.0-bin stephen.darlington$
>
> Regards,
> Stephen
>
> On 20 Mar 2020, at 19:19, joaogoncalves  wrote:
>
> Hi
> Recently started working with Ignite on version 2.8.0
>
> Can't find ignitevisorcmd.sh, was it removed? According to
> https://apacheignite-tools.readme.io/docs/command-line-interface
>    it
> should be under IGNITE_HOME/bin
>
> I found IGNITE_HOME/bin/include/visorcmd/ignite-visor-console-2.8.0.jar and
> tried to run it but got:
> "no main manifest attribute, in ignite-visor-console-2.8.0.jar"
>
> Clearly it must run somehow but I can't find any documentation on how to do
> it.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
>
>
>

Re: No ignitevisorcmd.sh in Ignite 2.8

[Stephen Darlington]

Where did you download it from? Did you download the binary or source version? 
It’s there in my download:

~ stephen.darlington$ cd $IGNITE_HOME
-ignite-2.8.0-bin stephen.darlington$ ls bin/*sh
bin/control.sh  bin/igniterouter.sh bin/sqlline.sh
bin/ignite.sh   bin/ignitevisorcmd.sh
apache-ignite-2.8.0-bin stephen.darlington$ 

Regards,
Stephen

> On 20 Mar 2020, at 19:19, joaogoncalves  wrote:
> 
> Hi
> Recently started working with Ignite on version 2.8.0
> 
> Can't find ignitevisorcmd.sh, was it removed? According to 
> https://apacheignite-tools.readme.io/docs/command-line-interface
>    it
> should be under IGNITE_HOME/bin
> 
> I found IGNITE_HOME/bin/include/visorcmd/ignite-visor-console-2.8.0.jar and
> tried to run it but got: 
> "no main manifest attribute, in ignite-visor-console-2.8.0.jar"
> 
> Clearly it must run somehow but I can't find any documentation on how to do
> it.
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

No ignitevisorcmd.sh in Ignite 2.8

[joaogoncalves]

Hi
Recently started working with Ignite on version 2.8.0

Can't find ignitevisorcmd.sh, was it removed? According to 
https://apacheignite-tools.readme.io/docs/command-line-interface
   it
should be under IGNITE_HOME/bin

I found IGNITE_HOME/bin/include/visorcmd/ignite-visor-console-2.8.0.jar and
tried to run it but got: 
"no main manifest attribute, in ignite-visor-console-2.8.0.jar"

Clearly it must run somehow but I can't find any documentation on how to do
it.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

[Community] Ignite 2.8 User Survey

[Kseniya Romanova]

Hi, Ignite Users and Enthusiasts!


Please take a few minutes to go through the small survey[1] about Ignite
2.8. The survey has only three questions and is anonymous. Your answers
will help contributors to understand which changes were most interesting
and relevant to users.

Please answer before April 5th, and I will share results with the community
after April 7th.

Cheers,

Kseniya

[1]
https://docs.google.com/forms/d/e/1FAIpQLScQIRn7cXJeAgT_wTqa54ekG0UZjmFjf_av8_jstP6R7roUpQ/viewform

Re: Re: RE: Re: Unsafe usage of org.h2.util.JdbcUtils in Ignite

[Andrey Davydov]

Hello,

Current implementation is really unsafe for multiple Ignite in same JVM.
In tests for our system when we stop/start nodes in different order we get
following error:

Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
initialize system DB connection:
jdbc:h2:mem:fd191fac-c2f1-4398-bf8a-0dcddf651830;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.H2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1402)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1035)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:921)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:820)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:690)
at com.example.testutils.TestNode.start(TestNode.java:75)
... 38 more
Caused by: class
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
initialize system DB connection:
jdbc:h2:mem:fd191fac-c2f1-4398-bf8a-0dcddf651830;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.H2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine
at
org.apache.ignite.internal.processors.query.h2.ConnectionManager.connectionNoCache(ConnectionManager.java:213)
at
org.apache.ignite.internal.processors.query.h2.ConnectionManager.(ConnectionManager.java:152)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:2070)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:256)
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1978)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1212)
... 46 more
Caused by: java.sql.SQLException: No suitable driver found for
jdbc:h2:mem:fd191fac-c2f1-4398-bf8a-0dcddf651830;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.H2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine
at java.sql.DriverManager.getConnection(DriverManager.java:689)
at java.sql.DriverManager.getConnection(DriverManager.java:270)
at
org.apache.ignite.internal.processors.query.h2.ConnectionManager.connectionNoCache(ConnectionManager.java:206)
... 51 more


On Thu, Mar 19, 2020 at 6:52 PM Andrey Davydov 
wrote:

> It seems like moving in right way =) Let wait for release.
>
>
>
> Andrey.
>
>
>
> *От: *Andrey Mashenkov 
> *Отправлено: *19 марта 2020 г. в 16:28
> *Кому: *user@ignite.apache.org
> *Тема: *Re: RE: Re: Unsafe usage of org.h2.util.JdbcUtils in Ignite
>
>
>
> Hi,
>
>
>
> In Apache Ignite master branch I see a separate class
> H2JavaObjectSerializer that implements JavaObjectSerializer.
>
> Seems, this won't be released in 2.8
>
> https://issues.apache.org/jira/browse/IGNITE-12609
>
>
>
> On Thu, Mar 19, 2020 at 4:03 PM Andrey Davydov 
> wrote:
>
> Seem that refactor h2serilizer method in following manner will be safe for
> marshallers which not depends on ignite instance and will be faster anyway,
> due to single clsLdr resolving. For binary marshaller solution is still
> unsafe =(((
>
>
>
> private JavaObjectSerializer h2Serializer() {
>
> ClassLoader clsLdr = ctx != null ?
> U.resolveClassLoader(ctx.config()) : null;
>
> return new CustomJavaObjectSerializer(marshaller, clsLdr);
>
> }
>
>
>
> private static final class CustomJavaObjectSerializer implements
> JavaObjectSerializer {
>
> private final Marshaller marshaller;
>
> private final ClassLoader clsLdr;
>
>
>
> CustomJavaObjectSerializer(Marshaller marshaller, ClassLoader
> clsLdr) {
>
> this.marshaller = marshaller;
>
> this.clsLdr = clsLdr;
>
> }
>
>
>
> @Override public byte[] serialize(Object obj) throws Exception {
>
> return U.marshal(marshaller, obj);
>
> }
>
>
>
> @Override public Object deserialize(byte[] bytes) throws Exception
> {
>
> return U.unmarshal(marshaller, bytes, clsLdr);
>
> }
>

Re: ClusterTopologyServerNotFoundException

[prudhvibiruda]

Hi ,

Please don't be confused.
Our plan is to use more  server nodes further. But as of now we have only
one server node.  
Since we are planning for more server nodes we are using
CacheMode.Replicated.
We don't want our nodes not to start just because other server nodes are not
working , that's why we didn't define baseline topology.





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Python - Ignite 2.8.0 - java.lang.NullPointerException

[dbutkovic]

I have one small error in py code, please remove last "," from UPDATE
statement in test_insert_update.py

SQL_UPDATE =''' UPDATE TEST SET 
COL1 = ?, 
COL2 = ?,
COL3 = ?,
COL4 = ?,
COL5 = ?,
COL6 = ?,
COL7 = ?,
COL8 = ?,
COL9 = ?,
COL10= ?,
COL11= ?,
COL12= ?
WHERE ID = ? 
''' 

regardless of this sintax error, insert on Ignite 2.8.0 is not ok.




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Python - Ignite 2.8.0 - java.lang.NullPointerException

[Dren Butković]

Hi,

random string insert/update test fails from time to time.
Tested with python 3.6 , pyignite and Ignite 2.8.0
On Ignite 2.7.6 work fine.
All logs and examples and py code for test in attachment.

Best regards
Dren



[dbutkovic@incumbosstest06 python]$ python3.6 test_insert_update.py
Connected to 192.168.50.106:10800
cnushrffacaexsruvuvkcpukrmqlqmyksafgagejdcdmzvrqsqacmlxsqrrzhfprkliafsyoodvxgfgoarbxeguzuwrgubhhgjv
INSERT
Connected to 192.168.50.106:10800
uebrapqingtsvbacfsvqdgrzthqdjmzqpevfcdqfrcxrhtxicwzvvjrluexmclyxyfnxswrmpdxgbuqacjetfrtsmivkbpzmcqz
INSERT
Connected to 192.168.50.106:10800
nkkrsplvfvnpaxcgrgdeuqxhxgbfdfuxzwqprzlyzuwngctlzeqrnazinkogoaqcrahnulgapwnnjldafhiyedpyhtexhbfymhn
INSERT
Connected to 192.168.50.106:10800
btqdzyqnexuvdglmopoiedjvxsnpspcsutvbicxaolxfuomksmvjtkyitzyfzllzukcukypttjzqqwvczglpxrstvruwpouempn
INSERT
Connected to 192.168.50.106:10800
eaujimzxedqdvakrdgjgwfkbkwaqtuflveblqcdrjvcgjibokswjxctrqsfkzvypditebwzwpzoxxtlaefxixegobixnguriotj
INSERT
Connected to 192.168.50.106:10800
zwtujlpgubnxsympstgensowrgglslbiplwmktbhoynvthcuwgwozidrikubqbsdjcfopcjqephutewyvlxjkpwwaakqwhfygqu
INSERT
Connected to 192.168.50.106:10800
ahvgtavnwukpjwgnjhwvuujfhkqzczyjaktlychridnaegkaxeffyanaxwsbvzwwocmgpxzstdwotmjurgxaenrnignvmavknxs
INSERT
Connected to 192.168.50.106:10800
xfmgaogjveltcbkbwsrlxpkbbphgfmswtrlmsnajwwjersxmebznobzdhkkenvawadwecpmvtuioppshstmuzehjlhfthlzypfw
INSERT
Connected to 192.168.50.106:10800
repofvdfjuuggzpwehidzgqorwweckiymzshikctkpzlybtswuwnazvmpcjxygjvxlmtyivmhgofpbeyiezkmnfxybikidwoqag
INSERT
Connected to 192.168.50.106:10800
stwsykcntmtmopxlywhhhlyklrletofkafedrwjdrgmndfsoxlkehjnlcpegylbtcnuyazhszoupkmezsnfiqlfaivhfpgjbnsl
INSERT
Connected to 192.168.50.106:10800
gkkufqbtaefbqrosfxfnfvpiucgqmipccfatrtajohrbqktjwmsxcnpykshjxftgowvwkcukbgrbamndrscrqkawkpcrwbqxvvx
INSERT
Connected to 192.168.50.106:10800
vbxjukcezwmhpjcpxlvyknmwoyxwdnvjgnpyqquxlfzlcwkefebrhomwrdhivzctktlrckktbhdvyhexswemmckbzrygzfbzllp
INSERT
Connected to 192.168.50.106:10800
dvjkqcxovijkdaftrerlwtjoxjviklpdhfrhbqqopdegarlgojvpsenepkprsbdcaiuowkihcexgyvoorkjrmiicobrkkuwrmhb
INSERT
Connected to 192.168.50.106:10800
rgsxplyhgbjhbzgkvsytcefwfdsknfnuavtanoqyfupmendojvunmnnorvqseipxdnbrhspomokkmgskzlpvmkhxvlwnhylxcnc
INSERT
Connected to 192.168.50.106:10800
pteybympxpmfsvkrzxsksmkszjybijwtghazafelueceevyaogavrklwoonuzugeamqgquweooygveiujejxagyilmghwdhdvpv
Traceback (most recent call last):
  File "test_insert_update.py", line 48, in 
result_EXIST = ignite_client.sql(query_str='SELECT COUNT(*) FROM TEST WHERE 
ID = ?', query_args=[i])
  File "/usr/local/lib/python3.6/site-packages/pyignite/client.py", line 404, 
in sql
raise SQLError(result.message)
pyignite.exceptions.SQLError: Failed to execute SQL query. General error: 
"java.lang.NullPointerException" [5-197]



[dbutkovic@incumbosstest06 python]$ python3.6 test_insert_update.py
Connected to 192.168.50.106:10800
nwkibmrhhbdgkgnaymzeyfbmeifbivxkzsdfvriwvmdtkgisfmgecilqxflkkqzztpviouslxunwxnygihlijopysupfkblghus
INSERT
Connected to 192.168.50.106:10800
digaffeohkpwnrscfqozxyvumvvjtzouiracvrnicdawwqqvtnzpjmjnabaygefxrcmpughveybmsfcexkunqxgubspfjijparv
INSERT
Connected to 192.168.50.106:10800
fwxjatjrtwydyqelxfewsabzknfckdboyswymskjsljptcwuqcltxeyybsppvvvtfhvbpcnckmpcythzvtdonuzjlrrvapnycpr
INSERT
Connected to 192.168.50.106:10800
labicsolxbrzumtatjihufwiucnkgjdrhwdqlpcwqoppntgdmfpibnsdxgihejmhguzckyowqqsielzkrkazkfrvxymydrdzpdk
INSERT
Connected to 192.168.50.106:10800
shndfldkqpqnltncyiflwgvpimaesotpphjtugyvfwdverjwsvjleswdfrkvpjotrtooxalbdubtiredyihjkpfartnjlwqunkw
INSERT
Connected to 192.168.50.106:10800
gdtrdsrdplzbrcnaeekwcapeukjdxonnfmivtfrnpfhsqkpgyxykqqsfempnxxleivhadqnchuzpkpoabreczxlnrroeqodtfds
INSERT
Connected to 192.168.50.106:10800
zovdjlqqenqouhggingtmumoqjqrwnrtpgfpuvdqtacmobnzcjdudgwkkhjghgkyumdvzlikkirgkcxbvotnfirnozygvkqchsk
Traceback (most recent call last):
  File "test_insert_update.py", line 48, in 
result_EXIST = ignite_client.sql(query_str='SELECT COUNT(*) FROM TEST WHERE 
ID = ?', query_args=[i])
  File "/usr/local/lib/python3.6/site-packages/pyignite/client.py", line 404, 
in sql
raise SQLError(result.message)
pyignite.exceptions.SQLError: Failed to execute SQL query. General error: 
"java.lang.NullPointerException" [5-197]
[dbutkovic@incumbosstest06 python]$
[dbutkovic@incumbosstest06 python]$





[15:38:03,379][SEVERE][client-connector-#67%UMBOSS%][ClientListenerNioListener] 
Failed to process client request 
[req=o.a.i.i.processors.platform.client.cache.ClientCacheSqlFieldsQueryRequest@291c5f1]
class org.apache.ignite.IgniteException: Failed to execute SQL query. General 
error: "java.lang.NullPointerException" [5-197]
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.lambda$executeSelect0$1(IgniteH2Indexing.java:1414)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iter(QueryCursorImpl.java:106)
at 
org.apache.ignite.internal.processors.cache

Re: Ignite client stuck

[ibelyakov]

Do you have server logs for the period of time when you were observing
"Blocked system-critical thread has been detected" error on the client?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: creating table on a pre-existing cache in ignite

[Surkov.Aleksandr]

I was wrong. 
Created a ticket https://issues.apache.org/jira/browse/IGNITE-12816



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to bind to any [host:port] from the range portFrom=10900 , portTo=11000

[AravindJP]

In this case , i am trying to connect to a kubernetes cluster remotely .
Using same IP , i am successfully able to put and get data via 10800




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: [DISCUSSION] Major changes in Ignite in 2020

[Pavel Tupitsyn]

My top priorities:

   - Thin Client API extension: Compute, Continuous Queries, Services
   - .NET Near Cache: soon to come in Thick API, to be investigated for
   Thin Clients
   - .NET Modernization for Ignite 3.0: drop legacy .NET Framework support,
   target .NET Standard 2.0, add nullable annotations to the API


On Fri, Mar 20, 2020 at 5:23 AM Saikat Maitra 
wrote:

> Hi Denis,
>
> Thank you for sharing the list of top changes. The list looks good.
>
> I wanted to share that efforts regarding IEP-36 is already underway and
> there are also open PRs under review and working through review feedback.
> One of the area that we are focussing is first we will merge changes in
> ignite-extensions repo before removing the specific migrated module from
> ignite repo.
>
> There are also contribution from community on bug fixes in
> ignite-extensions repo as well which we are verifying and merging in
> ignite-extensions repo after running through CI pipeline in teamcity.
>
> I like the focus area on docs and I really like the Apache Ignite Usecases
> page https://ignite.apache.org/provenusecases.html,  I would like to
> suggest if we can add a page like powered by Apache Ignite and list few Org
> who are already using Apache Ignite in prod.
>
> Something similar to this page https://flink.apache.org/poweredby.html
>
> Regards,
> Saikat
>
>
>
>
>
>
> On Thu, Mar 19, 2020 at 1:44 PM Denis Magda  wrote:
>
>> My top list of changes is as follows:
>>
>>- Feature: New lightweight Apache Ignite website with advanced search
>>engine optimizations and updated technical content. Why? Much better
>>discoverability of Ignite via search engines like Google to let many more
>>application developers learn about Ignite existence. This change is to be
>>brought to live soon:
>>
>> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Website-New-Look-td46324.html
>>
>>
>>- Feature: New Ignite documentation on a new platform and with a new
>>structure. Why? Ignite documentation has to help new application 
>> developers
>>to get up and running as quickly as possible, it also has to become a
>>primary source that answers most of the questions. Our current docs have a
>>lot of gaps: https://issues.apache.org/jira/browse/IGNITE-7595
>>
>>
>>- Process Change: to be successful with the point above,
>>documentation should be created/updated before we close a JIRA ticket for
>>code/API/feature contribution. Why? First, application developers learn
>>Ignite and create their Ignite-apps referring to API reference and
>>technical documentation (and not to the source code), thus, documentation
>>needs to be treated as an integral part of the whole project. Second, 
>> while
>>writing a new documentation paragraph we could discover incompleteness of 
>> a
>>fix/feature or usability issues before the change is released publicly.
>>
>>
>>- Feature: complete the modularization project by defining the Ignite
>>core that will be released separately from Ignite extensions. The 'why' is
>>written here:
>>
>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization
>>
>> -
>> Denis
>>
>>
>> On Thu, Mar 19, 2020 at 11:21 AM Denis Magda  wrote:
>>
>>> Dear Ignite community,
>>>
>>> Many of us want to see where Ignite is heading and ask for some sort of
>>> a 2020 course/plan/roadmap and a predictable schedule of major releases.
>>> Also, there are intentions to enhance some internal processes and
>>> collaboration approaches.
>>>
>>> Let's start moving in that direction by defining 3-5 major changes you
>>> would like to contribute this year personally or will be glad to drive
>>> (like processes changes) and work together with someone else. Dear, Ignite
>>> user community, please share your suggestions as well.
>>>
>>> Note, let's use this thread to collect major
>>> topics/directions/features/changes. Just respond with your proposals. Don't
>>> go into arguments if you don't agree with someone's opinions. Once the
>>> topics are collected, we'll create a wiki page and, most likely, will start
>>> working through specific items in focus groups and only then lay out a
>>> cohesive plan with some dates.
>>>
>>> -
>>> Denis
>>>
>>