Re: Do I need Map entry classes in Ignite's classpath?

[Andrew Munn]

How can you update those k,v classes?  Do you have to take the cluster down
or can you do a rolling upgrade somehow?

On Mon, Jun 8, 2020 at 7:37 AM Ilya Kasnacheev 
wrote:

> Hello!
>
> If these classes are used as key or value types, then yes. Key/value types
> are not peer loaded. Otherwise, you just need to enable peer class loading.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 8 июн. 2020 г. в 05:05, Andrew Munn :
>
>> Is there ever any reason for the classes of Objects being put in the Map
>> to be in the classpath for Ignite?  or does the cluster always handle that
>> automatically?
>>
>> Thanks,
>> Andrew
>>
>

Can you pass host name to ignite visor?

[Andrew Munn]

Is there any way to pass the cluster address to ignitevisorcmd.sh on the
command line or must it be set in the config.xml file used?

Do I need Map entry classes in Ignite's classpath?

[Andrew Munn]

Is there ever any reason for the classes of Objects being put in the Map to
be in the classpath for Ignite?  or does the cluster always handle that
automatically?

Thanks,
Andrew

Re: BinaryObjectException: Conflicting enum values

[Andrew Munn]

So once I insert an instance of a class in a Map I can't change the type of
any existing member variable in the class, even if I clear the map?
Seems like there should be some programatic way to clear any left-over
class metadata/schema if simply clearing the cache won't do it. Right?

On Sat, Jun 6, 2020 at 10:43 AM Denis Magda  wrote:

