Hello,
I'm curious about DataRegion with node start.
Does the DataRegion size configure allow space at the beginning of a node or
use space while using it?
Thank you so much!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi, can someone please suggest on above.
Why client is trying to use different port other than its for creating TCP
client and failing 30 times
Thanks.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Apache Ignite solutions can be built with many languages (e.g. Java,
C#/.NET, C++, etc.), using multiple deployment patterns (e.g. Cache, IMDG,
IMDB, DIH, etc.), and can be coded & built using an almost endless array of
tools, techniques, and templates (Gradle/Maven, #IGNITEHOME/examples,
Ignore the last email. Ivan your reply was sent to spam unfortunately so I
didn't see it.
I'll try setting the localhost property as you've suggested.
On Tue, Jun 30, 2020 at 6:25 AM Pavel Vinokurov
wrote:
> Hi Courtney,
>
> Probably you need to specify a local ip address to bind to by setting
Bumping this. Any suggestions on the below?
Not only is it undesirable to run the cluster on public IPs from a security
aspect but it incurs additional cost in the cloud env it is being deployed
in.
On Mon, Jun 29, 2020 at 7:18 PM Courtney Robinson
wrote:
> I've deployed Ignite bare-metal and
Thanks for replying.
The stackoverflow question was answered.
SELECT a, b, c, cntFROM T1 INNER JOIN (
> SELECT c, COUNT(c) as cnt
> FROM T1
> GROUP BY c) countsON counts.c = c
>
> The above produces the aggregate value as well as each row which
contributed to the aggregate.
On Mon, Jul 6,
After enabling the debug level logging we notice below
Machine in india(10.101.137.123) running on port 56037, but why the tcp
client is being tried to create with port 48104. Please note that 48104 is
the port of the other node in prague.
Could you please point out the things done wrong.
Hello!
We can only recommend to use the latest release of Apache Ignite, which is
currently 2.8.1.
Regards,
--
Ilya Kasnacheev
пн, 6 июл. 2020 г. в 07:48, Ishan Gandhi :
> Considering migrating from Gridgain Ignite version 8.5.8 or 8.7.13, So what
> are the equivalent Apache Ignite versions
Hi Stephen,
We have started our node with below JVM parameters. Also, we have increased
these timeouts
failureDetectionTimeout/clientFailureDetectionTimeout/networkTimeout to 48.
-XX:+AggressiveOpts -XX:+AlwaysPreTouch -XX:+UseG1GC -XX:+ScavengeBeforeFullGC
-XX:+DisableExplicitGC
I’m not sure I understand the question. Can you give an example of the source
data and the results you’re expecting?
> On 4 Jul 2020, at 19:17, Courtney Robinson wrote:
>
> I've posted this question on Stackoverflow here
>
There are a few issues here — the blocked thread, the communication error — but
I possibly the key one is the JVM pause:
[2020-07-03T18:17:21,793][WARN
][jvm-pause-detector-worker][IgniteKernal%CustomerCC] Possible too long JVM
pause: 10133 milliseconds.
This is usually due to garbage
11 matches
Mail list logo