Iurii, congratulations!
On 15.02.2024 21:35, Kseniya Romanova wrote:
Well deserved! Congrats!
On Thu, Feb 15, 2024 at 1:57 PM Maxim Muzafarov wrote:
Congratulations, Iurii!
On Thu, 15 Feb 2024 at 09:31, Юрий wrote:
Thank you everyone, I'm very pleased!
ср, 14 февр. 2024 г. в 17:28, Pavel
Alexander, congratulations!
--
Roman Kondakov
On 10.03.2022 19:32, Вячеслав Коптилин wrote:
Hi,
Congratulations, Alexander!
Thanks,
S.
ср, 9 мар. 2022 г. в 18:57, Ivan Pavlukhin :
Alex, congratulations, well deserved!
2022-03-09 18:18 GMT+03:00, Petr Ivanov :
Congratulations!
On 9
Congratulations, Vlad!
--
Roman Kondakov
On 23.12.2021 20:13, Kseniya Romanova wrote:
Congrats and welcome, Vlad!
чт, 23 дек. 2021 г. в 12:36, Вячеслав Коптилин :
Hi,
Congratulations, Vlad!
Thanks,
S.
чт, 23 дек. 2021 г. в 11:59, Anton Vinogradov :
Welcome aboard!
On Thu, Dec 23
Hello!
The word "traditional" here is not about the technology age. It's about
using buffer pool like in traditional databases (PG, Oracle, etc).
--
Roman Kondakov
On 17.09.2020 17:09, Ilya Kasnacheev wrote:
Hello!
Can you please clarify which databases you refer
[1] http://www.vldb.org/pvldb/vol8/p37-graefe.pdf
--
Roman Kondakov
On 17.09.2020 12:07, Pavel Tupitsyn wrote:
Agree with Val, even experienced developers have a hard time understanding
what "in-memory computing platform" really does.
"distributed memory-first database" i
Sergey, congratulations!
--
Roman Kondakov
On 17.07.2020 12:32, Dmitriy Pavlov wrote:
Dear Ignite Community,
The Project Management Committee (PMC) for Apache Ignite has invited Sergey
Chugunov to become a committer and we are pleased to announce that he has
accepted.
Sergey has a long
Congrats, Artem!
--
Roman Kondakov
On 16.07.2020 14:19, Ilya Kasnacheev wrote:
Hello!
The Project Management Committee for Apache Ignite project has invited
Artem Budnikov to become a committer and we are pleased to announce that he
has accepted.
He is the person behind a monumental effort
Roman Kondakov created IGNITE-13136:
---
Summary: Calcite integration. Improve join predicate testing.
Key: IGNITE-13136
URL: https://issues.apache.org/jira/browse/IGNITE-13136
Project: Ignite
Roman Kondakov created IGNITE-13125:
---
Summary: SQL regressions framework: Random query generation
Key: IGNITE-13125
URL: https://issues.apache.org/jira/browse/IGNITE-13125
Project: Ignite
Roman Kondakov created IGNITE-13070:
---
Summary: SQL regressions detection framework
Key: IGNITE-13070
URL: https://issues.apache.org/jira/browse/IGNITE-13070
Project: Ignite
Issue Type
e TeamCity suite for it. We can run this suite
nightly to detect regressions problems early.
What do you think?
--
Kind Regards
Roman Kondakov
On 23.05.2020 16:12, Roman Kondakov wrote:
> Hi Denis,
>
> I'm not sure we need a separate repository for it. What would be the
>
Hi Igor,
I think yes, this tool will be well suited for this.
--
Kind Regards
Roman Kondakov
On 22.05.2020 22:46, Igor Seliverstov wrote:
> Great idea I think.
>
> Can we also use the tool to compare, let's say, H2 indexing against Calcite
> based one to detect possible is
Kind Regards
Roman Kondakov
On 22.05.2020 22:36, Denis Magda wrote:
> Hi Roman,
>
> +1 for sure. On a side note, should we create a separate ASF/Git repository
> for the project? Not sure we need to put the suite in the main Ignite repo.
>
> -
> Denis
>
>
> On Fri, May
Or there might be another solution for such
optimizations?
Thank you.
[1] https://www.postgresql.org/docs/10/indexes-index-only-scans.html
[2] https://www.postgresql.org/message-id/12553.1135634...@sss.pgh.pa.us
--
Kind Regards
Roman Kondakov
On 22.05.2020 22:37, Igor Seliverstov wrote:
> Igniters
of SQL query regressions.
What do you think?
[1] http://www.vldb.org/pvldb/vol13/p57-jung.pdf
[2] https://github.com/anse1/sqlsmith
--
Kind Regards
Roman Kondakov
Roman Kondakov created IGNITE-13035:
---
Summary: Calcite integration. Support fallback on indexes rebuild
Key: IGNITE-13035
URL: https://issues.apache.org/jira/browse/IGNITE-13035
Project: Ignite
Roman Kondakov created IGNITE-13030:
---
Summary: Calcite integration. Push projections to scans and avoid
reading full row when possible
Key: IGNITE-13030
URL: https://issues.apache.org/jira/browse/IGNITE-13030
Roman Kondakov created IGNITE-13027:
---
Summary: Calcite integration. Query parallelism support.
Key: IGNITE-13027
URL: https://issues.apache.org/jira/browse/IGNITE-13027
Project: Ignite
Roman Kondakov created IGNITE-13026:
---
Summary: Calcite integration. Fix metadata for IgniteTable when it
has embedded filters.
Key: IGNITE-13026
URL: https://issues.apache.org/jira/browse/IGNITE-13026
Roman Kondakov created IGNITE-13025:
---
Summary: Calcite integration. Limit and offset support.
Key: IGNITE-13025
URL: https://issues.apache.org/jira/browse/IGNITE-13025
Project: Ignite
Roman Kondakov created IGNITE-13024:
---
Summary: Calcite integration. Support and simplification of
complex expressions in index conditions
Key: IGNITE-13024
URL: https://issues.apache.org/jira/browse/IGNITE
Roman Kondakov created IGNITE-13023:
---
Summary: Calcite integration. Page scan support.
Key: IGNITE-13023
URL: https://issues.apache.org/jira/browse/IGNITE-13023
Project: Ignite
Issue Type
Roman Kondakov created IGNITE-13022:
---
Summary: Calcite integration. Merge index conditions for the same
field.
Key: IGNITE-13022
URL: https://issues.apache.org/jira/browse/IGNITE-13022
Project
Roman Kondakov created IGNITE-13021:
---
Summary: Calcite integration. Avoid full scans for disjunctive
queries.
Key: IGNITE-13021
URL: https://issues.apache.org/jira/browse/IGNITE-13021
Project
Taras,
congratulations! Keep it up!
--
Kind Regards
Roman Kondakov
On 12.05.2020 19:09, Dmitriy Pavlov wrote:
> Hello Ignite Community,
>
>
>
> The Project Management Committee (PMC) for Apache Ignite has invited Taras
> Ledkov to become a committer and we are pleased t
Roman Kondakov created IGNITE-12915:
---
Summary: Calcite integration: Add push filter to join rule to the
planner
Key: IGNITE-12915
URL: https://issues.apache.org/jira/browse/IGNITE-12915
Project
Roman Kondakov created IGNITE-12914:
---
Summary: Calcite integration: Add aggregate project merge rule to
the planner
Key: IGNITE-12914
URL: https://issues.apache.org/jira/browse/IGNITE-12914
Project
Roman Kondakov created IGNITE-12913:
---
Summary: Calcite integration: Add semi join remove rule to the
planner
Key: IGNITE-12913
URL: https://issues.apache.org/jira/browse/IGNITE-12913
Project
Roman Kondakov created IGNITE-12912:
---
Summary: Calcite integration: Add filters merge rule to plannner
Key: IGNITE-12912
URL: https://issues.apache.org/jira/browse/IGNITE-12912
Project: Ignite
Roman Kondakov created IGNITE-12771:
---
Summary: Java Doc: Marshaller: behavior of "marshal" method if
null parameter passed
Key: IGNITE-12771
URL: https://issues.apache.org/jira/browse/IG
y id from
> the step 1.
> 3. User receive an exception when trying to fetch more data from any server
> node.
>
> Is this use-case correct?
yes, I think this is a correct use case.
[1] https://issues.apache.org/jira/browse/IGNITE-12732
--
Kind Regards
Roman Kondakov
On 0
Roman Kondakov created IGNITE-12732:
---
Summary: SQL: KILL QUERY command hangs on query when query cursor
is held by user or leak
Key: IGNITE-12732
URL: https://issues.apache.org/jira/browse/IGNITE-12732
rror message is solved, isn't it?
> Error is «Query with provided ID doesn’t exist»
The another problem you've encountered after running KILL QUERY command
with correct qryId is freezing. Am I correct? If yes, this is a known
issue and I am working on it.
--
Kind Regards
Roman Ko
.
> I tried and it doesn’t work, also.
> `KILL QUERY` command just freeze on
> `CommandProcessor#processKillQueryCommand` line 478.
--
Kind Regards
Roman Kondakov
On 02.03.2020 13:10, Nikolay Izhikov wrote:
> Hello, Roman.
>
> My initial query was about correct usage of KILL QUE
t get into that list.
Try to replace "ignite0" with a "client" node in this line. I think it
may help:
> List> sqlQries0 = SqlViewExporterSpiTest.execute(client, "SELECT
> QUERY_ID FROM SYS.SQL_QUERIES");
--
Kind Regards
Roman Kondakov
On 02.03.2020 12:
Roman Kondakov created IGNITE-12715:
---
Summary: Calcite integration. Secondary indexes support.
Key: IGNITE-12715
URL: https://issues.apache.org/jira/browse/IGNITE-12715
Project: Ignite
-1 Prohibit because there is a non-zero chance that the new API will
never be stabilized.
--
Kind Regards
Roman Kondakov
On 10.02.2020 11:13, Vyacheslav Daradur wrote:
> +1 Allow, because once the community has made a decision to introduce
> new APIs instead of an old one - stabilizat
even more.
I am a supporter of complete revising of the MVCC design.
[1] http://cs.yale.edu/homes/thomson/publications/calvin-sigmod12.pdf
--
Kind Regards
Roman Kondakov
On 07.02.2020 15:21, Alexei Scherbakov wrote:
> My point is MVCC should be redone from scratch without messing with ot
724ac6b127/core/src/main/java/org/apache/calcite/sql/SqlDialect.java#L1233
[2]
https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/sql/fun/SqlLibraryOperators.java
--
Kind Regards
Roman Kondakov
On 28.12.2019 11:08, Seliverstov Igor wrote:
> Forgot to mention,
o, we get to the same point without creating and removing redundant
sort, because we have all possible index scans registered before the
planning is actually started and we can demand sortedness of table scans
directly without applying IndexRules and Abstract converters.
--
Kind Regards
Roman
ion of
the same table) we can seamlessly use views to simulate indexes behavior
for Calcite planner.
[1] https://calcite.apache.org/docs/materialized_views.html
[2] https://calcite.apache.org/docs/lattice.html
--
Kind Regards
Roman Kondakov
On 11.12.2019 17:11, Vladimir Ozerov wrote:
> Roman,
of a table.
--
Kind Regards
Roman Kondakov
On 10.12.2019 17:44, Alexey Zinoviev wrote:
> I'd like Drill approach, worked and debugged with something similar, it's
> more easy to support
>
>
> Buuut, you have an implemented prototype (it votes for Phoenix in my mind)
&g
r applying DbScanSortRemovalRule we have:
Project
IndexScan
while for Phoenix approach we would have two equivalent subsets in our
planner:
Project
Sort
TableScan
and
Project
IndexScan
and most likely the last plan will be chosen as the best one.
--
Kind Regards
Roman Kondakov
On 10.12.
--
Kind Regards
Roman Kondakov
On 10.12.2019 16:40, Zhenya Stanilovsky wrote:
>
> Roman just as fast remark, Phoenix builds their approach on already existing
> monolith HBase architecture, most cases it`s just a stub for someone who
> wants use secondary indexes with a base with n
37%3A+New+query+execution+engine
[3] https://issues.apache.org/jira/browse/PHOENIX-2047
[4] https://issues.apache.org/jira/browse/DRILL-6381
[5] https://issues.apache.org/jira/browse/DRILL-3929
[6] https://github.com/apache/ignite/pull/7115
--
Kind Regards
Roman Kondakov
gnite-sql.readme.io/docs/distributed-joins
[2] https://github.com/hostettler/igniteParallelQueries/pull/1
--
Kind Regards
Roman Kondakov
On 16.11.2019 12:50, steve.hostett...@gmail.com wrote:
Actually I am now wondering whether this is not just a bug and that I should
record it as such. As the behavi
gging#query-parallelism
--
Kind Regards
Roman Kondakov
On 15.11.2019 12:53, steve.hostett...@gmail.com wrote:
Dear all,
would it be possible to also have then // execution of sql queries on single
node with that approach?
My understanding is that, for the moment, the SQL queries a re
single-thr
--
Kind Regards
Roman Kondakov
On 01.11.2019 17:07, Seliverstov Igor wrote:
Hi Igniters,
Working on new generation of Ignite SQL I faced a question: «Do we need local
queries at all and, if so, what semantic they should have?».
Current planing flow consists of next steps:
1) Parsing SQL to AST
2)
nderstand that our arguments may not be as obvious
for you as it obvious for SQL team. So, please arrange your questions in
a more constructive way.
Thank you!
--
Kind Regards
Roman Kondakov
On 27.09.2019 15:32, Maxim Muzafarov wrote:
Folks,
I agree with Nikolay, the idea of replacing the H2 engin
Hello Nikolay,
please see IEP--37 [1]. Issues are there.
[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=130028084
--
Kind Regards
Roman Kondakov
On 27.09.2019 14:20, Nikolay Izhikov wrote:
Hello, Roman.
Also Apache Calcite is commonly used in popular Apache
tps://www.memsql.com/blog/scaling-distributed-joins/
--
Kind Regards
Roman Kondakov
On 27.09.2019 12:20, Nikolay Izhikov wrote:
Hello, Igor.
Thanks for starting this discussion.
I think we should take a step back in it and answer the following questions:
1. What the exact issues with the H2 in
[1]
https://www.cse.iitb.ac.in/infolab/Data/Courses/CS632/Papers/Cascades-graefe.pdf
[2]
https://www.cse.iitb.ac.in/infolab/Data/Courses/CS632/Papers/Volcano-graefe.pdf
[3] https://drill.apache.org/
[4] https://phoenix.apache.org/
--
Kind Regards
Roman Kondakov
On 27.09.2019 11:44, Igor Seliverstov
Roman Kondakov created IGNITE-11839:
---
Summary: SQL: table join order changes may lead to incorrect result
Key: IGNITE-11839
URL: https://issues.apache.org/jira/browse/IGNITE-11839
Project: Ignite
Roman Kondakov created IGNITE-11764:
---
Summary: SQL: Do not use two step query in the case of single node
cluster
Key: IGNITE-11764
URL: https://issues.apache.org/jira/browse/IGNITE-11764
Project
Roman Kondakov created IGNITE-11756:
---
Summary: SQL: implement a table row count statistics for the local
queries
Key: IGNITE-11756
URL: https://issues.apache.org/jira/browse/IGNITE-11756
Project
Roman Kondakov created IGNITE-11712:
---
Summary: SQL: review security check for SQL/DML queries
Key: IGNITE-11712
URL: https://issues.apache.org/jira/browse/IGNITE-11712
Project: Ignite
Roman Kondakov created IGNITE-11679:
---
Summary: MVCC: Security check is violated for MVCC caches
Key: IGNITE-11679
URL: https://issues.apache.org/jira/browse/IGNITE-11679
Project: Ignite
Roman Kondakov created IGNITE-11673:
---
Summary: SQL: It looks like security check is missed in h2
indexing.
Key: IGNITE-11673
URL: https://issues.apache.org/jira/browse/IGNITE-11673
Project: Ignite
Roman Kondakov created IGNITE-11548:
---
Summary: MVCC: MVCC PDS 2 suite became unstable after the get
operation mapping fix
Key: IGNITE-11548
URL: https://issues.apache.org/jira/browse/IGNITE-11548
Roman Kondakov created IGNITE-11482:
---
Summary: MVCC: Error on TxLog initialization.
Key: IGNITE-11482
URL: https://issues.apache.org/jira/browse/IGNITE-11482
Project: Ignite
Issue Type
Roman Kondakov created IGNITE-11448:
---
Summary: SQL: Wrong results of select with aggregates in subquery
Key: IGNITE-11448
URL: https://issues.apache.org/jira/browse/IGNITE-11448
Project: Ignite
Roman Kondakov created IGNITE-11439:
---
Summary: MVCC: Error in transaction mode validation.
Key: IGNITE-11439
URL: https://issues.apache.org/jira/browse/IGNITE-11439
Project: Ignite
Issue
Roman Kondakov created IGNITE-11417:
---
Summary: Get rid of CacheRebalanceMode#NONE
Key: IGNITE-11417
URL: https://issues.apache.org/jira/browse/IGNITE-11417
Project: Ignite
Issue Type
Roman Kondakov created IGNITE-11349:
---
Summary: MVCC: Deadlock in query pool when executing DML over
caches with queryParallism > 1
Key: IGNITE-11349
URL: https://issues.apache.org/jira/browse/IGNITE-11
Roman Kondakov created IGNITE-11215:
---
Summary: MVCC: JVC crush in MVCC PDS 1 suite
Key: IGNITE-11215
URL: https://issues.apache.org/jira/browse/IGNITE-11215
Project: Ignite
Issue Type: Bug
Roman Kondakov created IGNITE-11107:
---
Summary: MVCC:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodes hangs
sometimes
Key: IGNITE-11107
URL: https://issues.apache.org/jira/browse
Roman Kondakov created IGNITE-11106:
---
Summary: MVCC: Test
CacheMvccVacuumTest.testStartStopVacuumPersistence fails sporadically
Key: IGNITE-11106
URL: https://issues.apache.org/jira/browse/IGNITE-11106
Roman Kondakov created IGNITE-11069:
---
Summary: MVCC: Refactor GridCacheMapEntry mvcc set/remove/lock
methods and listeners
Key: IGNITE-11069
URL: https://issues.apache.org/jira/browse/IGNITE-11069
Roman Kondakov created IGNITE-10967:
---
Summary: Assertion error in log during ExchangeFuture init
Key: IGNITE-10967
URL: https://issues.apache.org/jira/browse/IGNITE-10967
Project: Ignite
Roman Kondakov created IGNITE-10895:
---
Summary: MVCC: Document several modes of pessimistic transactions
are allowed for MVCC caches.
Key: IGNITE-10895
URL: https://issues.apache.org/jira/browse/IGNITE-10895
Roman Kondakov created IGNITE-10788:
---
Summary: MVCC: Get operation may hang in some cases
Key: IGNITE-10788
URL: https://issues.apache.org/jira/browse/IGNITE-10788
Project: Ignite
Issue
Roman Kondakov created IGNITE-10786:
---
Summary: MVCC: Flaky test
IgniteClusterActivateDeactivateTestWithPersistence#testDeactivateDuringEvictionAndRebalance
Key: IGNITE-10786
URL: https://issues.apache.org/jira
Roman Kondakov created IGNITE-10785:
---
Summary: MVCC: Grid can hang if transactions is failed to rollback
Key: IGNITE-10785
URL: https://issues.apache.org/jira/browse/IGNITE-10785
Project: Ignite
Roman Kondakov created IGNITE-10778:
---
Summary: MVCC: Invoke request may hang sometimes
Key: IGNITE-10778
URL: https://issues.apache.org/jira/browse/IGNITE-10778
Project: Ignite
Issue Type
Roman Kondakov created IGNITE-10770:
---
Summary: MVCC: testInsertAndQueryMultipleCaches in JDBC suite is
flaky
Key: IGNITE-10770
URL: https://issues.apache.org/jira/browse/IGNITE-10770
Project
Roman Kondakov created IGNITE-10769:
---
Summary: MVCC:
CacheMvccContinuousQueryClientTest.testNodeJoinsRestartQuery fails sometimes
Key: IGNITE-10769
URL: https://issues.apache.org/jira/browse/IGNITE-10769
Roman Kondakov created IGNITE-10768:
---
Summary: MVCC:
CacheMvccBasicContinuousQueryTest.testUpdateCountersGapClosedSimplePartitioned
may hang
Key: IGNITE-10768
URL: https://issues.apache.org/jira/browse/IGNITE
Roman Kondakov created IGNITE-10767:
---
Summary: MVCC: Unknown page type error during scan query
Key: IGNITE-10767
URL: https://issues.apache.org/jira/browse/IGNITE-10767
Project: Ignite
Roman Kondakov created IGNITE-10766:
---
Summary: MVCC:
CacheMvccTxRecoveryTest.testCountersNeighborcastServerFailed fails sporadically
Key: IGNITE-10766
URL: https://issues.apache.org/jira/browse/IGNITE-10766
Roman Kondakov created IGNITE-10765:
---
Summary: MVCC:
MvccReplicatedTxPessimisticOriginatingNodeFailureRecoveryTest.testManyKeysRollback
fails sometimes
Key: IGNITE-10765
URL: https://issues.apache.org/jira
Roman Kondakov created IGNITE-10764:
---
Summary: MVCC: Transactions failed to acquire lock within timeout
Key: IGNITE-10764
URL: https://issues.apache.org/jira/browse/IGNITE-10764
Project: Ignite
Roman Kondakov created IGNITE-10763:
---
Summary: MVCC: Transaction already completed error in some tests
Key: IGNITE-10763
URL: https://issues.apache.org/jira/browse/IGNITE-10763
Project: Ignite
Roman Kondakov created IGNITE-10756:
---
Summary: MVCC: Query trackers are not released sometimes
Key: IGNITE-10756
URL: https://issues.apache.org/jira/browse/IGNITE-10756
Project: Ignite
Roman Kondakov created IGNITE-10755:
---
Summary: MVCC: Flaky continuous query tests
Key: IGNITE-10755
URL: https://issues.apache.org/jira/browse/IGNITE-10755
Project: Ignite
Issue Type: Bug
Roman Kondakov created IGNITE-10753:
---
Summary: MVCC: Sometimes vacuum does not cleanup all outdated
versions
Key: IGNITE-10753
URL: https://issues.apache.org/jira/browse/IGNITE-10753
Project
Roman Kondakov created IGNITE-10752:
---
Summary: MVCC: Tests invariants are violated sometimes
Key: IGNITE-10752
URL: https://issues.apache.org/jira/browse/IGNITE-10752
Project: Ignite
Issue
Roman Kondakov created IGNITE-10750:
---
Summary: MVCC: Unexpected tx state exception after coordinator fail
Key: IGNITE-10750
URL: https://issues.apache.org/jira/browse/IGNITE-10750
Project: Ignite
Roman Kondakov created IGNITE-10743:
---
Summary: MVCC: Mute flaky mvcc tests
Key: IGNITE-10743
URL: https://issues.apache.org/jira/browse/IGNITE-10743
Project: Ignite
Issue Type: Task
Roman Kondakov created IGNITE-10741:
---
Summary: MVCC: Document disabled page evictions for in-memory MVCC
caches.
Key: IGNITE-10741
URL: https://issues.apache.org/jira/browse/IGNITE-10741
Project
Roman Kondakov created IGNITE-10738:
---
Summary: MVCC: Enable page evictions for MVCC caches with
in-memory mode
Key: IGNITE-10738
URL: https://issues.apache.org/jira/browse/IGNITE-10738
Project
MVCC caches with evictions will result to the performance
drop, which makes useless this application of MVCC caches.
Perhaps, we should prohibit MVCC caches creations in regions with
configured eviction policy, as you proposed?
Igor, Vladimir, what do you think?
--
Kind Regards
Roman Kondakov
Roman Kondakov created IGNITE-10694:
---
Summary: MVCC: Possible recycled pages leak.
Key: IGNITE-10694
URL: https://issues.apache.org/jira/browse/IGNITE-10694
Project: Ignite
Issue Type: Bug
t expect OOM when
he has configured eviction policy for cache.
What do you think?
--
Kind Regards
Roman Kondakov
On 13.12.2018 22:33, Vladimir Ozerov wrote:
It's hard to believe that entries are not locked on backups, because we
wrtite data right away. Even if it so, it should be very easy
ainst
it. Except we should decide what guaranties we can provide to user in
this case.
--
Kind Regards
Roman Kondakov
On 14.12.2018 13:21, Павлухин Иван wrote:
Hi folks,
I did not quite get what user problem we are trying to solve so far.
The simplest thing which comes to my mind is to pro
Vladimir,
we do not lock entries on backups when MVCC is enabled and therefore we
don't avoid entry eviction from backup by locking. So, your first
scenario with primary stop is still relevant.
--
Kind Regards
Roman Kondakov
On 13.12.2018 22:14, Vladimir Ozerov wrote:
No, I mean th
Regards
Roman Kondakov
On 13.12.2018 17:45, Vladimir Ozerov wrote:
Roman,
I would start with the fact that eviction can never be consistent unless it
utilizes atomic broadcast protocol, which is not the case for Ignite. In
Ignite entries on node are evicted independently.
So you may easily get
Roman Kondakov
On 13.12.2018 16:27, Ilya Kasnacheev wrote:
Hello!
Is it possible to 'touch' entries read by MVCC transactions to ensure that
they are considered recent and therefore are almost never targeted by
eviction?
This is 1) with benefits.
Regards,
ations in all points except possible repeatable read
violations.
What do you think?
[1] https://apacheignite.readme.io/docs/evictions
--
Kind Regards
Roman Kondakov
Roman Kondakov created IGNITE-10583:
---
Summary: MVCC: Assertion in txLog state update when recovering
from WAL.
Key: IGNITE-10583
URL: https://issues.apache.org/jira/browse/IGNITE-10583
Project
Roman Kondakov created IGNITE-10582:
---
Summary: MVCC: Error on txLog initialization.
Key: IGNITE-10582
URL: https://issues.apache.org/jira/browse/IGNITE-10582
Project: Ignite
Issue Type
1 - 100 of 164 matches
Mail list logo
