GitHub user alex-plekhanov opened a pull request:
https://github.com/apache/ignite/pull/4178
IGNITE-8763 java.nio.file.AccessDeniedException is not handled with default
failure handler
You can merge this pull request into a Git repository by running:
$ git pull
Mikhail Cherkasov created IGNITE-8778:
-
Summary: Cache tests fail due short timeout
Key: IGNITE-8778
URL: https://issues.apache.org/jira/browse/IGNITE-8778
Project: Ignite
Issue Type:
Ilya Borisov created IGNITE-8779:
Summary: Web console: simplify E2E test runner
Key: IGNITE-8779
URL: https://issues.apache.org/jira/browse/IGNITE-8779
Project: Ignite
Issue Type:
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/2705
---
Hello, guys.
I try my best to do review in a next few days.
В Вт, 12/06/2018 в 11:28 -0700, Denis Magda пишет:
> Agree with Ray. The ticket has been already reviewed and requires us to run
> tests for an isolated module - Spark.
>
> Dmitriy Pavlov, Nickolay Izhikov, could you step in as final
GitHub user dgarus opened a pull request:
https://github.com/apache/ignite/pull/4179
IGNITE-8184
ZookeeperDiscoverySpiTest#testTopologyChangeMultithreaded_RestartZk* tests fail
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/4180
IGNITE-8778 Cache tests fail due short timeout
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-master-8778
GitHub user chandresh-pancholi opened a pull request:
https://github.com/apache/ignite/pull/4181
IGNITE-8777: REST: metadata command failed on cluster of size 1
Signed-off-by: Chandresh Pancholi
You can merge this pull request into a Git repository by running:
$ git pull
Amir,
Thanks for attempt.
As far as I can see you have all changes at this commit:
https://github.com/apache/ignite/pull/3926/commits/cd0e50e05d3860788378ebf1a29dc0525460872a
You can simply apply it to local branch based on master by patch
Hi, Igniters,
Currently, I'm working on the thin C++ client implementation.
As you may already know, there is an issue with latency in our
thin clients, which also can result in performance issues (you
can see the "About Ignite Thin client performance" thread on
user list).
So, how about we
Pavel Kovalenko created IGNITE-8780:
---
Summary: File I/O operations must be retried if buffer hasn't
read/written completely
Key: IGNITE-8780
URL: https://issues.apache.org/jira/browse/IGNITE-8780
Vote for #2 since it can shed light on hidden bug at production.
ср, 13 июн. 2018 г. в 18:10, Alexey Goncharuk :
> Igniters,
>
> Bumping up this discussion. The fix has been implemented and it is fine
> from the technical point of view, but since the fix did not make it to the
> Ignite 2.0, the
Vote for #2. I think no one will change this defaults in configuration in
#1.
2018-06-13 18:29 GMT+03:00 Anton Vinogradov :
> Vote for #2 since it can shed light on hidden bug at production.
>
> ср, 13 июн. 2018 г. в 18:10, Alexey Goncharuk >:
>
> > Igniters,
> >
> > Bumping up this discussion.
+1 to Eduard.
It's a reasonable change, but we can't just break working code of all
the guys that access atomic caches in their transactions. If we try, we
will end up with another emergency release.
Best Regards,
Ivan Rakov
On 13.06.2018 19:13, Eduard Shangareev wrote:
Guys,
I believe,
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/4182
GG-13711 : Skipped compatibility submodule while generating classpath.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Igniters,
Recently we noticed the issue when we don't completely persist some data on
the disk:
https://issues.apache.org/jira/browse/IGNITE-8780 . In some cases it can
lead node to unrecoverable state.
I think this problem should be included to release.
ср, 13 июн. 2018 г. в 14:06, Alexey
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/4184
IGNITE-8386
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8386
Alternatively you can review and apply
Guys,
I believe, that it's not the case when we should change default behaviour.
So, #1 and make it default in 3.0.
On Wed, Jun 13, 2018 at 6:46 PM, Dmitrii Ryabov
wrote:
> Vote for #2. I think no one will change this defaults in configuration in
> #1.
>
> 2018-06-13 18:29 GMT+03:00 Anton
Andrey Gura created IGNITE-8781:
---
Summary: nio-acceptor threads are indistinguishable in
GridNioServer
Key: IGNITE-8781
URL: https://issues.apache.org/jira/browse/IGNITE-8781
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4152
---
Igniters,
Bumping up this discussion. The fix has been implemented and it is fine
from the technical point of view, but since the fix did not make it to the
Ignite 2.0, the implemented fix [1] now will be a breaking change for
current Ignite users.
I see the following options:
1) Have the fix
Ivan Rakov created IGNITE-8783:
--
Summary: Failover tests periodically cause hanging of the whole
Data Structures suite on TC
Key: IGNITE-8783
URL: https://issues.apache.org/jira/browse/IGNITE-8783
Pavel Kovalenko created IGNITE-8784:
---
Summary: Deadlock during simultaneous client reconnect and node
stop
Key: IGNITE-8784
URL: https://issues.apache.org/jira/browse/IGNITE-8784
Project: Ignite
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/4183
IGNITE-8781 GridNioServer accepter threads should have different names
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite
Pavel Kovalenko created IGNITE-8785:
---
Summary: Node may hang indefinitely in CONNECTING state during
cluster segmentation
Key: IGNITE-8785
URL: https://issues.apache.org/jira/browse/IGNITE-8785
GitHub user alex-plekhanov opened a pull request:
https://github.com/apache/ignite/pull/4185
IGNITE-7700 SQL system view for list of nodes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alex-plekhanov/ignite ignite-7700
Hi Igor,
How can we invoke the affinity function on the client, if we don't have the
implementation at hand?
Am I missing something?
Thanks,
Pavel
On Wed, Jun 13, 2018 at 5:34 PM, Igor Sapego wrote:
> Hi, Igniters,
>
> Currently, I'm working on the thin C++ client implementation.
> As you
Dana Shaw created IGNITE-8786:
-
Summary: session.removeAttribute does not work as expected
Key: IGNITE-8786
URL: https://issues.apache.org/jira/browse/IGNITE-8786
Project: Ignite
Issue Type: Bug
Hi,
Fix for IGNITE-8722 (https://issues.apache.org/jira/browse/IGNITE-8722) is
ready.
Diff
https://git1-us-west.apache.org/repos/asf?p=ignite.git=search=refs%2Fheads%2Fignite-8722=commit=IGNITE-8722
TC looks good for me.
Andrew Medvedev created IGNITE-8787:
---
Summary: Striped Executor thread failure is not processed by
IgniteFailureProcessor
Key: IGNITE-8787
URL: https://issues.apache.org/jira/browse/IGNITE-8787
Pavel,
Most likely the client will be pulling the partitioning map periodically.
If the local map is outdated, it won't be a big deal because a server node
that receives a request:
- can redirect it to a map that owns a partition
- will add an updated partition map to the client's response
31 matches
Mail list logo
