This does not look like a bug to me. Rendezvous affinity function is
stateless, while FairAffinityFunction relies on the previous partition
distribution among nodes, thus it IS stateful. The partition distribution
would be the same if caches were created on the same cluster topology and
then a sequ
Thanks for the answer. It is then much easier to add a level of indirection
and to have a random name for the cache.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Renaming-a-cache-tp10943p10987.html
Sent from the Apache Ignite Users mailing list archive at Nab
Hi Val,
This impacted all queries. I am not sure what went wrong all of sudden.
Thanks
On 2 March 2017 at 09:54, Anil wrote:
> Hi Val,
>
> i am using 1.8 for both client and server.
>
> select * from Person - is not working
>
> select id, name , from Person - working.
>
> This is strange
I start an Ingnite Server node first, Sometimes when I start the second
Server Node, following information outputted.
[09:52:21] Security status [authentication=off, tls/ssl=off]
[09:52:23,921][ERROR][main][IgniteKernal] Got exception while starting (will
rollback startup routine).
org.apache.igni
Hi,
I am using logback with slf4j in my Ignite application. When I start my node
using my custom code, it has started printing a lot of output to the console
which it does not when I just start the node using default Ignite.sh/bat. I
don't mind the Ignite startup banner.
How can I disable the Ig
Hi all,
I'm trying to use Ignite's RoundRobinLoadBalancingSpi with perTask enabled
to guarantee distribution of tasks to my ignite nodes, but it seems that the
load balancing is not working as expected.
Consider the following test:
@Test
public void testRR() {
Ignite node1 = Ignition.sta
Hi Ramzinator,
please try providing all runnables to single compute() method.
Thanks.
On 2 March 2017 at 19:17, Ramzinator wrote:
> Hi all,
>
> I'm trying to use Ignite's RoundRobinLoadBalancingSpi with perTask enabled
> to guarantee distribution of tasks to my ignite nodes, but it seems that
Thanks Anil! It worked great.
However, is there a way that Ignite can distribute tasks in a round robin
fashion if tasks are called sequentially?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-RoundRobinLoadBalancingSpi-Per-Task-not-distributing-tasks-t
Hi Ramzinator,
You created number of compute jobs with one task for each.
Thanks
On 2 March 2017 at 20:11, Ramzinator wrote:
> Thanks Anil! It worked great.
>
> However, is there a way that Ignite can distribute tasks in a round robin
> fashion if tasks are called sequentially?
>
>
>
>
> --
>
Hi,
Looks like some of your caches have *swapEnabled *property set to *true*.
Please try setting *FileSwapSpaceSpi *explicitly in configuration of your
nodes.
Vladimir.
On Thu, Mar 2, 2017 at 3:00 PM, ght230 wrote:
> I start an Ingnite Server node first, Sometimes when I start the second
> Ser
Yes - so taking CacheLoader route then. Thanks a lot for clearing this up.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Data-streamers-How-to-ensure-loading-data-for-the-current-partition-only-tp10949p10996.html
Sent from the Apache Ignite Users mailing list a
Hi Andrey,
my bad. We had some other bad commits in there which we are resolving to
avoid continous restarts. We will put in these changes and let u know how it
goes.
Regards,
Aswin
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Failure-to-start-a-bigger-ignit
Hello Ignite-Community!
I saw that Ignite sometimes logs whole cache-entries.
In addition to the whole content of an entry, such log entries contain e.g.
Ignite-details like extras=GridCachedObsoleteEntryExtras and messages like
"Value did not change, skip write swap entry".
Why does Ignite creat
Anil,
Something must have changed in your application then, I don't believe in
magic :)
In any case, 'select *' currently includes _key and _val fields which
represent key and value objects. If you don't have classes on client side
(which is most likely the case when JDBC driver is used), this qu
Neeraj,
This will be fixed in 2.0: https://issues.apache.org/jira/browse/IGNITE-4248
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Disabling-Ignite-console-logs-tp10990p11001.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Ramzinator,
For you case you just should not set perTask to true. What was the reason
for setting it in the first place?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-RoundRobinLoadBalancingSpi-Per-Task-not-distributing-tasks-tp10991p11002.html
Hi Peter,
Starting with 1.9 (which is about to be released) it will be possible to
avoid key-value printout by setting this system property:
-DIGNITE_TO_STRING_INCLUDE_SENSITIVE=true
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Whole-cache-entries-in-l
Hi Neeraj,
I see IGNITE-4248 is fixed in 1.9 version that has to be released soon.
On Fri, Mar 3, 2017 at 1:02 AM, vkulichenko
wrote:
> Neeraj,
>
> This will be fixed in 2.0: https://issues.apache.org/
> jira/browse/IGNITE-4248
>
> -Val
>
>
>
> --
> View this message in context: http://apache-i
Hi vkulichenko,
The reason is actually a two part problem that I am trying to solve.
1. I want to evenly distribute my ignite computations between the nodes of
my cluster as I had noticed that when having 3 nodes and 10 ignite calls,
they were being distributed as such 6+2+2=10.
Note here I am us
Hi Alex,
I see your point. Can you please outline its advantages vs rendezvous
function?
In my view issue discussed here makes it pretty much useless in vast
majority of use cases, and very error-prone in all others.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.n
Adding back the dev list.
Folks,
Are there any opinions on the problem discussed here? Do we really need
FairAffinityFunction if it can't guarantee cross-cache collocation?
-Val
On Thu, Mar 2, 2017 at 2:41 PM, vkulichenko
wrote:
> Hi Alex,
>
> I see your point. Can you please outline its adva
What??? Unbelievable. It sounds like a design flaw to me. Any ideas how to fix?
—
Denis
> On Mar 2, 2017, at 2:43 PM, Valentin Kulichenko
> wrote:
>
> Adding back the dev list.
>
> Folks,
>
> Are there any opinions on the problem discussed here? Do we really need
> FairAffinityFunction if i
Hi Val,
thank you for the answer!
Kind Regards,
Peter
2017-03-02 23:31 GMT+01:00 vkulichenko :
> Hi Peter,
>
> Starting with 1.9 (which is about to be released) it will be possible to
> avoid key-value printout by setting this system property:
>
> -DIGNITE_TO_STRING_INCLUDE_SENSITIVE=true
>
>
Hello Ignite-Community!
All our Ignite caches are offheap.
Now I've found the following entry in the logs:
"Value did not change, skip write swap entry..."
Checking the source-code I can see that it can just happen in
case hasOffHeapPointer returns true. What does that mean? We just have
"soft re
Thanks Andrey.
Regards,
Neeraj
Sent from my iPhone
> On 3 Mar 2017, at 09:32, Andrey Mashenkov wrote:
>
> Hi Neeraj,
>
> I see IGNITE-4248 is fixed in 1.9 version that has to be released soon.
>
>> On Fri, Mar 3, 2017 at 1:02 AM, vkulichenko
>> wrote:
>> Neeraj,
>>
>> This will be fixed i
25 matches
Mail list logo
