nto documentation I
> could not understand a good use case why would we want to run jobs on the
> collocated queue using affinityRun method of queue interface, since
> collocated queues are on the same node why can't I simply write my own
> lambda function. Specifically what benefits does
ld not understand a good use case why would we want to run jobs on the
collocated queue using affinityRun method of queue interface, since
collocated queues are on the same node why can't I simply write my own
lambda function. Specifically what benefits does the affinityRun offers for
ignite q
Hi guys,
That has been done.
https://issues.apache.org/jira/browse/IGNITE-13396
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I see it's already being picked up in another thread:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Queue-Documentation-or-Code-defect-td33703.html
I can't delete this thread.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Yes the common pattern is not documented. So was expecting if no exception is
thrown that I'm getting a queue and can put something on it. But then if I
don't check for null I'll get a NullpointerException.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Could you please file a ticket in Ignite JIRA for 2.10 release? That's
definitely an overlook in the current implementation.
-
Denis
On Tue, Aug 18, 2020 at 9:57 AM Humphrey wrote:
> Hope someone pics this up. That the code is not behaving as the
> documentation
> is saying.
> (Not throwing ex
It’s a good catch, but I think this is one of the developer mailing list.
I see the same behaviour. Arguably it’s consistent with the Ignite#cache()
which returns null if the cache doesn’t exist.
Regards,
Stephen
> On 18 Aug 2020, at 15:29, Humphrey wrote:
>
> Hope someone pics this up. That
Hope someone pics this up. That the code is not behaving as the documentation
is saying.
(Not throwing exception when queue can not be fetched).
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
I think that "could not be fetched or created" hints that some error should
happen to get an exception.
Returning null if an object does not exist is a common pattern in Ignite
API so I suspect this is what is the norm here.
Maybe I'm missing something?
Regards,
--
Ilya Kasnacheev
вт,
Great I see something went missing:
Ignite ignite = Ignition.start();
IgniteQueue queue = ignite.queue("Queue", 0, null);
ignite.close();
In the queue created above I expect it to throw an exception if the queue
can not be fetched, instead it is giving me a queue that is "null".
Check the JavaDo
According to the documentation (java doc) of ignite.queue():
Will get a named queue from cache and create one if it has not been created
yet and cfg is not null. If queue is present already, queue properties will
not be changed. Use collocation for CacheMode.PARTITIONED caches if you have
lots of r
When creating an ignite queue without an CollectionConfiguration (null) I'm
not getting the expected Queue or Exception as documented in the JavaDoc.
But i'm getting a cache that is null.
The documentation:
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
only way is to write igniterunnable compute where i should run
>> loop forever and perform the task on ignite queue element? But this is bad
>> as there are cases when the compute dies and no one can resume it or track
>> it.
>>
>> Is there a way a where we add some ignite runnable queue elements and the
>> elements pop up automatically and gets executed without any trigger?
>>
>
gt;
> I know only way is to write igniterunnable compute where i should run loop
> forever and perform the task on ignite queue element? But this is bad as
> there are cases when the compute dies and no one can resume it or track it.
>
> Is there a way a where we add some ignite runnab
Hi,
Is there a queue poller built-in ignite which constantly and indefinitely
polls the queue and can perform some task?
I know only way is to write igniterunnable compute where i should run loop
forever and perform the task on ignite queue element? But this is bad as
there are cases when the
ng the
> speed to LinkedBlockingQueue shouldn't be that unfair. My expectation
> here is that ignite is 10-50x slower due to serialization overhead
> still happening for localhost.
>
> But it seems that ignite queue is 100-500 times slower. What am I
> doing wrong here or did I s
Hello!
I think that you had too optimistic expectations. LinkedBlockingQueue is a
core Java data structure and it is very fast - it just writes a reference
to data structure in best case scenario.
Meanwhile, Ignite Queue will create several internal temporary objects
(such as distributed locks
e tuned to get a setup that
is okayish-fast and also without persistence and so comparing the speed
to LinkedBlockingQueue shouldn't be that unfair. My expectation here is
that ignite is 10-50x slower due to serialization overhead still
happening for localhost.
But it seems that ignite que
queue when node is starting
Thanks, I meant ignite queue.
If I have initialized an ignite queue in one node, and I want to just obtain
a reference to it on the second node; there is no API to do that currently
without passing in the entire configuration. Is there something I am
missing?
--
Sent
Thanks, I meant ignite queue.
If I have initialized an ignite queue in one node, and I want to just obtain
a reference to it on the second node; there is no API to do that currently
without passing in the entire configuration. Is there something I am
missing?
--
Sent from: http://apache
Hi,
If you mean IgniteQueue then, unfortunately, there is no way to describe it in
the XML.
You have to call Ignite.queue() to create one.
Thanks,
Stan
From: arunkjn
Sent: 10 июня 2018 г. 10:14
To: user@ignite.apache.org
Subject: Initialize ignite queue when node is starting
Hi,
I give my
Hi,
If you want to configure message queue limit, here is an example:
...
Best Regards,
Roman
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
I give my cache configuration in xml, which the node uses to initialize the
cache when starting up. I want to similarly do this for initializing ignite
queues.
what would be a substitue of -
for ignite queues
Ok. However, there was only one node and only node which holds that cache.
A little strange behaviour. Memory footprint in heap was also half.
On Sep 15, 2016 5:31 PM, "Vladislav Pyatkov" wrote:
> Hi,
>
> It look like you are losing elements. This may be because node of grid has
> failed.
> You
Hi,
It look like you are losing elements. This may be because node of grid has
failed.
You can try to increase count of backup copies, look at the setBackups() in
CollectionConfiguration[1].
[1]:
https://apacheignite.readme.io/v1.7/docs/queue-and-set#collection-configuration
On Wed, Sep 14, 2016
Hi,
We are seeing frequent messages while fetching from our ignite queu.
016-09-14 08:47:32.254 BST [WARN] - thread="AsyncBatchBondPersistence2" -
class="org.apache.ignite.internal.processors.datastructures.GridAtomicCacheQueueImpl"
- Failed to get item, will retry poll
[queue=PROCESSED_BONDS_Q
26 matches
Mail list logo
