Hi,
This is clearly a usability issue in Ignite. I've created a ticket for it:
https://issues.apache.org/jira/browse/IGNITE-8839.
On Tue, Jun 19, 2018 at 6:17 PM, aealexsandrov
wrote:
> As a workaround, you can try to add execution rights (like in your example)
> to all files under work
As a workaround, you can try to add execution rights (like in your example)
to all files under work directory.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Is this issue reproducible? Can you change the work directory path or clear
your work directory and check again? Did you try to modify or copy anything
from work directory?
However, could you please provide the cluster configuration and code
reproducer?
BR,
Andrei
--
Sent from:
Exception not coming after running ignite with sudo.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Additional logs, caused by AccessDeniedException
2018-06-19 16:27:51 ERROR GridDhtPartitionsExchangeFuture:495 - Failed to
activate node components [nodeId=7ff3a67c-ed86-452a-9097-2626a0252a6e,
client=false, topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1]]
class
I am using Ignite 2.4 and using 2 server nodes and 1 client node.
Due to power failure my nodes shutdown.
So, After started two server nodes. I am getting following error.
Even, I tried to activate cluster by control.sh --activate. But it's not
responding anything.
Even same for baseline
