Re: [DISCUSS] Remove a Patch-file contribution approach from guides
+1 Regards, Saikat On Sat, Oct 10, 2020 at 8:22 AM Alexey Zinoviev wrote: > Agree, need to update > > сб, 10 окт. 2020 г., 15:35 Ivan Pavlukhin : > > > Folks, > > > > A new contributor Bojidar tried to used a Patch-file contribution > > approach [1]. The approach is stated in our guides [2]. I suppose that > > the approach is obsolete. I several threads seem to confirm it [3, 4]. > > > > If nobody objects I will remove a section [2] from the guide. > > > > [1] > > > http://apache-ignite-developers.2346864.n4.nabble.com/Introduction-td49570.html > > [2] > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-2.CreateaPatch-file > > [3] > > > http://apache-ignite-developers.2346864.n4.nabble.com/ci-ignite-apache-Run-all-for-patch-jira-number-td24861.html > > [4] > > > http://apache-ignite-developers.2346864.n4.nabble.com/Disabling-patch-validation-mechanism-on-TC-td5400.html > > > > -- > > > > Best regards, > > Ivan Pavlukhin > > >
Re: [MTCGA]: new failures in builds [5655706] needs to be handled
Hi, I have made the changes to fix the testsuite failures. Regards, Saikat On Sat, Oct 10, 2020 at 12:41 PM wrote: > 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 this project, but things change and > you may no longer be able to finalize your contribution. > Could you respond to this email and indicate if you wish to continue and > fix test failures or step down and some committer may revert you commit. > > *New Critical Failure in master Streamers > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Streamers?branch=%3Cdefault%3E > Changes may lead to failure were done by > - samaitra > https://ci.ignite.apache.org/viewModification.html?modId=908297 > > - Here's a reminder of what contributors were agreed to do > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > - Should you have any questions please contact > dev@ignite.apache.org > > Best Regards, > Apache Ignite TeamCity Bot > https://github.com/apache/ignite-teamcity-bot > Notification generated at 20:41:17 10-10-2020 >
Re: Apache Ignite 3.0
Hi! I am back! Here are several ideas on top of my mind for Ignite 3.0 1. Client nodes should take the config from servers. Basically it should be enough to provide some cluster identifier or any known IP address to start a client. 2. Thread per partition. Again. I strongly recommend taking a look at how Scylla DB operates. I think this is the best distributed database threading model and can be a perfect fit for Ignite. Main idea is in "share nothing" approach - they keep thread switches to the necessary minimum - messages reading or updating data are processed within the thread that reads them (of course, the sender should properly route the message, i.e. send it to the correct socket). Blocking operations such as fsync happen outside of worker (shard) threads. This will require to split indexes per partition which should be quite ok for most of the use cases in my view. Edge cases with high-selectivity indexes selecting 1-2 rows for a value can be sped up with hash indexes or even by secondary index backed by another cache. 3. Replicate physical updates instead of logical. This will simplify logic running on backups to zero. Read a page sent by the primary node and apply it locally. Most probably this change will require pure thread per partition described above. 4. Merge (all?) network components (communication, disco, REST, etc?) and listen to one port. 5. Revisit transaction concurrency and isolation settings. Currently some of the combinations do not work as users may expect them to and some look just weird. Ready to discuss the above and other points. Thanks! Yakov
[MTCGA]: new failures in builds [5655706] needs to be handled
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 this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New Critical Failure in master Streamers https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Streamers?branch=%3Cdefault%3E Changes may lead to failure were done by - samaitra https://ci.ignite.apache.org/viewModification.html?modId=908297 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 20:41:17 10-10-2020
Re: Instance of IgniteClient in Multi threaded application
As per Ignite documentation "*only one thread reads/writes to the channel while other threads are waiting for the operation to complete."*.If we are using single client connection,then it may affect the performance -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: Instance of IgniteClient in Multi threaded application
Thanks Denis, Its a REST web service written in JAVA -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
[MTCGA]: new failures in builds [5655111] 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-nightly Disk Page Compressions https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_DiskPageCompressions?branch=%3Cdefault%3E No changes in the build - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 17:26:17 10-10-2020
Re: [DISCUSS] Remove a Patch-file contribution approach from guides
Agree, need to update сб, 10 окт. 2020 г., 15:35 Ivan Pavlukhin : > Folks, > > A new contributor Bojidar tried to used a Patch-file contribution > approach [1]. The approach is stated in our guides [2]. I suppose that > the approach is obsolete. I several threads seem to confirm it [3, 4]. > > If nobody objects I will remove a section [2] from the guide. > > [1] > http://apache-ignite-developers.2346864.n4.nabble.com/Introduction-td49570.html > [2] > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-2.CreateaPatch-file > [3] > http://apache-ignite-developers.2346864.n4.nabble.com/ci-ignite-apache-Run-all-for-patch-jira-number-td24861.html > [4] > http://apache-ignite-developers.2346864.n4.nabble.com/Disabling-patch-validation-mechanism-on-TC-td5400.html > > -- > > Best regards, > Ivan Pavlukhin >
[DISCUSS] Remove a Patch-file contribution approach from guides
Folks, A new contributor Bojidar tried to used a Patch-file contribution approach [1]. The approach is stated in our guides [2]. I suppose that the approach is obsolete. I several threads seem to confirm it [3, 4]. If nobody objects I will remove a section [2] from the guide. [1] http://apache-ignite-developers.2346864.n4.nabble.com/Introduction-td49570.html [2] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-2.CreateaPatch-file [3] http://apache-ignite-developers.2346864.n4.nabble.com/ci-ignite-apache-Run-all-for-patch-jira-number-td24861.html [4] http://apache-ignite-developers.2346864.n4.nabble.com/Disabling-patch-validation-mechanism-on-TC-td5400.html -- Best regards, Ivan Pavlukhin
