ignite

问题 We are seeing the JVM getting crashed at times with segfault. The only error we see in logs is as below. Anyone can suggest something by looking at the below error trace. # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fef7f1d3eb0, pid=42623, tid=0x00007feea62c8700 # # JRE version: OpenJDK Runtime Environment (8.0_222-b10) (build 1.8.0_222-b10) # Java VM: OpenJDK 64-Bit Server VM (25.222-b10 mixed mode linux-amd64 compressed oops) #

问题 We are seeing the JVM getting crashed at times with segfault. The only error we see in logs is as below. Anyone can suggest something by looking at the below error trace. # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fef7f1d3eb0, pid=42623, tid=0x00007feea62c8700 # # JRE version: OpenJDK Runtime Environment (8.0_222-b10) (build 1.8.0_222-b10) # Java VM: OpenJDK 64-Bit Server VM (25.222-b10 mixed mode linux-amd64 compressed oops) #

问题 I'm trying to enable Log4j logger by using the gridLogger property in the config file like below: <bean id="grid.cfg" class="org.apache.ignite.configuration.IgniteConfiguration"/> <property name="gridLogger"> <bean class="org.apache.ignite.logger.log4j.Log4JLogger"> <constructor-arg type="java.lang.String" value="config/ignite-log4j.xml"/> </bean> </property> But when starting the ignite.sh it is giving below error as it is not able to read the property parameter. [root@ignite1 ~]# /usr

问题 I'm trying to enable Log4j logger by using the gridLogger property in the config file like below: <bean id="grid.cfg" class="org.apache.ignite.configuration.IgniteConfiguration"/> <property name="gridLogger"> <bean class="org.apache.ignite.logger.log4j.Log4JLogger"> <constructor-arg type="java.lang.String" value="config/ignite-log4j.xml"/> </bean> </property> But when starting the ignite.sh it is giving below error as it is not able to read the property parameter. [root@ignite1 ~]# /usr

问题 My use case is as follow: We have about 500 servers running in an autoscaling EC2 cluster that need to access the same configuration data (layed out in a key/value fashion) several million times per second. The configuration data isn't very large (1 or 2 GBs) and doesn't change much (a few dozen updates/deletes/inserts per minute during peak time). Latency is critical for us, so the data needs to be replicated and kept in memory on every single instance running our application. Eventual

问题 I am using Apache Ignite 2.8.0. Actually now i am getting memory metrics by the following(Using Java thick client), ClusterGroup remoteGroup = ignite.cluster().forRemotes(); ClusterMetrics metrics = remoteGroup.metrics(); Is there any way to get the Memory metrics by Python or Java thin client? 回答1: It is not supported currently by thin clients, so you will have to gather this information using thick client or server node. Then you can store it somewhere (in e.g. cache) to be accessible by

问题 I am using Apache Ignite 2.8.0. Actually now i am getting memory metrics by the following(Using Java thick client), ClusterGroup remoteGroup = ignite.cluster().forRemotes(); ClusterMetrics metrics = remoteGroup.metrics(); Is there any way to get the Memory metrics by Python or Java thin client? 回答1: It is not supported currently by thin clients, so you will have to gather this information using thick client or server node. Then you can store it somewhere (in e.g. cache) to be accessible by

问题 Deploying an ignite cluster within Kubernetes, I cam across an issue that prevents cluster members from joining the group. If I use a readinessProbe and a livenessProbe, even with a delay as low as 10 seconds, they nodes never join each other. If I remove those probes, they find each other just fine. So, my question is: can you use these probes to monitor node health, and if so, what are appropriate settings. On top of that, what would be good, fast health checks for Ignite, anyway? 回答1:

问题 Deploying an ignite cluster within Kubernetes, I cam across an issue that prevents cluster members from joining the group. If I use a readinessProbe and a livenessProbe, even with a delay as low as 10 seconds, they nodes never join each other. If I remove those probes, they find each other just fine. So, my question is: can you use these probes to monitor node health, and if so, what are appropriate settings. On top of that, what would be good, fast health checks for Ignite, anyway? 回答1:

问题 Deploying an ignite cluster within Kubernetes, I cam across an issue that prevents cluster members from joining the group. If I use a readinessProbe and a livenessProbe, even with a delay as low as 10 seconds, they nodes never join each other. If I remove those probes, they find each other just fine. So, my question is: can you use these probes to monitor node health, and if so, what are appropriate settings. On top of that, what would be good, fast health checks for Ignite, anyway? 回答1: