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
and
start a cluster as 1st node. Try adding [own ip address]
Regards,
--
Ilya Kasnacheev
пт, 21 февр. 2020 г. в 14:52, Devin Anderson <mailto:dande...@akamai.com>>:
Hi Ilya,
That certainly makes sense, but I'm not totally sure how to act on that
information yet. A coupl
e is in topology, obviously it can't serve any requests.
Regards,
--
Ilya Kasnacheev
пт, 21 февр. 2020 г. в 01:55, Devin Anderson <mailto:dande...@akamai.com>>:
Hi Ilya,
I'm attaching the `jstack` dump to this message. When I took the dump,
there
were ten re
for any help. I'll take a look as well and try to figure out
what's going on.
Devin
On 2/20/20 5:43 AM, Ilya Kasnacheev wrote:
Hello!
Please collect thread dump (jstack) from affected node, share it with us.
Regards,
--
Ilya Kasnacheev
чт, 20 февр. 2020 г. в 16:17, Devin Anderson <mailto:da
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'
*
::Bump::
Devin
On 2/17/20 5:42 PM, Devin Anderson wrote:
Hi all,
I'm not sure if this is the correct mailing list to bring up this issue. If
I'm writing the wrong mailing list, please let me know and I'll gladly send
my message to a more appropriate list/person.
When I attempt to run
Hi all,
I'm not sure if this is the correct mailing list to bring up this issue. If
I'm writing the wrong mailing list, please let me know and I'll gladly send my
message to a more appropriate list/person.
When I attempt to run `apt-get update` on Ubuntu 18.04 with the Apache Ignite
