Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1613
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Regarding IgniteOnePhaseCommitNearSelfTest test , ignite's one phase
optimisation works not as you said.
I attached picture of message exchange. There are partial prepare phase
exists, along with finish phase.
пн, 3 апр. 2017 г. в 10:55, Christos Erotocritou :
> As far
Yakov,
I found following at first opened suite logs (Basic)
1) [INFO ][test-runner-#4966%future.GridEmbeddedFutureSelfTest%][root]
Failed with unhandled error (normal behaviour): java.lang.AssertionError:
Test assertion (should be ignored).
2) [INFO
As far as I know a partition is always allocated to a specific node and does
not span nodes. Ignite has default 1024 partitions on start that are split
equally across nodes.
> On 3 Apr 2017, at 08:10, ALEKSEY KUZNETSOV wrote:
>
> in ur blog u texted belonging to the
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1610
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Hello everybody!
Nikolay, I didn't have experience with ignite-yarn integration and didn't
have idea how fix it, but its interesting for me. Can you write name of
another java application, in which I can see how they connect to mesos.
Also, can you write how correctly to test working of
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/1721
Ignite 4477 Fix IgniteFuture.listen() and IgniteFuture.chain() semantics
PR to master
You can merge this pull request into a Git repository by running:
$ git pull
Hello everyone!
I added some change to method threadLocalForCache and added test
testEntityCacheNonStrictFails.
How to reproduce situation when updates can be recorded to another region?
Hi, Igniters! This is a subtask for "distributed transaction of non-single
coordinator" task.
Will appreciate your thoughts on it.
ticket : https://issues.apache.org/jira/browse/IGNITE-4887
and a commit :
https://github.com/voipp/ignite/commit/aa3487bd9c203394f534c605f84e06436b638e5c
--
*Best
Alexander Paschenko created IGNITE-4905:
---
Summary: ClassCastException in DML benchmarks
Key: IGNITE-4905
URL: https://issues.apache.org/jira/browse/IGNITE-4905
Project: Ignite
Issue
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/1722
IGNITE-4905 DML benchmarks ClassCastException fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4905
Hello, community. Sam, Yakov, Alex G., can you look my decision?
try (Transaction tx = ignite.transactions().txStart()) {
c.put(1, 1);
tx.savepoint("mysavepoint");
c.put(2, 2);
tx.rollbackToSavepoint("mysavepoint");
c.put(3, 3);
tx.commit();
}
I want to make it in
Aleksey,
The blog describes the 1-phase commit at a high level, but I am still
curious about the differences you found. Can you share them here?
D.
On Mon, Apr 3, 2017 at 2:11 AM, ALEKSEY KUZNETSOV
wrote:
> Regarding IgniteOnePhaseCommitNearSelfTest test , ignite's
yeah thats good but GSOC application last till today only so any suggestion
how to write the proposal or what need to be included in the proposal.
--
View this message in context:
http://apache-ignite-developers.2346864.n4.nabble.com/Adding-ML-to-Ignite-IGNITE-4572-tp13936p16070.html
Sent from
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/1724
IGNITE-3582 CPP: Replaced pointers with references in function signatures
where it's possible
You can merge this pull request into a Git repository by running:
$ git pull
Pavel Tupitsyn created IGNITE-4906:
--
Summary: .NET: Examples tests hang
Key: IGNITE-4906
URL: https://issues.apache.org/jira/browse/IGNITE-4906
Project: Ignite
Issue Type: Bug
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/1723
ignite-4851 : made GridDhtLocalPartition state change atomic with size check
You can merge this pull request into a Git repository by running:
$ git pull
Change this to RuntimeException. I think it would be fine. Assertion in
logs should mean something terrible from now and on.
--Yakov
I've attached test that prints messages exchange . Which shows us that
there are more messages then you declared in article. Perhaps,
implementation has changed.
I created it on base of IgniteOnePhaseCommitNearSelfTest
пн, 3 апр. 2017 г. в 19:03, Dmitriy Setrakyan :
>
Crossposted to dev:
Guys,
ScanQuery filter code (see IgniteBiPredicate implementation below) can be
cached on server side
that can cause unexpected results.
The main point here is server node never restarts while client does it with
filter code changed.
Is it ok?
I try to add
so what do u think on my idea?
пт, 31 Мар 2017 г., 11:05 ALEKSEY KUZNETSOV :
> sorry for misleading you. We planned to support multi-node transactions,
> but failed.
>
> пт, 31 мар. 2017 г. в 10:51, Alexey Goncharuk >:
>
> Well, now the
in ur blog u texted belonging to the same partition is nessesary for 1
phase commit. But its not guarantee belonging to the same node. Partition
may span many nodes
вс, 2 Апр 2017 г., 13:46 ALEKSEY KUZNETSOV :
> thank u !
>
> пт, 31 Мар 2017 г., 21:06 Denis Magda
Andrew Mashenkov created IGNITE-4907:
Summary: Excessive service instances can be started with dynamic
deployment.
Key: IGNITE-4907
URL: https://issues.apache.org/jira/browse/IGNITE-4907
Project:
Andrew Mashenkov created IGNITE-4908:
Summary: Reentrant lock looks much slower that cache locks.
Key: IGNITE-4908
URL: https://issues.apache.org/jira/browse/IGNITE-4908
Project: Ignite
24 matches
Mail list logo