Re: Node starting error

[kay]

Hello, 
Here is my configuration file

NexusCache-config.xml

  

Thank you!!



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

Re: Execution of local SqlFieldsQuery on client node disallowed

[Denis Magda]

Narges,

Also, keep in mind that if a local query is executed over a partitioned
table and it happens that partitions rebalancing starts, the local query
might return a wrong result (if partitions the query was executed over were
rebalanced to another node during the query execution time). To address
this:

   1. Execute the local query inside of an affinityCall/Run function (
   
https://ignite.apache.org/docs/latest/distributed-computing/collocated-computations#colocating-by-key).
   Those functions don't let partitions be evicted until the function
   execution completes.
   2. Don't use the local queries, let the Ignite SQL engine to run
   standard queries, and to take care of possible optimizations.


-
Denis


On Mon, Oct 26, 2020 at 8:50 AM Ilya Kasnacheev 
wrote:

> Hello!
>
> You are using an Ignite Thick Client driver. As its name implies, it will
> start a local client node and then connect to it, without the option of
> doing local queries.
>
> You need to use Ignite Thin JDBC driver: jdbc:ignite:thin://
> Then you can do local queries.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> сб, 24 окт. 2020 г. в 16:04, narges saleh :
>
>> Hello Ilya
>> Yes, it happens all the time. It seems ignite forces the "client"
>> establishing the jdbc connection into a client mode, even if I set
>> client=false.  The sample code and config are attached. The question is how
>> do I force JDBC connections from a server node.
>> thanks.
>>
>> On Fri, Oct 23, 2020 at 10:31 AM Ilya Kasnacheev <
>> ilya.kasnach...@gmail.com> wrote:
>>
>>> Hello!
>>>
>>> Does this happen every time? If so, do you have a reproducer for the
>>> issue?
>>>
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>>
>>>
>>> пт, 23 окт. 2020 г. в 13:06, narges saleh :
>>>
 Denis -- Just checked. I do specify my services to be deployed on
 server nodes only. Why would ignite think that I am running my code on a
 client node?

 On Fri, Oct 23, 2020 at 3:50 AM narges saleh 
 wrote:

> Hi Denis
> What would make an ignite node a client node? The code is invoked via
> an ignite service deployed on each node and I am not setting the client
> mode anywhere. The code sets the jdbc connection to local and tries to
> execute a sql code on the node in some interval. By the way, I didn't know
> one could deploy a service on client nodes. Do I need to explicitly mark a
> node as a server node when deploying a service?
> thanks
>
> On Thu, Oct 22, 2020 at 9:42 PM Denis Magda  wrote:
>
>> The error message says you're attempting to run the query on a client
>> node. If that's the case (if the service is deployed on the client node),
>> then the local flag has no effect because client nodes don't keep your 
>> data
>> locally but rather consume it from servers.
>>
>> -
>> Denis
>>
>>
>> On Thu, Oct 22, 2020 at 6:26 PM narges saleh 
>> wrote:
>>
>>> Hi All,
>>> I am trying to execute a sql query via a JDBC  connection on the
>>> service node (the query is run via a service), but I am getting 
>>> *Execution
>>> of local SqlFieldsQuery on client node disallowed.*
>>> *The JDBC connection has the option local=true as I want to run the
>>> query on the data on the local node only.*
>>> *Any idea why I am getting this error?*
>>>
>>> *thanks.*
>>>
>>

Re: Client App Object Allocation Rate

[ssansoy]

Hi, here's an example (using YourKit rather than JFR).

Apologies, I had to obfuscate some of the company specific information. This
shows a window of about 10 seconds of allocations

 

Looks like these come from GridDiscoveryManager - creating a new string
every time. This happens several times per second it seems. Some of these
mention other client nodes - so some other production app in our firm, that
uses the cluster, has an impact on a different production app. Is there any
way to turn this off? Each of our clients need to be isolated such that
other client apps do not interfere in any way

Also


 

These update messages seem to come in even though metricsEnabled is turned
off on the client (not specificied).







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

Re: Node starting error

[akurbanov]

Hello,

Could you please post full node configuration?




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

Re: Execution of local SqlFieldsQuery on client node disallowed

[Ilya Kasnacheev]

Hello!

You are using an Ignite Thick Client driver. As its name implies, it will
start a local client node and then connect to it, without the option of
doing local queries.

You need to use Ignite Thin JDBC driver: jdbc:ignite:thin://
Then you can do local queries.

Regards,
-- 
Ilya Kasnacheev


сб, 24 окт. 2020 г. в 16:04, narges saleh :

> Hello Ilya
> Yes, it happens all the time. It seems ignite forces the "client"
> establishing the jdbc connection into a client mode, even if I set
> client=false.  The sample code and config are attached. The question is how
> do I force JDBC connections from a server node.
> thanks.
>
> On Fri, Oct 23, 2020 at 10:31 AM Ilya Kasnacheev <
> ilya.kasnach...@gmail.com> wrote:
>
>> Hello!
>>
>> Does this happen every time? If so, do you have a reproducer for the
>> issue?
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> пт, 23 окт. 2020 г. в 13:06, narges saleh :
>>
>>> Denis -- Just checked. I do specify my services to be deployed on server
>>> nodes only. Why would ignite think that I am running my code on a client
>>> node?
>>>
>>> On Fri, Oct 23, 2020 at 3:50 AM narges saleh 
>>> wrote:
>>>
 Hi Denis
 What would make an ignite node a client node? The code is invoked via
 an ignite service deployed on each node and I am not setting the client
 mode anywhere. The code sets the jdbc connection to local and tries to
 execute a sql code on the node in some interval. By the way, I didn't know
 one could deploy a service on client nodes. Do I need to explicitly mark a
 node as a server node when deploying a service?
 thanks

 On Thu, Oct 22, 2020 at 9:42 PM Denis Magda  wrote:

> The error message says you're attempting to run the query on a client
> node. If that's the case (if the service is deployed on the client node),
> then the local flag has no effect because client nodes don't keep your 
> data
> locally but rather consume it from servers.
>
> -
> Denis
>
>
> On Thu, Oct 22, 2020 at 6:26 PM narges saleh 
> wrote:
>
>> Hi All,
>> I am trying to execute a sql query via a JDBC  connection on the
>> service node (the query is run via a service), but I am getting 
>> *Execution
>> of local SqlFieldsQuery on client node disallowed.*
>> *The JDBC connection has the option local=true as I want to run the
>> query on the data on the local node only.*
>> *Any idea why I am getting this error?*
>>
>> *thanks.*
>>
>

Re: alter table logging slow

[Ilya Kasnacheev]

Hello!

Usually it is I/O bound, meaning, you can only speed it up by having more,
faster disks.

However, in some cases, tuning persistence settings such as checkpoint
frequency, checkpoint page buffer size and checkpoint thread pool size may
help. You can also try the direct-io module, but you may see mixed results.

Regards,
-- 
Ilya Kasnacheev


пн, 26 окт. 2020 г. в 16:00, Matteo Durighetto :

> Hello Ilya ,
>thank you for your answer, it's make sense. I see
> the class called it's changewal and as you wrote, it's probably call a
> flush of the cache .
> Is it possible to speed up the flush to disk with more threads ? I think
> they are controlled by system pool or is it another parameter?
>
> Kind regards
>
> Matteo Durighetto
>
>
>
>
>
> Il giorno lun 26 ott 2020 alle ore 13:05 Ilya Kasnacheev <
> ilya.kasnach...@gmail.com> ha scritto:
>
>> Hello!
>>
>> I guess it has to write all the data to disk. After 'alter table logging'
>> returns, you are guaranteed consistency on this table, meaning all of its
>> pages have to be persisted to disk. Obviously, it may take a lot of time if
>> you have many gigabytes to flush.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> пн, 26 окт. 2020 г. в 11:59, Matteo Durighetto :
>>
>>> Hello,
>>>I found an expected behaviour on apache ignite.
>>> If you do ( TABLE partitioned with 1 backup and ATOMIC mode ):
>>>
>>> alter table ..  nologging;
>>> set stream on ;
>>> .. loading a lot of data with jdbc ..
>>> .. close connection to flush data ..
>>> .. reopen connection..
>>> alter table .. logging
>>>
>>> The last step "alter table logging" writes a lot of data and it's
>>> "slow", if we load the table
>>> with 26 threads in about 10 minute and every thread uses a dedicated
>>> partition, , the nologging phase is around 11 minutes.
>>>
>>> I would like to understand what it is doing and how to speed up the
>>> process, I try to understand from SqlAlterTableCommand.java what it's
>>> doing, but it's not straightforward.
>>>
>>> Kind Regards
>>>
>>> Matteo Durighetto
>>>
>>>
>>>
>>>
>>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>>>
>>> M I R I A D E - P L A Y  T H E  C H A N G E
>>>
>>> Via Castelletto 11, 36016 Thiene VI
>>> Tel. 0445030111 - Fax 0445030100
>>> Website: http://www.miriade.it/
>>>
>>> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 
>>> .
>>> *Clausola di riservatezza. *Le informazioni contenute o allegate al 
>>> presente messaggio sono dirette unicamente al Destinatario sopra indicato. 
>>> In caso di ricezione da parte di persona diversa è vietato qualunque tipo 
>>> di distribuzione o copia. Chiunque riceva questa comunicazione per errore è 
>>> tenuto ad informare immediatamente il mittente e a distruggere il 
>>> messaggio. Si informa che un eventuale trattamento di dati personali 
>>> contenuti nella presente comunicazione, in assenza dei presupposti di 
>>> liceità previsti dall’art 6 Reg. 679/16 (GDPR), è punito secondo la 
>>> normativa vigente in materia. Si informa che la casella di posta 
>>> elettronica è di titolarità di Miriade S.r.l. è concessa ai propri 
>>> dipendenti e collaboratori esclusivamente per rendere la prestazione 
>>> lavorativa.
>>>
>>> *Confidentiality notice.* This email and any files transmitted with it are 
>>> confidential and intended solely for the use of the individual or entity to 
>>> whom they are addressed. This message contains confidential information and 
>>> is intended only for the individual named. If you are not the named 
>>> addressee you should not disseminate, distribute or copy this e-mail. 
>>> Please notify the sender immediately by e-mail if you have received this 
>>> e-mail by mistake and delete this e-mail from your system. Any form of data 
>>> processing in absence of the lawfulness principles provided by the art. 6 
>>> of Reg. UE 697/16 (GDPR) is prohibited and it will be punishable by law. 
>>> This e-mail address is property of Miriade S.r.l. and it is used by its 
>>> employees solely for working.
>>>
>>>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
> M I R I A D E - P L A Y  T H E  C H A N G E
>
> Via Castelletto 11, 36016 Thiene VI
> Tel. 0445030111 - Fax 0445030100
> Website: http://www.miriade.it/
>
> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
> *Clausola di riservatezza. *Le informazioni contenute o allegate al presente 
> messaggio sono dirette unicamente al Destinatario sopra indicato. In caso di 
> ricezione da parte di persona diversa è vietato qualunque tipo di 
> distribuzione o copia. Chiunque riceva questa comunicazione per errore è 
> tenuto ad informare immediatamente il mittente e a distruggere il messaggio. 
> Si informa che un eventuale trattamento di dati personali contenuti nella 
> presente comunicazione, in assenza dei presupposti di liceità previsti 
> dall’art 6 Reg. 679/16 (GDPR), è punito secondo la normativa vigente 

Re: alter table logging slow

[Matteo Durighetto]

Hello Ilya ,
   thank you for your answer, it's make sense. I see
the class called it's changewal and as you wrote, it's probably call a
flush of the cache .
Is it possible to speed up the flush to disk with more threads ? I think
they are controlled by system pool or is it another parameter?

Kind regards

Matteo Durighetto





Il giorno lun 26 ott 2020 alle ore 13:05 Ilya Kasnacheev <
ilya.kasnach...@gmail.com> ha scritto:

> Hello!
>
> I guess it has to write all the data to disk. After 'alter table logging'
> returns, you are guaranteed consistency on this table, meaning all of its
> pages have to be persisted to disk. Obviously, it may take a lot of time if
> you have many gigabytes to flush.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 26 окт. 2020 г. в 11:59, Matteo Durighetto :
>
>> Hello,
>>I found an expected behaviour on apache ignite.
>> If you do ( TABLE partitioned with 1 backup and ATOMIC mode ):
>>
>> alter table ..  nologging;
>> set stream on ;
>> .. loading a lot of data with jdbc ..
>> .. close connection to flush data ..
>> .. reopen connection..
>> alter table .. logging
>>
>> The last step "alter table logging" writes a lot of data and it's "slow",
>> if we load the table
>> with 26 threads in about 10 minute and every thread uses a dedicated
>> partition, , the nologging phase is around 11 minutes.
>>
>> I would like to understand what it is doing and how to speed up the
>> process, I try to understand from SqlAlterTableCommand.java what it's
>> doing, but it's not straightforward.
>>
>> Kind Regards
>>
>> Matteo Durighetto
>>
>>
>>
>>
>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>>
>> M I R I A D E - P L A Y  T H E  C H A N G E
>>
>> Via Castelletto 11, 36016 Thiene VI
>> Tel. 0445030111 - Fax 0445030100
>> Website: http://www.miriade.it/
>>
>> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
>> *Clausola di riservatezza. *Le informazioni contenute o allegate al presente 
>> messaggio sono dirette unicamente al Destinatario sopra indicato. In caso di 
>> ricezione da parte di persona diversa è vietato qualunque tipo di 
>> distribuzione o copia. Chiunque riceva questa comunicazione per errore è 
>> tenuto ad informare immediatamente il mittente e a distruggere il messaggio. 
>> Si informa che un eventuale trattamento di dati personali contenuti nella 
>> presente comunicazione, in assenza dei presupposti di liceità previsti 
>> dall’art 6 Reg. 679/16 (GDPR), è punito secondo la normativa vigente in 
>> materia. Si informa che la casella di posta elettronica è di titolarità di 
>> Miriade S.r.l. è concessa ai propri dipendenti e collaboratori 
>> esclusivamente per rendere la prestazione lavorativa.
>>
>> *Confidentiality notice.* This email and any files transmitted with it are 
>> confidential and intended solely for the use of the individual or entity to 
>> whom they are addressed. This message contains confidential information and 
>> is intended only for the individual named. If you are not the named 
>> addressee you should not disseminate, distribute or copy this e-mail. Please 
>> notify the sender immediately by e-mail if you have received this e-mail by 
>> mistake and delete this e-mail from your system. Any form of data processing 
>> in absence of the lawfulness principles provided by the art. 6 of Reg. UE 
>> 697/16 (GDPR) is prohibited and it will be punishable by law. This e-mail 
>> address is property of Miriade S.r.l. and it is used by its employees solely 
>> for working.
>>
>>

-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

M I R I A 
D E - P L A Y  T H E  C H A N G E 


Via Castelletto 11, 36016 Thiene VI
Tel. 0445030111 - Fax 0445030100 
Website: http://www.miriade.it/ 










. . . . . . . . . . . . . . . . . . . . . 
. . . . . . . . . . . . . . . . . . 
*Clausola di riservatezza. *Le 
informazioni contenute o allegate al presente messaggio sono dirette 
unicamente al Destinatario sopra indicato. In caso di ricezione da parte di 
persona diversa è vietato qualunque tipo di distribuzione o copia. Chiunque 
riceva questa comunicazione per errore è tenuto ad informare immediatamente 
il mittente e a distruggere il messaggio. Si informa che un eventuale 
trattamento di dati personali contenuti nella presente comunicazione, in 
assenza dei presupposti di liceità previsti dall’art 6 Reg. 679/16 (GDPR), 
è punito secondo la normativa vigente in materia. Si informa che la casella 
di posta elettronica è di titolarità di Miriade S.r.l. è concessa ai propri 
dipendenti e collaboratori esclusivamente per rendere la prestazione 
lavorativa. 


*Confidentiality notice.* This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. This message contains 
confidential information and is intended only for the individual named. If 
you are not the named 

Re: Client App Object Allocation Rate

[Ilya Kasnacheev]

Hello!

Can you please run your app with JFR configured to record object
allocation, to see where it actually happens, and share some results?

Thanks,
-- 
Ilya Kasnacheev


пт, 23 окт. 2020 г. в 17:40, ssansoy :

> This doesn't seem to help unfortunately.
> Re-examining the allocation stats, it seems the app is actually allocating
> around 1.5mb per second with ignite (vs only 0.15mb per second without
> ignite in the app).
> I've read about past issues with IGNITE_EXCHANGE_HISTORY_SIZE causing a lot
> of allocations, but thought this had been fixed prior to 2.8 (we are on
> 2.8.1).
>
> Is there anything else we can tweak around this? Cache metrics etc are off
> on the server and client config. What kind of other objects might be being
> created at this rate?
>
> We can change the GC settings etc which we have done appropriately for our
> app, but we'd like to understand what is being created and why rather than
> change our GC settings to work around this.
>
> Thanks
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: alter table logging slow

[Ilya Kasnacheev]

Hello!

I guess it has to write all the data to disk. After 'alter table logging'
returns, you are guaranteed consistency on this table, meaning all of its
pages have to be persisted to disk. Obviously, it may take a lot of time if
you have many gigabytes to flush.

Regards,
-- 
Ilya Kasnacheev


пн, 26 окт. 2020 г. в 11:59, Matteo Durighetto :

> Hello,
>I found an expected behaviour on apache ignite.
> If you do ( TABLE partitioned with 1 backup and ATOMIC mode ):
>
> alter table ..  nologging;
> set stream on ;
> .. loading a lot of data with jdbc ..
> .. close connection to flush data ..
> .. reopen connection..
> alter table .. logging
>
> The last step "alter table logging" writes a lot of data and it's "slow",
> if we load the table
> with 26 threads in about 10 minute and every thread uses a dedicated
> partition, , the nologging phase is around 11 minutes.
>
> I would like to understand what it is doing and how to speed up the
> process, I try to understand from SqlAlterTableCommand.java what it's
> doing, but it's not straightforward.
>
> Kind Regards
>
> Matteo Durighetto
>
>
>
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
> M I R I A D E - P L A Y  T H E  C H A N G E
>
> Via Castelletto 11, 36016 Thiene VI
> Tel. 0445030111 - Fax 0445030100
> Website: http://www.miriade.it/
>
> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
> *Clausola di riservatezza. *Le informazioni contenute o allegate al presente 
> messaggio sono dirette unicamente al Destinatario sopra indicato. In caso di 
> ricezione da parte di persona diversa è vietato qualunque tipo di 
> distribuzione o copia. Chiunque riceva questa comunicazione per errore è 
> tenuto ad informare immediatamente il mittente e a distruggere il messaggio. 
> Si informa che un eventuale trattamento di dati personali contenuti nella 
> presente comunicazione, in assenza dei presupposti di liceità previsti 
> dall’art 6 Reg. 679/16 (GDPR), è punito secondo la normativa vigente in 
> materia. Si informa che la casella di posta elettronica è di titolarità di 
> Miriade S.r.l. è concessa ai propri dipendenti e collaboratori esclusivamente 
> per rendere la prestazione lavorativa.
>
> *Confidentiality notice.* This email and any files transmitted with it are 
> confidential and intended solely for the use of the individual or entity to 
> whom they are addressed. This message contains confidential information and 
> is intended only for the individual named. If you are not the named addressee 
> you should not disseminate, distribute or copy this e-mail. Please notify the 
> sender immediately by e-mail if you have received this e-mail by mistake and 
> delete this e-mail from your system. Any form of data processing in absence 
> of the lawfulness principles provided by the art. 6 of Reg. UE 697/16 (GDPR) 
> is prohibited and it will be punishable by law. This e-mail address is 
> property of Miriade S.r.l. and it is used by its employees solely for working.
>
>

Node starting error

[kay]

Hello, I have a 2 server nodes and I configure only one node Data region
eviction policy and restart.

and I got a the error 


org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
B+Tree is corrupted [pages(groupId, pageId)=[], msg=Runtime failure on
bounds: [lower=null, upper=null]]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:5927)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:1054)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.tree.CacheDataTree.find(CacheDataTree.java:164)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.tree.CacheDataTree.find(CacheDataTree.java:63)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:1021)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.cursor(IgniteCacheOffheapManagerImpl.java:2844)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.reservedIterator(IgniteCacheOffheapManagerImpl.java:1141)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.rebalanceIterator(IgniteCacheOffheapManagerImpl.java:1184)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:270)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.lambda$handleDemandMessage$1(GridDhtPreloader.java:370)
~[ignite-core-2.8.0.jar:2.8.0]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[?:1.8.0_181]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[?:1.8.0_181]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]
Caused by:
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTreeRuntimeException:
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTreeRuntimeException:
java.lang.IllegalArgumentException: Invalid object type: 0
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findLowerUnbounded(BPlusTree.java:1000)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:1039)
~[ignite-core-2.8.0.jar:2.8.0]
... 11 more
Caused by:
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTreeRuntimeException:
java.lang.IllegalArgumentException: Invalid object type: 0
at
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.doInitFromLink(CacheDataRowAdapter.java:290)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:160)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:131)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.tree.DataRow.(DataRow.java:55)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.tree.CacheDataRowStore.dataRow(CacheDataRowStore.java:130)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.tree.CacheDataTree.getRow(CacheDataTree.java:417)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.tree.CacheDataTree.getRow(CacheDataTree.java:63)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.fillFromBuffer0(BPlusTree.java:5608)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.fillFromBuffer(BPlusTree.java:5376)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.init(BPlusTree.java:5302)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findLowerUnbounded(BPlusTree.java:989)
~[ignite-core-2.8.0.jar:2.8.0]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:1039)
~[ignite-core-2.8.0.jar:2.8.0]
... 11 more
Caused by: java.lang.IllegalArgumentException: Invalid object type: 0
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toKeyCacheObject(CacheObjectBinaryProcessorImpl.java:1167)
~[ignite-core-2.8.0.jar:2.8.0]

