Hi @raksja!
Was your problem resolved? Otherwise can you provide detailed steps for
reproducing this behaviour?
On Thu, Nov 30, 2017 at 4:17 AM, vkulichenko
wrote:
> I don't think raksja had an issue with only one record in the RDD.
> IgniteRDD#count redirects
I don't think raksja had an issue with only one record in the RDD.
IgniteRDD#count redirects directly to IgniteCache#size, so if it returns 1,
so you indeed have only one entry in a cache for some reason.
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
-users.70518.x6.nabble.com/Ignite-behaving-strange-with-Spark-SharedRDD-in-AWS-EMR-Yarn-Client-Mode-tp16011p16065.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
roperty in the config provided to
> IgniteContext.
>
> I also created a ticket for this:
> https://issues.apache.org/jira/browse/IGNITE-5981
>
> -Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-behaving-strange-with-Spark-SharedRDD
/browse/IGNITE-5981
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-behaving-strange-with-Spark-SharedRDD-in-AWS-EMR-Yarn-Client-Mode-tp16011p16038.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
this in such mode? Also why its spinning up 38 different
executors itself, even though we specify only 1 to spark?
Any help would be much appreciated.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-behaving-strange-with-Spark-SharedRDD-in-AWS-EMR-Yarn-Client