Hi,
We are seeing 'Failed to resolve nodes topology' igniteexception. can
someone explain what are the possible rootcauses for coming across this kind
of scenario.
We start the ignite cluster while the job is in progress and stop it before
the job gets completed.
Thanks,
Hyma.
--
Hi,
Is there a way we can do like query on array field in ignite sql.
Able to retrieve records on exact search using array_contains function like
select * from market where array_contains(name,'LACL') - here name is an
array object
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Below is the corresponding code where ignite step was in hung state.
logInfo("Populating the canonical name Cache on Ignite Nodes")
val time = System.currentTimeMillis()
companyVORDD.mapPartitions(x => {
val kvs = x.map(comp =>
(comp.wcaId,comp)).toMap[String,CompanyVO].asJava
Thanks Mikhail.
I suspected to increase the spark heartbeat/network timeout. But my question
here is if an executor is lost, corresponding ignite node also gets out of
cluster. In that case, ignite takes care of re balancing between the other
active nodes right. My spark job was not killed and it
Hi,
When loading ignite cache, we saw the spark job went into hung state at this
step.
We see one of the executor task has been running for hours and below are the
logs from this executor that had the failure.
Stdout log
Launch class org.apache.spark.executor.CoarseGrainedExecutorBackend by
calli