alter table logging slow

[Matteo Durighetto]

Hello,
   I found an expected behaviour on apache ignite.
If you do ( TABLE partitioned with 1 backup and ATOMIC mode ):

alter table ..  nologging;
set stream on ;
.. loading a lot of data with jdbc ..
.. close connection to flush data ..
.. reopen connection..
alter table .. logging

The last step "alter table logging" writes a lot of data and it's "slow",
if we load the table
with 26 threads in about 10 minute and every thread uses a dedicated
partition, , the nologging phase is around 11 minutes.

I would like to understand what it is doing and how to speed up the
process, I try to understand from SqlAlterTableCommand.java what it's
doing, but it's not straightforward.

Kind Regards

Matteo Durighetto

-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

M I R I A 
D E - P L A Y  T H E  C H A N G E 


Via Castelletto 11, 36016 Thiene VI
Tel. 0445030111 - Fax 0445030100 
Website: http://www.miriade.it/ 










. . . . . . . . . . . . . . . . . . . . . 
. . . . . . . . . . . . . . . . . . 
*Clausola di riservatezza. *Le 
informazioni contenute o allegate al presente messaggio sono dirette 
unicamente al Destinatario sopra indicato. In caso di ricezione da parte di 
persona diversa è vietato qualunque tipo di distribuzione o copia. Chiunque 
riceva questa comunicazione per errore è tenuto ad informare immediatamente 
il mittente e a distruggere il messaggio. Si informa che un eventuale 
trattamento di dati personali contenuti nella presente comunicazione, in 
assenza dei presupposti di liceità previsti dall’art 6 Reg. 679/16 (GDPR), 
è punito secondo la normativa vigente in materia. Si informa che la casella 
di posta elettronica è di titolarità di Miriade S.r.l. è concessa ai propri 
dipendenti e collaboratori esclusivamente per rendere la prestazione 
lavorativa. 


*Confidentiality notice.* This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. This message contains 
confidential information and is intended only for the individual named. If 
you are not the named addressee you should not disseminate, distribute or 
copy this e-mail. Please notify the sender immediately by e-mail if you 
have received this e-mail by mistake and delete this e-mail from your 
system. Any form of data processing in absence of the lawfulness principles 
provided by the art. 6 of Reg. UE 697/16 (GDPR) is prohibited and it will 
be punishable by law. This e-mail address is property of Miriade S.r.l. and 
it is used by its employees solely for working.