Re: Ignite 2.3.0 hangs in startup

Hi, As I see in this error message: Failed to resolve default logging config file: config/java.util.logging.properties Console logging handler is not configured. You don't have java.util.logging.properties config file for SLF4j. I've checked 2.3.0 binaries and this file exists in folder config

Re: Ignite with Spark on Yarn

I still couldn't get it working on Yarn with spark-submit. Looking at the logs, the initial reading of default-config.xml succeeds and the ignite node is started OK, but is failing when it starts the Task. Please see below. NB: I tried spark-submit from Spark Master node as well as the Spark clien

RE: Node failed to startup due to deadlock

Hi Alexey, We are still seeing the deadlocks for the scenario i have specified earlier. We tried the below two changes, but still seeing the deadlocks. Can you please provide some pointers about the issue based on the logs and threaddumps attached. 1) As Rajeev mentioned, we tried offloading even

Re: getAverageGetTime/getAveragePutTime APIs of CacheMetrics always return 0

Thank you Pavel!!. I have not enabled statistics. Do you know what would be performance impact on enabling it? -Biren -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Data region's pages fill factor

Hi Andrey, Looks like the tooltip is wrong and should be fixed. Your interpretation of FreeListImpl.fillFactor() is correct - the former value is used space, the latter one is total allocated. So, your pages are 99% full. On Sun, Nov 5, 2017 at 4:08 AM, Andrey Kornev wrote: > Oops! Hit "Send" a