Can Apache Superset connect with Apache Ignite ?

[lan]

as the topic , if yes, please share the  approximate method,thanks.



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

Re: Getting Baseline Topology Error

[Evgenii Zhuravlev]

Hi,

When do you usually change the baseline topology? It looks like you changed
topology for part of the nodes and the changed it for another node
separately, so now they have different baseline topologies.

Do you have nodes for runs before this issue happened?

Thanks,
Evgenii

чт, 14 мая 2020 г. в 05:01, BEELA GAYATRI :

> Hi,
>
>
>
>Sometimes I am getting  the below error while starting the server
> nodes. After clearing the cache data in the persistence and Restart the
> nodes, then the nodes are up and running.
>
>
>
> I am using below code for setting BaseLineTopology
>
>
>
> ignite.cluster().active(true);
>
> ignite.cluster().setBaselineTopology(nodes);
>
>
>
>   Please provide some solution why this is happening and what needs to be
> done to get rid of the below error
>
>
>
> Failed to start manager: GridManagerAdapter [enabled=true,
> name=o.a.i.i.managers.discovery.GridDiscoveryManager]
>
> class org.apache.ignite.IgniteCheckedException: Failed to start SPI:
> TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
> marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@2f4d01b6],
> reconCnt=10, reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false, internalLsnr=null]
>
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
>
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:939)
>
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1682)
>
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1066)
>
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
>
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
>
> at
> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
>
> at
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
>
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
>
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
>
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
>
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
>
> at org.apache.ignite.Ignition.start(Ignition.java:348)
>
> at
> com.cmc.facts.grid.WorkerGridInvoker.loadNode(WorkerGridInvoker.java:140)
>
> at
> com.cmc.facts.grid.WorkerGridInvoker.main(WorkerGridInvoker.java:61)
>
> Caused by: class org.apache.ignite.spi.IgniteSpiException:
> BaselineTopology of joining node (bf9321c9-bc4f-49a7-ae07-b6895cdd6645) is
> not compatible with BaselineTopology in the cluster. Branching history of
> cluster BlT ([5934945015, 1007705614, 662484928]) doesn't contain branching
> point hash of joining node BlT (-251217758). Consider cleaning persistent
> storage of the node and adding it to the cluster again.
>
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:1946)
>
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:969)
>
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:391)
>
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:2020)
>
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
>
> ... 14 more
>
> [14:44:55,242][SEVERE][main][IgniteKernal%MATCHERWORKER] Got exception
> while starting (will rollback startup routine).
>
> class org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
>
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1687)
>
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1066)
>
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
>
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
>
> at
> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
>
> at
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
>
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
>
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
>
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
>
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
>
> at org.apache.ignite.Ignition.start(Ignition.java:348)
>
> at
> com.cmc.facts.grid.WorkerGridInvoker.loadNode(WorkerGridInvoker.java:140)
>
> at
> com.cmc

Re: SQL execution performance problems due to insufficient off-heap space

[akorensh]

The base rule is keep at 4K unless there is a very good reason to change it.

See here:
https://apacheignite.readme.io/docs/durable-memory-tuning#page-size

 also try to turn on direct IO:
https://apacheignite.readme.io/docs/durable-memory-tuning#enabling-direct-io

small page sizes might cause amplification on the hardware level:
https://www.cactus-tech.com/resources/blog/details/write-amplification-as-seen-in-solid-state-drives
 
Large  page size might causes write amplification By ignite. The whole 16k
page will be persisted if you have changed only few bytes.

It depends on the pageFillFactor:
https://apacheignite.readme.io/docs/memory-metrics#getting-metrics

// Get the metrics of all the data regions configured on a node.
Collection regionsMetrics = ignite.dataRegionMetrics();

// Print out some of the metrics.
for (DataRegionMetrics metrics : regionsMetrics) {
System.out.println(">>> Memory Region Name: " + metrics.getName());
System.out.println(">>> Allocation Rate: " +
metrics.getAllocationRate());
System.out.println(">>> Fill Factor: " + metrics.getPagesFillFactor());
System.out.println(">>> Allocated Size: " +
metrics.getTotalAllocatedPages());
System.out.println(">>> Physical Memory Size: " +
metrics.getPhysicalMemorySize());
}

