Evgenii Zhuravlev created IGNITE-11096:
--
Summary: Webagent: flag --disable-demo doesn't work
Key: IGNITE-11096
URL: https://issues.apache.org/jira/browse/IGNITE-11096
Project: Ignite
Dmitriy Govorukhin created IGNITE-11095:
---
Summary: Failed WalCompactionTest flaky test
Key: IGNITE-11095
URL: https://issues.apache.org/jira/browse/IGNITE-11095
Project: Ignite
Issue
Sergey Kozlov created IGNITE-11094:
--
Summary: Add SSL support for ignite zookeeper SPI
Key: IGNITE-11094
URL: https://issues.apache.org/jira/browse/IGNITE-11094
Project: Ignite
Issue Type:
Thank you Dmitriy!
I updated the wiki.
regards, Oleg
PS. Also thanks for the reference to "How To document" guidelines, that's a
useful read.
Dmitriy Pavlov-3 wrote
> Done, I've added permission for Oleg Ignatenko user.
>
> Just in case, let me share
>
Done, I've added permission for Oleg Ignatenko user.
Just in case, let me share
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document with you
:)
пт, 25 янв. 2019 г. в 20:55, oignatenko :
> Hello,
>
> Is it possible to get edit access to Apache Ignite wiki?
>
> I've been working on
Hello,
Is it possible to get edit access to Apache Ignite wiki?
I've been working on particular JIRA ticket [1] and one of reviewers
suggested me update particular wiki page [2] after the ticket is done.
Now that the ticket is done I would like to make proposed edits to wiki
page.
TIA,
Ivan Rakov created IGNITE-11093:
---
Summary: Introduce transaction state change tracking framework
Key: IGNITE-11093
URL: https://issues.apache.org/jira/browse/IGNITE-11093
Project: Ignite
Issue
Who can advice if mentioned tests change their name from time to time?
The bot will not notify for such tests correctly because it is impossible
to say if a test is the same with some passing test(s).
чт, 24 янв. 2019 г. в 22:17, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to
The test is still flaky and it seems to begin failing recently. Is there
any issue for this test fix?
вт, 22 янв. 2019 г. в 22:49, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
> If your changes can lead to this failure(s):
It seems to be passing now. Please ignore.
ср, 23 янв. 2019 г. в 00:03, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
> If your changes can lead to this failure(s): We're grateful that you were
> a volunteer to make the
Passing now, please ignore
вт, 22 янв. 2019 г. в 23:33, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
> If your changes can lead to this failure(s): We're grateful that you were
> a volunteer to make the contribution to
Sergey Antonov created IGNITE-11092:
---
Summary: CacheInterceptor add callbacks for binary objects
Key: IGNITE-11092
URL: https://issues.apache.org/jira/browse/IGNITE-11092
Project: Ignite
Ivan,
The idea is that certain changes to the system are not relevant for all
components. E.g. if SQL schema is changed, then some SQL caches needs to be
invalidated. When affinity topology changes, another part of caches needs
to be invalidated. Having a single version may lead to unexpected
Vladimir,
thank you for the reply. Topology and affinity changes are not reflected in
distributed metastorage, we didn't touch baseline history at all. I believe
that what you really need it just distributed property "sqlSchemaVer" that
is updated on each schema update. It could be achieved by
Igor Akkuratov created IGNITE-11091:
---
Summary: Visor shows all indexes in upper case
Key: IGNITE-11091
URL: https://issues.apache.org/jira/browse/IGNITE-11091
Project: Ignite
Issue Type:
Ivan,
The change you describe is extremely valuable thing as it allows to detect
changes into global configuration which is of great importance for SQL.
Will topology and affinity changes be reflected in metastore history as
well? From SQL perspective it is important for us to be able to
Initially, hard timeout should protect grid from constantly changing
topology(constantly blinking node). But in fact if we have constantly changing
topology, baseline adjust operation is failed in most cases. As result hard
timeout only added complexity but it don't give any new guarantee. So I
Ivan Rakov created IGNITE-11089:
---
Summary: Get rid of partition ID in intra-partition page links
stored in delta records
Key: IGNITE-11089
URL: https://issues.apache.org/jira/browse/IGNITE-11089
Andrew Mashenkov created IGNITE-11090:
-
Summary: Test
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testDestroySpecificCacheAndCacheGroupFirstGroup
hangs sporadically.
Key: IGNITE-11090
URL:
Andrew Mashenkov created IGNITE-11088:
-
Summary: Flacky
LocalWalModeChangeDuringRebalancingSelfTest.testWithExchangesMerge
Key: IGNITE-11088
URL: https://issues.apache.org/jira/browse/IGNITE-11088
Nikolai Kulagin created IGNITE-11087:
Summary: GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is
flaky
Key: IGNITE-11087
URL: https://issues.apache.org/jira/browse/IGNITE-11087
Project:
Anton,
As I understand from the IEP document policy was supposed to support two
timeouts: soft and hard, so here you're proposing a bit simpler
functionality.
Just to clarify, do I understand correctly that this feature when enabled
will auto-adjust blt on each node join/node left event, and
Vitaliy Biryukov created IGNITE-11086:
-
Summary: IGNITE_REST_SECURITY_TOKEN_TIMEOUT parameter is set in
deciseconds instead of seconds.
Key: IGNITE-11086
URL:
Andrew Mashenkov created IGNITE-11085:
-
Summary: MVCC: Mute
GridCachePartitionEvictionDuringReadThroughSelfTest.
Key: IGNITE-11085
URL: https://issues.apache.org/jira/browse/IGNITE-11085
Project:
Andrey Aleksandrov created IGNITE-11084:
---
Summary: Change copyrights to 2019
Key: IGNITE-11084
URL: https://issues.apache.org/jira/browse/IGNITE-11084
Project: Ignite
Issue Type: Task
Vladimir Ozerov created IGNITE-11083:
Summary: SQL: Extract query model from splitter
Key: IGNITE-11083
URL: https://issues.apache.org/jira/browse/IGNITE-11083
Project: Ignite
Issue
Andrew Mashenkov created IGNITE-11082:
-
Summary: Test
GridCacheDhtTxPreloadSelfTest.testLocalTxPreloadingPessimistic hangs on TC
sporadically.
Key: IGNITE-11082
URL:
Andrew Mashenkov created IGNITE-11081:
-
Summary: Flacky test
CacheGetReadFromBackupFailoverTest.testFailover
Key: IGNITE-11081
URL: https://issues.apache.org/jira/browse/IGNITE-11081
Project:
Andrew Mashenkov created IGNITE-11080:
-
Summary: Flacky test
GridCacheDhtPreloadDelayedSelfTest.testManualPreload
Key: IGNITE-11080
URL: https://issues.apache.org/jira/browse/IGNITE-11080
Andrew Mashenkov created IGNITE-11078:
-
Summary: MVCC: Tests fails sporadically with
ConcurrentModificationException
Key: IGNITE-11078
URL: https://issues.apache.org/jira/browse/IGNITE-11078
Andrew Mashenkov created IGNITE-11079:
-
Summary: MVCC: IgniteCacheContinuousQueryBackupQueueTest is flacky.
Key: IGNITE-11079
URL: https://issues.apache.org/jira/browse/IGNITE-11079
Project:
Sergey Antonov created IGNITE-11077:
---
Summary: Add information about SSL cipher suites to
apacheignite.readme.io
Key: IGNITE-11077
URL: https://issues.apache.org/jira/browse/IGNITE-11077
Project:
Sergey Antonov created IGNITE-11076:
---
Summary: Add documentation for control.sh idle_verify
--exclude-caches
Key: IGNITE-11076
URL: https://issues.apache.org/jira/browse/IGNITE-11076
Project:
Got it, makes sense.
On Fri, Jan 25, 2019 at 11:06 AM Anton Kalashnikov
wrote:
> Vladimir, thanks for your notes, both of them looks good enough but I
> have two different thoughts about it.
>
> I think I agree about enabling only one of manual/auto adjustment. It is
> easier than current
Hello, Igniters!
Here's more info "Distributed MetaStorage" feature [1]. It is a part of
Phase II for
IEP-4 (Baseline topology) [2] and was mentioned in recent "Baseline
auto-adjust`s
discuss" topic. I'll partially duplicate that message here.
One of key requirements is the ability to store
Sergey
You're right that both modes would be good to support.
My concerns are about the approaches for interactive mode and current
implementation for visor cmd looks ugly: in interactive mode you execute
command like in command-line:
*visor> disco -r -t=2m -c=1*
I think the interactive mode
Ivan, thank you. I started wrote same test today)
пт, 25 янв. 2019 г. в 10:16, Павлухин Иван :
> Pavel,
>
> Initially I meant Java thick client. And I see the difference between
> thin and thick Java clients. As was already mentioned thin Java client
> behaves in way like each cache is enforced
Vladimir, thanks for your notes, both of them looks good enough but I have two
different thoughts about it.
I think I agree about enabling only one of manual/auto adjustment. It is easier
than current solution and in fact as extra feature we can allow user to force
task to execute(if they
38 matches
Mail list logo
