Re: Ignite Extension - TC link
Hi Nikolay, Please find the TC link below https://ci.ignite.apache.org/project.html?projectId=IgniteExtensions=projectOverview Regards, Saikat On Wed, Jan 29, 2020 at 5:26 AM Nikolay Izhikov wrote: > Hello, Igniters. > > Can you, please, give me a link to the «Ignite Extension» project on the > TC?
Re: New channel about integration with Spring Framework
for Slack ) On Wed, Jan 29, 2020 at 8:17 PM Andrey Gura wrote: > > +1 > > > On Wed, Jan 29, 2020 at 7:59 PM Denis Magda wrote: > > > > Folks, why don't you name the channel "ignite-spring-framework_russian" in > > Slack ;) > > > > - > > Denis > > > > > > On Wed, Jan 29, 2020 at 12:50 AM Maksim Stepachev < > > maksim.stepac...@gmail.com> wrote: > > > > > Yes, I do. > > > > > > ср, 29 янв. 2020 г. в 11:22, Sergey Chernolyas < > > > sergey.chernol...@gmail.com > > > >: > > > > > > > Do you mean channel at Telegram ? > > > > > > > > On Wed, 29 Jan 2020 at 11:20, Maksim Stepachev < > > > maksim.stepac...@gmail.com > > > > > > > > > wrote: > > > > > > > > > Okey, but our channel has 90+ active members. > > > > > > > > > > ср, 29 янв. 2020 г. в 11:15, Sergey Chernolyas < > > > > > sergey.chernol...@gmail.com > > > > > >: > > > > > > > > > > > Hi Maksim! > > > > > > > > > > > > The link is unavailable :-( I can't open it. I think Slack is more > > > > > > preferable. > > > > > > > > > > > > On Wed, 29 Jan 2020 at 11:13, Maksim Stepachev < > > > > > maksim.stepac...@gmail.com > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > Could we use the telegram channel for it for the Russian > > > > > > > community? > > > > > > > > > > > > > > https://t.me/RU_Ignite > > > > > > > > > > > > > > ср, 29 янв. 2020 г. в 10:53, Sergey Chernolyas < > > > > > > > sergey.chernol...@gmail.com > > > > > > > >: > > > > > > > > > > > > > > > Hi igniters! > > > > > > > > > > > > > > > > I have created new channel "#ignite-spring-framework" for > > > > discussion > > > > > > > about > > > > > > > > integration with Spring Framework. > > > > > > > > > > > > > > > > -- > > > > > > > > - > > > > > > > > > > > > > > > > With best regards, Sergey Chernolyas > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > - > > > > > > > > > > > > With best regards, Sergey Chernolyas > > > > > > > > > > > > > > > > > > > > > > > -- > > > > - > > > > > > > > With best regards, Sergey Chernolyas > > > > > > >
Re: New channel about integration with Spring Framework
+1 On Wed, Jan 29, 2020 at 7:59 PM Denis Magda wrote: > > Folks, why don't you name the channel "ignite-spring-framework_russian" in > Slack ;) > > - > Denis > > > On Wed, Jan 29, 2020 at 12:50 AM Maksim Stepachev < > maksim.stepac...@gmail.com> wrote: > > > Yes, I do. > > > > ср, 29 янв. 2020 г. в 11:22, Sergey Chernolyas < > > sergey.chernol...@gmail.com > > >: > > > > > Do you mean channel at Telegram ? > > > > > > On Wed, 29 Jan 2020 at 11:20, Maksim Stepachev < > > maksim.stepac...@gmail.com > > > > > > > wrote: > > > > > > > Okey, but our channel has 90+ active members. > > > > > > > > ср, 29 янв. 2020 г. в 11:15, Sergey Chernolyas < > > > > sergey.chernol...@gmail.com > > > > >: > > > > > > > > > Hi Maksim! > > > > > > > > > > The link is unavailable :-( I can't open it. I think Slack is more > > > > > preferable. > > > > > > > > > > On Wed, 29 Jan 2020 at 11:13, Maksim Stepachev < > > > > maksim.stepac...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > Hi, > > > > > > > > > > > > Could we use the telegram channel for it for the Russian community? > > > > > > > > > > > > https://t.me/RU_Ignite > > > > > > > > > > > > ср, 29 янв. 2020 г. в 10:53, Sergey Chernolyas < > > > > > > sergey.chernol...@gmail.com > > > > > > >: > > > > > > > > > > > > > Hi igniters! > > > > > > > > > > > > > > I have created new channel "#ignite-spring-framework" for > > > discussion > > > > > > about > > > > > > > integration with Spring Framework. > > > > > > > > > > > > > > -- > > > > > > > - > > > > > > > > > > > > > > With best regards, Sergey Chernolyas > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > - > > > > > > > > > > With best regards, Sergey Chernolyas > > > > > > > > > > > > > > > > > > -- > > > - > > > > > > With best regards, Sergey Chernolyas > > > > >
Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]
Hello! Actually, it seems to me that such scenario "Joining persistence node to in-memory cluster" is not really supported in either 2.7.6 or 2.8. I suggest disabling it for good. What do you think? Nobody ever told us that it is broken, we can assume noone ever wanted that. We have no test coverage for it. Still, I think that baseline auto-adjust should not be enabled by default, since it is not configurable via IgniteConfiguration. Regards, -- Ilya Kasnacheev ср, 29 янв. 2020 г. в 16:14, Ilya Kasnacheev : > Hello! > > I have just promoted https://issues.apache.org/jira/browse/IGNITE-12504 > to Blocker. > > The reasoning for this, you can't seem to configure baseline auto-adjust > until your node is up (there is no configuration for this), and it will > refuse nodes joining outright with default configuration, making it > impossible to assemble some clusters. I will file a separate ticket about > that. > > "Caused by: class org.apache.ignite.spi.IgniteSpiException: Joining > persistence node to in-memory cluster couldn't be allowed due to baseline > auto-adjust is enabled and timeout equal to 0" > > Regards, > -- > Ilya Kasnacheev > > > ср, 29 янв. 2020 г. в 14:33, Andrey Gura : > >> Hi, >> >> one more issue which should be fixed in 2.8 release [1] >> >> [1] https://issues.apache.org/jira/browse/IGNITE-12598 >> >> On Tue, Jan 28, 2020 at 7:29 PM Maxim Muzafarov >> wrote: >> > >> > Igniters, >> > >> > >> > Here is the list of actual release BLOCKER issues: >> > >> > [1] Keep in mind unfinished discussion about internal classes >> > IGNITE-12456 [2] Cluster Data Store grid gets Corrupted for Load test >> > *[Unassigned]* OPEN >> > IGNITE-12398 Apache Ignite Cluster(Amazon S3 Based Discovery) Nodes >> getting >> > down [Emmanouil Gkatziouras] IN PROGRESS >> > IGNITE-12580 NPE in GridMetricManager [Nikolay Izhikov] PATCH AVAILABLE >> > IGNITE-12489 Error during purges by expiration: Unknown page type [Anton >> > Kalashnikov] OPEN >> > >> > [1] >> > >> http://apache-ignite-developers.2346864.n4.nabble.com/Internal-classes-are-exposed-in-public-API-td45146.html >> > [2] https://issues.apache.org/jira/browse/IGNITE-12456 >> > [3] https://issues.apache.org/jira/browse/IGNITE-12398 >> > [4] https://issues.apache.org/jira/browse/IGNITE-12580 >> > [5] https://issues.apache.org/jira/browse/IGNITE-12489 >> > >> > >> > On Tue, 28 Jan 2020 at 19:25, Maxim Muzafarov >> wrote: >> > >> > > Andrey, >> > > >> > > I've looked through those changes [1] and now they look good to me. >> > > Let's do the following: >> > > >> > > 1. Get a fresh TC.Bot visa >> > > 2. Merge these changes to the master branch. >> > > 3. After that and 3-day stabilization cherry-pick to 2.8 >> > > >> > > Should we wait for benchmarks? I think at this release stage any >> > > additional benchmarks can eliminate our risks with extending scope. >> > > We've already had one - [2] (2.7.6 compared to 2.8). >> > > >> > > >> > > [1] https://issues.apache.org/jira/browse/IGNITE-12576 >> > > [2] >> > > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Benchmarks >> > > >> > > On Mon, 27 Jan 2020 at 23:58, Nikolay Izhikov >> wrote: >> > > > >> > > > Andrey. >> > > > >> > > > > My choice: correctness over performance >> > > > >> > > > I don’t think we should select performance OR correctness here. >> > > > It seems we can got both. >> > > > >> > > > > May be we should rollback all metrics related changes because we >> don't >> > > have benchmark results >> > > > >> > > > I perform benchmarking for initial refactoring of >> > > TcpCommunicationMetricsListener. >> > > > Initial refactoring of TcpCommunicationMetricsListener doesn’t >> bring any >> > > performance drop according to the results of the tests I performed. >> > > > >> > > > I want to perform benchmarking just to be sure everything OK. >> > > > Please, wait while I gather benchmark results for this PR. >> > > > >> > > > > 27 янв. 2020 г., в 22:33, Andrey Gura >> написал(а): >> > > > > >> > > > >> We still can’t accept patches that badly affects the performance >> of >> > > TcpCommuncationMetricsListener. >> > > > >> So we should perform yardstick tests before the merge. >> > > > > >> > > > > Absolutely all metrics are on the hot path. They inevitably affect >> > > > > performance and this case is the same. May be we should rollback >> all >> > > > > metrics related changes because we don't have benchmark results& >> > > > > >> > > > >> I can help to run yardstick benchmarks if you don’t have free >> servers >> > > to do it. >> > > > > >> > > > > I don't need help in benchmarking. Once again, еhe current >> behavior is >> > > > > incorrect and should be fixed regardless of performance. >> > > > > >> > > > > Or... this functionality should be removed if performance is more >> > > > > important. In case of incorrect behavior it is the best option. >> > > > > >> > > > > My choice: correctness over performance. >> > > > > >> > > > > On Mon, Jan 27, 2020 at
Re: New channel about integration with Spring Framework
Folks, why don't you name the channel "ignite-spring-framework_russian" in Slack ;) - Denis On Wed, Jan 29, 2020 at 12:50 AM Maksim Stepachev < maksim.stepac...@gmail.com> wrote: > Yes, I do. > > ср, 29 янв. 2020 г. в 11:22, Sergey Chernolyas < > sergey.chernol...@gmail.com > >: > > > Do you mean channel at Telegram ? > > > > On Wed, 29 Jan 2020 at 11:20, Maksim Stepachev < > maksim.stepac...@gmail.com > > > > > wrote: > > > > > Okey, but our channel has 90+ active members. > > > > > > ср, 29 янв. 2020 г. в 11:15, Sergey Chernolyas < > > > sergey.chernol...@gmail.com > > > >: > > > > > > > Hi Maksim! > > > > > > > > The link is unavailable :-( I can't open it. I think Slack is more > > > > preferable. > > > > > > > > On Wed, 29 Jan 2020 at 11:13, Maksim Stepachev < > > > maksim.stepac...@gmail.com > > > > > > > > > wrote: > > > > > > > > > Hi, > > > > > > > > > > Could we use the telegram channel for it for the Russian community? > > > > > > > > > > https://t.me/RU_Ignite > > > > > > > > > > ср, 29 янв. 2020 г. в 10:53, Sergey Chernolyas < > > > > > sergey.chernol...@gmail.com > > > > > >: > > > > > > > > > > > Hi igniters! > > > > > > > > > > > > I have created new channel "#ignite-spring-framework" for > > discussion > > > > > about > > > > > > integration with Spring Framework. > > > > > > > > > > > > -- > > > > > > - > > > > > > > > > > > > With best regards, Sergey Chernolyas > > > > > > > > > > > > > > > > > > > > > > > -- > > > > - > > > > > > > > With best regards, Sergey Chernolyas > > > > > > > > > > > > > -- > > - > > > > With best regards, Sergey Chernolyas > > >
Re: Hello
Hi Sergey, welcome back! The dev list is a preferable way for communication. It's ok to keep the dev list in CC all the times even if Maksim will be working mostly with you on the Spring Data tasks. Anyway, you can use our community Slack channel for instant messaging: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Collaborate#HowtoCollaborate-IgniteSlack - Denis On Wed, Jan 29, 2020 at 12:21 AM Sergey Chernolyas < sergey.chernol...@gmail.com> wrote: > Hi! > > Cool! Thank you very much! Can I put your answer to new channel? Also ... > do you have Skype,Viber or Whatup for direct communication ? > > On Wed, 29 Jan 2020 at 11:19, Maksim Stepachev > > wrote: > > > Hi, > > > > I going to work with spring data. My plans add flux and mono to it. A few > > days ago Nikolay Izhikov finished the new spring boot starter. > > https://github.com/apache/ignite-extensions/tree/master/modules > > > > You may add the spring data module. > > > > > > ср, 29 янв. 2020 г. в 10:46, Sergey Chernolyas < > > sergey.chernol...@gmail.com > > >: > > > > > Hi Ivan! > > > > > > Thank you very much for your email. Yes, I need some assistance > because I > > > am new at contribution to the the project. But .. I did some PR to > Ignite > > > project two years ago. In spice of it, I need a assistance. > > > > > > I have created ticket > https://issues.apache.org/jira/browse/IGNITE-12582 > > . > > > My customer is needs to the feature and I want to implement it. I will > > try > > > to configure my developer environment as it wrote in the guide. Also > ... > > > do you know contributors who works with Spring Data? > > > > > > > > > On Wed, 29 Jan 2020 at 08:51, Ivan Pavlukhin > > wrote: > > > > > > > Hi Sergey, > > > > > > > > Welcome to the Apache Ignite Community. > > > > > > > > Do you need some assistance? Or might be you have something to tell > > > > the Community. Do not hesitate to write back. > > > > > > > > I see that your Jira account was already added to the contributors > > > > list. You can find some contribution guidelines at > > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > > > > > > > > вт, 28 янв. 2020 г. в 22:26, Sergey Chernolyas < > > > > sergey.chernol...@gmail.com>: > > > > > > > > > > > > > > My jiraId is schernolyas > > > > > > > > > > -- > > > > > - > > > > > > > > > > With best regards, Sergey Chernolyas > > > > > > > > > > > > > > > > -- > > > > Best regards, > > > > Ivan Pavlukhin > > > > > > > > > > > > > -- > > > - > > > > > > With best regards, Sergey Chernolyas > > > > > > > > -- > - > > With best regards, Sergey Chernolyas >
Data vanished from cluster after INACTIVE/ACTIVE switch
Hello, Igniters.
I found really confusing results of the simple test.
Data from the in-memory cache are vanished after change cluster state to
INACTIVE/ACTIVE.
Is this a bug or expected behavior?
```
public class ClusterDeactivateTest extends GridCommonAbstractTest {
String name = "my-cache";
/** */
@Test
public void testDataPresent() throws Exception {
IgniteEx i = startGrid(0);
i.createCache(name).put(1L, 1L);
assertEquals(1L, i.cache(name).get(1L));
i.cluster().state(ClusterState.INACTIVE);
i.cluster().state(ClusterState.ACTIVE);
assertEquals(1L, i.cache(name).get(1L)); //Assertion error here!
}
}
```
[jira] [Created] (IGNITE-12606) Parametrize IgniteTxStoreExceptionAbstractSelfTest
Vladimir Steshin created IGNITE-12606: - Summary: Parametrize IgniteTxStoreExceptionAbstractSelfTest Key: IGNITE-12606 URL: https://issues.apache.org/jira/browse/IGNITE-12606 Project: Ignite Issue Type: Sub-task Reporter: Vladimir Steshin Assignee: Vladimir Steshin IgniteTxStoreExceptionAbstractSelfTest seems to fit well the parametrization. It has only single depth of sub-tests which are used in one place together. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12605) Historical (WAL) rebalance can start on a cleared partition if some baseline node leaves the cluster and then joins back.
Pavel Pereslegin created IGNITE-12605:
-
Summary: Historical (WAL) rebalance can start on a cleared
partition if some baseline node leaves the cluster and then joins back.
Key: IGNITE-12605
URL: https://issues.apache.org/jira/browse/IGNITE-12605
Project: Ignite
Issue Type: Bug
Affects Versions: 2.9
Environment:
Reporter: Pavel Pereslegin
Assignee: Pavel Pereslegin
On partition map exchange initiated by baseline node leaving, the historical
supplier is not provided in the full message (assignPartitionStates() isn't
called when a node leaves).
Since we don't have a historical supplier "historical" partition scheduled for
clearing, then when a node joins back assignPartitionStates() is called and we
have a supplier for historical rebalance, but partition may be cleared already.
After such rebalance we have inconsistent partitions on a "historically
rebalanced" node (with consistent partition counters and state).
"Inlined" reproducer uses TestRecordingCommunicationSpi to sync nodes (but this
issue can be "unstable" reproduced without it (see attachment)).
Reproducer shows the following errors.
Error 1 (partitions have been cleared).
{noformat}
java.lang.AssertionError:
|--|---|
| | entries count |
| part |---|
| | node1 | node2 | node3 |
|--|---|
| 0 | 6250 | 6250 | 3125 |
| 1 | 6250 | 6250 | 3125 |
| 2 | 6250 | 6250 | 3125 |
...
| 31 | 6250 | 6250 | 3125 |
|--|---|---|---|
{noformat}
Error 2 (should be investigated deeply).
{noformat}
java.lang.AssertionError: Reached end of WAL but not all partitions are done
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.advance(GridCacheOffheapManager.java:1419)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.next(GridCacheOffheapManager.java:1295)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:1255)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:1163)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.nextX(IgniteRebalanceIteratorImpl.java:135)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:215)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.peek(IgniteRebalanceIteratorImpl.java:155)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:316)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.lambda$handleDemandMessage$1(GridDhtPreloader.java:374)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{noformat}
Reproducer:
{code:java}
import java.util.ArrayList;
import java.util.LinkedHashSet;
import java.util.List;
import java.util.Set;
import java.util.concurrent.CountDownLatch;
import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteCache;
import org.apache.ignite.IgniteDataStreamer;
import org.apache.ignite.cache.CacheAtomicityMode;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.cache.CacheRebalanceMode;
import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
import org.apache.ignite.cluster.ClusterNode;
import org.apache.ignite.cluster.ClusterState;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.DataRegionConfiguration;
import org.apache.ignite.configuration.DataStorageConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.configuration.WALMode;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.internal.TestRecordingCommunicationSpi;
import
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemandMessage;
import
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition;
import
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionState;
import org.apache.ignite.internal.util.typedef.G;
import org.apache.ignite.internal.util.typedef.P2;
import org.apache.ignite.internal.util.typedef.internal.CU;
import
Re: TeamCity registration issue
It works! Thank you! On 29 Jan 2020, 17:28 +0300, Petr Ivanov , wrote: > Artem, > > > Can you try registering in Incognito mode, please? > > > On 29 Jan 2020, at 16:15, Artem Demchenko wrote: > > > > Attempt #2. Here is the link: > > https://drive.google.com/file/d/1jUU6nsiRuhTsR5Vz4h621HkzkAypw3ZR/view?usp=sharing > > > > -- > > С уважением, > > Демченко Артем > > > > On 29 Jan 2020, 16:02 +0300, Ivan Pavlukhin , wrote: > > > Hi Artem, > > > > > > I do not see attached screenshot. Perhaps you need to share a > > > screenshot on web and provide a link. > > > > > > ср, 29 янв. 2020 г. в 15:41, Artem Demchenko : > > > > > > > > Hi! > > > > > > > > I faced a strange problem with TeamCity. > > > > When I try to register as a new user, I get such error (attached > > > > screenshot). > > > > How to fix it? > > > > > > > > -- > > > > Best regards, > > > > Demchenko Artem > > > > > > > > > > > > -- > > > Best regards, > > > Ivan Pavlukhin >
[jira] [Created] (IGNITE-12604) .NET: DotNetCore publish dir is not copied to bin dir
Pavel Tupitsyn created IGNITE-12604: --- Summary: .NET: DotNetCore publish dir is not copied to bin dir Key: IGNITE-12604 URL: https://issues.apache.org/jira/browse/IGNITE-12604 Project: Ignite Issue Type: Bug Components: platforms Affects Versions: 2.8, 2.9 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 2.8, 2.9 Recent changes in build.ps1 break the release build: publish folder is not present in dotnet/bin. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12603) Questions regarding Data Availability/Replication.
Aditya created IGNITE-12603: --- Summary: Questions regarding Data Availability/Replication. Key: IGNITE-12603 URL: https://issues.apache.org/jira/browse/IGNITE-12603 Project: Ignite Issue Type: Wish Reporter: Aditya Scenario: Datacenter 1 (Main) -> One Application Server (Client Node CN1) and One DB Server (Server Node SN1). Datacenter 2 (Recovery) -> One Application Server (Client Node CN2) and One DB Server (Server Node SN2). Usually, all the user requests go to CN1 but not CN2. So, technically we will not run CN2. So forget about CN2. I will tell you why it's used later. So there are three nodes here running -> CN1, SN1, SN2. Question 1: We don't use Apache Ignite for cache purposes, but we will use it for disk persistent storage. And we don't need Ignite for partitioning data (we will think about it later). Now, how to make sure that the data that is being stored in SN1 will be replicated to SN2. We want SN2 to be backup node for SN1. Is that possible? If so, how? Conditions: 1. CN1 usually should not make connections with SN2 (since it's backup). 2. SN1 and SN2 link will be very fragile and of less bandwidth. Usually, both will be in different network segments. Question 2: Let's say SN1 is down. Now, will the queries automatically reach SN2 without doing anything? And if SN1 is restarted, can we expect the queries to reach SN1 instead of SN2, as CN1 - SN2 link is slow? Question 3 : After a few months, we will flip the entire setup, making DC2 as Main and DC1 as Recovery. In this case, CN2 will make connections to SN2 and CN1 will not be running. How to quickly switch so that SN2 is replicated almost with SN1 and be ready to serve requests from CN2? PS: We are using JDBC Thin Client, so if possible please answer in that context with examples. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: TeamCity registration issue
Artem, Can you try registering in Incognito mode, please? > On 29 Jan 2020, at 16:15, Artem Demchenko wrote: > > Attempt #2. Here is the link: > https://drive.google.com/file/d/1jUU6nsiRuhTsR5Vz4h621HkzkAypw3ZR/view?usp=sharing > > -- > С уважением, > Демченко Артем > > On 29 Jan 2020, 16:02 +0300, Ivan Pavlukhin , wrote: >> Hi Artem, >> >> I do not see attached screenshot. Perhaps you need to share a >> screenshot on web and provide a link. >> >> ср, 29 янв. 2020 г. в 15:41, Artem Demchenko : >>> >>> Hi! >>> >>> I faced a strange problem with TeamCity. >>> When I try to register as a new user, I get such error (attached >>> screenshot). >>> How to fix it? >>> >>> -- >>> Best regards, >>> Demchenko Artem >> >> >> >> -- >> Best regards, >> Ivan Pavlukhin
[jira] [Created] (IGNITE-12602) Calcite integration. JDBC Thin driver support.
Igor Seliverstov created IGNITE-12602: - Summary: Calcite integration. JDBC Thin driver support. Key: IGNITE-12602 URL: https://issues.apache.org/jira/browse/IGNITE-12602 Project: Ignite Issue Type: Task Reporter: Igor Seliverstov Provide a way to use experimental engine via JDBC thin driver. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Please a reviewer for the case IGNITE-12518
Hi Saikat, Denis, I'll start to migrate the development to maven for your test. Best regards, *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión 09-57861903 Linkedin: https://cl.linkedin.com/in/luisalejandroarcemartinez El sáb., 25 ene. 2020 a las 23:24, Saikat Maitra () escribió: > Hi, Luis, Denis > > We can take up the changes in either Ignite-extensions repo as new > independent module or as part of ignite repo inside rest-http module but > since the changes are not in git pull request it is hard for us to review > and share feedback. > > 1. There are jar dependencies shared in the jira ticket[1] but we do not > accept jar instead we will require the changes in maven pom.xml file. > > 2. There are also changes in GridJettyRestHandler and GridJettyRestProtocol > but there are no corresponding tests for validation. It will be better if > required tests are added as part of PR. > > 3. It is also unclear how do we incorporate the changes mentioned in the > jira related to web.xml file, Do they need to be part of README.md? > > Please let me know if I can help in any way with PR process. > > Our docs for contribution are available here [2] > > [1] https://issues.apache.org/jira/browse/IGNITE-12518 > [2] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > > > Regards, > Saikat > > > > > > > > On Fri, Jan 24, 2020 at 11:09 AM Denis Magda wrote: > > > Hi Luis, > > > > Presently, the community is on the route of Ignite simplification. We're > > trying to define Ignite core that has minimal dependencies with 3rd party > > libraries. That also led to the modularization initiative [1] with the > > first results in the form of Ignite Extensions repository where we're > > moving all 3rd party integrations. > > > > Saikat, do you think Luis's contribution needs to reside in the > extensions > > repository? > > > > [1] > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization > > > > - > > Denis > > > > > > On Thu, Jan 23, 2020 at 8:48 PM Luis Arce wrote: > > > > > Hi Saikat, > > > Thanks for you response: > > > > > > My system need a web server for work. i work correctly with Wildfly > and i > > > use Ignite as Backend for database. > > > My problem is the combination of both is around 6 GB RAM for work in > the > > > VPS. > > > For this reason i modified the unique plugin with webserver inside > > > (rest-http module). > > > The change enabled the possibility for use only 3GB RAM in a VPS ( > > > vpsserver.com) saving money and enabling horizontal scalling. > > > I shared this change in the Jira ticket touching the two classes of > > > rest-http plugin. > > > The change has less impact (programaticly), the point is the library > > > dependencies (quantity of jars). > > > > > > It change has sense for you?, i think is a util because that > technologies > > > dont has present inside of ignite currently and is friendly with the > code > > > of rest-ignite. > > > > > > > > > > > > > > > Best regards, > > > > > > > > > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión > > > 09-57861903 > > > Linkedin: > > > https://cl.linkedin.com/in/luisalejandroarcemartinez > > > > > > > > > > > > > > > > > > El mié., 22 ene. 2020 a las 0:38, Saikat Maitra (< > > saikat.mai...@gmail.com > > > >) > > > escribió: > > > > > > > Hello Luis, > > > > > > > > Thank you for your email. You can plan to create a separate > application > > > for > > > > jaxws service and use any build tools like gradle or maven to define > > your > > > > dependencies. > > > > > > > > Please find below some of the performance tips related to Ignite > > > > > > > > https://apacheignite.readme.io/docs/durable-memory-tuning > > > > > > > > You can use IgniteClient in your service and can connect to remote > > > cluster > > > > of Apache Ignite for data persistence. > > > > > > > > Can you please correct my understanding on the usage of > > ignite-rest-http > > > > in IGNITE-12518, I see the dependencies you have mentioned are > related > > to > > > > your project and my understanding is you are trying to use > > > ignite-rest-http > > > > jetty server for running your application. My understanding is this > > > change > > > > will make ignite-rest-http very large jar file with dependencies > > > > like tomcat-servlet-api-9.0.10.jar may not needed outside of your > > project > > > > scope. > > > > > > > > Please let me know your thoughts. > > > > > > > > Regards, > > > > Saikat > > > > > > > > > > > > On Sun, Jan 19, 2020 at 9:47 PM Luis Arce wrote: > > > > > > > > > Hi Saikat, > > > > > I agree, the impact of changes is bigger on the module. > > > > > I have a question: If i need create a jaxws service what is your > > > > > recomendation? > > > > > My motivation for the changes is the next: > > > > > *Introduction.* > > > > > A few time ago i design a ABB for traceability for Oracle Service > Bus > > > > with > > > > > the objective of detecting failures points in many
[jira] [Created] (IGNITE-12601) DistributedMetaStoragePersistentTest.testUnstableTopology is flaky
Vyacheslav Koptilin created IGNITE-12601: Summary: DistributedMetaStoragePersistentTest.testUnstableTopology is flaky Key: IGNITE-12601 URL: https://issues.apache.org/jira/browse/IGNITE-12601 Project: Ignite Issue Type: Bug Reporter: Vyacheslav Koptilin Assignee: Vyacheslav Koptilin Fix For: 2.8 DistributedMetaStoragePersistentTest.testUnstableTopology is flaky Please take a look at TC: https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5923369202582779855=testDetails -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12600) Baseline auto-adjust makes it impossible to assemble mixed persistence clusters
Ilya Kasnacheev created IGNITE-12600:
Summary: Baseline auto-adjust makes it impossible to assemble
mixed persistence clusters
Key: IGNITE-12600
URL: https://issues.apache.org/jira/browse/IGNITE-12600
Project: Ignite
Issue Type: Bug
Components: persistence
Reporter: Ilya Kasnacheev
If you try to start a cluster of two nodes, where A only has default
non-persistent region, and B also has a persistent non-default region, it will
fail with:
{code}
Caused by: class org.apache.ignite.spi.IgniteSpiException: Joining persistence
node to in-memory cluster couldn't be allowed due to baseline auto-adjust is
enabled and timeout equal to 0
{code}
However, there seem to be no configuration settings to actually disable this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: TeamCity registration issue
Attempt #2. Here is the link: https://drive.google.com/file/d/1jUU6nsiRuhTsR5Vz4h621HkzkAypw3ZR/view?usp=sharing -- С уважением, Демченко Артем On 29 Jan 2020, 16:02 +0300, Ivan Pavlukhin , wrote: > Hi Artem, > > I do not see attached screenshot. Perhaps you need to share a > screenshot on web and provide a link. > > ср, 29 янв. 2020 г. в 15:41, Artem Demchenko : > > > > Hi! > > > > I faced a strange problem with TeamCity. > > When I try to register as a new user, I get such error (attached > > screenshot). > > How to fix it? > > > > -- > > Best regards, > > Demchenko Artem > > > > -- > Best regards, > Ivan Pavlukhin
Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]
Hello! I have just promoted https://issues.apache.org/jira/browse/IGNITE-12504 to Blocker. The reasoning for this, you can't seem to configure baseline auto-adjust until your node is up (there is no configuration for this), and it will refuse nodes joining outright with default configuration, making it impossible to assemble some clusters. I will file a separate ticket about that. "Caused by: class org.apache.ignite.spi.IgniteSpiException: Joining persistence node to in-memory cluster couldn't be allowed due to baseline auto-adjust is enabled and timeout equal to 0" Regards, -- Ilya Kasnacheev ср, 29 янв. 2020 г. в 14:33, Andrey Gura : > Hi, > > one more issue which should be fixed in 2.8 release [1] > > [1] https://issues.apache.org/jira/browse/IGNITE-12598 > > On Tue, Jan 28, 2020 at 7:29 PM Maxim Muzafarov wrote: > > > > Igniters, > > > > > > Here is the list of actual release BLOCKER issues: > > > > [1] Keep in mind unfinished discussion about internal classes > > IGNITE-12456 [2] Cluster Data Store grid gets Corrupted for Load test > > *[Unassigned]* OPEN > > IGNITE-12398 Apache Ignite Cluster(Amazon S3 Based Discovery) Nodes > getting > > down [Emmanouil Gkatziouras] IN PROGRESS > > IGNITE-12580 NPE in GridMetricManager [Nikolay Izhikov] PATCH AVAILABLE > > IGNITE-12489 Error during purges by expiration: Unknown page type [Anton > > Kalashnikov] OPEN > > > > [1] > > > http://apache-ignite-developers.2346864.n4.nabble.com/Internal-classes-are-exposed-in-public-API-td45146.html > > [2] https://issues.apache.org/jira/browse/IGNITE-12456 > > [3] https://issues.apache.org/jira/browse/IGNITE-12398 > > [4] https://issues.apache.org/jira/browse/IGNITE-12580 > > [5] https://issues.apache.org/jira/browse/IGNITE-12489 > > > > > > On Tue, 28 Jan 2020 at 19:25, Maxim Muzafarov wrote: > > > > > Andrey, > > > > > > I've looked through those changes [1] and now they look good to me. > > > Let's do the following: > > > > > > 1. Get a fresh TC.Bot visa > > > 2. Merge these changes to the master branch. > > > 3. After that and 3-day stabilization cherry-pick to 2.8 > > > > > > Should we wait for benchmarks? I think at this release stage any > > > additional benchmarks can eliminate our risks with extending scope. > > > We've already had one - [2] (2.7.6 compared to 2.8). > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12576 > > > [2] > > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Benchmarks > > > > > > On Mon, 27 Jan 2020 at 23:58, Nikolay Izhikov > wrote: > > > > > > > > Andrey. > > > > > > > > > My choice: correctness over performance > > > > > > > > I don’t think we should select performance OR correctness here. > > > > It seems we can got both. > > > > > > > > > May be we should rollback all metrics related changes because we > don't > > > have benchmark results > > > > > > > > I perform benchmarking for initial refactoring of > > > TcpCommunicationMetricsListener. > > > > Initial refactoring of TcpCommunicationMetricsListener doesn’t bring > any > > > performance drop according to the results of the tests I performed. > > > > > > > > I want to perform benchmarking just to be sure everything OK. > > > > Please, wait while I gather benchmark results for this PR. > > > > > > > > > 27 янв. 2020 г., в 22:33, Andrey Gura > написал(а): > > > > > > > > > >> We still can’t accept patches that badly affects the performance > of > > > TcpCommuncationMetricsListener. > > > > >> So we should perform yardstick tests before the merge. > > > > > > > > > > Absolutely all metrics are on the hot path. They inevitably affect > > > > > performance and this case is the same. May be we should rollback > all > > > > > metrics related changes because we don't have benchmark results& > > > > > > > > > >> I can help to run yardstick benchmarks if you don’t have free > servers > > > to do it. > > > > > > > > > > I don't need help in benchmarking. Once again, еhe current > behavior is > > > > > incorrect and should be fixed regardless of performance. > > > > > > > > > > Or... this functionality should be removed if performance is more > > > > > important. In case of incorrect behavior it is the best option. > > > > > > > > > > My choice: correctness over performance. > > > > > > > > > > On Mon, Jan 27, 2020 at 10:02 PM Nikolay Izhikov < > nizhi...@apache.org> > > > wrote: > > > > >> > > > > >>> I think it could be fixed easily by adding metricsEnabled flag to > > > TcpCommunicationSpi. > > > > >> > > > > >> We still can’t accept patches that badly affects the performance > of > > > TcpCommuncationMetricsListener. > > > > >> So we should perform yardstick tests before the merge. > > > > >> > > > > >> I can help to run yardstick benchmarks if you don’t have free > servers > > > to do it. > > > > >> > > > > >> > > > > >>> 27 янв. 2020 г., в 21:47, Andrey Gura > написал(а): > > > > >>> > > > > > "If it doesn’t work, it doesn’t matter how fast it doesn’t > work." >
Re: TeamCity registration issue
Here is the link. On 29 Jan 2020, 16:02 +0300, Ivan Pavlukhin , wrote: > Hi Artem, > > I do not see attached screenshot. Perhaps you need to share a > screenshot on web and provide a link. > > ср, 29 янв. 2020 г. в 15:41, Artem Demchenko : > > > > Hi! > > > > I faced a strange problem with TeamCity. > > When I try to register as a new user, I get such error (attached > > screenshot). > > How to fix it? > > > > -- > > Best regards, > > Demchenko Artem > > > > -- > Best regards, > Ivan Pavlukhin
TeamCity registration issue
Hi! I faced a strange problem with TeamCity. When I try to register as a new user, I get such error (attached screenshot). How to fix it? -- Best regards, Demchenko Artem
Re: [IGNITE-12582] Configuration by property
Hi! Main subject is the example https://apacheignite-mix.readme.io/docs/spring-data#section-apache-ignite-repository demonstrates mapping between particular repository and particular cache by annotation "RepositoryConfig". I need to do it by spring configuration. For example, property " *spring.data.mongodb.uri*" from spring data repository for mongodb On Wed, 29 Jan 2020 at 15:16, Sergey Chernolyas wrote: > Hi! > > It is seemed what I need. > > On Wed, 29 Jan 2020 at 15:14, Nikolay Izhikov wrote: > >> Hello, Sergey. >> >> What is «repository»? How it relates to the Ignite? >> >> ignite-spring-boot-autoconfigure confirms your requirements? >> >> >> https://github.com/apache/ignite-extensions/blob/master/modules/spring-boot-autoconfigure/examples/main/resources/application.yml >> >> ``` >> ignite: >> igniteInstanceName: properties-instance-name >> communicationSpi: >> localPort: >> dataStorageConfiguration: >> defaultDataRegionConfiguration: >> initialSize: 10485760 #10MB >> dataRegionConfigurations: >> - name: my-dataregion >> initialSize: 104857600 #100MB >> cacheConfiguration: >> - name: accounts >> queryEntities: >> - tableName: ACCOUNTS >> keyFieldName: ID >> keyType: java.lang.Long >> valueType: java.lang.Object >> fields: >> ID: java.lang.Long >> amount: java.lang.Double >> updateDate: java.util.Date >> - name: my-cache2 >> ``` >> >> >> > 29 янв. 2020 г., в 15:09, Sergey Chernolyas < >> sergey.chernol...@gmail.com> написал(а): >> > >> > Hi Nikolay! >> > I need to configure particulate repository by usual Spring configuration >> > without using >> > >> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/springdata20/repository/config/RepositoryConfig.html >> > >> > Am I investing to a bicycle? >> > >> > On Wed, 29 Jan 2020 at 14:58, Nikolay Izhikov >> wrote: >> > >> >> Hello, Sergey. >> >> >> >> Your proposal is not clear for me >> >> Can you, please, describe the issue you are trying to solve? >> >> And the way you want to do it. >> >> >> >> >> >>> 29 янв. 2020 г., в 14:53, Sergey Chernolyas < >> sergey.chernol...@gmail.com> >> >> написал(а): >> >>> >> >>> Hi! >> >>> It is proposed to use the structure for configuration. >> >>> >> >>> spring.data.ignite: >> >>> - name: cache1 >> >>> sqlSchema: schema1 >> >>> atomicityMode: TRANSACTIONAL_SNAPSHOT >> >>> - name: cache2 >> >>> sqlSchema: schema2 >> >>> storeKeepBinary: true >> >>> - name: cache3 >> >>>sqlQuery: CREATE TABLE IF NOT EXISTS Person (id int, city_id int, >> >> name >> >>> varchar, age int, company varchar, PRIMARY KEY (id, city_id)) >> >>> >> >>> Other ideas ? >> >>> >> >>> >> >>> >> >>> -- >> >>> - >> >>> >> >>> With best regards, Sergey Chernolyas >> >> >> >> >> > >> > -- >> > - >> > >> > With best regards, Sergey Chernolyas >> >> > > -- > - > > With best regards, Sergey Chernolyas > -- - With best regards, Sergey Chernolyas
Re: [IGNITE-12582] Configuration by property
Hi! It is seemed what I need. On Wed, 29 Jan 2020 at 15:14, Nikolay Izhikov wrote: > Hello, Sergey. > > What is «repository»? How it relates to the Ignite? > > ignite-spring-boot-autoconfigure confirms your requirements? > > > https://github.com/apache/ignite-extensions/blob/master/modules/spring-boot-autoconfigure/examples/main/resources/application.yml > > ``` > ignite: > igniteInstanceName: properties-instance-name > communicationSpi: > localPort: > dataStorageConfiguration: > defaultDataRegionConfiguration: > initialSize: 10485760 #10MB > dataRegionConfigurations: > - name: my-dataregion > initialSize: 104857600 #100MB > cacheConfiguration: > - name: accounts > queryEntities: > - tableName: ACCOUNTS > keyFieldName: ID > keyType: java.lang.Long > valueType: java.lang.Object > fields: > ID: java.lang.Long > amount: java.lang.Double > updateDate: java.util.Date > - name: my-cache2 > ``` > > > > 29 янв. 2020 г., в 15:09, Sergey Chernolyas > написал(а): > > > > Hi Nikolay! > > I need to configure particulate repository by usual Spring configuration > > without using > > > https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/springdata20/repository/config/RepositoryConfig.html > > > > Am I investing to a bicycle? > > > > On Wed, 29 Jan 2020 at 14:58, Nikolay Izhikov > wrote: > > > >> Hello, Sergey. > >> > >> Your proposal is not clear for me > >> Can you, please, describe the issue you are trying to solve? > >> And the way you want to do it. > >> > >> > >>> 29 янв. 2020 г., в 14:53, Sergey Chernolyas < > sergey.chernol...@gmail.com> > >> написал(а): > >>> > >>> Hi! > >>> It is proposed to use the structure for configuration. > >>> > >>> spring.data.ignite: > >>> - name: cache1 > >>> sqlSchema: schema1 > >>> atomicityMode: TRANSACTIONAL_SNAPSHOT > >>> - name: cache2 > >>> sqlSchema: schema2 > >>> storeKeepBinary: true > >>> - name: cache3 > >>>sqlQuery: CREATE TABLE IF NOT EXISTS Person (id int, city_id int, > >> name > >>> varchar, age int, company varchar, PRIMARY KEY (id, city_id)) > >>> > >>> Other ideas ? > >>> > >>> > >>> > >>> -- > >>> - > >>> > >>> With best regards, Sergey Chernolyas > >> > >> > > > > -- > > - > > > > With best regards, Sergey Chernolyas > > -- - With best regards, Sergey Chernolyas
Re: [IGNITE-12582] Configuration by property
Hello, Sergey. What is «repository»? How it relates to the Ignite? ignite-spring-boot-autoconfigure confirms your requirements? https://github.com/apache/ignite-extensions/blob/master/modules/spring-boot-autoconfigure/examples/main/resources/application.yml ``` ignite: igniteInstanceName: properties-instance-name communicationSpi: localPort: dataStorageConfiguration: defaultDataRegionConfiguration: initialSize: 10485760 #10MB dataRegionConfigurations: - name: my-dataregion initialSize: 104857600 #100MB cacheConfiguration: - name: accounts queryEntities: - tableName: ACCOUNTS keyFieldName: ID keyType: java.lang.Long valueType: java.lang.Object fields: ID: java.lang.Long amount: java.lang.Double updateDate: java.util.Date - name: my-cache2 ``` > 29 янв. 2020 г., в 15:09, Sergey Chernolyas > написал(а): > > Hi Nikolay! > I need to configure particulate repository by usual Spring configuration > without using > https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/springdata20/repository/config/RepositoryConfig.html > > Am I investing to a bicycle? > > On Wed, 29 Jan 2020 at 14:58, Nikolay Izhikov wrote: > >> Hello, Sergey. >> >> Your proposal is not clear for me >> Can you, please, describe the issue you are trying to solve? >> And the way you want to do it. >> >> >>> 29 янв. 2020 г., в 14:53, Sergey Chernolyas >> написал(а): >>> >>> Hi! >>> It is proposed to use the structure for configuration. >>> >>> spring.data.ignite: >>> - name: cache1 >>> sqlSchema: schema1 >>> atomicityMode: TRANSACTIONAL_SNAPSHOT >>> - name: cache2 >>> sqlSchema: schema2 >>> storeKeepBinary: true >>> - name: cache3 >>>sqlQuery: CREATE TABLE IF NOT EXISTS Person (id int, city_id int, >> name >>> varchar, age int, company varchar, PRIMARY KEY (id, city_id)) >>> >>> Other ideas ? >>> >>> >>> >>> -- >>> - >>> >>> With best regards, Sergey Chernolyas >> >> > > -- > - > > With best regards, Sergey Chernolyas
Re: [IGNITE-12582] Configuration by property
Hi Nikolay! I need to configure particulate repository by usual Spring configuration without using https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/springdata20/repository/config/RepositoryConfig.html Am I investing to a bicycle? On Wed, 29 Jan 2020 at 14:58, Nikolay Izhikov wrote: > Hello, Sergey. > > Your proposal is not clear for me > Can you, please, describe the issue you are trying to solve? > And the way you want to do it. > > > > 29 янв. 2020 г., в 14:53, Sergey Chernolyas > написал(а): > > > > Hi! > > It is proposed to use the structure for configuration. > > > > spring.data.ignite: > > - name: cache1 > > sqlSchema: schema1 > > atomicityMode: TRANSACTIONAL_SNAPSHOT > > - name: cache2 > > sqlSchema: schema2 > > storeKeepBinary: true > > - name: cache3 > > sqlQuery: CREATE TABLE IF NOT EXISTS Person (id int, city_id int, > name > > varchar, age int, company varchar, PRIMARY KEY (id, city_id)) > > > > Other ideas ? > > > > > > > > -- > > - > > > > With best regards, Sergey Chernolyas > > -- - With best regards, Sergey Chernolyas
Re: [IGNITE-12582] Configuration by property
Hello, Sergey. Your proposal is not clear for me Can you, please, describe the issue you are trying to solve? And the way you want to do it. > 29 янв. 2020 г., в 14:53, Sergey Chernolyas > написал(а): > > Hi! > It is proposed to use the structure for configuration. > > spring.data.ignite: > - name: cache1 > sqlSchema: schema1 > atomicityMode: TRANSACTIONAL_SNAPSHOT > - name: cache2 > sqlSchema: schema2 > storeKeepBinary: true > - name: cache3 > sqlQuery: CREATE TABLE IF NOT EXISTS Person (id int, city_id int, name > varchar, age int, company varchar, PRIMARY KEY (id, city_id)) > > Other ideas ? > > > > -- > - > > With best regards, Sergey Chernolyas
[IGNITE-12582] Configuration by property
Hi! It is proposed to use the structure for configuration. spring.data.ignite: - name: cache1 sqlSchema: schema1 atomicityMode: TRANSACTIONAL_SNAPSHOT - name: cache2 sqlSchema: schema2 storeKeepBinary: true - name: cache3 sqlQuery: CREATE TABLE IF NOT EXISTS Person (id int, city_id int, name varchar, age int, company varchar, PRIMARY KEY (id, city_id)) Other ideas ? -- - With best regards, Sergey Chernolyas
[jira] [Created] (IGNITE-12599) Cluster fails when cache name is too long
Arsen Manucharyan created IGNITE-12599: -- Summary: Cluster fails when cache name is too long Key: IGNITE-12599 URL: https://issues.apache.org/jira/browse/IGNITE-12599 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.7.6 Reporter: Arsen Manucharyan When I create a cache with long name the whole cluster fails with such error: Failed to initialize cache working directory (failed to crea te, make sure the work folder has correct permissions): /platform/ignite/work/db/node00-852c7eca-e bf7-41fb-ac5a-4a65b2593780/cache-A AA _Int3_UnitTests.Models.Tes_007900a400b400ee005100ba004c00ac00c1002500cf00e f002500be000600d9]] It looks that Ignite tries to write a file that is not supported by Linux. The service is stopping and I have to start the service. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]
Hi, one more issue which should be fixed in 2.8 release [1] [1] https://issues.apache.org/jira/browse/IGNITE-12598 On Tue, Jan 28, 2020 at 7:29 PM Maxim Muzafarov wrote: > > Igniters, > > > Here is the list of actual release BLOCKER issues: > > [1] Keep in mind unfinished discussion about internal classes > IGNITE-12456 [2] Cluster Data Store grid gets Corrupted for Load test > *[Unassigned]* OPEN > IGNITE-12398 Apache Ignite Cluster(Amazon S3 Based Discovery) Nodes getting > down [Emmanouil Gkatziouras] IN PROGRESS > IGNITE-12580 NPE in GridMetricManager [Nikolay Izhikov] PATCH AVAILABLE > IGNITE-12489 Error during purges by expiration: Unknown page type [Anton > Kalashnikov] OPEN > > [1] > http://apache-ignite-developers.2346864.n4.nabble.com/Internal-classes-are-exposed-in-public-API-td45146.html > [2] https://issues.apache.org/jira/browse/IGNITE-12456 > [3] https://issues.apache.org/jira/browse/IGNITE-12398 > [4] https://issues.apache.org/jira/browse/IGNITE-12580 > [5] https://issues.apache.org/jira/browse/IGNITE-12489 > > > On Tue, 28 Jan 2020 at 19:25, Maxim Muzafarov wrote: > > > Andrey, > > > > I've looked through those changes [1] and now they look good to me. > > Let's do the following: > > > > 1. Get a fresh TC.Bot visa > > 2. Merge these changes to the master branch. > > 3. After that and 3-day stabilization cherry-pick to 2.8 > > > > Should we wait for benchmarks? I think at this release stage any > > additional benchmarks can eliminate our risks with extending scope. > > We've already had one - [2] (2.7.6 compared to 2.8). > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12576 > > [2] > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Benchmarks > > > > On Mon, 27 Jan 2020 at 23:58, Nikolay Izhikov wrote: > > > > > > Andrey. > > > > > > > My choice: correctness over performance > > > > > > I don’t think we should select performance OR correctness here. > > > It seems we can got both. > > > > > > > May be we should rollback all metrics related changes because we don't > > have benchmark results > > > > > > I perform benchmarking for initial refactoring of > > TcpCommunicationMetricsListener. > > > Initial refactoring of TcpCommunicationMetricsListener doesn’t bring any > > performance drop according to the results of the tests I performed. > > > > > > I want to perform benchmarking just to be sure everything OK. > > > Please, wait while I gather benchmark results for this PR. > > > > > > > 27 янв. 2020 г., в 22:33, Andrey Gura написал(а): > > > > > > > >> We still can’t accept patches that badly affects the performance of > > TcpCommuncationMetricsListener. > > > >> So we should perform yardstick tests before the merge. > > > > > > > > Absolutely all metrics are on the hot path. They inevitably affect > > > > performance and this case is the same. May be we should rollback all > > > > metrics related changes because we don't have benchmark results& > > > > > > > >> I can help to run yardstick benchmarks if you don’t have free servers > > to do it. > > > > > > > > I don't need help in benchmarking. Once again, еhe current behavior is > > > > incorrect and should be fixed regardless of performance. > > > > > > > > Or... this functionality should be removed if performance is more > > > > important. In case of incorrect behavior it is the best option. > > > > > > > > My choice: correctness over performance. > > > > > > > > On Mon, Jan 27, 2020 at 10:02 PM Nikolay Izhikov > > wrote: > > > >> > > > >>> I think it could be fixed easily by adding metricsEnabled flag to > > TcpCommunicationSpi. > > > >> > > > >> We still can’t accept patches that badly affects the performance of > > TcpCommuncationMetricsListener. > > > >> So we should perform yardstick tests before the merge. > > > >> > > > >> I can help to run yardstick benchmarks if you don’t have free servers > > to do it. > > > >> > > > >> > > > >>> 27 янв. 2020 г., в 21:47, Andrey Gura написал(а): > > > >>> > > > > "If it doesn’t work, it doesn’t matter how fast it doesn’t work." > > (c) > > > Please, clarify, what do you mean by «doesn’t work»? > > > Are there any unresolved bugs? > > > >>> > > > >>> Obviously some communication metrics can't be monitored or analyzed > > > >>> retrospectively due to changing node ID during node restart. It's > > bug. > > > >>> > > > > User can disable metrics if it will affect performance. > > > Users can’t disable TcpCommunicationListener nor in any release nor > > in current master so we should change this code carefully > > > >>> > > > >>> This is another bug. I think it could be fixed easily by adding > > > >>> metricsEnabled flag to TcpCommunicationSpi. > > > >>> > > > >>> On Mon, Jan 27, 2020 at 9:17 PM Nikolay Izhikov > > wrote: > > > > > > Andrey. > > > > > > > "If it doesn’t work, it doesn’t matter how fast it doesn’t work." > > (c) > > > > > > Please, clarify, what do you mean by «doesn’t
[jira] [Created] (IGNITE-12598) Metrics configuration will be deleted on cache stop
Andrey N. Gura created IGNITE-12598: --- Summary: Metrics configuration will be deleted on cache stop Key: IGNITE-12598 URL: https://issues.apache.org/jira/browse/IGNITE-12598 Project: Ignite Issue Type: Bug Reporter: Andrey N. Gura Fix For: 2.8 This issue is related with IGNITE-12580 where NPE occures on attempt to remove cache configuration. While NPE is fixed the root cause doesn't. Root cause is attempt to remove metric configuration on cache stop while it should be done only on cache destroy. Cache stop will be performed for example on node stop. After node start cache will be started too but metric configuration is already removed and will not applied to the cache metrics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Ignite Extension - TC link
Hello, Igniters. Can you, please, give me a link to the «Ignite Extension» project on the TC?
Re: Question: Table scheme 'default'
Vladimir. Please, provide a simple, self-contained reproducer to the issue you described. > 29 янв. 2020 г., в 11:16, Vladimir Steshin написал(а): > > Hi ppl. Wanted to ask is issue a bug. Minor propably. > > Recently noticed that one simple query returns a value which can't be found > 'as is' in following query. I tried to find and drop all the tables I > created with "create table": > > select schema_name, table_name, cache_name from sys.tables > > And there are tables which were not created with 'create table...'. For > example, table 'default.Person' from the test/tutorial I was researching. > Ok. I tried to delete them too. Now I know this is prohibited. But why I > got error: scheme 'default' not found? I just received this schema name > from previous query. > > To avoid this I had to capitalize schema name taking it into "": > "default".Person. Then I got normal error like 'only cache created tables > can be removed with drop table.'. > > One select returns value which can't be found in second select > (delete/drop). Isn't it a bug from SQL's point of view?
Re: New channel about integration with Spring Framework
Yes, I do. ср, 29 янв. 2020 г. в 11:22, Sergey Chernolyas : > Do you mean channel at Telegram ? > > On Wed, 29 Jan 2020 at 11:20, Maksim Stepachev > > wrote: > > > Okey, but our channel has 90+ active members. > > > > ср, 29 янв. 2020 г. в 11:15, Sergey Chernolyas < > > sergey.chernol...@gmail.com > > >: > > > > > Hi Maksim! > > > > > > The link is unavailable :-( I can't open it. I think Slack is more > > > preferable. > > > > > > On Wed, 29 Jan 2020 at 11:13, Maksim Stepachev < > > maksim.stepac...@gmail.com > > > > > > > wrote: > > > > > > > Hi, > > > > > > > > Could we use the telegram channel for it for the Russian community? > > > > > > > > https://t.me/RU_Ignite > > > > > > > > ср, 29 янв. 2020 г. в 10:53, Sergey Chernolyas < > > > > sergey.chernol...@gmail.com > > > > >: > > > > > > > > > Hi igniters! > > > > > > > > > > I have created new channel "#ignite-spring-framework" for > discussion > > > > about > > > > > integration with Spring Framework. > > > > > > > > > > -- > > > > > - > > > > > > > > > > With best regards, Sergey Chernolyas > > > > > > > > > > > > > > > > > > -- > > > - > > > > > > With best regards, Sergey Chernolyas > > > > > > > > -- > - > > With best regards, Sergey Chernolyas >
Re: New channel about integration with Spring Framework
Do you mean channel at Telegram ? On Wed, 29 Jan 2020 at 11:20, Maksim Stepachev wrote: > Okey, but our channel has 90+ active members. > > ср, 29 янв. 2020 г. в 11:15, Sergey Chernolyas < > sergey.chernol...@gmail.com > >: > > > Hi Maksim! > > > > The link is unavailable :-( I can't open it. I think Slack is more > > preferable. > > > > On Wed, 29 Jan 2020 at 11:13, Maksim Stepachev < > maksim.stepac...@gmail.com > > > > > wrote: > > > > > Hi, > > > > > > Could we use the telegram channel for it for the Russian community? > > > > > > https://t.me/RU_Ignite > > > > > > ср, 29 янв. 2020 г. в 10:53, Sergey Chernolyas < > > > sergey.chernol...@gmail.com > > > >: > > > > > > > Hi igniters! > > > > > > > > I have created new channel "#ignite-spring-framework" for discussion > > > about > > > > integration with Spring Framework. > > > > > > > > -- > > > > - > > > > > > > > With best regards, Sergey Chernolyas > > > > > > > > > > > > > -- > > - > > > > With best regards, Sergey Chernolyas > > > -- - With best regards, Sergey Chernolyas
Re: Hello
Hi! Cool! Thank you very much! Can I put your answer to new channel? Also ... do you have Skype,Viber or Whatup for direct communication ? On Wed, 29 Jan 2020 at 11:19, Maksim Stepachev wrote: > Hi, > > I going to work with spring data. My plans add flux and mono to it. A few > days ago Nikolay Izhikov finished the new spring boot starter. > https://github.com/apache/ignite-extensions/tree/master/modules > > You may add the spring data module. > > > ср, 29 янв. 2020 г. в 10:46, Sergey Chernolyas < > sergey.chernol...@gmail.com > >: > > > Hi Ivan! > > > > Thank you very much for your email. Yes, I need some assistance because I > > am new at contribution to the the project. But .. I did some PR to Ignite > > project two years ago. In spice of it, I need a assistance. > > > > I have created ticket https://issues.apache.org/jira/browse/IGNITE-12582 > . > > My customer is needs to the feature and I want to implement it. I will > try > > to configure my developer environment as it wrote in the guide. Also ... > > do you know contributors who works with Spring Data? > > > > > > On Wed, 29 Jan 2020 at 08:51, Ivan Pavlukhin > wrote: > > > > > Hi Sergey, > > > > > > Welcome to the Apache Ignite Community. > > > > > > Do you need some assistance? Or might be you have something to tell > > > the Community. Do not hesitate to write back. > > > > > > I see that your Jira account was already added to the contributors > > > list. You can find some contribution guidelines at > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > > > > > > вт, 28 янв. 2020 г. в 22:26, Sergey Chernolyas < > > > sergey.chernol...@gmail.com>: > > > > > > > > > > > My jiraId is schernolyas > > > > > > > > -- > > > > - > > > > > > > > With best regards, Sergey Chernolyas > > > > > > > > > > > > -- > > > Best regards, > > > Ivan Pavlukhin > > > > > > > > > -- > > - > > > > With best regards, Sergey Chernolyas > > > -- - With best regards, Sergey Chernolyas
Re: New channel about integration with Spring Framework
Okey, but our channel has 90+ active members. ср, 29 янв. 2020 г. в 11:15, Sergey Chernolyas : > Hi Maksim! > > The link is unavailable :-( I can't open it. I think Slack is more > preferable. > > On Wed, 29 Jan 2020 at 11:13, Maksim Stepachev > > wrote: > > > Hi, > > > > Could we use the telegram channel for it for the Russian community? > > > > https://t.me/RU_Ignite > > > > ср, 29 янв. 2020 г. в 10:53, Sergey Chernolyas < > > sergey.chernol...@gmail.com > > >: > > > > > Hi igniters! > > > > > > I have created new channel "#ignite-spring-framework" for discussion > > about > > > integration with Spring Framework. > > > > > > -- > > > - > > > > > > With best regards, Sergey Chernolyas > > > > > > > > -- > - > > With best regards, Sergey Chernolyas >
Re: Hello
Hi, I going to work with spring data. My plans add flux and mono to it. A few days ago Nikolay Izhikov finished the new spring boot starter. https://github.com/apache/ignite-extensions/tree/master/modules You may add the spring data module. ср, 29 янв. 2020 г. в 10:46, Sergey Chernolyas : > Hi Ivan! > > Thank you very much for your email. Yes, I need some assistance because I > am new at contribution to the the project. But .. I did some PR to Ignite > project two years ago. In spice of it, I need a assistance. > > I have created ticket https://issues.apache.org/jira/browse/IGNITE-12582 . > My customer is needs to the feature and I want to implement it. I will try > to configure my developer environment as it wrote in the guide. Also ... > do you know contributors who works with Spring Data? > > > On Wed, 29 Jan 2020 at 08:51, Ivan Pavlukhin wrote: > > > Hi Sergey, > > > > Welcome to the Apache Ignite Community. > > > > Do you need some assistance? Or might be you have something to tell > > the Community. Do not hesitate to write back. > > > > I see that your Jira account was already added to the contributors > > list. You can find some contribution guidelines at > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > > > > вт, 28 янв. 2020 г. в 22:26, Sergey Chernolyas < > > sergey.chernol...@gmail.com>: > > > > > > > > My jiraId is schernolyas > > > > > > -- > > > - > > > > > > With best regards, Sergey Chernolyas > > > > > > > > -- > > Best regards, > > Ivan Pavlukhin > > > > > -- > - > > With best regards, Sergey Chernolyas >
Question: Table scheme 'default'
Hi ppl. Wanted to ask is issue a bug. Minor propably. Recently noticed that one simple query returns a value which can't be found 'as is' in following query. I tried to find and drop all the tables I created with "create table": select schema_name, table_name, cache_name from sys.tables And there are tables which were not created with 'create table...'. For example, table 'default.Person' from the test/tutorial I was researching. Ok. I tried to delete them too. Now I know this is prohibited. But why I got error: scheme 'default' not found? I just received this schema name from previous query. To avoid this I had to capitalize schema name taking it into "": "default".Person. Then I got normal error like 'only cache created tables can be removed with drop table.'. One select returns value which can't be found in second select (delete/drop). Isn't it a bug from SQL's point of view?
Re: New channel about integration with Spring Framework
Hi Maksim! The link is unavailable :-( I can't open it. I think Slack is more preferable. On Wed, 29 Jan 2020 at 11:13, Maksim Stepachev wrote: > Hi, > > Could we use the telegram channel for it for the Russian community? > > https://t.me/RU_Ignite > > ср, 29 янв. 2020 г. в 10:53, Sergey Chernolyas < > sergey.chernol...@gmail.com > >: > > > Hi igniters! > > > > I have created new channel "#ignite-spring-framework" for discussion > about > > integration with Spring Framework. > > > > -- > > - > > > > With best regards, Sergey Chernolyas > > > -- - With best regards, Sergey Chernolyas
Re: New channel about integration with Spring Framework
Hi, Could we use the telegram channel for it for the Russian community? https://t.me/RU_Ignite ср, 29 янв. 2020 г. в 10:53, Sergey Chernolyas : > Hi igniters! > > I have created new channel "#ignite-spring-framework" for discussion about > integration with Spring Framework. > > -- > - > > With best regards, Sergey Chernolyas >