If you see a pageFillFactor of say 60% consistently then data is not aligned
correctly and extra pages w/corresponding read/writes are necessary. Here
tuning the pageFillFactor might be neccessary


 Ignite does not read only one page at a time but uses a variety of
algorithms to
 batch page reads/writes/replacements.

Your particular use case dictates what the best parameters are.
  
https://apacheignite.readme.io/docs/durable-memory-tuning#pages-writes-throttling
 
 see also:
https://www.intel.com/content/dam/www/public/us/en/documents/white-papers/ssd-server-storage-applications-paper.pdf

detailed information on how Ignite persistence and memory pagination work:
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood




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

Re: Question on the log of public pool thread [pub-#14505].

[Evgenii Zhuravlev]

James,

> But whether could I know the other threads are stopped and destroy?
That's how it works, Here in the code:
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/IgnitionEx.java#L1763
you
can see that Ignite create ThreadPoolExecutor with a max size equals to
yours configured size.

ср, 13 мая 2020 г. в 19:01, James Yuan :

> Thank you for reply.
>
> It seems I should create custom thread pool for the business logics rather
> than use the public pool and reduce its size.
>
> So [pub-#14505] means the 14505th new created thread in public pool? But
> whether could I know the other threads are stopped and destroy? I am afraid
> that the huge threads cause long GC and hang the whole system.
>
> Thanks,
> James.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Scheduling Cache Refresh

[akorensh]

can you share the server logs.
turn on debug for the appropriate package:
org/apache/ignite/cache/store/jdbc
https://apacheignite.readme.io/docs/logging

  What is the behavior you are getting? No logs related to this at all.

you should be getting the following:
   Start loading entries from db using user queries from arguments.

Started load cache using custom statement [cache=" + U.maskName(cacheName) +
  ", keyType=" + keyType + ", stmt=" +
stmt + ']'

"Started load cache using custom query [cache=" + U.maskName(cacheName) +
  ", keyType=" + keyType + ", query=" + qry
+ ']'


The actual loading occurs here: 
https://github.com/apache/ignite/blob/fb2f608005a29e9a558942dd648bac771bc44830/modules/core/src/main/java/org/apache/ignite/cache/store/jdbc/CacheAbstractJdbcStore.java#L680


Thanks, Alex



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

Re: BinaryObject field is not update

[akorensh]

Hi,
  See:
https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/binary/datagrid/CacheClientBinaryPutGetExample.java


  and:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/binary/BinaryObject.html

  https://apacheignite.readme.io/docs/binary-marshaller

https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datagrid/CacheEntryProcessorExample.java
  
 
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/CacheEntry.html


  If you are still having issues, please send a full reproducer and I'll
take a look.
Thanks, Alex

   



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

Re: Scheduling Cache Refresh

[nithin91]

Hi 

Actually the Bean File which contains  the Cache Store Factory Details  and
Cache Configuration Details 
is deployed in Linux Server on which the Ignite Instance is running.I am try
to connect to the ignite instance running on the Linux Server from my local
machine.

PFA for the bean file that is deployed. Ignite-Server.xml
  





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

Re: Scheduling Cache Refresh

[akorensh]

Hi,  
   loadCache(..) is designed to load the cache from a 3rd party store.

   you are not setting the cache factory in your app. 

  See: https://apacheignite.readme.io/docs/3rd-party-store#rdbms-integration 

  example:
https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datagrid/store/jdbc/CacheJdbcStoreExample.java

  it has:  
cacheCfg.setCacheStoreFactory(FactoryBuilder.factoryOf(CacheJdbcPersonStore.class));
   this tell loadCache(..) where to get the data from.

Thanks, Alex




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

Re: Restarting the Main node when it goes down

[akorensh]

Hi,
   A baseline topology is set when you activate a cluster w/a set of nodes
the first time around.
  You can subsequently change baseline  the topology using the public API or
control.sh command.

  Once all the baseline topology nodes are up the cluster automatically
activates.

  use control --baseline to see which nodes are in your baseline

  when the cluster restarts  look for:

   Topology snapshot [ver=2, locNode=..., servers=2, clients=0,
state=INACTIVE, CPUs=.., offheap=.., heap=...]
 ^-- Baseline [id=0, size=2, online=2, offline=0]
   ^-- All baseline nodes are online, will start auto-activation

  See: https://apacheignite.readme.io/docs/baseline-topology


   Send the logs of your two nodes and I'll take a look.
Thanks, Alex



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

Re: About index inline size of primary key

[38797715]

Hi,

I see this property.
If this property is configured, it has a global impact? What is the 
influence range of this parameter?


在 2020/5/14 下午9:41, Stephen Darlington 写道:
Exactly as the warning says, with the IGNITE_MAX_INDEX_PAYLOAD_SIZE 
property:


./ignite.sh -J-DIGNITE_MAX_INDEX_PAYLOAD_SIZE=33

Regards,
Stephen

On 14 May 2020, at 14:23, 38797715 <38797...@qq.com 
> wrote:


Hi,

Today, I see the following information in the log:

[2020-05-14T16:42:04,346][WARN][query-#7759][IgniteH2Indexing] 
Indexed columns of a row cannot be fully inlined into index what may 
lead to slowdown due to additional data page reads, increase index 
inline size if needed (set system property 
IGNITE_MAX_INDEX_PAYLOAD_SIZE with recommended size (be aware it will 
be used by default for all indexes without explicit inline size)) 
[cacheName=NEW, tableName=NEW, idxName=_key_PK, idxCols=(CO_NUM, 
CUST_ID), idxType=PRIMARY KEY, curSize=10, recommendedInlineSize=33]


I know that the create index statement has an inline_ size clause, 
but I want to ask, how to adjust theinline size of primary key?

Re: About index inline size of primary key

[Stephen Darlington]

Exactly as the warning says, with the IGNITE_MAX_INDEX_PAYLOAD_SIZE property:

./ignite.sh -J-DIGNITE_MAX_INDEX_PAYLOAD_SIZE=33

Regards,
Stephen

> On 14 May 2020, at 14:23, 38797715 <38797...@qq.com> wrote:
> 
> Hi,
> 
> Today, I see the following information in the log:
> 
> [2020-05-14T16:42:04,346][WARN][query-#7759][IgniteH2Indexing] Indexed 
> columns of a row cannot be fully inlined into index what may lead to slowdown 
> due to additional data page reads, increase index inline size if needed (set 
> system property IGNITE_MAX_INDEX_PAYLOAD_SIZE with recommended size (be aware 
> it will be used by default for all indexes without explicit inline size)) 
> [cacheName=NEW, tableName=NEW, idxName=_key_PK, idxCols=(CO_NUM, CUST_ID), 
> idxType=PRIMARY KEY, curSize=10, recommendedInlineSize=33]
> 
> I know that the create index statement has an inline_ size clause, but I want 
> to ask, how to adjust the inline size of primary key?
> 

Re: SQL execution performance problems due to insufficient off-heap space

[18624049226]

Hi,

I tested and found that pageSize can be configured up to 16K.

If 4K, 8K and 16K are configured respectively, the read performance will 
increase linearly, but the write performance will decrease linearly, and 
the disk space occupation of persistent files will also increase 
significantly.


In terms of actual effect, there are only two options: 4K and 8K.
In other words, it's hard to improve the speed of data exchange between 
memory and disk. Is that so?


Or what's wrong with my understanding, operation and configuration?

在 2020/5/14 上午9:53, 18624049226 写道:

Hi,

If only the pageSize data is read in each disk access, will the disk 
read speed increase tenfold if the pageSize is increased by 10 times? 
What are the negative effects on ignite as a whole?


在 2020/5/13 下午3:17, 18624049226 写道:

Hi,

You are right. The memory of this node is small, but the data volume 
is large. There is data exchange between memory and disk during SQL 
query, which we think is normal.


But according to iostat's statistics,

r/s 2852 *4k = 11.4M~rMB/s

That is, each time the disk reads data, it only reads about 4KB 
(pageSize) of data? Is this very inefficient? Not one block of data 
at a time?


Or do I need to optimize some parameter?

在 2020/5/13 上午3:51, akorensh 写道:

Hi,
   Attach the logs and I'll take a look. Include the details of your 
sql

request: # of rows/size of objects/
   indexs/sql queries/etc..

    It might be using the disk and swapping memory back and forth.
https://apacheignite.readme.io/docs/durable-memory-tuning#pages-writes-throttling 



       Use this guide to tune memory:
https://apacheignite.readme.io/docs/durable-memory-tuning
   more optimizations here:
https://apacheignite.readme.io/docs/performance-tips

https://apacheignite.readme.io/docs/preparing-for-production

Thanks, Alex



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

About index inline size of primary key

[38797715]

Hi,

Today, I see the following information in the log:

[2020-05-14T16:42:04,346][WARN][query-#7759][IgniteH2Indexing] Indexed 
columns of a row cannot be fully inlined into index what may lead to 
slowdown due to additional data page reads, increase index inline size 
if needed (set system property IGNITE_MAX_INDEX_PAYLOAD_SIZE with 
recommended size (be aware it will be used by default for all indexes 
without explicit inline size)) [cacheName=NEW, tableName=NEW, 
idxName=_key_PK, idxCols=(CO_NUM, CUST_ID), idxType=PRIMARY KEY, 
curSize=10, recommendedInlineSize=33]



I know that the create index statement has an inline_ size clause, but I 
want to ask, how to adjust the inline size of primary key?

Getting Baseline Topology Error

[BEELA GAYATRI]

Hi,

   Sometimes I am getting  the below error while starting the server nodes. 
After clearing the cache data in the persistence and Restart the nodes, then 
the nodes are up and running.

I am using below code for setting BaseLineTopology

ignite.cluster().active(true);
ignite.cluster().setBaselineTopology(nodes);

  Please provide some solution why this is happening and what needs to be done 
to get rid of the below error

Failed to start manager: GridManagerAdapter [enabled=true, 
name=o.a.i.i.managers.discovery.GridDiscoveryManager]
class org.apache.ignite.IgniteCheckedException: Failed to start SPI: 
TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000, 
marsh=JdkMarshaller 
[clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@2f4d01b6], 
reconCnt=10, reconDelay=2000, maxAckTimeout=60, forceSrvMode=false, 
clientReconnectDisabled=false, internalLsnr=null]
at 
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:939)
at 
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1682)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1066)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
at org.apache.ignite.Ignition.start(Ignition.java:348)
at 
com.cmc.facts.grid.WorkerGridInvoker.loadNode(WorkerGridInvoker.java:140)
at com.cmc.facts.grid.WorkerGridInvoker.main(WorkerGridInvoker.java:61)
Caused by: class org.apache.ignite.spi.IgniteSpiException: BaselineTopology of 
joining node (bf9321c9-bc4f-49a7-ae07-b6895cdd6645) is not compatible with 
BaselineTopology in the cluster. Branching history of cluster BlT ([5934945015, 
1007705614, 662484928]) doesn't contain branching point hash of joining node 
BlT (-251217758). Consider cleaning persistent storage of the node and adding 
it to the cluster again.
at 
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:1946)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:969)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:391)
at 
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:2020)
at 
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
... 14 more
[14:44:55,242][SEVERE][main][IgniteKernal%MATCHERWORKER] Got exception while 
starting (will rollback startup routine).
class org.apache.ignite.IgniteCheckedException: Failed to start manager: 
GridManagerAdapter [enabled=true, 
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at 
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1687)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1066)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
at org.apache.ignite.Ignition.start(Ignition.java:348)
at 
com.cmc.facts.grid.WorkerGridInvoker.loadNode(WorkerGridInvoker.java:140)
at com.cmc.facts.grid.WorkerGridInvoker.main(WorkerGridInvoker.java:61)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start SPI: 
TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000, 
marsh=JdkMarshaller 
[clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@2f4d01b6], 
reconCnt=10, reconDelay=2000, maxAckTimeout=60, forceSrvMode=false, 
clientReconnectDisabled=false, internalLsnr=null]
at 
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
at 
org.apache.ignite.inter

