Yeah I faced the same issue, ended up disabling it. Better to query
cluster.isActive() if you need to apply wait for readiness anywhere in
native persistence mode.
Otherwise cluster size in non persistence mode.
On Thu, 17 Aug 2023, 03:01 Humphrey Lopez, wrote:
> Has anyone deploy ignite in
Hello,
Hope this helps you with some more examples. This is my GitHub repo which
has examples on various features of ignite.
https://github.com/Rednirus/apache-ignite-masterclass
Cheers !
On Mon, 6 Mar 2023, 13:47 Humphrey Lopez, wrote:
> What I need is a nice example where I can demonstrate
Given link has all the details needed. You either write your db queries in
custom cache store or move them to a separate db DAO class and have it's
instance in cache store. Then it will be similar to how you connect your
app to DB. Next you need to have these custom classes in ignite class path
l options would be good.
>
> On Wed, 1 Feb 2023, 14:51 Aleksandr Pakhomov, wrote:
>
>> Hi,
>>
>> Do you have a chance to use a java client?
>>
>> https://ignite.apache.org/docs/latest/thin-clients/java-thin-client
>>
>> It seems this could help
>
ava-thin-client
>
> It seems this could help
> igniteClient.cluster().forServers().nodes().count();
>
> Best regards,
> Aleksandr
>
> On 1 Feb 2023, at 10:21, Surinder Mehra wrote:
>
> Hi,
> I am trying to find a way to fetch the count of server nodes in ignite
> cluster but
Hi,
I am trying to find a way to fetch the count of server nodes in ignite
cluster but don't see any control script option or in Rest api. Could you
please suggest if it is possible. Below link shows this is exposed as a
cluster metric but not accessible through above two options.
rk. You could also use transactions.
>
> On 21 Dec 2022, at 17:58, Surinder Mehra wrote:
>
> Gentle reminder.
>
> On Tue, 20 Dec 2022, 12:53 Surinder Mehra, wrote:
>
>> Hi,
>> If we have cache synchronization mode as Primary Sync and read from
>> backup as true
Gentle reminder.
On Tue, 20 Dec 2022, 12:53 Surinder Mehra, wrote:
> Hi,
> If we have cache synchronization mode as Primary Sync and read from backup
> as true(default), would this cause consistency issues if primary goes down
> without flushing all data to disk.
> I underst
Hi,
If we have cache synchronization mode as Primary Sync and read from backup
as true(default), would this cause consistency issues if primary goes down
without flushing all data to disk.
I understand WAL is used to replay unflushed data when a node comes back
online again. But if say out of 10
same time.
>
> On Sun, Nov 6, 2022, 09:58 Surinder Mehra wrote:
>
>> That's partially true. Whole excercise of configuring AZ as backup filter
>> is because we want to handle AZ level failure.
>>
>> Anyway, thanks for inputs. Will figure out further steps
>>
>>
ins.
>
> You're worried about node level failure, but you're telling Ignite to
> worry about AZ level failure.
>
>
> On Sat, Nov 5, 2022, 21:57 Surinder Mehra wrote:
>
>> Yeah I think there is a misunderstanding. Although I figured out my
>> answers from our disc
)
Wouldn't this mean node 3 need 2X space as compared to node 1 and node2.
Assuming backup partitions of node 3 would be equally distributed among
other two nodes. They would need almost same space.
On Tue, 1 Nov 2022, 23:30 Jeremy McMillan,
wrote:
>
>
> On Tue, Nov 1, 2022 at 10:02 AM Surin
g any Ignite nodes with a
> deployment automation tool exception.
>
> On Tue, Nov 1, 2022 at 9:49 AM Surinder Mehra wrote:
>
>> Thanks for your reply. Let me try to answer your 2 questions below.
>> 1. I understand that it sacrifices the backups incase it can't place
>> back
are clear to you now
On Tue, 1 Nov 2022, 20:19 Surinder Mehra, wrote:
> Thanks for your reply. Let me try to answer your 2 questions below.
> 1. I understand that it sacrifices the backups incase it can't place
> backups appropriately. Question is, is it possible to fail the deployment
>
more than 2 copies of the data distribute
> across only two failure domains?
>
> Also "fail fast" means discover your implementation defects faster than
> your release cycle, not how fast you can cause data loss.
>
> On Tue, Nov 1, 2022, 09:01 Surinder Mehra wrote:
>
>&g
gentle reminder.
One additional question: We have observed that if available AZs are less
than backups count, ignite skips creating backups. Is this correct
understanding? If yes, how can we fail fast if backups can not be placed
due to AZ limitation?
On Mon, Oct 31, 2022 at 6:30 PM Surinder
Hi,
As per link attached, to ensure primary and backup partitions are not
stored on same node, We used AWS AZ as backup filter and now I can see if I
start two ignite nodes on the same machine, primary partitions are evenly
distributed but backups are always zero which is expected.
Hi,
Throttling is disabled in ignite config as mentioned in prev reply. What do
you suggest to make ignite catchup with SSD limits on checkpointing.
On Mon, 12 Sept 2022, 11:32 Zhenya Stanilovsky via user, <
user@ignite.apache.org> wrote:
>
>
>
>
>
> We have observed one interesting issue with
We have observed one interesting issue with checkpointing. We are using 64G
RAM 12 CPU with 3K iops/128mbps SSDs. Our application fills up the WAL
directory really fast and hence the RAM. We made the following observations
0. Not so bad news first, it resumes processing after getting stuck for
gt; }
>
> @Override
> public void execute(ServiceContext serviceContext) throws Exception {
>
> }
>
> @Override
> public void sayHello() {
> System.out.println("Hello, world.");
> }
> }
>
> On 31 Aug 2022, at 04:17,
@gridgain.com> wrote:
>
>> Your service needs to implement org.apache.ignite.services.Service.
>>
>> > On 30 Aug 2022, at 12:40, Surinder Mehra wrote:
>> >
>> > Hi,
>> > can you help me find out the reason for this exception in thick client
>
implement org.apache.ignite.services.Service.
>
> > On 30 Aug 2022, at 12:40, Surinder Mehra wrote:
> >
> > Hi,
> > can you help me find out the reason for this exception in thick client
> while getting instance of ignite service:
> >
> > getIgnite()
> > .services()
>
Hi,
can you help me find out the reason for this exception in thick client
while getting instance of ignite service:
getIgnite()
.services()
.serviceProxy("sampleService", SampleService.class, false)
java.lang.ClassCastException: class com.sun.proxy.$Proxy148 cannot be cast
to class
eing used anywhere.
> You can see it's an old jar from year 2015, so definitely ancient and not
> up to date.
> I never had to use that ignite-schedule anywhere in my projects.
> Any particular reason to resurrect this old component?
>
> Cheers
> Gianluca
>
> On Fri, 26 Aug
Hi,
Could you please suggest if it is safe to use below version of
ignite-schedule
It has warnings about CVE
https://mvnrepository.com/artifact/org.apache.ignite/ignite-schedule/1.2.0-incubating
Vulnerabilities from dependencies:
CVE-2020-1963
t; https://ignite.apache.org/docs/2.11.1/data-modeling/affinity-collocation#configuring-affinity-key
>
> On Wed, Jun 22, 2022 at 9:49 PM Surinder Mehra wrote:
>
>> Thanks for the reply. I have another question on the affinity key
>> index(if any). When we enable sql on
it uses primary
key index or hash index when* IndexQuery* is executed with _KEY in criteria*
?*
[image: image.png]
[image: image.png]
On Wed, Jun 22, 2022 at 9:35 PM Николай Ижиков wrote:
> SELECT * FROM SYS.INDEXES
>
> 22 июня 2022 г., в 18:38, Surinder Mehra написал(а):
>
> Hi,
&g
Hi,
We have defined indexes on sql enabled ignite cache and are able to see
indexes being used while querying.
sqline *!indexes* also shows those indexes in output. But we cant see
default index created by ignite on *primary key *and *affinity key*.
We would like to use index on key and affinity
, about how to get involved here:
> https://ignite.apache.org/our-community.html#faq
>
> On 13 Jun 2022, at 11:38, Surinder Mehra wrote:
>
> Hello,
> Can someone please log a feature request. This would be very useful
> feature for everyone using SQL queries
>
> On Fri, Apr 8, 2
Hello,
Can someone please log a feature request. This would be very useful feature
for everyone using SQL queries
On Fri, Apr 8, 2022 at 8:03 PM Surinder Mehra wrote:
> Ok thanks for letting me know. Is there a guideline for raising feature
> request.
>
> On Fri, 8 Apr 2022, 1
Thanks Stephen. Will check with them
On Wed, 8 Jun 2022, 15:18 Stephen Darlington, <
stephen.darling...@gridgain.com> wrote:
> This is a mailing list for Apache ignite users. Please contact GridGain
> for support of their software.
>
> On 8 Jun 2022, at 09:53, Surinder Mehra
Hi,
I deployed gridgain ultimate 2.8.18 to kubernetes with mount point for work
directory to store ignite data as per steps mentioned below
https://www.gridgain.com/docs/latest/installation-guide/kubernetes/amazon-eks-deployment
It works if I don't use an external mount point for the work
On Thu, Jun 2, 2022 at 2:52 PM Surinder Mehra > wrote:
>
> Hi,
> Please find the attached java file which reproduces the issue. As you can
> see, the cache key is used as a join condition but LEFT join is still
> giving only common values.
>
> output:
> [2, Keyboard, 2]
gt; Cheers
> Gianluca
> Gianluca
>
> On Tue, 7 Jun 2022 at 07:35, Surinder Mehra wrote:
>
>> Hi,
>> I was going through this post on stackoverflow which is about the same
>> issue. The fact that snapshot works for apache ignite bit not in ultimate
>> ed
see this issue. Could you please advise further.
https://stackoverflow.com/questions/72041292/is-there-a-fix-for-too-many-open-files-error-in-gridgain-cluster
On Mon, Jun 6, 2022 at 9:13 PM Surinder Mehra wrote:
> Hi,
> I was experimenting with the GG ultimate edition to take sna
Hi,
I was experimenting with the GG ultimate edition to take snapshots and
encountered the below error and cluster stops. Please note that this works
in the ignite free version and we don't see too many files open error. Is
this a bug or we are missing some configuration?
version:
Hi,
Just wondering if you had an opportunity to look into this.
On Thu, Jun 2, 2022 at 2:52 PM Surinder Mehra wrote:
> Hi,
> Please find the attached java file which reproduces the issue. As you can
> see, the cache key is used as a join condition but LEFT join is still
> giving
Ng Kwong Sang, wrote:
> https://lists.apache.org/thread/76b271wdq3dog0ggxyo6rwjr9hrgc6ss
>
>
>
> On 2022/06/02 14:12:54 Surinder Mehra wrote:
>
> > Hi,
>
> > We are running 3 node cluster and suddenly it went into maintenance mode.
>
> > Now i am able
Hi,
We are running 3 node cluster and suddenly it went into maintenance mode.
Now i am able to login into nodes but cant do any action like activating
the cluster or removing other nodes from it. All 3 nodes run in
isolated mode. I restarted the cluster, but it didn't help.
Is there a way to exit
:48 AM Zhenya Stanilovsky
wrote:
> Hi, Surinder Mehra ! I check your sql and it work correct for me.
>
>1. You no need to define AffinityKeyMapped for Key, check additionally
>[1], you can simple modify [2] according to your case
>2. I problem still exist somehow, plz a
ions will be released!
>
>
> Best regards,
>
> Rose.
> --
> *From:* Surinder Mehra
> *Sent:* Thursday, June 2, 2022 9:33:08 AM
> *To:* user@ignite.apache.org
> *Subject:* [POTENTIALLY_MALICIOUS] Re: Docker image for Apache Ignite
> with Java 11
>
>
hello,
Just wondering if you got time to look into this one
On Wed, Jun 1, 2022 at 12:45 PM Surinder Mehra wrote:
> Hi,
> I have the following sample code to demo issue in SQL joins. I have
> created an affinity key and value as shown below and added some sample data
> to it. Whe
Hi,
I have the following sample code to demo issue in SQL joins. I have created
an affinity key and value as shown below and added some sample data to it.
When I try LEFT self join on this table it always gives me common rows
irrespective of LEFT or RIGHT JOIN
Could you please help me find what
just want to make sure this has no side effects before I start
implementing my approach to restore data.
On Fri, May 27, 2022 at 11:33 PM Surinder Mehra wrote:
> Hi Maxim,
> As I explained in original email, I do cleanup as part of init container.
> Since ignite nodes starts after one ano
>
> On Fri, 27 May 2022 at 10:29, Surinder Mehra wrote:
> >
> > Hi,
> > Please find ignite config and error log below
> >
> > config :
> >
> >
> >
essage.
>
> 26 мая 2022 г., в 17:50, Surinder Mehra написал(а):
>
> Hello,
> I upgraded to 2.13.0 and I am able to take sync snapshots now. However, I
> ran into another problem while restoring from snapshot using manual steps
> mentioned in documentation.
>
> We run ignite
tarted yet, waiting
for 2nd node to be in running state.
Any idea how can we make main containers wait until all init containers are
completed
Asking this here as its related to ignite setup in kubernetes.
Any help wil be appreciated. Thanks
On Wed, 25 May 2022, 00:04 Surinder Mehra, wrote:
>
onsistent cluster-wide copy of all data
> records persisted on disk and some other files needed for a restore
> procedure.»
>
> > will this be a stop the world process
>
> No.
>
>
> 24 мая 2022 г., в 21:17, Surinder Mehra написал(а):
>
> Hi
> Thanks for reply.
>
).
> `EVT_CLUSTER_SNAPSHOT_FINISHED` raise on snapshot create finish.
>
> > 3. Is there a way around to speed up this other than increasing
> snapshot threads
>
> Stop write operations.
> The less you change the quicker snapshot will be created.
>
> 24 мая 2022 г., в 20:12,
Hi,
I have 3 node ignite cluster each node contains 60G work directory(ebs) and
I need to create snapshots.
I followed steps to create snapshots and run create snapshot command using
control utility. Command completed in 500millis but snapshot directory only
had 400Mb data. Later I realised
to log4j. It does not contain a
> copy of log4j.
>
> Log4j is version 1.x of log4j, which wasn’t vulnerable. IIRC, log4j 1.x
> has subsequently been removed from Ignite.
>
> On 20 May 2022, at 15:03, Surinder Mehra wrote:
>
> Hi, as per page below, log4j CVE is alrea
Hi, as per page below, log4j CVE is already fixed in ignite 2.11.1
https://blogs.apache.org/ignite/entry/apache-ignite-2-11-1
Affected log4j versions were 2.0-2.14. I can see ignite 2.11.1 contains two
log4j jar files below. Can you please confirm these log4j versions are not
affected by CVE
Hi,
We are seeing this error on one of the nodes while restarting the ignite
cluster. We are using native persistence and version 2.11.1. It only
happens randomly. Any idea what could be wrong?
class org.apache.ignite.IgniteException: GridWorker [name=sys-stripe-2,
igniteInstanceName=null,
Hi,
Please reply
On Sat, 30 Apr 2022, 07:19 Surinder Mehra, wrote:
> Hi
> In ignite documentation 2.12, we could see SQL window functions but
> removed in 2.13. could you please confirm if they are not supported. Apache
> calcite support window functions so we expected to see them in ignite.
>
Hi
In ignite documentation 2.12, we could see SQL window functions but removed
in 2.13. could you please confirm if they are not supported. Apache calcite
support window functions so we expected to see them in ignite.
Hey guys,
I wanted to know if window functions are supported in ignite 2.13. Calcite
supports it so wanted to check.
On Fri, 29 Apr 2022, 19:44 Nikita Amelchev, wrote:
> Hello, guys.
>
> Thanks for pointing it out.
>
> The calcite module was properly published to the maven. [1] The sync
> with
Hey, it's enabled already. Please check the console log in my email
On Thu, 28 Apr 2022, 13:16 Zhenya Stanilovsky, wrote:
>
> Hi, can you check the same with lazy [1] flag ?
>
> [1]
>
Hi,
We are running a sql field query to fetch 4million records from ignite
cache. We have created a group index for all fields used in where clause
and can see group index used. But the query takes 20 minutes to fetch all
records. If we provide more strict criteria to fetch only say 500 records,
Ok thanks, just more query.
"If all 10 segments are filled, then it will be expected (wait) for the
first of the segments to go to the archive."
Does it mean application writes will wait until one of the wal segment is
made free(that means atleast checkpoint must complete so segment file can
Sorry for typo in last thread point 5, I meant to type "the ones which
moves segments from WAL to WAL Archive"
On Fri, 22 Apr 2022, 17:13 Surinder Mehra, wrote:
> Ok thanks for clarifying. O have follow up queries
> 1. Wal has only 10 segments and default checkpoint freque
Ok thanks for clarifying. O have follow up queries
1. Wal has only 10 segments and default checkpoint frequency is 3 minutes
What if application writes fill up all 10 segments before next checkpoint
interval, would it trigger another checkpoint followed by moving of segments
2. Does it always
Hi,
I have a question about WAL file cleanup.
1. A cache update appends updates to WAl file and writes it to RAM. WAL can
rollover older than 10 files to WalArchive.
2. So checkpoint moves data from RAM to Disk
As per docs link below, after checkpoint, WAl files created before it can
be deleted.
TMODEL_TESTFIELD3_ASC_IDX: TESTFIELD3 = 'EN' */
>
> Thanks & Regards,
> Charlin
>
>
> On Tue, 19 Apr 2022 at 19:34, Surinder Mehra wrote:
>
>> I may be wrong but as an excercise, can you try group index on these
>> fields please and see if it makes any
__C0_1 AS TESTFIELD2,
> __C0_2 AS TESTFIELD3,
> __C0_3 AS TESTFIELD4,
> __C0_4 AS TESTFIELD5
> FROM PUBLIC.__T0
> /* "TestModel"."merge_scan" */
>
> Thanks & Regards,
> Charlin
>
> On Tue, 19 Apr 2022 at 18:04, Surinder Mehra wrote:
romMilliseconds(1) };
> List list = new List();
> // public ICache IgniteCache { get; set; }
> IFieldsQueryCursor queryCursor =
> IgniteCache.Query(fieldsQuery);
>
> //our implementation
> queryCursor.Dispose();
>
> Thanks,
> Charlin
>
Can you please show slow query console log output if it's using index scan
or full cache scan.
I ran into one scenario where index wasn't used and it ended up scaning
whole cache.
You can try this locally by using control centre and run explain query
On Mon, 18 Apr 2022, 13:08 Charlin S, wrote:
ith DirectIO disabled?
>
> On 2022/04/14 10:55:23 Surinder Mehra wrote:
> > Hi,
> > We have an application with ignite thick clients which writes to ignite
> > caches on ignite grid deployed separately. Below is the ignite
> > configuration per node
> >
Hi,
We have an application with ignite thick clients which writes to ignite
caches on ignite grid deployed separately. Below is the ignite
configuration per node
With this configuration, we see throttling happening and checkpointing time
is between 20-30 seconds. Did we miss something in
quest ticket.
>
> On 8 Apr 2022, at 13:30, Surinder Mehra wrote:
>
> Hi,
> I was going through the below example and have a question if we can get
> fields using field names from query results.
> like "select name as person_name, p.age as person_age from Person p"
>
Hi,
I was going through the below example and have a question if we can get
fields using field names from query results.
like "select name as person_name, p.age as person_age from Person p"
It would return List. The inner list is each person row returned
with results as per order in sql query.
our tasks and nested classes should be in the class path of the
> server node. You can deploy them manually or automatically by means of
> peer-class loading [1].
>
> 1.
> https://ignite.apache.org/docs/latest/code-deployment/peer-class-loading
>
> пт, 1 апр. 2022 г. в 15:12,
Hi, I am trying to return the result stream from ignite compute task. When
compute task has a map() on stream it fails with below error . Can someone
please explain.
"Exception in thread "main" class
org.apache.ignite.binary.BinaryObjectException: Failed to deserialize
object
Hi,
We have a 4 node cluster with 64G RAM and 40G DISK per node attached for
/work and /walarchive each. WAL dir is 10G per node
Below is our data region configuration and jvm_opts. We are getting
timeouts on checkpointing and WalArchive is getting filled up and no data
is moving to the /work
>
> 22.03.2022 23:14, Surinder Mehra пишет:
> > Hi,
> > We noticed that WalArchive size is going beyond the default max of
> > 1GB, so we tried to increase it in DataStorageConfiguration. But while
> > starting the ignite node, it always throws the below exception
Hi,
We noticed that WalArchive size is going beyond the default max of 1GB, so
we tried to increase it in DataStorageConfiguration. But while starting the
ignite node, it always throws the below exception. Could you please explain
why. complete log in file attached.
Reason for change:
Starting to
ey and value to the heap,
> so it’s likely to use more memory than a SQL query.
>
> On 8 Mar 2022, at 10:04, Surinder Mehra wrote:
>
> Hi,
> Actually SQL is not enabled on these caches.
> We can try compute but I was thinking to use scan query with 'transformer'
> . I assume tran
Hi,
As per ignite deployment on EKS docs, we need to activate the cluster once
all replicas are up.
Activating it manually is not a production ready setup. We were trying to
add a postStart hook to the pod but that causes issues since it activates
the cluster when first replicas start and the
@gridgain.com> wrote:
> You could use SQL. “select _key from table”
>
> But really, copying all the data over the network is often not the best
> strategy. Send a compute job to each node or partition and work on the data
> “in place” on the data nodes.
>
> On 8 Mar 2022, at
Hi,
I was looking for a way to fetch all cache keys in an efficient manner from
ignite cache. Looks like there is no such api yet.
Would it be correct to use a transformer in Scan query to just fetch the
key from entry being scanned. This will avoid fetching full cache entry
from server nodes
Or
Hi,
While go through blogpost below, I couldn't completely understand why
ignite chose Rendezvous over consistent hashing for partition to node
mapping.
Does the later gives some clear performance boost.
https://www.gridgain.com/resources/blog/data-distribution-in-apache-ignite
s say all entries are removed from cache, disk space used
> for the cache remains as is.
>
> My observation is that the data is deleted from disk after
> cache.destroy(), but I can not do this operation as the data is
> continuously being read/written on the cache.
>
>
>
Do you manually remove that entry from cache or using eviction/expiration
policy.
Can you share cache configuration please.
This thread might help you(comments)
https://stackoverflow.com/questions/48951091/ignite-how-eviction-expiry-and-rebalancing-work-with-external-cachestore
On Tue, Feb 22,
Yes thank you !
On Wed, Feb 16, 2022, 14:33 Pavel Tupitsyn wrote:
> I think schema name is required:
> SELECT * FROM "deptCache".DEPARTMENT
>
> On Wed, Feb 16, 2022 at 11:55 AM Surinder Mehra
> wrote:
>
>> Hi,
>> I tried to execute sql commands
Hi,
I tried to execute sql commands in control centre as per demo in ignite
training on 15h feb
I always get thai error " table not found"
As you can see table name and schema is present on control centre. Same
query works in java code.
Am I missing something?
Cache Config:
CacheConfiguration
Hey guys,
Can someone explain pls why snaphot restore doesnt work woth control.sh
On Fri, Feb 4, 2022, 18:57 Surinder Mehra wrote:
> hey,
> Did you get a chance to review my queries please.
>
> On Thu, Feb 3, 2022 at 4:40 PM Surinder Mehra wrote:
>
>> Hi,
>> So t
hey,
Did you get a chance to review my queries please.
On Thu, Feb 3, 2022 at 4:40 PM Surinder Mehra wrote:
> Hi,
> So the way I am thinking to use it is if we lose the EBS volume and we
> need to restore the cluster state back. I would have a secondary EBS as my
> snapshot direct
> - run ./control.sh --snapshot restore snapshot_1 --start
>
> Can you provide the directory structure of the Ignite working
> directory? (use `tree` command)
>
> On Wed, 2 Feb 2022 at 22:15, Surinder Mehra wrote:
> >
> > Hi,
> > Could you please point out if i miss
Hi,
Could you please point out if i missed something?
On Wed, Feb 2, 2022, 13:39 Surinder Mehra wrote:
> Hey thanks for your suggestions.
>
> I tried restoring using control.sh but it doesn't seem to work. Below are
> steps
> 1. Started 3 nodes and added data using a thick clie
rom the snapshot.
> - do not forget to backup and clear the original wal directory in case
> of restoration.
> - you may use control.sh --snapshot restore command to restore from a
> snapshot (this was added in 2.11)
>
> [1] https://issues.apache.org/jira/browse/IGNITE-13805
>
> On
join it
11. Cluster is ready
On Mon, Jan 31, 2022 at 7:14 PM Surinder Mehra wrote:
> Hi,
> We are using ignite 2.11.1 to experiment with ignite snapshots. We tried
> steps mentioned on below page to restore ignite data from snapshot
> https://ignite.apache.org/docs/latest/snapsho
I was trying to add and remove nodes as mentioned in the blog below.
When I kill a node and try running ./control.sh --baseline. It consistently
throws errors
https://dzone.com/articles/apache-ignite-baseline-topology-by-examples
I tried it several times. When I restarted that node, it started
Hi Stephen,
I tried it again to identify issues. This time I commented out the line
which was activating the cluster everytime client started. It looks to work
properly now.
Thanks for your help.
On Mon, Jan 31, 2022 at 8:58 PM Surinder Mehra wrote:
> Hi,
> Backups are configured,
e deptCache =
> ignite.getOrCreateCache(deptCacheConfig);
>
> The default is zero backups, so loss of a single node results in lost
> partitions.
>
> Note, that since you have persistence enabled, you’ll have to drop and
> recreate the table for the change to take effect.
>
&g
Hi,
We are using ignite 2.11.1 to experiment with ignite snapshots. We tried
steps mentioned on below page to restore ignite data from snapshot
https://ignite.apache.org/docs/latest/snapshots/snapshots
But we get the below error when we start a cluster after copying data
manually as mentioned on
ate=ACTIVE, CPUs=8, offheap=19.0GB, heap=24.0GB]
[17:40:44] ^-- Baseline [id=0, size=3, online=2, offline=1]
Does it mean for query to run, baseline must have all nodes up ?
On Mon, Jan 31, 2022 at 4:46 PM Surinder Mehra wrote:
> Hi, thanks for pointing out the problem of why data is being st
e completed only once, not every time
> the cluster (or node) starts. This is probably why all the data is being
> stored on a single machine.
>
> Second, you create a cache but without any backups. That means that when a
> node dies, you lose access to all the data.
>
> > On
Hi Guys,
I observed below behavior with persistence enabled. Could you please check
and confirm if it's a bug or I missed some configuration.
Steps:
1. Start ignite node1 and 2 with persistence enabled
2. Step 1 will write few entries to ignite cache
3. All entries go to one node
4. Stop node
Just curious, why can't we use continuous query here with "appropriate"
event type to write to another cache. So your listener will do below things
1. Write entry to another cache
2. remove entry from source cache
Just an idea, please correct if I am wrong
On Fri, Jan 28, 2022 at 3:49 PM Sumit
Hi,
Asking further queries on this post here. Is it possible to use S3 as
backend persistent store for ignite caches.
We are exploring options to backup and restore data into ignite.
2.11.x snapshots don't support incremental backups and PITR.
I found the link how to read full object. But would still like to
understand why SqlQuery is deprecated.
https://stackoverflow.com/questions/66248464/how-to-get-ignite-cache-sql-query-to-return-value-object
On Mon, Jan 17, 2022 at 4:54 PM Surinder Mehra wrote:
> Hi,
> With Igni
1 - 100 of 128 matches
Mail list logo