> You might have hit the following specificity ("Cluster Doesn’t Start After
> Field Type Changes") that happens if you change a type of a field:
> https://www.gridgain.com/docs/latest/perf-troubleshooting-guide/troubleshooting#cluster-doesnt-start-after-field-type-changes
>
> -
> Denis
>
>
> On Fri, Jun 5, 2020 at 10:53 AM Andrew Munn  wrote:
>
>> I'm seeing the same issue as this one
>> <http://apache-ignite-users.70518.x6.nabble.com/Help-needed-with-BinaryObjectException-td22938.html>
>> .
>>
>> I had values in the cache.  I cleared the cache, but did not shutdown the
>> cluster node.  I modified the enums in the class.  Then I repopulated the
>> cache with instances of the updated class.  There must be some way to purge
>> leftover metadata without bringing the cluster down, right?   Can it be
>> purged when the cache is cleared?
>>
>> Thanks
>>
>>

Re: How to get POJOs in Python?

[Andrew Munn]

I have only a few classes but they have a large number of fields.   I will
think about some code generation for Python.

On Fri, Jun 5, 2020 at 12:53 PM Ilya Kasnacheev 
wrote:

> Hello!
>
> I think that people usually have few enough classes so they can define
> them by hand.
>
> Regards.
> --
> Ilya Kasnacheev
>
>
> пт, 5 июн. 2020 г. в 19:48, Andrew Munn :
>
>> That's very helpful.  Thanks.  So it appears if I want to put in an
>> object using Java and consume it using Python I have to define the matching
>> class as done in that example.
>>
>> Do you know how this is being used in practice?  Are people generally
>> kicking off a build job that looks at Java classes and performs code
>> generation to output Python version that get included in libs?
>>
>> On Fri, Jun 5, 2020 at 7:04 AM Ilya Kasnacheev 
>> wrote:
>>
>>> Hello!
>>>
>>> Please take a look at
>>> https://github.com/apache/ignite/blob/master/modules/platforms/python/examples/binary_basics.py
>>>
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>>
>>>
>>> пт, 5 июн. 2020 г. в 01:38, Andrew Munn :
>>>
>>>> Thanks Ilya.  I don't see anything in that post about registering the
>>>> binary type.  I am not defining any tables using SQL.  I'm just
>>>> instantiating POJOs, putting them in the cache and then expecting to get
>>>> them in Python.  Can you tell me what else is required?  Is there some
>>>> process to register the binary type?  How can I view all registered binary
>>>> types?
>>>>
>>>> Thanks!
>>>>
>>>> On Wed, Jun 3, 2020 at 11:59 AM Ilya Kasnacheev <
>>>> ilya.kasnach...@gmail.com> wrote:
>>>>
>>>>> Hello!
>>>>>
>>>>> Have you tried the following example:
>>>>>
>>>>> https://github.com/apache/ignite/blob/master/modules/platforms/python/examples/read_binary.py
>>>>>
>>>>> (yes, it mostly works with tables, but tables and POJOs are mapped in
>>>>> the same fashion).
>>>>>
>>>>> Regards,
>>>>> --
>>>>> Ilya Kasnacheev
>>>>>
>>>>>
>>>>> ср, 3 июн. 2020 г. в 18:54, Andrew Munn :
>>>>>
>>>>>> I'm having the same issues as these guys:
>>>>>>
>>>>>>
>>>>>> http://mail-archives.apache.org/mod_mbox/ignite-user/201901.mbox/%3csn6pr14mb2240feb74bc77de79b54ca67ca...@sn6pr14mb2240.namprd14.prod.outlook.com%3E
>>>>>>
>>>>>>
>>>>>> I would like to put POJOs in a map and get them using pyignite.
>>>>>> Python gives me ParseError('Binary type is not registered'). I was
>>>>>> hoping that Ignite would automatically store any required schema info for
>>>>>> the class so Python could use it. Especially if my simple POJO was 
>>>>>> composed
>>>>>> only of primitives.
>>>>>>
>>>>>> Are there any examples of consuming POJOs from a cache using Python?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>>

BinaryObjectException: Conflicting enum values

[Andrew Munn]

I'm seeing the same issue as this one

.

I had values in the cache.  I cleared the cache, but did not shutdown the
cluster node.  I modified the enums in the class.  Then I repopulated the
cache with instances of the updated class.  There must be some way to purge
leftover metadata without bringing the cluster down, right?   Can it be
purged when the cache is cleared?

Thanks

Re: How to get POJOs in Python?

[Andrew Munn]

That's very helpful.  Thanks.  So it appears if I want to put in an object
using Java and consume it using Python I have to define the matching class
as done in that example.

Do you know how this is being used in practice?  Are people generally
kicking off a build job that looks at Java classes and performs code
generation to output Python version that get included in libs?

On Fri, Jun 5, 2020 at 7:04 AM Ilya Kasnacheev 
wrote:

> Hello!
>
> Please take a look at
> https://github.com/apache/ignite/blob/master/modules/platforms/python/examples/binary_basics.py
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 5 июн. 2020 г. в 01:38, Andrew Munn :
>
>> Thanks Ilya.  I don't see anything in that post about registering the
>> binary type.  I am not defining any tables using SQL.  I'm just
>> instantiating POJOs, putting them in the cache and then expecting to get
>> them in Python.  Can you tell me what else is required?  Is there some
>> process to register the binary type?  How can I view all registered binary
>> types?
>>
>> Thanks!
>>
>> On Wed, Jun 3, 2020 at 11:59 AM Ilya Kasnacheev <
>> ilya.kasnach...@gmail.com> wrote:
>>
>>> Hello!
>>>
>>> Have you tried the following example:
>>>
>>> https://github.com/apache/ignite/blob/master/modules/platforms/python/examples/read_binary.py
>>>
>>> (yes, it mostly works with tables, but tables and POJOs are mapped in
>>> the same fashion).
>>>
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>>
>>>
>>> ср, 3 июн. 2020 г. в 18:54, Andrew Munn :
>>>
>>>> I'm having the same issues as these guys:
>>>>
>>>>
>>>> http://mail-archives.apache.org/mod_mbox/ignite-user/201901.mbox/%3csn6pr14mb2240feb74bc77de79b54ca67ca...@sn6pr14mb2240.namprd14.prod.outlook.com%3E
>>>>
>>>>
>>>> I would like to put POJOs in a map and get them using pyignite.  Python
>>>> gives me ParseError('Binary type is not registered'). I was hoping
>>>> that Ignite would automatically store any required schema info for the
>>>> class so Python could use it. Especially if my simple POJO was composed
>>>> only of primitives.
>>>>
>>>> Are there any examples of consuming POJOs from a cache using Python?
>>>>
>>>> Thanks
>>>>
>>>>

Re: How to get POJOs in Python?

[Andrew Munn]

Thanks Ilya.  I don't see anything in that post about registering the
binary type.  I am not defining any tables using SQL.  I'm just
instantiating POJOs, putting them in the cache and then expecting to get
them in Python.  Can you tell me what else is required?  Is there some
process to register the binary type?  How can I view all registered binary
types?

Thanks!

On Wed, Jun 3, 2020 at 11:59 AM Ilya Kasnacheev 
wrote:

> Hello!
>
> Have you tried the following example:
>
> https://github.com/apache/ignite/blob/master/modules/platforms/python/examples/read_binary.py
>
> (yes, it mostly works with tables, but tables and POJOs are mapped in the
> same fashion).
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 3 июн. 2020 г. в 18:54, Andrew Munn :
>
>> I'm having the same issues as these guys:
>>
>>
>> http://mail-archives.apache.org/mod_mbox/ignite-user/201901.mbox/%3csn6pr14mb2240feb74bc77de79b54ca67ca...@sn6pr14mb2240.namprd14.prod.outlook.com%3E
>>
>>
>> I would like to put POJOs in a map and get them using pyignite.  Python
>> gives me ParseError('Binary type is not registered'). I was hoping that
>> Ignite would automatically store any required schema info for the class so
>> Python could use it. Especially if my simple POJO was composed only of
>> primitives.
>>
>> Are there any examples of consuming POJOs from a cache using Python?
>>
>> Thanks
>>
>>

How to get POJOs in Python?

[Andrew Munn]

I'm having the same issues as these guys:

http://mail-archives.apache.org/mod_mbox/ignite-user/201901.mbox/%3csn6pr14mb2240feb74bc77de79b54ca67ca...@sn6pr14mb2240.namprd14.prod.outlook.com%3E


I would like to put POJOs in a map and get them using pyignite.  Python
gives me ParseError('Binary type is not registered'). I was hoping that
Ignite would automatically store any required schema info for the class so
Python could use it. Especially if my simple POJO was composed only of
primitives.

Are there any examples of consuming POJOs from a cache using Python?

Thanks

Re: Can you create a cache using Ignite Visor CLI?

[Andrew Munn]

It looks like control.sh won't create caches either.  How can they be
created by a utility in the shell?

On Tue, May 19, 2020 at 3:58 PM akorensh  wrote:

> yes. That is correct:
> https://apacheignite-tools.readme.io/docs/command-line-interface
>
> use the "help cache" command inside the visor to see all of the
> capabilities.
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Can you create a cache using Ignite Visor CLI?

[Andrew Munn]

It looks like the Visor CLI can only operate on existing caches, not create
new ones.  Is that correct?

Re: ERROR: h2 Unsupported connection setting "MULTI_THREADED"

[Andrew Munn]

Yes I'm using spring boot.  Can Ignite be updated to work with the latest
h2?

On Fri, Feb 21, 2020, 6:25 AM Ilya Kasnacheev 
wrote:

> Hello!
>
> I've heard about issues with e.g. Spring Boot overriding h2 database
> version and breaking our runtime. I'm not sure who else does that.
>
> Regards,
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> Ilya Kasnacheev
>
>
> чт, 20 февр. 2020 г. в 19:24, Andrew Munn :
>
>> Thanks.  Adding this runtime dependency to build.gradle fixed it:
>>
>> dependencies {
>> runtime("com.h2database:h2:1.4.197")
>> ...
>> compile group: 'org.apache.ignite', name: 'ignite-spring', version:
>> '2.7.6'
>> compile group: 'org.apache.ignite', name: 'ignite-core', version:
>> '2.7.6'
>> }
>>
>> But I suspect this should be getting enforced automatically if using h2
>> ver1.4.200 breaks something.  Am I specifying the Ignite dependency
>> incorrectly?
>>
>>
>> On Thu, Feb 20, 2020 at 4:08 AM Taras Ledkov 
>> wrote:
>>
>>> Hi,
>>>
>>> Ignite uses H2 version 1.4.197 (see [1]).
>>>
>>>
>>> [1]. https://github.com/apache/ignite/blob/master/parent/pom.xml#L74
>>>
>>> On 20.02.2020 4:36, Andrew Munn wrote:
>>> > I'm building/running my client app w/Gradle and I'm seeing this
>>> > error.  Am I overloading the Ingite H2 fork with the real H2 or
>>> > something?  It appears I have the latest h2:
>>> >
>>> > [.gradle]$ find ./ -name *h2*
>>> > ./caches/modules-2/metadata-2.82/descriptors/com.h2database
>>> > ./caches/modules-2/metadata-2.82/descriptors/com.h2database/h2
>>> > ./caches/modules-2/files-2.1/com.h2database
>>> > ./caches/modules-2/files-2.1/com.h2database/h2
>>> >
>>> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/6178ecda6e9fea8739a3708729efbffd88be43e3/h2-1.4.200.pom
>>> >
>>> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/f7533fe7cb8e99c87a43d325a77b4b678ad9031a/h2-1.4.200.jar
>>> >
>>> >
>>> >
>>> > 2020-02-19 19:59:28.229 ERROR 102356 --- [   main]
>>> > o.a.i.internal.IgniteKernal%dev-cluster  : Exception during start
>>> > processors, node will be stopped and close connections
>>> > org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
>>> > to initialize system DB connection:
>>> >
>>> jdbc:h2:mem:b52dce26-ba01-4051-9130-e087e19fab4f;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.GridH2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine
>>> > at
>>> >
>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.systemConnection(IgniteH2Indexing.java:434)
>>>
>>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>>> > at
>>> >
>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:699)
>>>
>>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>>> > at
>>> >
>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSchema0(IgniteH2Indexing.java:646)
>>>
>>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>>> > at
>>> >
>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:3257)
>>>
>>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>>> > at
>>> >
>>> org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:248)
>>>
>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>> > at
>>> >
>>> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1700)
>>>
>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>> > at
>>> > org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1017)
>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>> > at
>>> >
>>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
>>>
>>> > ~[ignite-core-2.7.6.

Re: ERROR: h2 Unsupported connection setting "MULTI_THREADED"

[Andrew Munn]

Thanks.  Adding this runtime dependency to build.gradle fixed it:

dependencies {
runtime("com.h2database:h2:1.4.197")
...
compile group: 'org.apache.ignite', name: 'ignite-spring', version:
'2.7.6'
compile group: 'org.apache.ignite', name: 'ignite-core', version:
'2.7.6'
}

But I suspect this should be getting enforced automatically if using h2
ver1.4.200 breaks something.  Am I specifying the Ignite dependency
incorrectly?


On Thu, Feb 20, 2020 at 4:08 AM Taras Ledkov  wrote:

> Hi,
>
> Ignite uses H2 version 1.4.197 (see [1]).
>
>
> [1]. https://github.com/apache/ignite/blob/master/parent/pom.xml#L74
>
> On 20.02.2020 4:36, Andrew Munn wrote:
> > I'm building/running my client app w/Gradle and I'm seeing this
> > error.  Am I overloading the Ingite H2 fork with the real H2 or
> > something?  It appears I have the latest h2:
> >
> > [.gradle]$ find ./ -name *h2*
> > ./caches/modules-2/metadata-2.82/descriptors/com.h2database
> > ./caches/modules-2/metadata-2.82/descriptors/com.h2database/h2
> > ./caches/modules-2/files-2.1/com.h2database
> > ./caches/modules-2/files-2.1/com.h2database/h2
> >
> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/6178ecda6e9fea8739a3708729efbffd88be43e3/h2-1.4.200.pom
> >
> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/f7533fe7cb8e99c87a43d325a77b4b678ad9031a/h2-1.4.200.jar
> >
> >
> >
> > 2020-02-19 19:59:28.229 ERROR 102356 --- [   main]
> > o.a.i.internal.IgniteKernal%dev-cluster  : Exception during start
> > processors, node will be stopped and close connections
> > org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> > to initialize system DB connection:
> >
> jdbc:h2:mem:b52dce26-ba01-4051-9130-e087e19fab4f;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.GridH2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine
> > at
> >
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.systemConnection(IgniteH2Indexing.java:434)
>
> > ~[ignite-indexing-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:699)
>
> > ~[ignite-indexing-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSchema0(IgniteH2Indexing.java:646)
>
> > ~[ignite-indexing-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:3257)
>
> > ~[ignite-indexing-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:248)
>
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1700)
>
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1017)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
>
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
>
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
>
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at org.apache.ignite.Ignition.start(Ignition.java:348)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> >
> com.centiva.ig.etl.loader.LoaderApplication.main(LoaderApplication.java:14)
> > ~[main/:na]
> > Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException:
> > Unsupported connection setting "MULTI_THREADED" [90113-200]
> > at
> > org.h2.message.DbException.getJdbcSQLException(DbException.java:622)
> > ~[h2-1.4.200.jar:1.4.200]
>
> --
> Taras Ledkov
> Mail-To: tled...@gridgain.com
>
>