Re: Scheduling Cache Refresh

[nithin91]

Hi 

Attached link is at the end of post.However i am attaching it again here.
srcandpom.zip
  

Please let me know in case of any difficulties while opening the attachment.



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

Re: ignite node ports

[Stephen Darlington]

If you download Ignite and run it, the REST server isn’t enabled. You have to 
copy ignite-rest-http from libs/optional to libs.

Assuming you did that, you can start Ignite like this:

./ignite.sh -J-DIGNITE_JETTY_PORT=8088

That will start the REST service on port 8088.

> On 14 May 2020, at 01:12, kay  wrote:
> 
> oh.. I see thank you so much
> 
> For REST port(8080) is open, you said i have to enable it.
> but i didn't understand exactly. how can i enable it? 
> you mean server machine(disk) port enable to use?
> 
> If i some application already use port(8080) so i set change port number
> using IGNITE_JETTY_PORT property, is it going to be not fails to start??
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Basic Affinity Question

[Stephen Darlington]

No, it needs to be able to determine which node the data should be on without 
reference to anything else. This means that you’d need company-id in your 
address table. 

> On 13 May 2020, at 21:23, narges saleh  wrote:
> 
> 
> My other question is whether affinity is transitive.
> Company (primary key: company-id)
> Employee(primary key: employee-id + company-id) <- company id = affinity key
> Address(Primary key: address-id + employee -id) <- employee id = affinity key
> 
> Would the records  related company, employee and address for the employee end 
> up on the same node? In other words, I won't need to drag company id in the 
> address table, in order to collocate all three record types.
> 
>> On Wed, May 13, 2020 at 10:50 AM narges saleh  wrote:
>> Thanks.
>> If I try AffinityRun with collection of caches and the affinity key, I'd get 
>> NPE with cache.localpeek using the primary key of the dependent cache/table 
>> but the cache query itself succeeds. 
>> Is there a working example?
>> 
>>> On Wed, May 13, 2020 at 8:10 AM Stephen Darlington 
>>>  wrote:
>>> Yes, but you also need to make sure you use the correct affinityRun method. 
>>> There’s one where you specify multiple caches and you need to use that one.
>>> 
>>> > On 13 May 2020, at 12:50, narges saleh  wrote:
>>> > 
>>> > Hi All,
>>> > If I have these two caches/tables defined via query entities, in a  
>>> > config file,
>>> > Employee (partitioned)
>>> >   employee-id
>>> >   company-id
>>> >   name
>>> >  primary key(employee-id, company-id), affinity(company-id)
>>> > 
>>> > Company (partitioned)
>>> >   company-id.
>>> >   name
>>> >   primary key(company-id)
>>> > 
>>> > If I do AffinityRun or mapkeystonodes with two server ignite nodes 
>>> > running on the same physical box, shouldn't I see the employee records 
>>> > with the same company-id and the company record with the same company-id 
>>> > on the same ignite node?
>>> > 
>>> > thanks.
>>> > 
>>> 
>>> 

