Re: Extensions section on the downloads page

[Valentin Kulichenko]

Agree. I brought the section back because there was a broken link, and I
believe I removed it earlier by mistake. We definitely should add more
details though.

-Val

On Wed, May 12, 2021 at 9:20 AM Dmitry Pavlov  wrote:

> Hi Denis,
>
> +1 from my side.
>
> Now extensions in the download page looks like a bit incomplete snippet of
> code.
>
> It is better than nothing, but completed table would look better.
>
> Sincerely,
> Dmitriy Pavlov
>
> On 2021/05/12 14:02:04, Denis Magda  wrote:
> > Igniters, Val,
> >
> > I came across the Extensions section that was restored on the downloads
> > page. It looks clumsy, broken, and incomplete. We're listing spring boot
> > artifacts without any reference to other modules:
> > https://ignite.apache.org/download.cgi#extensions
> >
> > How about:
> >
> >- Removing the code snippets of the Spring Boot extensions
> >- Add a paragraph and a list with references to all the extensions we
> >have documented on our pages. See extensions and integrations section:
> >https://ignite.apache.org/docs/latest/
> >
> > @Igor Gusev , @Nikita Safonov
> >  could
> > you also join this thread?
> >
> > -
> > Denis
> >
>

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

[dpavlov . tasks]

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 RDD 
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Rdd?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 21:55:23 12-05-2021 

Re: Extensions section on the downloads page

[Dmitry Pavlov]

Hi Denis,

+1 from my side. 

Now extensions in the download page looks like a bit incomplete snippet of code.

It is better than nothing, but completed table would look better.

Sincerely,
Dmitriy Pavlov

On 2021/05/12 14:02:04, Denis Magda  wrote: 
> Igniters, Val,
> 
> I came across the Extensions section that was restored on the downloads
> page. It looks clumsy, broken, and incomplete. We're listing spring boot
> artifacts without any reference to other modules:
> https://ignite.apache.org/download.cgi#extensions
> 
> How about:
> 
>- Removing the code snippets of the Spring Boot extensions
>- Add a paragraph and a list with references to all the extensions we
>have documented on our pages. See extensions and integrations section:
>https://ignite.apache.org/docs/latest/
> 
> @Igor Gusev , @Nikita Safonov
>  could
> you also join this thread?
> 
> -
> Denis
> 

Re: Thin Clients: enable partition awareness by default

[Dmitry Pavlov]

+1 

Without awareneess, on the contrary, we can get huge memory utilization on one 
server node. 
With awareness we're more scalable on that matter. 

Sincerely,
Dmitriy Pavlov

On 2021/05/12 15:39:53, Igor Sapego  wrote: 
> +1 from me. There were no major issues with this feature and it gives
> good performance boost for many cases.
> 
> Best Regards,
> Igor
> 
> 
> On Wed, May 12, 2021 at 5:18 PM Ivan Daschinsky  wrote:
> 
> > Huge +1 from me. PA should be enabled by default.
> >
> > ср, 12 мая 2021 г. в 13:33, Pavel Tupitsyn :
> > >
> > > Igniters,
> > >
> > > Partition Awareness (PA) is implemented in 5 out of 6 thin clients [1].
> > >
> > > However, this feature is disabled by default in most clients for
> > > compatibility reasons:
> > > initially we only used one connection to the cluster, but with PA enabled
> > > we establish
> > > connections to every server node, which may be not desirable in some use
> > > cases.
> > >
> > > I expect those scenarios to be rare, and in most cases it makes sense to
> > > enable PA by default.
> > > Thoughts, objections?
> > >
> > >
> > > [1]
> > https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features
> >
> >
> >
> > --
> > Sincerely yours, Ivan Daschinskiy
> >
> 

Re: Thin Clients: enable partition awareness by default

[Igor Sapego]

+1 from me. There were no major issues with this feature and it gives
good performance boost for many cases.

Best Regards,
Igor


On Wed, May 12, 2021 at 5:18 PM Ivan Daschinsky  wrote:

