Hi Ilya,
I have a working cluster now. Thanks again for your help. :)
Devin
On 2/21/20 4:31 AM, Devin Anderson wrote:
Hi Ilya,
Thank you very much. I suspect (1) is the missing piece of information I was
looking for. I'll add it when I get a chance and will report back.
Thanks again,
D
Hi Ilya,
Thank you very much. I suspect (1) is the missing piece of information I was
looking for. I'll add it when I get a chance and will report back.
Thanks again,
Devin
On 2/21/20 4:24 AM, Ilya Kasnacheev wrote:
Hello!
I'll start in the reverse order:
3. If everything is OK, the pro
Hello!
I'll start in the reverse order:
3. If everything is OK, the process should take around a second (for
non-persistent cluster).
2. As soon you see "Topology snapshot" in the log, the process is complete.
1. From your configuration I see suspicious that it only lists two other
nodes and not
Hi Ilya,
That certainly makes sense, but I'm not totally sure how to act on that
information yet. A couple questions:
1.) Given the configuration file I posted (which is basically the same on each
node in the cluster, save that the IP addresses of the nodes to discover are
different), shoul
Hello!
Your node has never finished joining to cluster nor was able to
self-discover to form a cluster of its own, as evident by:
"main" #1 prio=5 os_prio=0 tid=0x7f7e8000d000 nid=0x5fed waiting on
condition [0x7f7e8875f000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lan
Hi Ilya,
I'm attaching the `jstack` dump to this message. When I took the dump, there
were ten requests that had been made to the Apache Ignite REST API using POST
data of the form:
cmd=add&key=[key]&value=[value]
... where [key] and [value] were proper URI encoded data.
Thanks in adva
Hello!
Please collect thread dump (jstack) from affected node, share it with us.
Regards,
--
Ilya Kasnacheev
чт, 20 февр. 2020 г. в 16:17, Devin Anderson :
> Hi all,
>
> I'm seeing issues wherein the Apache Ignite REST API appears to accept
> requests, but doesn't ever reply. This doesn't al
Hi all,
I'm seeing issues wherein the Apache Ignite REST API appears to accept
requests, but doesn't ever reply. This doesn't always happen; for example, if
I make a request that I expect the API to reject, I get back a response:
--
# curl -v -X GET 'http://127.0.0.1:8080/ignite'
*
