Can we Upgrade from 2.13.0 to 2.16.0 Opensource or we need to kill the
whole cluster and all clients?
On Tue, Dec 26, 2023 at 2:33 PM Nikita Amelchev
wrote:
> The Apache Ignite Community is pleased to announce the release of
> Apache Ignite 2.16.0.
>
> Apache Ignite® is an in-memory computing pl
The other is that you've enabled write throttling.
> Counter-intuitively, you might want to *dis*able that. It'll still do
> write throttling, just using a different algorithm.
>
> On Tue, 31 Oct 2023 at 15:35, John Smith wrote:
>
>> I understand you have no time and I h
be a *big* problem. You need to
> tune your JVM. There are some hints in the documentation:
> https://ignite.apache.org/docs/latest/perf-and-troubleshooting/memory-tuning
>
>
> On Tue, 31 Oct 2023 at 13:16, John Smith wrote:
>
>> Does any of this infor help? I included what we
Does any of this infor help? I included what we do more or less plus stats
and configs.
There are 9 caches of which the biggest one is 5 million records
(partitioned with 1 backup), the key is String (11 chars) and the value
integer.
The rest are replicated and some partitioned but max a few thou
Mon, 30 Oct 2023 at 15:12, John Smith wrote:
>
>> Hi I see this error message on the server node...
>>
>> [21:37:20,310][SEVERE][query-#2884155%raange%][GridMapQueryExecutor]
>> Failed to send message.
>> class org.apache.ignite.internal.cluster.ClusterTopologyChec
Hi I see this error message on the server node...
[21:37:20,310][SEVERE][query-#2884155%raange%][GridMapQueryExecutor] Failed
to send message.
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
Failed to send message (node left topology): TcpDiscoveryNode
[id=d6a33cc0-59e7-4
that.
My question now would be, if using the HTTP REST Api, can we specify the
type of the value when doing a put?
On Fri, Sep 29, 2023 at 1:29 PM John Smith wrote:
> Hi, running 2.12
>
> When I use the put command like so:
> http://xx/ignite?cmd=put&cacheName=carrier-ids-for-
Hi, running 2.12
When I use the put command like so:
http://xx/ignite?cmd=put&cacheName=carrier-ids-for-phones&key=15149838779&val=10009&exp=60001
Then I call the Java get async function, it seems to block and doesn't
return.
If I use this command:
http://xx/ignite?cmd=put&cacheName=carr
Never mind, my Kubernetes Service wasn't getting endpoints. But weirdly
enough there was still some sort of connection going on.
On Thu, Jul 20, 2023 at 9:16 PM John Smith wrote:
> So the client is exposed as node ports and I have been able to provide the
> proper ports back to the
So the client is exposed as node ports and I have been able to provide the
proper ports back to the client and cluster...
When I look at the node details I see...
| Address (0) | 10.xxx.xxx.xxx|
< Kubernetes internal I.P
| Address (1) |
apache.org/docs/latest/code-deployment/deploying-user-code
>
> On 1 Mar 2023, at 18:59, John Smith wrote:
>
> So I'm stuck with a catch 22 here... I can't enable the flag on the server
> nodes without shutting down all the client nodes and vise versa
>
> Unless I
hared
folder to periodically load classes?
On Mon., Feb. 27, 2023, 11:11 a.m. John Smith,
wrote:
> Sorry to be clear the applications are thick clients but client = true
> flag is enabled.
>
> On Mon, Feb 27, 2023 at 11:09 AM John Smith
> wrote:
>
>> Oh god! Forget that then! l
lace.
>
> If your data is skewed in some way so that there is more data in some
> partitions than others, then you could find one machine with more work to
> do than others. All else being equal, you’ll also get better distribution
> with more than three nodes.
>
> On 1 Mar 202
23, at 20:32, John Smith wrote:
>
> The last thing I can add to clarify is, the 3 node cluster is a
> centralized cluster and the CSV loader is a thick client running on its own
> machine.
>
> On Tue, Feb 28, 2023 at 2:52 PM John Smith wrote:
>
>> Btw when I run a que
The last thing I can add to clarify is, the 3 node cluster is a centralized
cluster and the CSV loader is a thick client running on its own machine.
On Tue, Feb 28, 2023 at 2:52 PM John Smith wrote:
> Btw when I run a query like SELECT COLUMN_2, COUNT(COLUMN_1) FROM MY_TABLE
> GROUP BY CO
, but
same thing, one node runs full tilt while the others are "slowish"
Queries are ok, all nodes are fully utilized.
On Tue, Feb 28, 2023 at 12:54 PM John Smith wrote:
> Hi so I'm using it in a pretty straight forward kind of way at least I
> think...
>
> I'm lo
is skewed such that one node
> gets more data than 2x the data sent to other partitions because of
> affinity? In this case, for example, changes to affinity/colocation design
> or changes to cluster topology (more nodes with greater CPU to RAM ratio?)
> can help distribute the load so that no single node becomes a bottleneck.
>
> On Tue, Feb 28, 2023 at 9:27 AM John Smith wrote:
>
>> Hi I'm using the data streamer to insert into a 3 cluster node. I have
>> noticed that 1 node is pegging at 100% cpu while the others are at 40ish %.
>>
>> Is that normal?
>>
>>
>>
Hi I'm using the data streamer to insert into a 3 cluster node. I have
noticed that 1 node is pegging at 100% cpu while the others are at 40ish %.
Is that normal?
Sorry to be clear the applications are thick clients but client = true flag
is enabled.
On Mon, Feb 27, 2023 at 11:09 AM John Smith wrote:
> Oh god! Forget that then! lol Really? So If I have 10 applications they
> all need to be recompiled/reconfigured and redeployed?
>
> On Mon,
ue on all
> nodes, both server and thick-client.
>
> > On 27 Feb 2023, at 15:58, John Smith wrote:
> >
> > I have 3 node clusters and I'm trying to enable peer class loading on
> the cluster, but it keeps shutting off after restart because it says the
> remote node
I have 3 node clusters and I'm trying to enable peer class loading on the
cluster, but it keeps shutting off after restart because it says the remote
node doesn't have it enabled.
So is peer class loading required to be enabled on the server nodes or can
it just be enabled per client that needs it
Ok figured out. Needed to delete the cache files for the cache in
maintenance mode.
On Thu., Feb. 23, 2023, 6:03 p.m. John Smith,
wrote:
> Ok i noticed this when I put -v
>
> Node is being started in maintenance mode. Starting IsolatedDiscoverySpi
> instead of configured discovery
Ok i noticed this when I put -v
Node is being started in maintenance mode. Starting IsolatedDiscoverySpi
instead of configured discovery SPI.
How do I fix this? I guess resizing the VM fucked up soemthing.
On Thu, Feb 23, 2023 at 5:36 PM John Smith wrote:
> Hi I'm running Ignite in o
Hi I'm running Ignite in openstack and I attempted to resize the virtual
machine, that part seems to have worked but now when I restart ignite it
can't seem to join the cluster.
It seems maybe like a permission issue but not sure... Any ideas?
1- Ignite was installed using deb package.
2- When I
; temporarily lost some availability.
>
> However, that’s not how it currently works. If you shut down more nodes
> than you have backups, then you have to reset lost partitions.
>
> On 20 Feb 2023, at 18:14, John Smith wrote:
>
> My cache config for distributed cache is as follows...
ated way to reset lost partitions. Nor should there be
> (IMHO). If you have lost partitions, you have probably lost data. That
> should require manual intervention.
>
> On 14 Feb 2023, at 17:58, John Smith wrote:
>
> Hello, does anyone have insights on this?
>
> On Thu., Feb. 9
Hello, does anyone have insights on this?
On Thu., Feb. 9, 2023, 4:28 p.m. John Smith, wrote:
> Any thoughts on this?
>
> On Mon., Feb. 6, 2023, 8:38 p.m. John Smith,
> wrote:
>
>> That Jira doesn't look like the issue at all. That issue seems to suggest
>
Any thoughts on this?
On Mon., Feb. 6, 2023, 8:38 p.m. John Smith, wrote:
> That Jira doesn't look like the issue at all. That issue seems to suggest
> that there is a "data loss" exception. In our case the grid sets the cache
> in a "safe" mode... "
ag.
On Mon, Feb 6, 2023 at 7:46 PM 18624049226 <18624049...@163.com> wrote:
> https://issues.apache.org/jira/browse/IGNITE-17657
> 在 2023/2/7 05:41, John Smith 写道:
>
> Hi, sometimes when we perform maintenance and reboot nodes we get "All
> partition owners have left the gri
Hi, sometimes when we perform maintenance and reboot nodes we get "All
partition owners have left the grid" and then we go and run ./control.sh
--host ignite-xx --cache reset_lost_partitions some-cache and
everything is fine again...
This seems to happen with partitioned caches and we are runn
It started fine and it also recreated the partitions for that cache.
On Fri, Dec 16, 2022 at 10:48 AM John Smith wrote:
> Weird because after restart and just deleting the
> work/db/node-xx/cache-my-cache folder on the node that shutdown. It
> started up fine and I have the same
ease update your /etc/security/limits.conf records for the user you run
> your app with.
>
> I also raised fs.file-max to 2097152 which may be excessive, but I don't
> see a problem with setting it that high.
>
> Cheers
> Gianluca
>
> On Fri, 16 Dec 2022 at 01:39, John Smith
Hi it seems the JVM was forcefully shutdown when I tried to create a new
partitioned cache.
The error seems to indicate that it was "too many files" can someone from
Ignite confirm this?
I have checked with lsof and Ignite only has about 3600 files open. It's
the only service running on that serv
Something like this?
https://ignite.apache.org/use-cases/hadoop-acceleration.html
On Thu., Sep. 22, 2022, 3:44 a.m. Stephen Darlington, <
stephen.darling...@gridgain.com> wrote:
> I don’t know of anyone doing this, however it looks like it should be
> possible.
>
> According to a quick skim of t
Nah, it's fine just wanted to make sure what it was. Unless you think I
should log at least an issue?
On Wed, Sep 14, 2022 at 3:13 AM Zhenya Stanilovsky via user <
user@ignite.apache.org> wrote:
> Yep, i already mention that you can`t disable this pool at all and 1
> worker thread still be visib
Ok so just to understand on the client side. Set the pool size for data
streamer to 1.
But it will still look blocked?
On Mon., Sep. 12, 2022, 8:59 a.m. Zhenya Stanilovsky via user, <
user@ignite.apache.org> wrote:
> John, seems all you can here is just to set this pool size into «1» , «0»
> — t
Hi I'm profiling my application through YourKit and it indicates that a
bunch of these threads (data-streamer-stripe) are "frozen" for 21 days.
This
I'm not using data streaming, is there a way to disable it or just ignore
the messages? The application is configured as thick client (client = true)
Ok but since I dropped and recreated the table I'm fine? It won't somehow
throw that error again? And if I upgrade to 2.13 from 2.12 will I have the
same issue?
On Wed, Aug 31, 2022 at 3:31 PM Alex Plehanov
wrote:
> John Smith,
>
> Thank you. This issue will be fixed in up
25 AM Alex Plehanov
wrote:
> John Smith,
>
> Can you please show DDL for the car_code table? Does PK of this table
> include provider_id or car_code columns?
> I found a compatibility issue, with the same behaviour, it happens when
> storage created with Ignite version before
The only other thing I can think of is that I did an upgrade to 2.12.0
On Thu, Aug 4, 2022 at 12:52 PM John Smith wrote:
> Personally I think there is some sort of index corruption. I dropped the
> table and recreated it and my problem went away.
> I never restarted the applicati
Personally I think there is some sort of index corruption. I dropped the
table and recreated it and my problem went away.
I never restarted the application and it started to work again.
Maybe you can make a copy of your table, insert the data fresh and point
your app to the copied table. And see i
Let me know if that makes any sense, because the test data is the same and
the application code is the same. Only dropped and created the table again
using DbEaver.
On Wed, Aug 3, 2022 at 11:39 AM John Smith wrote:
> Hi, so I dropped the table and simply recreated it. Did NOT restart
Hi, so I dropped the table and simply recreated it. Did NOT restart the
application.
Now it works fine.
On Wed, Aug 3, 2022 at 9:58 AM John Smith wrote:
> How? The code is 100% the same between production and dev. And it's part
> of a bigger application.
>
> Only dev has the i
How? The code is 100% the same between production and dev. And it's part of
a bigger application.
Only dev has the issue. I will drop and recreate the table if that fixes
the issue then what?
You are saying mismatch, it's a string period.
"select car_id from car_code where provider_id = ? and ca
tion.
>
> I am still trying to create a smaller repro case, that’s why I haven’t
> described my solution in more detail in my other thread yet.
>
>
>
> On 02.08.22 at 23:04, John Smith wrote:
>
> From: "John Smith"
> Date: 2. August 2022
> To: user@ignite
ков wrote:
> Hello, John.
>
> Provided stack trace not enough to answer your question.
> Can you, please, provide log from the remote node?
>
> 2 авг. 2022 г., в 17:14, John Smith написал(а):
>
> Anyone?
>
> On Fri, Jul 29, 2022 at 8:44 AM John Smith wrote:
>
>
Anyone?
On Fri, Jul 29, 2022 at 8:44 AM John Smith wrote:
> Any thoughts on this?
>
> On Mon., Jul. 25, 2022, 11:29 a.m. John Smith,
> wrote:
>
>> Hi I have the following code and I get the below exception. The cache
>> runs on 3 remote nodes and it is accessed by
Any thoughts on this?
On Mon., Jul. 25, 2022, 11:29 a.m. John Smith,
wrote:
> Hi I have the following code and I get the below exception. The cache runs
> on 3 remote nodes and it is accessed by thick client (client = true)
>
> String sql = "select car_id from car_code where pr
Hi I have the following code and I get the below exception. The cache runs
on 3 remote nodes and it is accessed by thick client (client = true)
String sql = "select car_id from car_code where provider_id = ? and
car_code = ? order by car_id asc limit 1;"
Integer providerId = 1;
String cardCode = "
ert
> data to the table?
>
> Thanks,
> Maksim
>
> On Fri, Feb 25, 2022 at 9:32 PM John Smith wrote:
>
>> Hi Maksim did you look into this?
>>
>> On Tue., Feb. 22, 2022, 9:51 a.m. John Smith,
>> wrote:
>>
>>> Hi. This is it.
>
Hi Maksim did you look into this?
On Tue., Feb. 22, 2022, 9:51 a.m. John Smith,
wrote:
> Hi. This is it.
>
> create table if not exists car_code (
> provider_id int,
> car_id int,
> car_code varchar(16),
> primary key (provider_id, car_id)
> ) with "tem
issue.
>
> Maksim
>
> On Tue, Feb 15, 2022 at 3:28 PM John Smith wrote:
>
>> It's weird. I dropped the table and recreated it without restarting the
>> client applications and it started worked.
>>
>> This hapenned after upgrading from 2.8.1 to 2.12.0
>
Maksim
>
> On Tue, Feb 15, 2022 at 8:54 AM John Smith wrote:
>
>> Hi, on the client side I'm getting the below Exception and on the server
>> side it is pasted below.
>>
>>
>> javax.cache.CacheException: Failed to execute map query on remote
Hi, on the client side I'm getting the below Exception and on the server
side it is pasted below.
javax.cache.CacheException: Failed to execute map query on remote node
[nodeId=6e350b53-7224-4b11-b81b-00f44c699b87, errMsg=General error: \"class
org.apache.ignite.IgniteCheckedException: Runtime fa
Appart the fact that we can't do rolling upgrades. The update worked.
On Fri., Jan. 21, 2022, 10:51 p.m. John Smith,
wrote:
> Is there an update compatibility guide somewhere? Running 2.8 and would
> like to update to 2.12?
>
Is there an update compatibility guide somewhere? Running 2.8 and would
like to update to 2.12?
So far I haven't seen anyone ask about the issue here in the lists. So I'll
give it a go.
I'm personally using 2.8.1
1- If we are running as a service using .DEB or .RPM or other linux
packages: The default logging is JUL so nothing to worry about.
2- If we aren' t specifically enabling the ignit
s. All in all, a very problematic
> situation, and the lack of automatic failover in particular has made me
> seriously question if Ignite is production-ready software.
>
> On Wed, Oct 6, 2021 at 8:52 AM John Smith wrote:
>
>> Ok. For now I rebooted all nodes... But it's fair
d5-4feb-417e-b965-bdc34a0a6f4f],
> super=CompletableLatch [id=CompletableLatchUid [id=exchange,
> topVer=AffinityTopologyVersion [topVer=103, minorTopVer=0]
>
> On Tue, 5 Oct 2021 at 10:07, John Smith > wrote:
>
> And I see this...
>
> [14:04:15,150][WARNING][ex
d [id=exchange,
topVer=AffinityTopologyVersion [topVer=103, minorTopVer=0]
On Tue, 5 Oct 2021 at 10:07, John Smith wrote:
> And I see this...
>
> [14:04:15,150][WARNING][exchange-worker-#43%raange%][GridDhtPartitionsExchangeFuture]
> Unable to await partitions release latch within
=false,
ver=2.8.1#20200521-sha1:86422096, isClient=false], ackSent=true,
super=CompletableLatch [id=CompletableLatchUid [id=exchange,
topVer=AffinityTopologyVersion [topVer=103, minorTopVer=0]
On Tue, 5 Oct 2021 at 10:02, John Smith wrote:
> Actually to be more clear...
>
> http://xx
Actually to be more clear...
http://xx-0001:8080/ignite?cmd=version responds immediately.
http://xx-0001:8080/ignite?cmd=size&cacheName=my-cache doesn't respond
at all.
On Tue, 5 Oct 2021 at 09:59, John Smith wrote:
> Yeah ever since I got this erro for example the R
Yeah ever since I got this erro for example the REST APi wont return and
the request are slower. But when I connect with visor I can get stats I can
scan the cache etc...
Is it possible that these async futures/threads are not released?
On Tue, 5 Oct 2021 at 04:11, Zhenya Stanilovsky wrote:
> H
Hi, using 2.8.1 I understand the message as in my async TRX is taking
longer but is there a way to prevent it?
When this happened I was pushing about 50, 000 get/puts per second from my
API.
So if I understand correctly the logs below...
The node that shut off was timing out trying to get partition exchange from
the indicated nodes and it shut itself off correct? Does this mean this
node was also the master?
1- The time indicated in the log is that UTC?
2- I'm trying to see if it was
So if I understand correctly the logs below...
The node that shut off was timing out trying to get partition exchange from
the indicated nodes and it shut itself off correct? Does this mean this
node was also the master?
1- The time indicated in the log is that UTC?
2- I'm trying to see if it was
rmance of some operations where the failed node has to be involved.
>
> Btw, what's the tool you are using for the monitoring? Looks nice.
>
> -
> Denis
>
>
> On Thu, Aug 20, 2020 at 6:44 AM John Smith wrote:
>
>> Hi here is an example of our cluster during our
s.
>
> It seems that you have too-long full GC. Either make sure it does not
> happen, or increase failureDetectionTimeout to be longer than any expected
> GC.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 17 авг. 2020 г. в 17:51, John Smith :
>
>> Hi
gt; No, the client will be getting an exception on an attempt to get an
> IgniteCache instance.
>
> -
> Denis
>
>
> On Fri, Aug 14, 2020 at 4:14 PM John Smith wrote:
>
>> Yeah I can maybe use vertx event bus or something to do this... But now I
>> have to t
Hi guys it seems every couple of weeks we lose a node... Here are the logs:
https://www.dropbox.com/sh/8cv2v8q5lcsju53/AAAU6ZSFkfiZPaMwHgIh5GAfa?dl=0
And some extra details. Maybe I need to do more tuning then what is already
mentioned below, maybe set a higher timeout?
3 server nodes and 9 clien
You can create templates in the XML and programmatically when you say
getOrCreate() you can specify the template to use and pass in random name
for the cache name ...
https://apacheignite.readme.io/docs/cache-template#:~:text=Cache%20templates%20are%20useful%20when,CREATE%20TABLE%20and%20REST%20co
when the cluster is not activated yet.
> Does this work for you?
>
> -
> Denis
>
>
> On Fri, Aug 14, 2020 at 3:12 PM John Smith wrote:
>
>> Is there any work around? I can't have an HTTP server block on all
>> requests.
>>
>> 1- I need to figure out
ue,
> compute, etc.). But I'll let the maintainers of those modules clarify.
>
> -
> Denis
>
>
> On Fri, Aug 14, 2020 at 1:44 PM John Smith wrote:
>
>> Hi Denis, so to understand it's all operations or just the query?
>>
>> On Fri., Aug. 14, 202
erations fail if
> the cluster is deactivated. Could you propose the change by starting a
> discussion on the dev list? You can refer to this user list discussion for
> reference. Let me know if you need help with this.
>
> -
> Denis
>
>
> On Thu, Aug 13, 2020 at 5:55 PM John
tly, Ignite
> verifies the activation status and generates the exception above whenever
> you're getting a reference to an IgniteCache or IgniteCompute. But once you
> got those references and try to run some operations then those get stuck if
> the cluster is not activated.
>
the third
> node joins the cluster and the cluster gets activated automatically?
>
> -
> Denis
>
>
> On Wed, Aug 12, 2020 at 11:08 AM John Smith
> wrote:
>
>> Ok Denis here they are...
>>
>> 3 nodes and I capture a yourlit screenshot of what it thinks ar
Ok Denis here they are...
3 nodes and I capture a yourlit screenshot of what it thinks are deadlocks
on the client app.
https://www.dropbox.com/sh/2cxjkngvx0ubw3b/AADa--HQg-rRsY3RBo2vQeJ9a?dl=0
On Wed, 12 Aug 2020 at 11:07, John Smith wrote:
> Hi Denis. I will asap but you I think you w
as cache.readAll() or
> cache.writeAll(..).
>
> Please take and attach thread dumps from all the cluster nodes for
> analysis if we need to dig deeper.
>
> -
> Denis
>
>
> On Mon, Aug 10, 2020 at 6:23 PM John Smith wrote:
>
>> Hi Denis, I think you are right. I
Hi Denis, I think you are right. It's the query that blocks the other k/v
operations are ok.
Any thoughts on this?
On Mon, 10 Aug 2020 at 15:28, John Smith wrote:
> I tried with 2.8.1, same issue. Operations block indefinitely...
>
> 1- Start 3 node cluster
> 2- Start client a
n all operations just block.
Basically the client application is an HTTP Server on each HTTP request
does cache exception.
On Fri, 7 Aug 2020 at 19:46, John Smith wrote:
> No, everything blocks... Also using 2.7.0 just in case.
>
> Only time I get exception is if the cluster is complete
calls fail with an exception if the cluster is deactivated. Do those fail
> on your end?
>
> As for the async and SQL operations, let's see what other community
> members say.
>
> -
> Denis
>
>
> On Fri, Aug 7, 2020 at 1:06 PM John Smith wrote:
>
>> Hi
Hi any thoughts on this?
On Thu, 6 Aug 2020 at 23:33, John Smith wrote:
> Here is another example where it blocks.
>
> SqlFieldsQuery query = new SqlFieldsQuery(
> "select * from my_table")
> .setArgs(providerId, carrierCode);
> query.setTimeout
even with the timeout set.
Is there a way to timeout and at least have the application continue and
respond with an appropriate message?
On Thu, 6 Aug 2020 at 23:06, John Smith wrote:
> Hi running 2.7.0
>
> When I reboot a node and it begins to rejoin the cluster or the cluster is
&g
Hi running 2.7.0
When I reboot a node and it begins to rejoin the cluster or the cluster is
not yet activated with baseline topology operations seem to block forever,
operations that are supposed to return IgniteFuture. I.e: putAsync,
getAsync etc... They just block, until the cluster resolves it'
genii
>
> чт, 6 авг. 2020 г. в 09:03, John Smith :
>
>> I'm testing failover scenarios and currently I have the full cluster shut
>> off. I would still like my application to continue working even if the
>> cache is not there...
>>
>> When my applicatio
I'm testing failover scenarios and currently I have the full cluster shut
off. I would still like my application to continue working even if the
cache is not there...
When my application starts...
It calls Ignition.start(config)
The application will not start until Ignition.start(config) finishe
ackup to afford losing a node.
>
> You should have all data nodes in the baseline.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 5 авг. 2020 г. в 17:56, John Smith :
>
>> I mean I have 3 nodes and the baseline is set to 3. Does it mean if I put
>> 2 as basel
will I still be able to do operations on
the cache?
On Wed, 5 Aug 2020 at 08:21, John Smith wrote:
> I have 3 nodes and baseline topology is 3 so if I lose 1 I guess it's
> enough... Should it be 2?
>
> On Tue., Aug. 4, 2020, 10:57 a.m. Ilya Kasnacheev, <
> ilya.kasn
ve lost enough nodes of your distributed grid that data is nowhere to be
> found now.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 3 авг. 2020 г. в 19:12, John Smith :
>
>> I get the below exception on my client...
>>
>> #1 I rebooted the cache nodes er
I get the below exception on my client...
#1 I rebooted the cache nodes error still continued.
#2 restarted the client node error went away.
#3 this seems to happen every few weeks.
#4 is there some sort of timeout values and retries I can put?
#5 cache operations seem to block when rebooting the
15 Jul 2020 at 17:45, Evgenii Zhuravlev
wrote:
> John,
>
> Then you should just get a new builder every time when you need it:
> myIgniteInstance.binary().builder("MyKey"). I don't see why you need to
> reuse builder from multiple threads here.
>
> Evgenii
>
> 2. No, you still can work with BinaryObjects instead of actual classes.
>
> Evgenii
>
> ср, 15 июл. 2020 г. в 08:50, John Smith :
>
>> Hi Evgenii, it works good. I have two questions...
>>
>> 1- Is the BinaryObjectBuilder obtained from
>> myIgniteInstance.b
Hi, testing some failover scenarios etc...
When we call cache.getAsync() and the state of the cluster is not active.
It seems to block.
I implemented a cache repository as follows and using Vertx.io. It seems to
block at the cacheOperation.apply(cache)
So when I call myRepo.get(myKey) which unde
l MyKey class then I suppose that needs to be
in the classpath on all nodes?
On Wed, 15 Jul 2020 at 10:43, John Smith wrote:
> Ok I will try it...
>
> On Tue, 14 Jul 2020 at 22:34, Evgenii Zhuravlev
> wrote:
>
>> John,
>>
>> It's not necessary to have class
Ok I will try it...
On Tue, 14 Jul 2020 at 22:34, Evgenii Zhuravlev
wrote:
> John,
>
> It's not necessary to have class at all, you can specify any type, you
> just need to use this type when creating binary object for this key.
>
> вт, 14 июл. 2020 г. в 17:50, John Smith
atest/developers-guide/key-value-api/binary-objects#creating-and-modifying-binary-objects
>
> Evgenii
>
> вт, 14 июл. 2020 г. в 07:18, John Smith :
>
>> Hi, I have an SQL table
>>
>> create table if not exists my_table (
>> column1 int,
>> column2 int,
>
Hi, I have an SQL table
create table if not exists my_table (
column1 int,
column2 int,
column3 varchar(16),
PRIMARY KEY (column1, column2)
) with "template=replicatedTpl";
and I'm creating my near cache as follows...
IgniteCache myCache;
NearCacheConfiguration nearConfig = new
NearCacheConfigu
Hi I want to get how many entries are on the thick client's near cache. Is
there a way?
You mean the connection config for visor to connect to the cluster?
On Wed., Jul. 8, 2020, 5:53 p.m. Humphrey, wrote:
> Not sure if this will help, I've also had issues with Visor keeps hanging
> the
> cluster.
>
> When I changed the configuration to ClientMode (default is ServerMode) it
> solve
493, expectedBackups=512.00,
> actualBackups=171, warningThreshold=50.00%]"
> How do you restart nodes? Do you wait until rebalance completed?
>
> Evgenii
>
>
>
> пт, 3 июл. 2020 г. в 09:03, John Smith :
>
>> Hi Evgenii, did you have a chance to look at the latest logs?
&g
1 - 100 of 217 matches
Mail list logo