> Huge +1 from me. PA should be enabled by default.
>
> ср, 12 мая 2021 г. в 13:33, Pavel Tupitsyn :
> >
> > Igniters,
> >
> > Partition Awareness (PA) is implemented in 5 out of 6 thin clients [1].
> >
> > However, this feature is disabled by default in most clients for
> > compatibility reasons:
> > initially we only used one connection to the cluster, but with PA enabled
> > we establish
> > connections to every server node, which may be not desirable in some use
> > cases.
> >
> > I expect those scenarios to be rare, and in most cases it makes sense to
> > enable PA by default.
> > Thoughts, objections?
> >
> >
> > [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features
>
>
>
> --
> Sincerely yours, Ivan Daschinskiy
>

[VOTE][EXTENSION] Release Apache Ignite spring-data-all-ext extensions 1.0.0 RC3

[Nikita Amelchev]

Dear Ignite Community,

I have uploaded a release candidate of the following extension modules:

spring-data-commons
spring-data-ext
spring-data-2.0-ext
spring-data-2.2-ext

The release candidate of the extensions:

spring-data-commons
https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-data-commons/1.0.0-rc3/

spring-data-ext
https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-data-ext/1.0.0-rc3/

spring-data-2.0-ext
https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-data-2.0-ext/1.0.0-rc3/

spring-data-2.2-ext
https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-data-2.2-ext/1.0.0-rc3/

The instruction for building from the source package is placed in the
DEVNOTES file.

The following staging can be used for testing:
https://repository.apache.org/content/repositories/orgapacheignite-1515

Tags were created:

ignite-spring-data-commons-1.0.0-rc3
ignite-spring-data-ext-1.0.0-rc3
ignite-spring-data-2.2-ext-1.0.0-rc3
ignite-spring-data-2.0-ext-1.0.0-rc3
ignite-spring-data-all-ext-1.0.0-rc3
https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=cfec73eeca94a675167751409e3203ce516c3b39

RELEASE NOTES:
https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=blob;f=RELEASE_NOTES.txt;h=22f8d665c194ba2dfa6167354d97ad53d5ef206f;hb=c8de80ee14d1fb76d6cbb0b18513bb70b499c3cb

DOCUMENTATION:
Documentation of listed extensions was updated in the following issues:
https://issues.apache.org/jira/issues/?filter=-1&jql=key%20in%20(IGNITE-14662%2CIGNITE-14398%2CIGNITE-14493)

The vote is formal, see voting guidelines
https://www.apache.org/foundation/voting.html

+1 - to accept all the Apache Ignite spring-data-all-ext extensions
1.0.0-rc3 listed in the thread
0 - don't care either way
-1 - DO NOT accept either of the Apache Ignite spring-data-all-ext
extensions 1.0.0-rc3 (explain why)

The vote will hold for 5 days and will end on May 17 2021 18:00 UTC
https://www.timeanddate.com/countdown/generic?iso=20210517T18&p0=0&font=cursive

-- 
Best wishes,
Amelchev Nikita

[VOTE][EXTENSION] Release Apache Ignite performance-statistics-ext extension 1.0.0 RC3

[Nikita Amelchev]

Dear Ignite Community,

I have uploaded a release candidate of the performance-statistics-ext
extension module.

The release candidate of the performance-statistics-ext extension:
https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-performance-statistics-ext/1.0.0-rc3/

The instruction for building from the source package is placed in the
DEVNOTES file.

The following staging can be used for testing:
https://repository.apache.org/content/repositories/orgapacheignite-1514

Tag was created:

ignite-performance-statistics-ext-1.0.0-rc3
https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=refs/tags/ignite-performance-statistics-ext-1.0.0-rc3

RELEASE NOTES:
https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=blob;f=RELEASE_NOTES.txt;h=22f8d665c194ba2dfa6167354d97ad53d5ef206f;hb=c8de80ee14d1fb76d6cbb0b18513bb70b499c3cb

DOCUMENTATION:
Documentation of extension was updated in the issue:
https://issues.apache.org/jira/browse/IGNITE-14417

The vote is formal, see voting guidelines
https://www.apache.org/foundation/voting.html

+1 - to accept the Apache Ignite performance-statistics-ext extension 1.0.0-rc3
0 - don't care either way
-1 - DO NOT accept the Apache Ignite performance-statistics-ext
extension 1.0.0-rc3 (explain why)

The vote will hold for 5 days and will end on May 17 2021 18:00 UTC
https://www.timeanddate.com/countdown/generic?iso=20210517T18&p0=0&font=cursive

-- 
Best wishes,
Amelchev Nikita

Re: Thin Clients: enable partition awareness by default

[Ivan Daschinsky]

Huge +1 from me. PA should be enabled by default.

ср, 12 мая 2021 г. в 13:33, Pavel Tupitsyn :
>
> Igniters,
>
> Partition Awareness (PA) is implemented in 5 out of 6 thin clients [1].
>
> However, this feature is disabled by default in most clients for
> compatibility reasons:
> initially we only used one connection to the cluster, but with PA enabled
> we establish
> connections to every server node, which may be not desirable in some use
> cases.
>
> I expect those scenarios to be rare, and in most cases it makes sense to
> enable PA by default.
> Thoughts, objections?
>
>
> [1] https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features



-- 
Sincerely yours, Ivan Daschinskiy

Extensions section on the downloads page

[Denis Magda]

Igniters, Val,

I came across the Extensions section that was restored on the downloads
page. It looks clumsy, broken, and incomplete. We're listing spring boot
artifacts without any reference to other modules:
https://ignite.apache.org/download.cgi#extensions

How about:

   - Removing the code snippets of the Spring Boot extensions
   - Add a paragraph and a list with references to all the extensions we
   have documented on our pages. See extensions and integrations section:
   https://ignite.apache.org/docs/latest/

@Igor Gusev , @Nikita Safonov
 could
you also join this thread?

-
Denis

Re: Greetings

[Ivan Pavlukhin]

Hi Ilya,

Welcome to Apache Ignite Community!

I added your account to contributors list in JIRA. Now you can assign
ticket to yourself.

2021-05-12 16:29 GMT+03:00, Ilya Korol :
> Hello Ignite Community!
>
> My name isIlya Korol. I want to contribute to Apache Ignite. My JIRA
> username*Korol*.
>
> Thanks!
>
>


-- 

Best regards,
Ivan Pavlukhin

Greetings

[Ilya Korol]

Hello Ignite Community!

My name isIlya Korol. I want to contribute to Apache Ignite. My JIRA 
username*Korol*.


Thanks!

Re: Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Configuraton

[Eduard Rakhmankulov]

Hi!

I propose to add a new MBean linked to DMS that contains the property
IGNITE_PDS_WAL_REBALANCE_THRESHOLD.
That enables configuration through JMX.

WDYT?


On Tue, 11 May 2021 at 16:52, Eduard Rakhmankulov 
wrote:

> Hi Stanislav,
>
> I think this is an excellent idea to use distributed metastore.
>
> Should I leave system property for backward compatibility?
>
>
> On Sun, 9 May 2021 at 19:04, Atri Sharma  wrote:
>
>> +1
>>
>> On Sun, 9 May 2021, 21:33 Stanislav Lukyanov, 
>> wrote:
>>
>> > Hi Eduard,
>> >
>> > I strongly believe that if a configuration option is cluster wide then
>> it
>> > belongs to distributed metastore and not to IgniteConfiguration.
>> > This allows to get cluster-wide consistency guarantees and API for
>> dynamic
>> > change out of the box (need to teach the internals to re-read the
>> property
>> > from DMS every time of course).
>> >
>> > WDYT?
>> >
>> > Stan
>> >
>> > > On 6 May 2021, at 16:35, Eduard Rakhmankulov 
>> > wrote:
>> > >
>> > > Some addition.
>> > >
>> > > I want to add configuration to
>> > >
>> >
>> org.apache.ignite.configuration.DataStorageConfiguration#getDefaultWarmUpConfiguration#getP
>> > > artitionWalRebalanceThreshold
>> > > which will have same semantics as system property (number of entries
>> in
>> > WAL
>> > > to trigger rebalance).
>> > >
>> > > On Thu, 6 May 2021 at 15:50, Eduard Rakhmankulov > >
>> > > wrote:
>> > >
>> > >> Hello, Igniters!
>> > >>
>> > >> I suggest changing IGNITE_PDS_WAL_REBALANCE_THRESHOLD from system
>> > >> properties to IgniteConfiguration.
>> > >> This configuration is effectively cluster-wide (because only the
>> > >> coordinator's configuration matters when the heuristic with this
>> > property
>> > >> applies).
>> > >>
>> > >> It is easier to validate that we have the same configuration on all
>> > nodes
>> > >> than system property (in the case when another coordinator was
>> elected).
>> > >>
>> > >> --
>> > >> Best regards, Eduard.
>> > >>
>> > >
>> > >
>> > > --
>> > > С уважением, Рахманкулов Э.Р.
>> >
>> >
>>
>
>
> --
> С уважением, Рахманкулов Э.Р.
>


-- 
Best regards, Eduard.

Thin Clients: enable partition awareness by default

[Pavel Tupitsyn]

Igniters,

Partition Awareness (PA) is implemented in 5 out of 6 thin clients [1].

However, this feature is disabled by default in most clients for
compatibility reasons:
initially we only used one connection to the cluster, but with PA enabled
we establish
connections to every server node, which may be not desirable in some use
cases.

I expect those scenarios to be rare, and in most cases it makes sense to
enable PA by default.
Thoughts, objections?


[1] https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features

Re: Issue building Ignite 2.10 branch

[Ivan Pavlukhin]

Hi Raymond,

Following comes to my mind as a workaround. If you need to build only
kubernetes module you can specify it directly with mvn command
arguments.

mvn clean install -Pall-java,all-scala,licenses -DskipTests -pl
modules/kubernetes -am

Or possibly exclude only jta module from build.

mvn clean install -Pall-java,all-scala,licenses -DskipTests -pl '!modules/jta'

2021-05-12 4:29 GMT+03:00, Raymond Wilson :
> Hi Vishwas,
>
> I added the following to my global Maven settings.xml file in the .m2
> folder:
>
> 
> http://maven.apache.org/SETTINGS/1.0.0";
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
> http://maven.apache.org/xsd/settings-1.0.0.xsd";>
>
> 
>
>  myprofile
>  
>
>  my-repo2
>  your custom repo
>  https://repository.ow2.org/nexus/content/repositories/public/
> 
>
>  
>
>  
> 
>
> I get the same result on running the "mvn clean install
> -Pall-java,all-scala,licenses -DskipTests" command line:
>
> [ERROR] Failed to execute goal on project ignite-jta: Could not resolve
> dependencies for project org.apache.ignite:ignite-jta:jar:2.10.0: Failed to
> collect dependencies at org.ow2.jotm:jotm-core:jar:2.2.3 ->
> org.ow2.carol:carol:jar:3.0.8 ->
> org.jacorb:jacorb:jar:2.2.3-jonas-patch-20071018: Failed to read artifact
> descriptor for org.jacorb:jacorb:jar:2.2.3-jonas-patch-20071018: Could not
> transfer artifact org.jacorb:jacorb:pom:2.2.3-jonas-patch-20071018 from/to
> maven-default-http-blocker (http://0.0.0.0/): transfer failed for
> http://0.0.0.0/org/jacorb/jacorb/2.2.3-jonas-patch-20071018/jacorb-2.2.3-jonas-patch-20071018.pom:
> Connect to 0.0.0.0:80 [/0.0.0.0] failed: Connection refused: connect ->
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :ignite-jta
>
> Raymond.
>
> On Wed, May 12, 2021 at 12:50 PM Vishwas Bm  wrote:
>
>> Hi Raymond,
>>
>> This is an issue related to repository configuration in settings.xml.
>>
>> You can find more information in below thread
>>
>> http://apache-ignite-developers.2346864.n4.nabble.com/Building-Ignite-with-Adopt-OpenJDK-11-td52389.html#a52391
>>
>>
>>
>> Regards,
>> Vishwas
>>
>> On Wed, 12 May, 2021, 05:17 Raymond Wilson, 
>> wrote:
>>
>> > Hi,
>> >
>> > I have made a small modification to the ignite-kubernetes module to
>> > allow
>> > specification of a port for the IP finder.
>> >
>> > To build Ignite, I am using this comment from DEVNOTES.TXT:
>> >
>> > mvn clean install -am -Pall-java,all-scala,licenses -DskipTests
>> >
>> > This ultimately fails with the following error:
>> >
>> > [ERROR] Failed to execute goal on project ignite-jta: Could not resolve
>> > dependencies for project org.apache.ignite:ignite-jta:jar:2.10.0:
>> > Failed
>> to
>> > collect dependencies at org.ow2.jotm:jotm-core:jar:2.2.3 ->
>> > org.ow2.carol:carol:jar:3.0.8 ->
>> > org.jacorb:jacorb:jar:2.2.3-jonas-patch-20071018: Failed to read
>> > artifact
>> > descriptor for org.jacorb:jacorb:jar:2.2.3-jonas-patch-20071018: Could
>> not
>> > transfer artifact org.jacorb:jacorb:pom:2.2.3-jonas-patch-20071018
>> from/to
>> > maven-default-http-blocker (http://0.0.0.0/): transfer failed for
>> >
>> >
>> http://0.0.0.0/org/jacorb/jacorb/2.2.3-jonas-patch-20071018/jacorb-2.2.3-jonas-patch-20071018.pom
>> > :
>> > Connect to 0.0.0.0:80 [/0.0.0.0] failed: Connection refused: connect ->
>> > [Help 1]
>> > [ERROR]
>> > [ERROR] To see the full stack trace of the errors, re-run Maven with
>> > the
>> -e
>> > switch.
>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> > [ERROR]
>> > [ERROR] For more information about the errors and possible solutions,
>> > please read the following articles:
>> > [ERROR] [Help 1]
>> >
>> >
>> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
>> > [ERROR]
>> > [ERROR] After correcting the problems, you can resume the build with
>> > the
>> > command
>> > [ERROR]   mvn  -rf :ignite-jta
>> >
>> > I found some release notes that indicated the Maven (as of 3.8.1) is no
>> > longer supporting HTTP addresses for dependencies. I downgraded to
>> > Maven
>> > 3.8.0 with no change to the result.
>> >
>> > Is there an easy work around for this?
>> >
>> > Thanks,
>> > Raymond.
>> >
>> >
>> > --
>> > 
>> > Raymond Wilson
>> > Trimble Distinguished Engineer, Civil Construction Software (CCS)
>> > 11 Birmingham Drive | Christchurch, New Zealand
>> > raymond_wil...@trimble.com