Re: tailing Ignite cache for events?

[Andrew Munn]

Can you easily register a continuous query using Visor or something?  I
would like to see all cache activity including the before and after
toString() representation of objects being modified.  I just want to
eyeball it during development, not pipe it into another application etc

On Wed, Feb 19, 2020 at 6:03 PM Evgenii Zhuravlev 
wrote:

> Hi,
>
> Usually it's Continuous Queries:
> https://www.gridgain.com/docs/latest/developers-guide/key-value-api/continuous-queries,
> but it depends on your use case. What do you want to do with these events?
>
> Best Regards,
> Evgenii
>
> ср, 19 февр. 2020 г. в 14:54, Andrew Munn :
>
>> What's the best way to watch a cache for insert/update/delete events?
>>
>

ERROR: h2 Unsupported connection setting "MULTI_THREADED"

[Andrew Munn]

I'm building/running my client app w/Gradle and I'm seeing this error.  Am
I overloading the Ingite H2 fork with the real H2 or something?  It appears
I have the latest h2:

[.gradle]$ find ./ -name *h2*
./caches/modules-2/metadata-2.82/descriptors/com.h2database
./caches/modules-2/metadata-2.82/descriptors/com.h2database/h2
./caches/modules-2/files-2.1/com.h2database
./caches/modules-2/files-2.1/com.h2database/h2
./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/6178ecda6e9fea8739a3708729efbffd88be43e3/h2-1.4.200.pom
./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/f7533fe7cb8e99c87a43d325a77b4b678ad9031a/h2-1.4.200.jar



