You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by wt <wa...@gmail.com> on 2018/07/19 12:41:06 UTC
spark - Failed to process custom exchange task
*Everything was working fine this morning then i had to reboot to install an
update on other software. Starting it all up again the ignite server starts,
cache is loaded and can be queried from DBBeaver. When i access from spark
however it all falls apart. *
*import org.apache.ignite.spark.IgniteDataFrameSettings._
import org.apache.ignite.spark._
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi
import
org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder
import org.apache.ignite.configuration.IgniteConfiguration
import java.util.ArrayList
import java.util.List
val igniteContext = new IgniteContext(sc, () =>{
val tcpDiscoverySpi: TcpDiscoverySpi = new TcpDiscoverySpi
val ipFinder: TcpDiscoveryVmIpFinder = new TcpDiscoveryVmIpFinder
val addressList: java.util.List[String] = new java.util.ArrayList[String]
addressList.add("127.0.0.1:47500")
ipFinder.setAddresses(addressList)
tcpDiscoverySpi.setIpFinder(ipFinder)
tcpDiscoverySpi.setLocalAddress("127.0.0.1")
val igniteConf : IgniteConfiguration = new
IgniteConfiguration().setClientMode(true).setDiscoverySpi(tcpDiscoverySpi)
igniteConf})
*
/18/07/19 13:26:36 ERROR : Failed to resolve default logging config file:
config/java.util.logging.properties
Console logging handler is not configured.
[13:26:37] __________ ________________
[13:26:37] / _/ ___/ |/ / _/_ __/ __/
[13:26:37] _/ // (7 7 // / / / / _/
[13:26:37] /___/\___/_/|_/___/ /_/ /___/
[13:26:37]
[13:26:37] ver. 2.5.0#20180523-sha1:86e110c7
[13:26:37] 2018 Copyright(C) Apache Software Foundation
[13:26:37]
[13:26:37] Ignite documentation: http://ignite.apache.org
[13:26:37]
[13:26:37] Quiet mode.
[13:26:37] ^-- Logging by 'JavaLogger [quiet=true, config=null]'
[13:26:37] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
or "-v" to ignite.{sh|bat}
[13:26:37]
[13:26:37] OS: Windows 7 6.1 amd64
[13:26:37] VM information: Java(TM) SE Runtime Environment 1.8.0_151-b12
Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.151-b12
[13:26:37] Configured plugins:
18/07/19 13:26:37 WARN GridDiagnostic: Initial heap size is 128MB (should be
no less than 512MB, use -Xms512m -Xmx512m).
[13:26:37] ^-- None
[13:26:37]
[13:26:37] Configured failure handler: [hnd=StopNodeOrHaltFailureHandler
[tryStop=false, timeout=0]]
[13:26:37] Initial heap size is 128MB (should be no less than 512MB, use
-Xms512m -Xmx512m).
18/07/19 13:26:37 WARN TcpCommunicationSpi: Message queue limit is set to 0
which may lead to potential OOMEs when running cache operations in
FULL_ASYNC or PRIMARY_SYNC modes due to message queues growth on sender and
receiver sides.
[13:26:37] Message queue limit is set to 0 which may lead to potential OOMEs
when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
message queues growth on sender and receiver sides.
18/07/19 13:26:37 WARN NoopCheckpointSpi: Checkpoints are disabled (to
enable configure any GridCheckpointSpi implementation)
18/07/19 13:26:37 WARN GridCollisionManager: Collision resolution is
disabled (all jobs will be activated upon arrival).
[13:26:37] Security status [authentication=off, tls/ssl=off]
[13:26:38] REST protocols do not start on client node. To start the
protocols on client node set '-DIGNITE_REST_START_ON_CLIENT=true' system
property.
[13:26:39] Performance suggestions for grid (fix if possible)
[13:26:39] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[13:26:39] ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM
options)
[13:26:39] ^-- Set max direct memory size if getting 'OOME: Direct buffer
memory' (add '-XX:MaxDirectMemorySize=<size>[g|G|m|M|k|K]' to JVM options)
[13:26:39] ^-- Disable processing of calls to System.gc() (add
'-XX:+DisableExplicitGC' to JVM options)
[13:26:39] Refer to this page for more performance suggestions:
https://apacheignite.readme.io/docs/jvm-and-system-tuning
[13:26:39]
[13:26:39] To start Console Management & Monitoring run
ignitevisorcmd.{sh|bat}
[13:26:39]
[13:26:39] Ignite node started OK (id=c5538774)
[13:26:39] Topology snapshot [ver=4, servers=1, clients=1, CPUs=2,
offheap=0.98GB, heap=1.4GB]
[13:26:39] ^-- Node [id=C5538774-53F6-442D-BE1A-87C94BF35721,
clusterState=ACTIVE]/
*val igniteCache = igniteContext.fromCache("COMPLIANCESUMMARYCACHE") *
/igniteCache: org.apache.ignite.spark.IgniteRDD[Nothing,Nothing] =
IgniteRDD[0] at RDD at IgniteAbstractRDD.scala:32/
*igniteCache.sql("select * from ComplianceSummary")*
/18/07/19 13:31:28 ERROR GridCachePartitionExchangeManager: Failed to
process custom exchange task: ClientCacheChangeDummyDiscoveryMessage
[reqId=2dcca340-351c-4747-afb5-2c285265a4f4, cachesToClose=null,
startCaches=[COMPLIANCESUMMARYCACHE]]
class org.apache.ignite.IgniteException: Spring application context resource
is not injected.
at
org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory.create(CacheJdbcPojoStoreFactory.java:171)
at
org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory.create(CacheJdbcPojoStoreFactory.java:100)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1437)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1945)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processClientCacheStartRequests(CacheAffinitySharedManager.java:438)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processClientCachesChanges(CacheAffinitySharedManager.java:622)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCustomExchangeTask(GridCacheProcessor.java:376)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.processCustomTask(GridCachePartitionExchangeManager.java:2235)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2371)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2299)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)/
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: spark - Failed to process custom exchange task
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
I don't understand how will Ignite know of your Spring context in this
case. You never tell Ignite that you have it.
Regards,
--
Ilya Kasnacheev
2018-07-19 17:24 GMT+03:00 wt <wa...@gmail.com>:
> is this bug still active (generated from web console)
>
> https://issues.apache.org/jira/browse/IGNITE-4829
>
> Spring context is not injected into POJO store when JDBC driver is utilized
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: spark - Failed to process custom exchange task
Posted by wt <wa...@gmail.com>.
is this bug still active (generated from web console)
https://issues.apache.org/jira/browse/IGNITE-4829
Spring context is not injected into POJO store when JDBC driver is utilized
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/