Re: Suggest a better way to access a particular K-V store

[Ilya Kasnacheev]

Hello!

Have you tried adding an index on URLS (APPNAME_ID, SCORE DESC)? (or ASC if
you are going to order ascending)

Regards,
-- 
Ilya Kasnacheev


вт, 12 мая 2020 г. в 13:42, adipro :

> We've already tried that but we are receiving these errors. We are using
> index in a correct way only
> We are using Ignite persistence.
>
> ```
> [15:32:19,481][WARNING][long-qry-#110][LongRunningQueryManager] Query
> execution is too long [duration=3898ms, type=MAP, distributedJoin=false,
> enforceJoinOrder=false, lazy=false, schema=PUBLIC, sql='SELECT
> "__Z0"."ID" "__C0_0",
> "__Z0"."URL" "__C0_1",
> "__Z0"."SCORE" "__C0_2",
> "__Z0"."APPNAME_ID" "__C0_3"
> FROM "PUBLIC"."URLS" "__Z0"
> WHERE "__Z0"."APPNAME_ID" = ?1
> ORDER BY 3 FETCH FIRST ?2 ROWS ONLY', plan=SELECT
> __Z0.ID AS __C0_0,
> __Z0.URL AS __C0_1,
> __Z0.SCORE AS __C0_2,
> __Z0.APPNAME_ID AS __C0_3
> FROM PUBLIC.URLS __Z0
> /* PUBLIC.IDX_2_URLS */
> /* scanCount: 1342938 */
> WHERE __Z0.APPNAME_ID = ?1
> ORDER BY 3
> FETCH FIRST ?2 ROWS ONLY
> /* index sorted */, node=TcpDiscoveryNode
> [id=1acf85ab-112a-4bbf-95f3-b6d3eb8c38b8,
> consistentId=1acf85ab-112a-4bbf-95f3-b6d3eb8c38b8, addrs=ArrayList
> [127.0.0.1, 192.168.177.58], sockAddrs=HashSet [/127.0.0.1:0,
> /192.168.177.58:0], discPort=0, order=4, intOrder=4,
> lastExchangeTime=1589276400188, loc=false,
> ver=8.7.10#20191227-sha1:c481441d, isClient=true], reqId=482, segment=0]
> ```
> The thing is we are running this in an 8 GB machine. According to the
> documents about tuning, we were told that 70% of the RAM should be given to
> heap and non heap so we gave 2GB heap + 2GB offheap + 1GB
> directbuffmemory..
>
> Till 60Lakh records, it didn't throw any warnings, but after that we are
> receiving many warnings.
>
> Is it got to do something with Off-heap size or BTree data size that is
> stored in RAM? Should we increase RAM? We don't want to increase RAM. Is it
> possible without increasing RAM? Or is there a way we can calculate how
> much
> RAM we need for how much data?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Scheduling Cache Refresh

