I tried the argument fix proposed in the Jira ticket on Coretto - this
results in a JVM failure with an unknown option message.
On Wed, Jul 29, 2020 at 11:59 AM Evgenii Zhuravlev
wrote:
> Hi,
>
> It's a known issue related to the java11:
> https://issues.apache.org/jira/browse/IGNITE-13306
>
> E
Hi,
It's a known issue related to the java11:
https://issues.apache.org/jira/browse/IGNITE-13306
Evgenii
пн, 27 июл. 2020 г. в 03:17, Mat :
> Tested with Windows and Linux K8 containers all on Java 11.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Tested with Windows and Linux K8 containers all on Java 11.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
We see the same things on Windows/Linux, Coretto v11, and in K8s
containers. Ignite 2.8.0
On Sat, Jul 25, 2020 at 7:44 AM Evgenii Zhuravlev
wrote:
> Hi,
>
> What OS and java version do you use?
>
> Evgenii
>
> пт, 24 июл. 2020 г. в 12:32, Mat :
>
>> Ignite is logging "strange" CPU metrics for me
Hi,
What OS and java version do you use?
Evgenii
пт, 24 июл. 2020 г. в 12:32, Mat :
> Ignite is logging "strange" CPU metrics for me:
>
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=c2a76580, name=embedded, uptime=00:01:00.153]
> ^-- H/N/C [hosts=1,
Ignite is logging "strange" CPU metrics for me:
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=c2a76580, name=embedded, uptime=00:01:00.153]
^-- H/N/C [hosts=1, nodes=1, CPUs=12]
^-- *CPU [cur=-100%, avg=-96.15%, GC=0%]*
^-- PageMemory [pages=200]
