Apache Ignite 2.8 RELEASE [Time, Scope, Manager]
Maxim, performance fix issue [1] already in master, if no objections, can u merge it into 2.8 ? Thanks ! [1] https://issues.apache.org/jira/browse/IGNITE-12547 >Igniters, > > >Here is the actual list of BLOCKER release issues: > >IGNITE-12456 Cluster Data Store grid gets Corrupted for Load test >*[Unassigned]* OPEN >IGNITE-12489 Error during purges by expiration: Unknown page type* >[Unassigned]* OPEN >IGNITE-8641 SpringDataExample should use example-ignite.xml config >*[Unassigned]* OPEN > >IGNITE-12398 Apache Ignite Cluster(Amazon S3 Based Discovery) Nodes getting >down [Emmanouil Gkatziouras] OPEN >IGNITE-9184 Cluster hangs during concurrent node client and server nodes >restart [Dmitriy Sorokin] IN PROGRESS >IGNITE-12553 [IEP-35] public Java metric API Improvement [Nikolay Izhikov] >Blocker IN PROGRESS > >IGNITE-12227 Default auto-adjust baseline enabled flag calculated >incorrectly [Anton Kalashnikov] PATCH AVAILABLE >IGNITE-12470 Pme-free switch feature should be deactivatable [Sergei >Ryzhov] PATCH AVAILABLE >IGNITE-12552 [IEP-35] Expose MetricRegistry to the public API Improvement >[Nikolay Izhikov] PATCH AVAILABLE > > >[1] https://issues.apache.org/jira/browse/IGNITE-12456 >[2] https://issues.apache.org/jira/browse/IGNITE-12489 >[3] https://issues.apache.org/jira/browse/IGNITE-8641 >[8] https://issues.apache.org/jira/browse/IGNITE-12398 >[3] https://issues.apache.org/jira/browse/IGNITE-9184 >[6] https://issues.apache.org/jira/browse/IGNITE-12553 >[7] https://issues.apache.org/jira/browse/IGNITE-12227 >[9] https://issues.apache.org/jira/browse/IGNITE-12470 >[5] https://issues.apache.org/jira/browse/IGNITE-12552 > > >On Sat, 18 Jan 2020 at 19:11, Sergey Antonov < antonovserge...@gmail.com > >wrote: > >> Maxim, >> >> Conflicts in pr [1] are resolved. TC Run all is started. >> >> [1] https://github.com/apache/ignite/pull/7238 >> >> пт, 17 янв. 2020 г. в 16:04, Sergey Antonov < antonovserge...@gmail.com >: >> >>> Maxim, >>> >>> I will do that on monday (20/01). >>> >>> пт, 17 янв. 2020 г. в 13:08, Maxim Muzafarov < mmu...@apache.org >: >>> Sergey, Can you, please, resolve the PR conflicts [1] [2]? [1] https://github.com/apache/ignite/pull/7238 [2] https://issues.apache.org/jira/browse/IGNITE-11256 On Thu, 16 Jan 2020 at 16:59, Ilya Kasnacheev < ilya.kasnach...@gmail.com > wrote: > > Hello! > > I have bumped beanutils and re-ran Cassandra Store tests. Can you please > comment on the ticket? > > I think that fixing ZooKeeper is too much effort (there's chaos with > jackson vs. jackson-asl), maybe it should be split up as a separate ticket > to be done later. > > Regards, > -- > Ilya Kasnacheev > > > ср, 15 янв. 2020 г. в 18:31, Vladimir Pligin < vova199...@yandex.ru >: > > > Thanks, Ilya. It would be really great to have your patch included into 2.8 > > scope. > > I'd like to give my two cent as well. For example we have vulnerable > > dependencies here: > > modules/cassandra/store/pom.xml - commons-beanutils > > modules/zookeeper/pom.xml - transitive Jackson from Curator > > > > I'd suggest to uprgrade commons-beanutils:commons-beanutils to 1.9.4 and > > override com.fasterxml.jackson.core:jackson-databind to our common jackson > > version from other modules. > > > > > > > > -- > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > >>> >>> >>> -- >>> BR, Sergey Antonov >>> >> >> >> -- >> BR, Sergey Antonov >>
Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]
Igniters, Here is the actual list of BLOCKER release issues: IGNITE-12456 Cluster Data Store grid gets Corrupted for Load test *[Unassigned]* OPEN IGNITE-12489 Error during purges by expiration: Unknown page type* [Unassigned]* OPEN IGNITE-8641 SpringDataExample should use example-ignite.xml config *[Unassigned]* OPEN IGNITE-12398 Apache Ignite Cluster(Amazon S3 Based Discovery) Nodes getting down [Emmanouil Gkatziouras] OPEN IGNITE-9184 Cluster hangs during concurrent node client and server nodes restart [Dmitriy Sorokin] IN PROGRESS IGNITE-12553 [IEP-35] public Java metric API Improvement [Nikolay Izhikov] Blocker IN PROGRESS IGNITE-12227 Default auto-adjust baseline enabled flag calculated incorrectly [Anton Kalashnikov] PATCH AVAILABLE IGNITE-12470 Pme-free switch feature should be deactivatable [Sergei Ryzhov] PATCH AVAILABLE IGNITE-12552 [IEP-35] Expose MetricRegistry to the public API Improvement [Nikolay Izhikov] PATCH AVAILABLE [1] https://issues.apache.org/jira/browse/IGNITE-12456 [2] https://issues.apache.org/jira/browse/IGNITE-12489 [3] https://issues.apache.org/jira/browse/IGNITE-8641 [8] https://issues.apache.org/jira/browse/IGNITE-12398 [3] https://issues.apache.org/jira/browse/IGNITE-9184 [6] https://issues.apache.org/jira/browse/IGNITE-12553 [7] https://issues.apache.org/jira/browse/IGNITE-12227 [9] https://issues.apache.org/jira/browse/IGNITE-12470 [5] https://issues.apache.org/jira/browse/IGNITE-12552 On Sat, 18 Jan 2020 at 19:11, Sergey Antonov wrote: > Maxim, > > Conflicts in pr [1] are resolved. TC Run all is started. > > [1] https://github.com/apache/ignite/pull/7238 > > пт, 17 янв. 2020 г. в 16:04, Sergey Antonov : > >> Maxim, >> >> I will do that on monday (20/01). >> >> пт, 17 янв. 2020 г. в 13:08, Maxim Muzafarov : >> >>> Sergey, >>> >>> >>> Can you, please, resolve the PR conflicts [1] [2]? >>> >>> [1] https://github.com/apache/ignite/pull/7238 >>> [2] https://issues.apache.org/jira/browse/IGNITE-11256 >>> >>> On Thu, 16 Jan 2020 at 16:59, Ilya Kasnacheev >>> wrote: >>> > >>> > Hello! >>> > >>> > I have bumped beanutils and re-ran Cassandra Store tests. Can you >>> please >>> > comment on the ticket? >>> > >>> > I think that fixing ZooKeeper is too much effort (there's chaos with >>> > jackson vs. jackson-asl), maybe it should be split up as a separate >>> ticket >>> > to be done later. >>> > >>> > Regards, >>> > -- >>> > Ilya Kasnacheev >>> > >>> > >>> > ср, 15 янв. 2020 г. в 18:31, Vladimir Pligin : >>> > >>> > > Thanks, Ilya. It would be really great to have your patch included >>> into 2.8 >>> > > scope. >>> > > I'd like to give my two cent as well. For example we have vulnerable >>> > > dependencies here: >>> > > modules/cassandra/store/pom.xml - commons-beanutils >>> > > modules/zookeeper/pom.xml - transitive Jackson from Curator >>> > > >>> > > I'd suggest to uprgrade commons-beanutils:commons-beanutils to 1.9.4 >>> and >>> > > override com.fasterxml.jackson.core:jackson-databind to our common >>> jackson >>> > > version from other modules. >>> > > >>> > > >>> > > >>> > > -- >>> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >>> > > >>> >> >> >> -- >> BR, Sergey Antonov >> > > > -- > BR, Sergey Antonov >
Re: Please a reviewer for the case IGNITE-12518
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 processes of a customer. In first instance my team worked with rest-http module in ignite 2.4 with poor results, the quantity of TPS was 4.Then we make a implementation of Rest service inside Apache Tomcat and call to Apache Ignite directly to Database with persistence activated. This change, enabled the possibility for work with 4 environment of the customer (Development, Testing, QA, Production) with 8GB of RAM in the machine, the configuration of the client had a Oracle Portal for the View layer, EJB for composition of the controller layer, and OSB for the integration the TPS of the client are biggest. *AS-IS* [image: imagen.png] *To Be roadmap* [image: imagen.png] With the ignite modification published in Jira is possible run JSF for run my reports and forms, JaxWS for the service SOAP and Jersey for Rest (i start modification in this task). The code published in Jira have capabilites for work with Primefaces (tested ok), JaxWS (tested ok), but jersey is not included yet. 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 jue., 16 ene. 2020 a las 0:25, Saikat Maitra () escribió: > Hi Luis, > > Thank you for sharing the details on the changes. I reviewed the > dependencies that you shared in the jira issue and wanted to discuss on the > changes. > > The purpose of ignite-rest-http is to provide a web based interface to > easily access and use the ignite features and the changes you suggested can > be built as part of separate application and ignite-rest-http can be used > as an add on dependency. This will help keep ignite-rest-http module as > minimal and thin as possible. > > Please review and share your thoughts. > > Regards, > Saikat > > > > > > > > > On Mon, Jan 13, 2020 at 7:24 PM Luis Arce wrote: > > > Hi Saikat, > > I add information for evidence for the changes of ignite rest-http > module. > > > > 1. Can you please share more information on the issue that will be > resolved > > with this change? > > R: This change add the possibility for publish war files with webpages > in > > JSF or webservices JaxWS inside of the jetty server embedded. > > When the WAR file is loade automatically attached the JNDI for lockup to > > Ignite DataBase to the context of the page. > > (I have a mvc4 application with ignite as a backend, with it change i > dont > > need a primary web server). > > > > [image: imagen.png] > > > > [image: imagen.png] > > > > My webpage > > [image: imagen.png] > > > > My mvc4 > > [image: imagen.png] > > > > The WebService > > > > [image: imagen.png] > > The WSDL > > [image: imagen.png] > > > > SoapUI > > [image: imagen.png] > > > > TestSuite SoapUI > > [image: imagen.png] > > > > > > > > > > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión > > 09-57861903 > > Linkedin: > > https://cl.linkedin.com/in/luisalejandroarcemartinez > > > > > > > > > > > > El dom., 12 ene. 2020 a las 14:43, Saikat Maitra (< > saikat.mai...@gmail.com>) > > escribió: > > > >> Hi Luis, > >> > >> 1. Can you please share more information on the issue that will be > >> resolved > >> with this change? > >> 2. To accommodate the change, would you be able to raise a PR please. > >> Please take a look into the PR process > >> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > >> 3. Can you please add tests and execute the related testsuite in > teamcity > >> https://ci.ignite.apache.org/ > >> > >> Regards, > >> Saikat > >> > >> On Fri, Jan 10, 2020 at 5:39 PM Luis Arce wrote: > >> > >> > Dear community, > >> > > >> > I made modifications to the module rest-http. > >> > It works correctly. > >> > Is possible if anybody take my case for the review? > >> > > >> > The modifications are: > >> > Support for webpages (test with jsf and primefaces), support for root > >> > context. > >> > Support to JaxWS with RI version. > >> > Support for access to Ignite database with JNDI and basic connection > >> > pooling' > >> > > >> > Se despide Atentamente, > >> > > >> > > >> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión > >> > 09-57861903 > >> > Linkedin: > >> > https://cl.linkedin.com/in/luisalejandroarcemartinez > >> > > >> > > >
Re: AWS EBS Discovery: Contributor Wanted
Hi all! I have spinned up an Application Load Balancer and an autoscaling group on AWS and the Ignite discovery using TcpDiscoveryAlbIpFinder works as expected. - On startup nodes discover each other. - On ec2 node down, connection is lost and the cluster decreases. - On an extra node addition the cluster size increases This contribution is essential since the Previous ELB based discovery uses the Classic Load Balancer which is still available however AWS advices users to use the Application one. [1] While my pull request gets reviewed I will also have a look at the IGNITE-12398 [2] issue which has to do with the S3 discovery. Another idea would also be to implement a `TCP Load Balancer based` discovery. In order to test this issue and future ones I implemented some terraform scripts (which I shall use for other issues too) [3]. If some automated e2e testing on AWS is being considered they might be of value. I can help on implementing those tests by provisioning the infrastructure in an automated way and validate the discovery. [1] https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/migrate-to-application-load-balancer.html [2] https://issues.apache.org/jira/browse/IGNITE-12398 [3] https://github.com/gkatzioura/ignite-aws-deploy Kind regards, *Emmanouil Gkatziouras* https://egkatzioura.com/ | https://www.linkedin.com/in/gkatziourasemmanouil/ https://github.com/gkatzioura On Tue, 14 Jan 2020 at 22:22, Denis Magda wrote: > Hi Emmanouil, > > Agree, let's check that the IP finder functions normally in the cloud > environment and the mock tests can be used for regular testing on Team > City. That's the way we tested other environment-specific IP finders > including the Kubernetes one. > > Let us know once the IP finder is tested on AWS and then we can proceed > with the review. > > - > Denis > > > On Tue, Jan 14, 2020 at 2:47 AM Emmanouil Gkatziouras < > gkatzio...@gmail.com> > wrote: > > > Hi all! > > > > With regards to the `Node Discovery Using AWS Application ELB` issue [1] > > I made this pull request to fix the merge conflicts [2]. > > Will also check if the concerns described on the mailing list topic > > `Volunteer needed: AWS Elastic Load Balancer IP Finders implemented` are > > addressed [3] > > Since I did not test it on an AWS infrastructure the next step would be > to > > spin up some AWS resources and test it. > > By doing so it will help me on checking the Amazon S3 Based Discovery > issue > > [4] . > > I will try to make the deployment as infrastructure as code, and see if > > this can be of value for the ignite project and testing. > > > > Kind regards, > > Emmanouil > > > > [1] https://issues.apache.org/jira/browse/IGNITE-8617 > > [2] https://github.com/apache/ignite/pull/7247 > > [3] > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/Volunteer-needed-AWS-Elastic-Load-Balancer-IP-Finders-implemented-td33847.html#a39793 > > [4] https://issues.apache.org/jira/browse/IGNITE-12398 > > > > > > > >
