Re: Ignite partitioned

Hi, As long as you see state=ACTIVE and servers=(number of nodes in your config), the cluster has been formed and is active. You can check by executing sql queries and putting data into it. If you are having issues w/your existing cluster then send the logs from all nodes on startup. Let m

Re: Ignite partitioned

$ ./control.sh --baseline Control utility [ver. 2.8.0#20200226-sha1:341b01df] 2020 Copyright(C) Apache Software Foundation User: Time: 2020-08-21T09:13:11.334 Command [BASELINE] started Arguments: --baseline Faile

Re: Ignite partitioned

Hello! Please provide additional information that I have requested: Do you have persistence? If so, can you please also show your baseline topology? You can get it from log or via control.sh utility. Thanks, -- Ilya Kasnacheev вт, 18 авг. 2020 г. в 18:23, itsmeravikiran.c : > Could you plea

Re: Ignite partitioned

Hello! Yes, this looks OK. Do you have persistence? If so, can you please also show your baseline topology? You can get it from log or via control.sh utility. Regards, -- Ilya Kasnacheev вт, 18 авг. 2020 г. в 14:05, itsmeravikiran.c : > My topology snap shot: > [06:46:33,961][INFO][disco-eve

Re: Ignite partitioned

Could you please help with this. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite partitioned

My topology snap shot: [06:46:33,961][INFO][disco-event-worker-#44][GridDiscoveryManager] Topology snapshot [ver=27, locNode=, servers=2, clients=17, state=ACTIVE, CPUs=32, offheap=90.0GB, heap=160.0GB] How should we know, is it formed cluster or not. -- Sent from: http://apache-ignite-use

Re: Ignite partitioned

Hello! Do you have "Topology snapshot" messages in your nodes' output, can you share them? It is likely that your nodes did not form a cluster. Regards, -- Ilya Kasnacheev вт, 18 авг. 2020 г. в 13:17, itsmeravikiran.c : > Our application running with 2 ignite node,. > But data is available in

Ignite partitioned

Our application running with 2 ignite node,. But data is available in one node, and not available in the second node. Our cache configuration: Cache mode:partitioned Automatic mode:atomic Write Synchronization mode:full_sync Backups:1 Rebalance delay:1 We have above cache configuration. Could

Re: Ignite partitioned mode not scaling

could you please share the benchmark code with us? >>>>> do you run queries against the same amount of records each time? >>>>> what host machines do you use for your nodes? when you say that you >>>>> have 5 nodes, does it mean that you use 5 dedicates machines fo

Re: Ignite partitioned mode not scaling

he bottleneck, so your >>>> system can handle more QPS, but you need to run a benchmark from several >>>> machines. Please try to use at least 2 hosts for the benchmark application >>>> and check if there any changes in QPS. >>>> >>>> Tha

Re: Ignite partitioned mode not scaling

o use at least 2 hosts for the benchmark application >>> and check if there any changes in QPS. >>> >>> Thanks, >>> Mike. >>> >>> On Thu, Jan 2, 2020 at 2:49 AM Rajan Ahlawat >>> wrote: >>> >>>> >>>> >>&

Re: Ignite partitioned mode not scaling

; Thanks, >> Mike. >> >> On Thu, Jan 2, 2020 at 2:49 AM Rajan Ahlawat >> wrote: >> >>> >>> >>> -- Forwarded message - >>> From: Rajan Ahlawat >>> Date: Thu, Jan 2, 2020 at 4:05 PM >>> Subject: Ig

Re: Ignite partitioned mode not scaling

d message - >> From: Rajan Ahlawat >> Date: Thu, Jan 2, 2020 at 4:05 PM >> Subject: Ignite partitioned mode not scaling >> To: >> >> >> We are moving from replicated (1-node cluster) to multinode partitioned >> cluster. >> So assumption

Re: Ignite partitioned mode not scaling

: > > > -- Forwarded message - > From: Rajan Ahlawat > Date: Thu, Jan 2, 2020 at 4:05 PM > Subject: Ignite partitioned mode not scaling > To: > > > We are moving from replicated (1-node cluster) to multinode partitioned > cluster. > So assumption

Fwd: Ignite partitioned mode not scaling

-- Forwarded message - From: Rajan Ahlawat Date: Thu, Jan 2, 2020 at 4:05 PM Subject: Ignite partitioned mode not scaling To: We are moving from replicated (1-node cluster) to multinode partitioned cluster. So assumption was that max QPS we can reach would be more if no. of

Re: Ignite Partitioned Cache / Use for an in-memory transaction-log

Hello! You can have any number of backups, but you can either update all of them in sync, or primary only. You can't have a subset of backups updated, despite such possibility being discussed. Regards, -- Ilya Kasnacheev ср, 7 авг. 2019 г. в 13:29, Johannes Lichtenberger < johannes.lichtenber.

Re: Ignite Partitioned Cache / Use for an in-memory transaction-log

Hi, if I want to replicate data from one node to N-nodes (that is only a subset of nodes in the whole cluster), could I also specify that not only the primary is updated in synchronous mode, but some of the backup nodes, too? I also would like to somehow guarantee read-your-own-writes semant

Re: Ignite Partitioned Cache / Use for an in-memory transaction-log

Hello! You can use ignite.affinity(cacheName).mapKeyToNode(key): it returns ClusterNode which is primary for this key. Not sure that I understand you about the quorum. Regards, -- Ilya Kasnacheev вт, 6 авг. 2019 г. в 15:47, Johannes Lichtenberger < johannes.lichtenber...@unitedplanet.com>: >

Ignite Partitioned Cache / Use for an in-memory transaction-log

Hi, can I somehow query on which cluster-nodes a partitioned cache stores values for specific keys? I might want to use a cache for replicating an in-memory transaction log (which does not have to be persisted) to replicate a document of a NoSQL document store to a few nodes. Thus, instead o

Re: About Apache Ignite Partitioned Cache

Thanks Evgenii and Denis . On Tue, Sep 5, 2017 at 9:57 AM, Denis Mekhanikov wrote: > > The backups which is mentioned in the documentation, how do I define > which node is the primary node and which node is the backup node. > > You can either define your own affinity function or use > Rendezvous

Re: About Apache Ignite Partitioned Cache

> The backups which is mentioned in the documentation, how do I define which node is the primary node and which node is the backup node. You can either define your own affinity function or use RendezvousAffinityFunction and set a backup filter using setAffinityBackupFilter

Re: About Apache Ignite Partitioned Cache

>The backups which is mentioned in the documentation, how do I define which node is the primary node and >which node is the backup node. It defined by Affinity Function, you can read about it here: https://apacheignite.readme.io/docs/affinity-collocation#section-affinity-function >I will have a f

About Apache Ignite Partitioned Cache

Hi, I am using Apache Ignite 1.9 in the embedded mode, I am using it as an inmemory data grid. I want to use the mode Partitioned Mode cache and I am trying to gather usage information. - The backups which is mentioned in the documentation, how do I define which node is the primary node an

Re: Ignite - Partitioned Cache - Are clients aware of the partitions ?

Hi, Client is aware about cache configuration so it is also aware about cache affinity and therefore it is aware about partitions distribution. Hence query will request data from primary nodes regardless of cache concurrency mode (transactional or atomic). On Sun, Jul 24, 2016 at 7:54 PM, M Sing

Ignite - Partitioned Cache - Are clients aware of the partitions ?

Hi: In case of a partitioned cache, does is the client aware of the partitions and does the query contact the primary partition ? Also, how the scenario work for a transaction where multiple partitions might be accessed ? Thanks