[Ilya Kasnacheev]

Hello!

Unfortunately I don't see any attachment to your message. Can you please
share a link?

Regards,
-- 
Ilya Kasnacheev


чт, 14 мая 2020 г. в 10:09, nithin91 <
nithinbharadwaj.govindar...@franklintempleton.com>:

> Hi
>
> Attached the Sample Spring Boot Application that i am running in my local
> machine to connect to ignite cluster deployed in Unix as a client node and
> refreshes the cache when ever a GET Request is made.
>
> Facing the following error.Can you please help me in resolving the errors
>
> *org.apache.ignite.IgniteException: Spring application context resource is
> not injected.*
>
> I am facing this error while trying to refresh the cache using the
> following
> method
>
> ignite.cache("NumberandDateFormatCache").loadCache(null,"java.lang.Long",
> "select a.*,row_number() over(order by COUNTRY_CODE) AS ID
> FROM
> \"vwNumberAndDateFormat\" a where rownum<=10 ");
>
> but the application gets executed fine when i try to get the list of caches
> using the following method
>
> ignite.cacheNames();
>
> Attached the entire project for your reference.Can you please help me in
> resolving this issue.
>
> Also can you please let me know is this the right way to instantiate ignite
> instance for a building
> Rest-API using Spring Boot.
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: IOException in log and reference for dataRegion&cache configure