2020-02-19 19:59:28.229 ERROR 102356 --- [   main]
o.a.i.internal.IgniteKernal%dev-cluster  : Exception during start
processors, node will be stopped and close connections
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
initialize system DB connection:
jdbc:h2:mem:b52dce26-ba01-4051-9130-e087e19fab4f;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.GridH2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.systemConnection(IgniteH2Indexing.java:434)
~[ignite-indexing-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:699)
~[ignite-indexing-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSchema0(IgniteH2Indexing.java:646)
~[ignite-indexing-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:3257)
~[ignite-indexing-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:248)
~[ignite-core-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1700)
~[ignite-core-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1017)
~[ignite-core-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
~[ignite-core-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
~[ignite-core-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
~[ignite-core-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
~[ignite-core-2.7.6.jar:2.7.6]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
~[ignite-core-2.7.6.jar:2.7.6]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
~[ignite-core-2.7.6.jar:2.7.6]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
~[ignite-core-2.7.6.jar:2.7.6]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
~[ignite-core-2.7.6.jar:2.7.6]
at org.apache.ignite.Ignition.start(Ignition.java:348)
~[ignite-core-2.7.6.jar:2.7.6]
at
com.centiva.ig.etl.loader.LoaderApplication.main(LoaderApplication.java:14)
~[main/:na]
Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported
connection setting "MULTI_THREADED" [90113-200]
at
org.h2.message.DbException.getJdbcSQLException(DbException.java:622)
~[h2-1.4.200.jar:1.4.200]

tailing Ignite cache for events?

[Andrew Munn]

What's the best way to watch a cache for insert/update/delete events?

visor mcompact command?

[Andrew Munn]

what's mcompact about?  it says only this:

visor> help mcompact
 mcompact  Finds and fills gap in Visor console memory variables.

What are these gaps?

Ignite Web Console requires root?

[Andrew Munn]

https://www.gridgain.com/docs/web-console/latest/deploying-web-console

says:

By default, the Web Console control process will listen for incoming
connections on port 3000, requiring it and its various child processes to
run with root-level privileges on UNIX-like operating systems (e.g., Linux
and MacOS).

Why root?? 3000 > 1024. Nobody should want this agent running as root,
right?

Best GUI for viewing caches

[Andrew Munn]

What generally works best for querying and viewing/updating cached
objects?  Some JDBC client or does some memcached one work better?

Accessing Ignite from MS Excel

[Andrew Munn]

What's the best way to access Ignite data from MS Excel?  It looks like I 
could use the ODBC driver but I'd like updates pushed into Excel, not 
Excel polling for updates.  I could use Excel-DNA and use the C# client.  
Is there a better way?