Dmitriy Govorukhin created IGNITE-9244:
--
Summary: Partition eviction may use all threads in sys pool, it
leads to hangs send a message via sys pool
Key: IGNITE-9244
URL: https://issues.apache.org/jira/browse
Artem Budnikov created IGNITE-9245:
--
Summary: Document how to monitor Ignite with Zabbix
Key: IGNITE-9245
URL: https://issues.apache.org/jira/browse/IGNITE-9245
Project: Ignite
Issue Type:
Hello, Igniters.
We have 3 not assigned tickets for a 2.7 which is labeled "Important".
Who can pick up this tickets?
https://issues.apache.org/jira/browse/IGNITE-4191 - SQL: support transactions
https://issues.apache.org/jira/browse/IGNITE-5473 - Create ignite
troubleshooting logger
https://iss
Hello, Petr.
TDE tests succeed on "publicagent03_9091".
https://ci.ignite.apache.org/viewLog.html?buildId=1626049&buildTypeId=IgniteTests24Java8_BasicTestsWithPersistence&tab=testsInfo
> If everything is OK — I’ll distribute this Java among all other agents.
Can you do it?
В Чт, 09/08/2018 в 1
Nikolay, thanks for helping with tests.
I will proceed with Java updates. Will notify when finished.
> On 10 Aug 2018, at 11:37, Nikolay Izhikov wrote:
>
> Hello, Petr.
>
> TDE tests succeed on "publicagent03_9091".
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1626049&buildTypeId
GitHub user dgarus opened a pull request:
https://github.com/apache/ignite/pull/4512
fail create cache on client node
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dgarus/ignite create_cache_fail_on_client
Alternatively you ca
Alexei Scherbakov created IGNITE-9246:
-
Summary: Optimistic transactions can wait for topology future on
remap for a long time even if timeout is set.
Key: IGNITE-9246
URL: https://issues.apache.org/jira/brows
Hi, Igniters!
Currently, errors of creation dynamic caches on server nodes and client
nodes are different.
If an error occurs on a server node, all cache nodes should revert the
changes [1].
If an error occurred on a client node, the client reverts the changes,
servers nodes start cache.
In tha
Hi,
Dmitriy thanks for note, I will keep metrics IEP in mind.
Roman it sounds quite a straightforward approach. Moreover current cache
transactions follow it: there could be a number of invisible actions in
private workspace (e.g. creating and then deleting the same entry) but only
final changes
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/4513
IGNITE-9244 Rework partition eviction.
- add evict shared manager
- concurrent evict partition from one group
- balanced executors by partition size
- limitation concurrent evi
Stanislav Lukyanov created IGNITE-9247:
--
Summary: CPP Thin: implement GetAll
Key: IGNITE-9247
URL: https://issues.apache.org/jira/browse/IGNITE-9247
Project: Ignite
Issue Type: New Featu
Hi Denis,
As my understanding right, to prevent potential OOM Local CQ either
shouldn't collect anything in backup queue or other nodes should send akcs.
Second way look strange as Local CQ runs on local node only and doesn't
care whats going on other nodes.
It is not clear what events and when o
Peter,
I checked PR
Tests [1] seems to be ok
Comparision [2] with 2.6 seems to be ok
Sample result [3] - ok
Please check the rest.
[1]
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&branch_IgniteTests24Java8=ignite-7251
[2]
https://ci.ignite.apache.org/repository/download/
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4446
---
Igor Sapego created IGNITE-9248:
---
Summary: CPP: Support Clang compiler
Key: IGNITE-9248
URL: https://issues.apache.org/jira/browse/IGNITE-9248
Project: Ignite
Issue Type: Improvement
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4514
IGNITE-9171 Use lazy mode with results pre-fetch
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9171
A
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4429
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4499
---
Ilya Lantukh created IGNITE-9249:
Summary: Tests hang when different threads try to start and stop
nodes at the same time.
Key: IGNITE-9249
URL: https://issues.apache.org/jira/browse/IGNITE-9249
Proje
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/4515
IGNITE-9249 : Configured node join timeout for all tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9249
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4145
---
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4516
gg-14053
For test purposes.
Fix mvcc tx handling.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite gg-14053
Altern
Andrey,
I also think, that remote nodes shouldn't be involved.
> Instead of using backup queue we can notify CQ on backup events instantly
This would be an incompatible change. It would break users' code, that
doesn't expect notifications on backup entries.
On the other hand, it would make our AP
Hi John,
1. There is no "begin prepare" record, nodes acquire locks on TX keys and
then transfer local TX to PREPARED state.
2. TxRecord is logged when local TX state changes to PREPARED, COMMITED or
ROLLED_BACK before sending a response to what you call "coordinator" (in
Ignite we use the term "n
Anton Kalashnikov created IGNITE-9250:
-
Summary: Replace CacheAffinitySharedManager.CachesInfo by
ClusterCachesInfo
Key: IGNITE-9250
URL: https://issues.apache.org/jira/browse/IGNITE-9250
Project:
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4517
IGNITE-8559 Replace CacheAffinitySharedManager.CachesInfo by ClusterCâ¦
â¦achesInfo
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/a
Hi,
I believe we can just move this tickets to the next version.
On Fri, Aug 10, 2018 at 11:35 AM Nikolay Izhikov wrote:
>
> Hello, Igniters.
>
> We have 3 not assigned tickets for a 2.7 which is labeled "Important".
> Who can pick up this tickets?
>
> https://issues.apache.org/jira/browse/IGNITE
Hi, Ivan
Looks like a bug. Metrics counting described at JSR107 (JCache)
specification. It says, that "cache removals" metric should be incremented
if remove() method returns true. Since there are no matching keys in the
first remove() call should be found, remove() should return false and
"cache
Stas,
SkipList implementation offers O(log n) for get/put/contains
operations while CLHM - O(1). So it is suitable for small data sets
but will have serious performance impact for the big ones.
However, it seems it's time for right choice: correctness or
performance. The answer seems obvious )
On
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4495
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4506
---
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4518
IGNITE-9227 Fast reply on single message if exchange future has already
completed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apac
Anton,
I have experience with the yardstick and can help you sometimes.
My possibilities in this matter are limited and it is possible that your
request will be delayed.
Please, try to use the last version of the yardstick and then we can
discuss specific yardstick
issues that you couldn't solve.
Hi,
I was testing out the Yardstick benchmark in my local machine and it looks to
me that there is no direct way to run the benchmarks with persistent store
enabled. I modified the ignite-localhost-config.xml with persistentEnabled and
then had to modify
https://github.com/apache/ignite/blob/m
Hi,
Try to add "-pds" flag in input arguments for Ignite benchmarks to
enable persistence.
On Sat, Aug 11, 2018 at 12:19 AM Mammo, Mulugeta
wrote:
>
> Hi,
>
> I was testing out the Yardstick benchmark in my local machine and it looks to
> me that there is no direct way to run the benchmarks with
GitHub user SomeFire opened a pull request:
https://github.com/apache/ignite/pull/4519
IGNITE-9209: GridDistributedTxMapping.toString() returns broken string
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SomeFire/ignite ignite-
36 matches
Mail list logo
