You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by John Smith <ja...@gmail.com> on 2023/02/23 22:36:09 UTC

Apache ignite.sh script can't detect CPUs or network etc///

Hi I'm running Ignite in openstack and I attempted to resize the virtual
machine, that part seems to have worked but now when I restart ignite it
can't seem to join the cluster.

It seems maybe like a permission issue but not sure... Any ideas?

1- Ignite was installed using deb package.
2- When I run "sudo /usr/share/apache-ignite/bin/ignite.sh" the node
detects the OS info and displays: Topology snapshot [ver=1,
locNode=532afd5c, servers=1, clients=0, state=ACTIVE, CPUs=4,
offheap=6.3GB, heap=7.9GB]
3- When I run sudo /usr/share/apache-ignite/bin/ignite.sh
/etc/apache-ignite/basic-config.xml" the node can't detect the info and
displays: Topology snapshot [ver=1, locNode=1ea0058d, servers=1, clients=0,
state=INACTIVE, CPUs=-1, offheap=3.0GB, heap=0.1GB]
4- Same with Systemd service as #3 above. This used to work before.

Re: Apache ignite.sh script can't detect CPUs or network etc///

Posted by John Smith <ja...@gmail.com>.
Ok figured out. Needed to delete the cache files for the cache in
maintenance mode.

On Thu., Feb. 23, 2023, 6:03 p.m. John Smith, <ja...@gmail.com>
wrote:

> Ok i noticed this when I put -v
>
> Node is being started in maintenance mode. Starting IsolatedDiscoverySpi
> instead of configured discovery SPI.
>
> How do I fix this? I guess resizing the VM fucked up soemthing.
>
> On Thu, Feb 23, 2023 at 5:36 PM John Smith <ja...@gmail.com> wrote:
>
>> Hi I'm running Ignite in openstack and I attempted to resize the virtual
>> machine, that part seems to have worked but now when I restart ignite it
>> can't seem to join the cluster.
>>
>> It seems maybe like a permission issue but not sure... Any ideas?
>>
>> 1- Ignite was installed using deb package.
>> 2- When I run "sudo /usr/share/apache-ignite/bin/ignite.sh" the node
>> detects the OS info and displays: Topology snapshot [ver=1,
>> locNode=532afd5c, servers=1, clients=0, state=ACTIVE, CPUs=4,
>> offheap=6.3GB, heap=7.9GB]
>> 3- When I run sudo /usr/share/apache-ignite/bin/ignite.sh
>> /etc/apache-ignite/basic-config.xml" the node can't detect the info and
>> displays: Topology snapshot [ver=1, locNode=1ea0058d, servers=1, clients=0,
>> state=INACTIVE, CPUs=-1, offheap=3.0GB, heap=0.1GB]
>> 4- Same with Systemd service as #3 above. This used to work before.
>>
>

Re: Apache ignite.sh script can't detect CPUs or network etc///

Posted by John Smith <ja...@gmail.com>.
Ok i noticed this when I put -v

Node is being started in maintenance mode. Starting IsolatedDiscoverySpi
instead of configured discovery SPI.

How do I fix this? I guess resizing the VM fucked up soemthing.

On Thu, Feb 23, 2023 at 5:36 PM John Smith <ja...@gmail.com> wrote:

> Hi I'm running Ignite in openstack and I attempted to resize the virtual
> machine, that part seems to have worked but now when I restart ignite it
> can't seem to join the cluster.
>
> It seems maybe like a permission issue but not sure... Any ideas?
>
> 1- Ignite was installed using deb package.
> 2- When I run "sudo /usr/share/apache-ignite/bin/ignite.sh" the node
> detects the OS info and displays: Topology snapshot [ver=1,
> locNode=532afd5c, servers=1, clients=0, state=ACTIVE, CPUs=4,
> offheap=6.3GB, heap=7.9GB]
> 3- When I run sudo /usr/share/apache-ignite/bin/ignite.sh
> /etc/apache-ignite/basic-config.xml" the node can't detect the info and
> displays: Topology snapshot [ver=1, locNode=1ea0058d, servers=1, clients=0,
> state=INACTIVE, CPUs=-1, offheap=3.0GB, heap=0.1GB]
> 4- Same with Systemd service as #3 above. This used to work before.
>