I had checked the resource you mentioned, but I was confused with grid-gain
doc describing it as protection against split-brain. Because if the node
is segmented the only thing one can do is stop/restart/noop.
I was just wondering how it provides protection against split-brain.
Now I think by prot
Hello, Igniters.
Join us on Ignite meetup!
There will be cool old fashioned geeky Ignite talks and a "round table"
discussion about Ignite future.
It will happen on *December 3 in Moscow* and will be hosted by Sberbank near
the subway Kutuzovskaya.
Topics:
* Ignite affinity function.
* upcom
Not sure i follow. The data is on server node/s. Even for a single/multiple
requests, 'get' from a client will need to make a n/w round trip if server
and client are on different boxes vs both being on the same box. So n/w
latency becomes quite relevant.
--
Sent from: http://apache-ignite-users.
Hi,
Have just found an issue in Ignite JIRA:
https://issues.apache.org/jira/browse/IGNITE-10840
Does it fits your case?
Seems like this point is crucial:
/4)Change the walArchivePath to walPath as it described here:
See config2.xml
https://apacheignite.readme.io/docs/write-ahead-log#section-d
Hello,
Could you please share the full log? This must shed some light on events
happened prior to the issue.
I suspect that there is some checkpoint process failure logged, you might
look up for occurences of "Failed to process checkpoint" or "Failed to find
checkpoint record at the given WAL po
Hello,
Basically this is a mechanism to implement custom logical/network
split-brain protection. Segmentation resolvers allow you to implement a way
to determine if node has to be segmented/stopped/etc in method
isValidSegment() and possibly use different combinations of resolvers within
processor
Hello,
Can confirm that this is not working because multistatement execution is not
yet supported by the console/visor.
I've tested your case a little with JDBC and it works just fine for the
statements you have shared with snippet like this:
try (Connection conn =
DriverManager.getConne
Hello!
I don't understand why the network hop is relevant here, if you are
(supposedly) running those gets in parallel.
Regards,
--
Ilya Kasnacheev
чт, 28 нояб. 2019 г. в 04:09, Victor :
> Performed one more test. Moved the client on the same box, and changed the
> off & on heap values.
>
> T
Hello!
Are you actually sure that city_id is not null for this row of city table?
Regards,
--
Ilya Kasnacheev
чт, 28 нояб. 2019 г. в 15:47, Shravya Nethula <
shravya.neth...@aline-consulting.com>:
> Hi,
>
> I am trying to select same city_id value for all the rows in "person"
> table, using
Hi,
I am trying to select same city_id value for all the rows in "person" table,
using the following query:
SELECT id, name, age, (SELECT city_id FROM city WHERE id=1001) AS cityId FROM
person
But it is not giving results as expected. Please find the screenshot below:
[cid:8255bcba-f678-4814-9
Hi - I am currently using ignite version 2.7.6 and the files do get deleted
whenever i restart the server but after that they continuously stack-up. One
thing that i have noticed in the log files is this message "Could not clear
historyMap due to WAL reservation on cp:". I checked the code and foun
I have below question:
Do both on-heap & off-heap caches use memory from data regions (by setting
initial & max
of DataRegionConfiguration)?
Does Ignite use heap provided to the application (-Xms & -Xmx) for cache
storage?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Can someone please help me out with following questions.
1) If the ignite is capable of detecting nodes segmentation and taking
STOP,RESTART_JVM or NOOP action based on configured failure handlers then
why do we need explicit SegmentationResolvers?
2) Does ignite always treat node segmentati
13 matches
Mail list logo
