:679)
at
org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:164)
... 46 more
--
Regards,
Rajarshi Pain
2)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
--
Regards,
Raj
-9a91-a3a9f2ec48d3]
--
Regards,
Rajarshi Pain
23.153.56:47500
>
>
> Evgenii
>
>
> 2017-11-29 18:20 GMT+03:00 Rajarshi Pain :
>
>> Hi,
>>
>> I was working on Ignite 2,3, and my colleague is working on 1.8. We are
>> running different application on our local machine using the example ignite
>> xml, but i
you sure that you are using not Multicast IP finder? Please share
> configuration for all nodes that find each other and log files
>
> 2017-11-30 9:32 GMT+03:00 Rajarshi Pain :
>
>> Hi Evgenii,
>>
>> We both tried to specify the port, but still we rae getting same erro
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:733)
... 17 more
--
Regards,
Rajarshi Pain
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
--
Regards,
Rajarshi Pain
pringframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1372)
... 31 more
--
Regards,
Rajarshi Pain
em on the remote nodes.
> Probably query could not be parsed or something wrong with config.
> Could you please share Ignite config and the query you run?
>
> Kind regards,
> Alex
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
--
Regards,
Rajarshi Pain
Hi Alex,
Can you please tell me which jar is missing?
If i remove the below then it's running perfectly. So i guess there is some
issue with this portion.
ONHEAP_TIERED"/>
On Wed 13 Dec, 2017, 22:47 afedotov, wrote:
> Hi,
>
> Looks like you don't have required Ignite libs on your c
wrote:
> You have a wrong class name CacheFifoEvictionPolicy. It should be
> FifoEvictionPolicy
>
--
Regards,
Rajarshi Pain
Hello,
Check if you have log4j jar in build path? I guess jar is missing.
Thanks,
Raj
On Thu 14 Dec, 2017, 23:22 sherryhw, wrote:
> Hi guys,
> I am using Log4j2 for Ignite logging, but I always have this error:
> "* Failed to instantiate [org.apache.ignite.logger.log4j2.Log4J2Logger]:
> Constru
;http://h2database.com/html/source.html?file=org/h2/command/dml/Query.java&line=333&build=195>
)
at org.h2.command.CommandContainer.query(CommandContainer.java:113
<http://h2database.com/html/source.html?file=org/h2/command/CommandContainer.java&line=113&build=195>
)
at org.h2.command.Command.executeQuery(Command.java:201
<http://h2database.com/html/source.html?file=org/h2/command/Command.java&line=201&build=195>
)
... 9 more
--
Regards,
Rajarshi Pain
Hi Slava,
Yes i have set it as true and after running the application, i am querying
the cache from h2 console, but getting same error while running a select
query.
Is there anything else i need to set for this or how i will initialize
GridH2QueryContext?
On Thu 28 Dec, 2017, 19:11 slava.koptili
Hi Val,
I can not share the code as it is on client machine.
My application is working perfectly. I have created some cache using ignite
getorcreatecache and loading data from database (using spring) . I have
created pojo to keep the data in different cache. There is no issue with
data loading.
I am using 2.3
On Thu 4 Jan, 2018, 01:43 vkulichenko,
wrote:
> Which version are you on?
>
> -Val
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
--
Thanks
Rajarshi
Hi Slava,
Yes it might be the root cause as i have set QueryParallelism as 4.
On Thu 4 Jan, 2018, 20:25 slava.koptilin, wrote:
> Hi Rajarshi,
>
> I was able to reproduce the issue.
> It seems that using CacheConfiguration#QueryParallelism greater than 1 may
> lead to this behavior.
> I will inve
Hi,
I am using Ignite 2.3 for my application. But got Cache closed exception
while running.
This is a multi threaded application through testing on single thread. it
will load the reference number from database to cache during startup and
while processing a message, it will check if that particul
resources.
> When *IgniteCache.close()* is called, then cache is destroyed.
>
> Denis
>
> чт, 4 янв. 2018 г. в 18:17, Rajarshi Pain :
>
>> Hi,
>>
>> I am using Ignite 2.3 for my application. But got Cache closed exception
>> while running.
>>
>> Th
tchUpdateException: ORA-00001: unique
constraint
--
Regards,
Rajarshi Pain
Hello,
Can someone please help me on this scenario if somewhere I am making any
mistake ?
Thanks,
Raj
On Fri, Jan 12, 2018 at 11:57 PM, Rajarshi Pain
wrote:
> Hi,
>
> We were doing a POC(Ignite 2.3 - oracle) to check how cache Persistence
> Store works using writeBehind, We are u
Hello,
I am trying to explore different functionality offered by Ignite (2.3) but
this AffinityKey concept is not quite clear to me so need some suggestion
from Ignite experts.
we are having a scenario where we will load all static data from DB to
cache and do various validations for the incoming
Hello,
We are trying to scale up our application to achieve more throughput. Right
now we are running 4 nodes (same physical system) and getting almost 1200
tps.
But when we are adding more node performance is getting decreased and not
able to get more than 600 tps while adding more than 6 nodes.
e and after
> this, you add 2 additional nodes on the same physical machine?
>
> Evgenii
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
--
Regards,
Rajarshi Pain
Hi,
Previously i was manually adding all the jars to my build path, now i am
using maven to do this. Is there any way to add all ignite jars with it's
dependency in to the project?
Or i have to add one by into the pom file?
--
Thanks
Rajarshi
--
Thanks
Rajarshi
26 matches
Mail list logo
