[MTCGA]: new failures in builds [6077403] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New Critical Failure in master Cache (Restarts) 1 https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E No changes in the build

Re: Ignite 3.0 Ignition API, node startup, and thin client startup

Hi Ivan, Ignition IS the entry point to Ignite, so I'm not sure I got your point :) Where is the contradiction? Either way, please feel free to give your suggestions for an alternative name if you have any. -Val On Wed, Jul 7, 2021 at 7:56 PM Ivan Pavlukhina wrote: > A side note. Actually

Re: Ignite 3.0 Ignition API, node startup, and thin client startup

A side note. Actually “Ignition” naming always confused me. I think about it as some fancy named API entry point for Ignite. Perhaps it is a good moment to revisit naming. > On 8 Jul 2021, at 07:09, Valentin Kulichenko > wrote: > > Hi Pavel, > > I don't think we will need the pure embedded

Re: Ignite 3.0 Ignition API, node startup, and thin client startup

Hi Pavel, I don't think we will need the pure embedded mode, but we still need to be able to access the API from compute and services. That said, there are two usages of the 'Ignite' API: 1. Remote, via the binary protocol. 2. Local - needed for compute and services. (This is how it works

[MTCGA]: new failures in builds [6072371] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *Test with high flaky rate in master ZookeeperDiscoveryConcurrentStartAndStartStopTest.testMultipleClusters

Re: Problem with dropping the index

I'll try to explain: We create indexes through InlineIndexFactory#createIndex, where at the beginning we create the root page using QueryIndexDefinition#treeName, so if we create the same index 2 times, then we will refer to the same root. In order to make the deletion of the index

Ignite 3.0 Ignition API, node startup, and thin client startup

Igniters, I have a few questions regarding server node startup and thin clients. State of things: - Server nodes will be started with 'ignite run' from CLI [1] - ignite-api module represents our public API - ignite-api has Ignition interface to start server nodes Questions: - What's the idea

Re: IEP-76 Thin Client Protocol for Ignite 3.0

Thanks everyone, I've moved the proposal to Active status. Working on the implementation. On Tue, Jul 6, 2021 at 10:31 PM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > The proposal looks good to me. > > -Val > > On Tue, Jul 6, 2021 at 2:24 AM Ivan Daschinsky > wrote: > > > I

Re: Data out of sync between maillist and nabble.com

Hello! Nabble is an external resource and we do not have much say in how it works. I recommend using Apache's Pony Mail: https://lists.apache.org/list.html?dev@ignite.apache.org While not without drawbacks, it is overall an useful tool. Regards, -- Ilya Kasnacheev ср, 7 июл. 2021 г. в

Re: MOVING Partitions and Rebalancing

Hi. It's ok to have MOVING partitions in the described scenario, because the second node is started after the first and starts a rebalancing on the next topology version. But it shouldn't break query consistency, because reading from the MOVING partition is not allowed. Why does it happen for

Re: Problem with dropping the index

вт, 6 июл. 2021 г. в 15:57, ткаленко кирилл : > >> Can you clarify what it means to rename root index trees ? > Replacing > org.apache.ignite.internal.processors.cache.persistence.IndexStorageImpl.IndexItem, > changing IndexItem#idxName, but keeping fIndexItem#pageId. > Changing to what ? Some