Hi,
We are trying to use Apache Ignite along with Hadoop Accelerator on *WINDOWS
7*.
Hadoop is installed with all native library dependencies. We are able to
execute 'hadoop fs' commands successfully.
When we are trying to start up an Ignite server node , we get the following
error and the node
Hi,
Node could be segmented if it doesn't respond during some time. The most
common reasons for that:
1) Long GC pause.
2) Operation system could slow down process (f.e. starts swap to disk
process memory).
3) Network issues.
To find out the actual reason you should take GC logs
Hi, could you please describe your use case a bit more detailed? If I
understand correctly you want to send jobs into another JVM processes?
What's the point of such solution?
--
View this message in context:
>From logs that you sent I see discovery issue: unsuccessful first connect and
long retry. Please do the following: in discovery config leave only server
address and reset timeouts to default value. Small timeouts will force
client fail fast and do not wait response from server.
--
View this
Hi Vaibhav,
Java heap size can only be set via startup options -Xms and -Xmx.
On Fri, Nov 25, 2016 at 1:45 PM, vaibhav sharma <
vaibhav.dutt.sha...@gmail.com> wrote:
> Hi All,
>
> I am starting a ignite server node via Java and observed that it spins out
> with default 0.5 GB on heap size.
>
>
Hi All,
I am starting a ignite server node via Java and observed that it spins out
with default 0.5 GB on heap size.
I'd like know how can we manipulate the JVM on heap size from Java code
while doing ignition.start ()
Regards,
Vaibhav
Hi all.
On one of our clusters we have 3 server nodes. 2 times in this week one of
the nodes in cluster stops. We are getting errors that stating the node is
stopping. We listen node joined and left events and before errors we see
logs saying node x left cluster. I suspect that the reason is
