Sure. Will take a look.
On Thu, Mar 9, 2017 at 6:05 PM, Yakov Zhdanov wrote:
> Alexander,
>
> Page https://github.com/apache/ignite/pull/1435 reports several conflicts.
> Can you please check and resolve if necessary. Then resubmit for review
> again.
>
> --Yakov
>
>
Hi all! Is it possible to test on multiple jvm's ? Let's say, to have
multiple ignite instances deployed on different jvms ? If yes, how can i
create them and address them in code ?
--
*Best Regards,*
*Kuznetsov Aleksey*
Hi all! Consider we've got local transaction. How can i simulate node
breakage in tests so that transaction will be in ROLLED_BACK state?
--
*Best Regards,*
*Kuznetsov Aleksey*
Alexey, you should understand how caches startup and partition map exchange
work. I would suggest you start couple of nodes in single VM and simply do
step-by-step debug in your IDE.
I don't think you will need to introduce any new message, but I think you
will have to add info to
Alexander,
Page https://github.com/apache/ignite/pull/1435 reports several conflicts.
Can you please check and resolve if necessary. Then resubmit for review
again.
--Yakov
2017-03-03 13:24 GMT+03:00 Alexander Fedotov :
> Hi, it's ready for review
>
DHT refers to server side cache. Near cache is a part of distributed cache,
but not a part of DHT.
-Val
On Thu, Mar 9, 2017 at 3:39 PM, Alexander Fedotov <
alexander.fedot...@gmail.com> wrote:
> Probably, the reasoning for it is that near entries have distributed form,
> i.e. they are kept in
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/1607
IGNITE-4803
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4803
Alternatively you can review and apply
Ivan Veselovsky created IGNITE-4808:
---
Summary: Add all Hadoop examples as Ignite unit tests with default
multi-JVM execution mode
Key: IGNITE-4808
URL: https://issues.apache.org/jira/browse/IGNITE-4808
Yakov,
However an end user still will be able to provide its own implementation for
this combiner discovery & communication layers, right?
Just want to be sure that if I want to add some custom RDMA, RoCe or InfiniBand
implementation then I’ll be able to do this.
—
Denis
> On Mar 9, 2017, at
Hi,
Can someone add me to contributors list?
I want to assign a ticket to myself, but unable to.
Regards,
Kartik
Hi Aleksey,
GridAbstractTest has isMultiJvm() parameter that when set to ‘true’ will
execute the nodes in separate JVM processes. Refer to the tests that contain
“MultiJvm” in their names as to examples of usage.
P.S.
Renamed the subject. Please give more specific names to email subjects.
To my understanding, Yakov is suggesting that we simply have one very low
level SPI - let's call it IgniteTcpSpi and current implementations of
discovery and communication will be removed from SPI layer and will
register callbacks with this new SPI.
I think this is too big of a change to try to
Andrew Mashenkov created IGNITE-4809:
Summary: Cache.getAll can return partially commited results.
Key: IGNITE-4809
URL: https://issues.apache.org/jira/browse/IGNITE-4809
Project: Ignite
Hi, Kartik!
What is your Apache JIRA ID?
On Fri, Mar 10, 2017 at 2:38 AM, Kartik Somani <
kartiksomani.offic...@gmail.com> wrote:
> Hi,
>
> Can someone add me to contributors list?
>
> I want to assign a ticket to myself, but unable to.
>
> Regards,
> Kartik
>
--
Alexey Kuznetsov
Hi Aleksey,
In order to ensure that a transaction is rolled back during a node failure,
you need to orchestrate messages in such a way that at least one
participating node does not receive a prepare request. As an example, you
can look
at
I suppose, GridDistributedCacheEntry contains common logic for Near and DHT
entries, while
GridDhtCacheEntry is it's subclass and contains common logic for DHT
entries.
For more details check the class hierarchy.
On Tue, Mar 7, 2017 at 3:07 PM, ALEKSEY KUZNETSOV
wrote:
Regarding your comment in ticket. Do you mean broken factory node ought to
send notifications to cache nodes through sharedCtx.io().send(...) ?
вт, 7 мар. 2017 г. в 14:23, ALEKSEY KUZNETSOV :
> Regarding your comment in ticket. Do you mean broken factory node ought to
>
OK, I created it: https://issues.apache.org/jira/browse/IGNITE-4802
-Val
On Thu, Mar 9, 2017 at 9:58 AM, Vladimir Ozerov
wrote:
> Valya,
>
> Not yet.
>
> On Thu, Mar 9, 2017 at 11:50 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Vladimir,
> >
> >
Igor Seliverstov created IGNITE-4803:
Summary: Create a test to check processing doesn't break when
discovery cache history overflows
Key: IGNITE-4803
URL: https://issues.apache.org/jira/browse/IGNITE-4803
Hi Vadim,
Results are a bit confusing. Any idea why it's better on long string, but
worse on a short string? If that's actually the case, there is no any
reason to make the change and I would just close the ticket.
-Val
On Thu, Mar 9, 2017 at 9:20 AM, Вадим Опольский
GitHub user svladykin opened a pull request:
https://github.com/apache/ignite/pull/1604
Sorted merge index and SQL related fixes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/svladykin/ignite ignite-1.9-midx
Alternatively you
Hello everyone!
Colleagues, take a look please at the results of measuring.
Can I close this ticket ?
Should I add JMH benchmark and unit test to Ignite project ?
Results of measuring
https://github.com/javaller/mybenchmark/blob/master/out.txt
Benchmark
Vladimir,
This makes sense to me. Is there a ticket for separate thread pool for
services?
-Val
On Thu, Mar 9, 2017 at 2:52 AM, Dmitriy Setrakyan
wrote:
> Vladimr, it sounds like what you are suggesting is allowing users specify
> named executors in configuration and
Dmitry, yes, your understanding is correct.
Denis, I remember I already shared the idea a while ago, but completely
forgot about the ticket. Thanks for bringing it up! You should give me
couple of tips on how to use "Search" function in Jira :)
Guys, this will be compatibility breaking change,
Vyacheslav Daradur created IGNITE-4804:
--
Summary: Remove duplicated properties in parent-pom
Key: IGNITE-4804
URL: https://issues.apache.org/jira/browse/IGNITE-4804
Project: Ignite
it looks strange. Because, DHT = distributed
чт, 9 мар. 2017 г. в 14:26, Alexander Fedotov :
> I suppose, GridDistributedCacheEntry contains common logic for Near and DHT
> entries, while
> GridDhtCacheEntry is it's subclass and contains common logic for DHT
>
Vladimir Ozerov created IGNITE-4807:
---
Summary: Move inner classes of GridQueryProcessor to top-level if
possible
Key: IGNITE-4807
URL: https://issues.apache.org/jira/browse/IGNITE-4807
Project:
27 matches
Mail list logo