[kay]

Hello again :)

I read  memory configuration section.

https://apacheignite.readme.io/docs/memory-configuration

and I don't know exactly what 'setSystemRegionInitialSize',
'setSystemRegionMaxSize' do? 
is it limit the global data storage of node? 
I didn't configure those things and configured only dataRegionSize. 
but it is working well.

some one tell me about 'setSystemRegionInitialSize',
'setSystemRegionMaxSize' infomation more

Thank you

 




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

Restarting the Main node when it goes down

[nithin91]

Hi 

I have two nodes Node A(Main Node) and Node B with persistence enabled.When
node B  is restarted whenever it  goes down, it is able to recognize node A
and is joining the Baseline Topology but when Node A alone goes down and
once Node A is restarted, it is not able to recognize Node B and it is not
included in the base line topology.This issue is fixed, only if i stop Node
B and again restarts it.

Information of the baseline Topology that gets displayed on console,
whenever i connect to the cluster as client.

*-- Baseline [id=0, size=2, online=1, offline=1]*

Is there a way to fix this issue with just restarting Node A instead of
stopping and starting the node B.

Is this happening because of enabling Persistence.Also can anyone please let
me know what needs to be done, if the same thing happens without Persistence
being enabled.




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

Re: Scheduling Cache Refresh

[nithin91]

Hi 

Attached the Sample Spring Boot Application that i am running in my local
machine to connect to ignite cluster deployed in Unix as a client node and
refreshes the cache when ever a GET Request is made.

Facing the following error.Can you please help me in resolving the errors

*org.apache.ignite.IgniteException: Spring application context resource is
not injected.*

I am facing this error while trying to refresh the cache using the following
method

ignite.cache("NumberandDateFormatCache").loadCache(null,"java.lang.Long",
"select a.*,row_number() over(order by COUNTRY_CODE) AS ID FROM
\"vwNumberAndDateFormat\" a where rownum<=10 ");

but the application gets executed fine when i try to get the list of caches
using the following method

ignite.cacheNames();

Attached the entire project for your reference.Can you please help me in
resolving this issue.

Also can you please let me know is this the right way to instantiate ignite
instance for a building
Rest-API using Spring Boot.




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