Anton Kalashnikov created IGNITE-9307:
-
Summary: Node is hang when it was stopping during eviction
Key: IGNITE-9307
URL: https://issues.apache.org/jira/browse/IGNITE-9307
Project: Ignite
Hi Igniters,
It is not an easy fix, so I'm not sure it is possible to do in 2.7.
Offheap size is not reported by VM (it returns -1). To implement it we need
totally migrate off-heap memory metrics to durable memory data.
I think this issue was reported and I'll find the duplicate.
Sincerely,
Dm
Hi Dmitriy, thanks - that’s done now,
Stuart.
On 16 Aug 2018, at 22:23, Dmitriy Setrakyan wrote:
Stuart, can you please move the ticket into PATCH_AVAILABLE state? You need
to click "Submit Patch" button in Jira.
D.
On Wed, Aug 15, 2018 at 10:22 AM, Stuart Macdonald
wrote:
> Here's the init
ARomantsov created IGNITE-9308:
--
Summary: Add baseline topology command to REST API
Key: IGNITE-9308
URL: https://issues.apache.org/jira/browse/IGNITE-9308
Project: Ignite
Issue Type: Bug
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4564
IGNITE-9307 Added completing eviction future if node was stopped
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-
Github user ezhuravl closed the pull request at:
https://github.com/apache/ignite/pull/1479
---
Igniters,
Suppose, Dmitry is talking about IGNITE-5583 [1] - `Switch non-heap memory
metrics
to new page memory semantics` and related previous disscustions to it [4].
Also we have some additional improvements to CacheMetrics:
IGNITE-5490 [2] - `Implement replacement for obsolete
CacheMetrics#get
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4539
---
Maxim Muzafarov created IGNITE-9309:
---
Summary: LocalNodeMovingPartitionsCount metrics may calculates
incorrect due to processFullPartitionUpdate
Key: IGNITE-9309
URL: https://issues.apache.org/jira/browse/IGNITE
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4507
---
Hi Maxim,
thank you for stepping in and for finding these issues. Yes, these tickets
are correct.
I can move https://issues.apache.org/jira/browse/IGNITE-5583 to unassigned
if someone would like to implement this change. I will not have enough time
to complete it in 1 month (before 2.7 release).
Folks,
As you know we are developing multi-version concurrency control for Ignite
caches, which is essentially new mode for transactional cache with snapshot
semantics. One of the most important applications of this mode would be
fully transactional SQL The question is how to implement continuous
Hello!
It turns out there's some problem with checkpointing-WAL interference.
close(true) cancels current checkpoint, and upon restart some data is
missing from the cache.
We are investigating this.
Regards,
--
Ilya Kasnacheev
2018-08-16 10:34 GMT+03:00 Alexey Goncharuk :
> Ilya,
>
> Can yo
Vladimir Ozerov created IGNITE-9310:
---
Summary: SQL: throw exception when missing cache is attempted to
be created inside a transaction
Key: IGNITE-9310
URL: https://issues.apache.org/jira/browse/IGNITE-9310
Maxim Muzafarov created IGNITE-9311:
---
Summary: Add missing @Override annotation
Key: IGNITE-9311
URL: https://issues.apache.org/jira/browse/IGNITE-9311
Project: Ignite
Issue Type: Bug
Maxim Muzafarov created IGNITE-9312:
---
Summary: Remove unnecessary @SuppressWarnings annotation
Key: IGNITE-9312
URL: https://issues.apache.org/jira/browse/IGNITE-9312
Project: Ignite
Issue
GitHub user macrergate opened a pull request:
https://github.com/apache/ignite/pull/4565
IGNITE-9296 should not wait if walWriter is cancelled
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9296
Al
Stepan Pilschikov created IGNITE-9313:
-
Summary: ML TF integration: killed user script or chief processes
didn't restart workers
Key: IGNITE-9313
URL: https://issues.apache.org/jira/browse/IGNITE-9313
Igor Seliverstov created IGNITE-9314:
Summary: MVCC TX: Datastreamer operations
Key: IGNITE-9314
URL: https://issues.apache.org/jira/browse/IGNITE-9314
Project: Ignite
Issue Type: Task
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4564
---
Query is not executed on specific cache. It is executed on many caches.
On Fri, Aug 17, 2018 at 6:10 AM Dmitriy Setrakyan
wrote:
> But internally the SQL query still runs on some cache, no? What happens to
> the metrics accumulated on that cache?
>
> D.
>
> On Thu, Aug 16, 2018, 18:51 Alexey Kuz
Hi team,
I need you opinion again. I wrote some tests for metrics and felt a
confusion with metrics count for the same key update during transaction.
Imagine following case:
BEGIN;
INSERT INTO person(id, name) VALUES(1, 'ivan');
UPDATE person SET name = 'vanya' WHERE id = 1;
COMMIT;
My intuition
Hello, Vladimir.
> 1) *Event ordering*.
I vote to keep things as is.
> 2) *Initial query*
> With MVCC it is now
> technically possible to query data on certain snapshot and then receive
> only events happened after this snapshot
I think it a usefull extension for current implementation.
В Пт,
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4445
---
Folks,
We already have this:
>>> PageMemory [pages=6997377]
Then we can multiply it by page size and get occupied memory. Am I wrong?
On Fri, Aug 17, 2018 at 12:56 PM Dmitriy Pavlov
wrote:
> Hi Maxim,
>
> thank you for stepping in and for finding these issues. Yes, these tickets
> are correct.
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4543
---
GitHub user dmekhanikov opened a pull request:
https://github.com/apache/ignite/pull/4566
IGNITE-3653 Fix P2P class loading for remote filter and filter factory in
CQs.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/ap
Dmitriy,
Thanks a lot for stepping in! Your help is appreciated.
I've looked through your changes and left a comment in JIRA issue.
Best Regards,
Ivan Rakov
On 16.08.2018 23:56, Dmitriy Govorukhin wrote:
Ivan,
I implemented this issue, please review my changes.
https://reviews.ignite.apache.o
asfgit closed pull request #1: MTCGA-002 Build trigger timeout.
URL: https://github.com/apache/ignite-teamcity-bot/pull/1
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull r
Hi.
There is another similar case, what if update actually change nothing?
BEGIN;
INSERT INTO person(id, name) VALUES(1, 'ivan');
UPDATE person SET name = 'ivan' WHERE id = 1;
COMMIT;
Should it we take into account both operations or not?
I'd think current implementation is correct one as
TX wi
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4281
---
Stanislav Lukyanov created IGNITE-9315:
--
Summary: Eviction meta from near cache may appear in DHT entries
Key: IGNITE-9315
URL: https://issues.apache.org/jira/browse/IGNITE-9315
Project: Ignite
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4567
IGNITE-9220 Uncomment tests from internal test suites.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9220
Alter
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4549
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4477
---
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/4568
IGNITE-9315: Eviction meta from near cache may appear in DHT entries.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite i
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4557
---
Vladimir,
1. Continuous queries are asynchronous in general case, so I don't think
it's even possible to provide transactional ordering, especially for the
case of distributed transactions. I would leave current guarantees as-is.
2. This one might be pretty useful. If it's not very hard to do, le
On Fri, Aug 17, 2018 at 3:18 AM, Vladimir Ozerov
wrote:
> Folks,
>
> As you know we are developing multi-version concurrency control for Ignite
> caches, which is essentially new mode for transactional cache with snapshot
> semantics. One of the most important applications of this mode would be
>
To be more precise we need to multiply it by page size with system overhead
(systemPageSize). If we want to print only used offheap memory, this will
solve the problem. If we want to print, for example, currently allocated
(commited) offheap memory (if persistence is disabled for data region then
o
Yes, I agree.
To calculate free (currently -1) we need to know total & used.
Used=sysPageSize*usedPages, but overall should be obtained from all
segments and chunks. So it would be a remarkable part of all mem.metrics
migration (required by IGNITE-5583).
пт, 17 авг. 2018 г. в 23:55, Alex Plehanov
Vova, the things are even simpler - we have this
ignite.dataRegionMetrics().getPhysicalMemorySize() that returns the
number equal/comparabel to pageNumber X pageSize.
Igniters, if you believe that we need to do more work here then let's
do it iteratively. Let's fix the off-heap occupied size the
Peter, Anton V, Igniters,
The board communicated the following release policy changes:
-- for new releases :
-- you MUST supply a SHA-256 and/or SHA-512 file
-- you SHOULD NOT supply MD5 or SHA-1 files
Are we good? More details are below.
*2 Release Dist Policy Changes (Q? us...@
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New Critical Failure in master Cache 4
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache4&branch=%3Cdefault%3E&tab=buildTypeStatusDiv
Changes
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New Critical Failure in master Cache 4
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache4&branch=%3Cdefault%3E&tab=buildTypeStatusDiv
Changes
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New Critical Failure in master Cache 4
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache4&branch=%3Cdefault%3E&tab=buildTypeStatusDiv
No chang
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New Critical Failure in master Cache 4
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache4&branch=%3Cdefault%3E&tab=buildTypeStatusDiv
No chang
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New Critical Failure in master Cache 4
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache4&branch=%3Cdefault%3E&tab=buildTypeStatusDiv
No chang
48 matches
Mail list logo
