[GitHub] ignite pull request #5328: Remove direct threadID call

[dgovorukhin]

GitHub user dgovorukhin opened a pull request:

https://github.com/apache/ignite/pull/5328

Remove direct threadID call



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dgovorukhin/ignite master-remove-threadId

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5328.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5328


commit 526de89b3ceebdef2592dbdc0c0ae293cfd83921
Author: Dmitriy Govorukhin 
Date:   2018-11-06T23:41:25Z

- replace direct Thread.currentThread().getId() to static call
- custom threadLocal

Signed-off-by: Dmitriy Govorukhin 

commit ffdd73d835e2e4b9fe2c3df123c9a2feacb00ab8
Author: Dmitriy Govorukhin 
Date:   2018-11-06T23:44:45Z

fix stackOverFlow + test cleanup

Signed-off-by: Dmitriy Govorukhin 




---

[GitHub] ignite pull request #5327: IGNITE-10085 Compressed files were made more user...

[antonovsergey93]

GitHub user antonovsergey93 opened a pull request:

https://github.com/apache/ignite/pull/5327

IGNITE-10085 Compressed files were made more user friendly.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10085

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5327.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5327


commit 886f01fc6fffc0d445ec6b34eca8d4e3d6b944e7
Author: Sergey Antonov 
Date:   2018-11-06T19:21:13Z

IGNITE-10085 Compressed files were made more user friendly.




---

[GitHub] ignite pull request #5326: Test drive Junit4

[pavlukhin]

GitHub user pavlukhin opened a pull request:

https://github.com/apache/ignite/pull/5326

Test drive Junit4



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite junit4

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5326.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5326


commit c7c2fb4b4c85642461a8fcea0495c197a65c
Author: ipavlukhin 
Date:   2018-11-03T09:30:29Z

test drive junit4 adoption




---

[jira] [Created] (IGNITE-10152) Allow warming up data region before a node has joined

[Stanislav Lukyanov (JIRA)]

Stanislav Lukyanov created IGNITE-10152:
---

 Summary: Allow warming up data region before a node has joined
 Key: IGNITE-10152
 URL: https://issues.apache.org/jira/browse/IGNITE-10152
 Project: Ignite
  Issue Type: New Feature
Reporter: Stanislav Lukyanov


After a node with existing PDS joins the cluster its performance will be low 
for a while - until it loads all data into RAM. This is a feature of Ignite - 
cold restart - that allows nodes to start as fast as possible.
However, it would be good to also allow "hot restart" - a way to preload as 
much data into RAM as needed before the node has joined. Then the node will not 
slow the cluster down during its warm-up.

There are several recent improvements with similar goals:
- IGNITE-8873 added methods to preload data of a specific partition
- IGNITE-7196 and IGNITE-9420 moved data recovery to before node joins the 
cluster

Combining the above approaches we could have allow a user to trigger 
synchronous preloading right after the data recovery but before discovery 
starts up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #5081: IGNITE-9997

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/5081


---

[GitHub] ignite pull request #5230: IGNITE-10103: Fix IgnitePersistentStoreDataStruct...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/5230


---

[GitHub] ignite pull request #5317: IGNITE-10150: Fixed handling of non-existing cach...

[slukyano]

GitHub user slukyano opened a pull request:

https://github.com/apache/ignite/pull/5317

IGNITE-10150: Fixed handling of non-existing cache context in GridRed…

…uceQueryExecutor.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10150

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5317.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5317


commit eeffdd1503c38a6ab138c8b4c1fdffd427f33cba
Author: Stanislav Lukyanov 
Date:   2018-11-06T15:29:40Z

IGNITE-10150: Fixed handling of non-existing cache context in 
GridReduceQueryExecutor.




---

[GitHub] ignite pull request #5316: IGNITE-10151 Fix BinaryMarshallerSelfTest#testDef...

[ibessonov]

GitHub user ibessonov opened a pull request:

https://github.com/apache/ignite/pull/5316

IGNITE-10151 Fix BinaryMarshallerSelfTest#testDefaultMapping test



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10151

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5316.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5316


commit 11f0fddb3e21e0f62d8d9f111ed80d08830516b0
Author: ibessonov 
Date:   2018-11-06T15:51:40Z

IGNITE-10151 Fix of commented test.




---

Re: Time to remove automated messages from the devlist?

[Dmitriy Pavlov]

Petr, some manual digest, is probably not needed because Apache list allows
subscribing to digest. dev-digest-subsr...@ignite.apache.org if I remember
this correctly.

вт, 6 нояб. 2018 г. в 18:28, Petr Ivanov :

> Can be Jira notifications united in some kind of daily digest?
> Maybe we can add special filter (new tasks / updates during last 24 hours)
> with notification scheme?
>
>
> > On 6 Nov 2018, at 18:15, Dmitriy Pavlov  wrote:
> >
> > I should mention I disagree to remove JIRA issues as the first step. It
> > helps everyone to understand what other people are going to do in the
> > project.  You always can comment if it is not the best approach, find a
> > duplicate issue, and you may suggest help.
> >
> > PR notification is more or less duplicates JIRA (as 1 JIRA 1..* PR), so
> it
> > may be ok to move Git's messages to notificati...@ignite.apache.org
> > 
> >
> > But we should keep JIRA and test failures.
> >
> > вт, 6 нояб. 2018 г. в 17:49, Alexey Kuznetsov :
> >
> >> Hi!
> >>
> >> I have filter for e-mail from JIRA (very useful, I can quick search
> issue
> >> there without visiting JIRA).
> >>
> >> And I'm just deleting tons of e-mails from GitBox & about PRs.
> >>
> >> I don't know what for we need them?
> >>
> >> May by we try to move GitBox & PRs-related mails first and see how it
> goes?
> >>
> >> --
> >> Alexey Kuznetsov
> >>
>
>

Re: IGNITE-2.7. New Features

[Maxim Muzafarov]

Vladimir,

We have a major IgniteSet improvement `Separate cache for non-collocated
IgniteSet.` [1] which is not mentioned yet.
Should we also include it to the release notes?

[1] https://issues.apache.org/jira/browse/IGNITE-7823


On Tue, 6 Nov 2018 at 16:50 Vladimir Ozerov  wrote:

> Igniters,
>
> Any more comments on release notes?
>
> On Tue, Nov 6, 2018 at 9:01 AM Nikolay Izhikov 
> wrote:
>
> > Vladimir, Thank you so much for this list!
> >
> > пн, 5 нояб. 2018 г., 23:25 Vladimir Ozerov voze...@gridgain.com:
> >
> > > Igniters,
> > >
> > > I assembled information about new features I am aware of. Please find
> the
> > > list below and review it, so that we do not miss anything important.
> Note
> > > that normally we do not include information about every single fix or
> > minor
> > > feature, as it will make release notes too big. Instead, we strive to
> > keep
> > > only the most prominent features/fixes in release notes. Minor things
> are
> > > grouped into generic points such as "Stability and performance
> > > improvements". Also we typically try to place the most important
> features
> > > first, to catch user's attention as quickly as possible.
> > >
> > > Ignite:
> > > * Added experimental support for multi-version concurrency control with
> > > snapshot isolation
> > >   - available for both cache API and SQL
> > >   - use CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT to enable it
> > >   - not production ready, data consistency is not guaranteed in case of
> > > node failures
> > > * Implemented Transparent Data Encryption based on JKS certificates
> > > * Implemented Node.JS Thin Client
> > > * Implemented Python Thin Client
> > > * Implemented PHP Thin Client
> > > * Ignite start scripts now support Java 9 and higher
> > > * Added ability to set WAL history size in bytes
> > > * Added SslContextFactory.protocols and SslContextFactory.cipherSuites
> > > properties to control which SSL encryption algorithms can be used
> > > * Added JCache 1.1 compliance
> > > * Added IgniteCompute.withNoResultCache method with semantics similar
> to
> > > ComputeTaskNoResultCache annotation
> > > * Spring Data 2.0 is now supported in separate module
> > > 'ignite-spring-data_2.0'
> > > * Added monitoring of critical system workers
> > > * Added ability to provide custom implementations of ExceptionListener
> > for
> > > JmsStreamer
> > > * Ignite KafkaStreamer was upgraded to use new KafkaConsmer
> configuration
> > > * S3 IP Finder now supports subfolder usage instead of bucket root
> > > * Improved dynamic cache start speed
> > > * Improved checkpoint performance by decreasing mark duration.
> > > * Added ability to manage compression level for compressed WAL
> archives.
> > > * Added metrics for Entry Processor invocations.
> > > * Added JMX metrics: ClusterMetricsMXBean.getTotalBaselineNodes and
> > > ClusterMetricsMXBean.getActiveBaselineNodes
> > > * Node uptime metric now includes days count
> > > * Exposed info about thin client connections through JMX
> > > * Inrtoduced new system property IGNITE_REUSE_MEMORY_ON_DEACTIVATE to
> > > enable reuse of allocated memory on node deactivation (disabled by
> > default)
> > > * Optimistic transaction now will be properly rolled back if waiting
> too
> > > long for new topology on remap
> > > * ScanQuery with setLocal flag now checks if partition is actually
> > present
> > > on local node
> > > * Improved cluster behavior when left node does not cause partition
> > > affinity assignment changes
> > > * Interrupting user thread during partition initialization will no
> longer
> > > cause node to stop
> > > * Fixed problem when partition lost event were not triggered if
> multiple
> > > nodes left cluster
> > > * Fixed massive node drop from cluster on temporary network issues
> > > * Fixed service redeployment on cluster reactivation
> > > * Fixed client node stability under ZooKeeper discovery
> > > * Massive performance and stability improvements
> > >
> > > Ignite .Net:
> > > * Add .NET Core 2.1 support
> > > * Added thin client connection failover
> > >
> > > Ignite C++:
> > > * Implemented Thin Client with base cache operations
> > > * Implemented smart affinity routing for Thin Client to send requests
> > > directly to nodes containing data when possible
> > > * Added Clang compiler support
> > >
> > > SQL:
> > > * Added experimental support for fully ACID transactional SQL with
> > snapshot
> > > isolation:
> > >   - use CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT to enable it
> > >   - transaction can be started through native API (IgniteTransactions),
> > > thin JDBC driver or ODBC driver
> > >   - not production ready, data consistency is not guaranteed in case of
> > > node failures
> > > * Added a set of system views located in "IGNITE" schema to view
> cluster
> > > information (NODES, NODE_ATTRIBUTES, NODE_METRICS, BASELINE_NODES)
> > > * Added ability to create predefined SQL schemas
> > > * Added GROUP_CONCAT function support
> > > * Added string

[jira] [Created] (IGNITE-10151) Fix BinaryMarshallerSelfTest#testDefaultMapping test

[Ivan Bessonov (JIRA)]

Ivan Bessonov created IGNITE-10151:
--

 Summary: Fix BinaryMarshallerSelfTest#testDefaultMapping test
 Key: IGNITE-10151
 URL: https://issues.apache.org/jira/browse/IGNITE-10151
 Project: Ignite
  Issue Type: Improvement
Reporter: Ivan Bessonov
Assignee: Ivan Bessonov


BinaryMarshallerSelfTest#testDefaultMapping:
reflectively refers method {{BinaryContext.typeName}} that was removed per 
IGNITE-2191 in [commit 
40f9a8d|https://github.com/apache/ignite/commit/62502b2c44d7d35584b31c8f1284b810840f9a8d]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ololo3000 opened a new pull request #60: IGNITE-10146 Refresh missing from Git prs while full reindex

[GitBox]

ololo3000 opened a new pull request #60: IGNITE-10146 Refresh missing from Git 
prs while full reindex
URL: https://github.com/apache/ignite-teamcity-bot/pull/60
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Apache Ignite 2.7. Last Mile

[Igor Sapego]

Guys,

I've found the following issue: [1]. It is quite local (only affects
Ignite C++ Linux build system) but quite critical too. I think it
should be included in 2.7.

What do you think?

[1] - https://issues.apache.org/jira/browse/IGNITE-10147

Best Regards,
Igor


On Tue, Oct 30, 2018 at 4:35 PM Вячеслав Коптилин 
wrote:

> Hello Nikolay, Igniters,
>
> It seems that we lost the following commit that should be included in
> 'ignite-2.7' branch
> (It looks like the change was not accidentally cherry-picked from 'master'
> to 'ignite-2.7')
>  -
>
> https://github.com/apache/ignite/commit/6e0ff06f8e309657a16c94da605348d9c3b804ad
>
> The most important part is the change introduced into GridDhtAtomicCache,
> the fix prevents NullPointerException during cache updates under some
> circumstances.
> So, I propose including the fix into ignite-2.7, at least the change of
> GridDhtAtomicCache.
>
> Thanks,
> Slava.
>
> пн, 29 окт. 2018 г. в 11:20, Nikolay Izhikov :
>
> > Hello, guys.
> >
> > For today we have 11 tickets mapped to 2.7
> >
> > IGNITE-10010 Alexey Goncharuk Node halted if second node was stopped,
> then
> > cache destroyed, then second node returned
> > IGNITE-10015 Alexey Goncharuk Sporadic JVM crash due to restart nodes
> > IGNITE-10013 Unassigned Node restart may lead to NPE in
> > GridDhtPartitionsExchangeFuture
> > IGNITE-9928 Igor Seliverstov MVCC TX: Late affinity assignment support.
> > IGNITE-9985 Igor Seliverstov MVCC TX: fix backup mappings
> > IGNITE-10007 Sergey Kozlov Deactivation hangs if an open transaction
> exists
> > IGNITE-10004 Andrew Mashenkov Parse error leads to leave the transaction
> > IGNITE-10024 Ivan Pavlukhin MVCC TX: Stackoverflow during DhtEnlistFuture
> > mapping
> > IGNITE-9996 Alexey Goncharuk Investigate possible performance drop in
> FSYNC
> > mode for ignite-2.7 compared to ignite-2.6
> > IGNITE-9982 Ivan Pavlukhin SQLLine: can't run with option
> > --autoCommit=false or true
> > IGNITE-9828 Roman Kondakov MVCC: Continuous query failover.
> >
> >
> > пт, 26 окт. 2018 г. в 9:59, Vladimir Ozerov :
> >
> > > Hi Nikolay,
> > >
> > > I do not know. We need to investigate them first. These are all
> > > regressions, so decision about impact and urgency should be made
> > separately
> > > for every ticket.
> > >
> > > On Fri, Oct 26, 2018 at 9:57 AM Nikolay Izhikov 
> > > wrote:
> > >
> > > > Hello, Igniters.
> > > >
> > > > We have *9* tickets mapped to 2.7 today
> > > >
> > > > Vladimir, do you think 1 week delay will be enough to resolve all
> this
> > > > tickets?
> > > >
> > > > IGNITE-9828 Roman Kondakov  MVCC: Continuous query
> > failover.
> > > > IGNITE-9928 Igor SeliverstovMVCC TX: Late affinity
> > assignment
> > > > support.
> > > > IGNITE-9985 Igor SeliverstovMVCC TX: fix backup mappings
> > > > IGNITE-9982 Ivan Pavlukhin  SQLLine: can't run with
> option
> > > > --autoCommit=false or true
> > > > IGNITE-10010Unassigned  Node halted if table was
> > dropped
> > > > IGNITE-10013Unassigned  Node restart may lead to NPE
> in
> > > > GridDhtPartitionsExchangeFuture
> > > > IGNITE-9996 Unassigned  Investigate possible
> > performance
> > > > drop in FSYNC mode for ignite-2.7 compared to ignite-2.6
> > > > IGNITE-10007Unassigned  Deactivation hangs if an open
> > > > transaction exists
> > > > IGNITE-10004Unassigned  Parse error leads to leave
> the
> > > > transaction
> > > >
> > > > В Ср, 24/10/2018 в 12:30 +0300, Nikolay Izhikov пишет:
> > > > > Hello, Igniters.
> > > > >
> > > > > We have 3 ticket mapped to 2.7 today:
> > > > >
> > > > > Igor Seliverstov - IGNITE-9892 - MVCC: Exchange hangs on mvcc
> > > > coordinator fail
> > > > > Roman Kondakov   - IGNITE-9828 - MVCC: Continuous query failover.
> > > > > Roman Kondakov   - IGNITE-9928 - MVCC TX: Bug in SQL query mapping.
> > > > >
> > > > > В Вт, 23/10/2018 в 15:01 +0300, Nikolay Izhikov пишет:
> > > > > > Hello, Dmitriy.
> > > > > >
> > > > > > I'm OK with including this patch to 2.7.
> > > > > >
> > > > > > Can you ensure it completely fix the issue?
> > > > > > I left comment in ticket.
> > > > > >
> > > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/IGNITE-9854?focusedCommentId=16660516&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16660516
> > > > > >
> > > > > >
> > > > > > В Вт, 23/10/2018 в 13:10 +0300, Dmitriy Govorukhin пишет:
> > > > > > > Nikolay,
> > > > > > >
> > > > > > > I have an issue which I want to include in 2.7 release,
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-9854
> > > > > > > It is a very small fix but very important, it protects us from
> > NPE
> > > > in some
> > > > > > > race scenario.
> > > > > > > Changes already in master, but the issue still not resolve,
> need
> > > your
> > > > > > > approval for cherry-picking changes to ignite-2.7.
> > > > > > >
> > > > > > > On Tue, Oct 23, 201

Re: Time to remove automated messages from the devlist?

[Petr Ivanov]

Can be Jira notifications united in some kind of daily digest?
Maybe we can add special filter (new tasks / updates during last 24 hours) with 
notification scheme?


> On 6 Nov 2018, at 18:15, Dmitriy Pavlov  wrote:
> 
> I should mention I disagree to remove JIRA issues as the first step. It
> helps everyone to understand what other people are going to do in the
> project.  You always can comment if it is not the best approach, find a
> duplicate issue, and you may suggest help.
> 
> PR notification is more or less duplicates JIRA (as 1 JIRA 1..* PR), so it
> may be ok to move Git's messages to notificati...@ignite.apache.org
> 
> 
> But we should keep JIRA and test failures.
> 
> вт, 6 нояб. 2018 г. в 17:49, Alexey Kuznetsov :
> 
>> Hi!
>> 
>> I have filter for e-mail from JIRA (very useful, I can quick search issue
>> there without visiting JIRA).
>> 
>> And I'm just deleting tons of e-mails from GitBox & about PRs.
>> 
>> I don't know what for we need them?
>> 
>> May by we try to move GitBox & PRs-related mails first and see how it goes?
>> 
>> --
>> Alexey Kuznetsov
>> 

[GitHub] ignite pull request #5315: IGNITE-10147: CPP Thin headers now installed on m...

[isapego]

GitHub user isapego opened a pull request:

https://github.com/apache/ignite/pull/5315

IGNITE-10147: CPP Thin headers now installed on make install



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10147

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5315.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5315


commit 208cf6e08d9f3a9ee2c8057e3008b9e484bfba47
Author: Igor Sapego 
Date:   2018-11-06T15:23:49Z

IGNITE-10147: CPP Thin headers now installed on make install




---

[jira] [Created] (IGNITE-10150) DisappearedCacheWasNotFoundMessageSelfTest fails with NPE

[Stanislav Lukyanov (JIRA)]

Stanislav Lukyanov created IGNITE-10150:
---

 Summary: DisappearedCacheWasNotFoundMessageSelfTest fails with NPE
 Key: IGNITE-10150
 URL: https://issues.apache.org/jira/browse/IGNITE-10150
 Project: Ignite
  Issue Type: Bug
Reporter: Stanislav Lukyanov


https://ci.ignite.apache.org/viewLog.html?buildId=2226328&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Queries2

{code}
java.lang.NullPointerException
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.nodesForPartitions(GridReduceQueryExecutor.java:1702)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:690)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$8.iterator(IgniteH2Indexing.java:1801)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$9.iterator(IgniteH2Indexing.java:1869)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:114)
at 
org.apache.ignite.internal.processors.query.h2.twostep.DisappearedCacheWasNotFoundMessageSelfTest.testDisappearedCacheWasNotFoundMessage(DisappearedCacheWasNotFoundMessageSelfTest.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2206)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:144)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2121)
at java.lang.Thread.run(Thread.java:748)
{code]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Time to remove automated messages from the devlist?

[Dmitriy Pavlov]

I should mention I disagree to remove JIRA issues as the first step. It
helps everyone to understand what other people are going to do in the
project.  You always can comment if it is not the best approach, find a
duplicate issue, and you may suggest help.

PR notification is more or less duplicates JIRA (as 1 JIRA 1..* PR), so it
may be ok to move Git's messages to notificati...@ignite.apache.org


But we should keep JIRA and test failures.

вт, 6 нояб. 2018 г. в 17:49, Alexey Kuznetsov :

> Hi!
>
> I have filter for e-mail from JIRA (very useful, I can quick search issue
> there without visiting JIRA).
>
> And I'm just deleting tons of e-mails from GitBox & about PRs.
>
> I don't know what for we need them?
>
> May by we try to move GitBox & PRs-related mails first and see how it goes?
>
> --
> Alexey Kuznetsov
>

[GitHub] ignite pull request #5313: IGNITE-10149: Make ignite-tf.sh executable by def...

[dmitrievanthony]

GitHub user dmitrievanthony opened a pull request:

https://github.com/apache/ignite/pull/5313

IGNITE-10149: Make ignite-tf.sh executable by default.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10149

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5313.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5313


commit 012cc3b7391fa79a69196bf70ce37f74d5451c8f
Author: Anton Dmitriev 
Date:   2018-11-06T15:09:38Z

Make ignite-tf.sh executable by default.




---

[jira] [Created] (IGNITE-10149) ML: Make ignite-tf.sh utility executable by default

[Anton Dmitriev (JIRA)]

Anton Dmitriev created IGNITE-10149:
---

 Summary: ML: Make ignite-tf.sh utility executable by default
 Key: IGNITE-10149
 URL: https://issues.apache.org/jira/browse/IGNITE-10149
 Project: Ignite
  Issue Type: Bug
  Components: ml
Affects Versions: 2.7
Reporter: Anton Dmitriev
Assignee: Anton Dmitriev
 Fix For: 2.8






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #5308: IGNITE-9989: Fixed jdbc v2 PK metadata

[pavel-kuznetsov]

GitHub user pavel-kuznetsov opened a pull request:

https://github.com/apache/ignite/pull/5308

IGNITE-9989: Fixed jdbc v2 PK metadata



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-9989

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5308.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5308


commit c8521cb526367a2d9448dcb7e1ca500e8494b74b
Author: Pavel Kuznetsov 
Date:   2018-11-06T00:01:46Z

ignite-9989: Draft of the fix.

In jdbc v2, now we avoid using distributed task that fetches metadata to
get PK metadata. We use existing cache descriptors instead.

commit 1e7b3f1947da236b071465c661525ffbe40af06b
Author: Pavel Kuznetsov 
Date:   2018-11-06T14:39:11Z

ignite-9989: Updated tests to work with many tables.

Backported test for primary keys metadata from metadata test of jdbc
thin driver. This change made IGNITE-10118 highlighted.

commit f12c8549b0de14a3dbecc464d5f19d927560ca56
Author: Pavel Kuznetsov 
Date:   2018-11-06T14:50:01Z

ignite-9989: Jdbc v2 PK meta refactoring.

javadoc, moved method to QueryUtils.




---

[jira] [Created] (IGNITE-10148) Add aws s3 and elb configs to benchmarks/config

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-10148:
-

 Summary: Add aws s3 and elb configs to benchmarks/config 
 Key: IGNITE-10148
 URL: https://issues.apache.org/jira/browse/IGNITE-10148
 Project: Ignite
  Issue Type: Bug
Reporter: Ilya Suntsov
Assignee: Ilya Suntsov


Add to yardstick:
 * S3 discovery config
 * ELB discovery config



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Time to remove automated messages from the devlist?

[Alexey Kuznetsov]

Hi!

I have filter for e-mail from JIRA (very useful, I can quick search issue
there without visiting JIRA).

And I'm just deleting tons of e-mails from GitBox & about PRs.

I don't know what for we need them?

May by we try to move GitBox & PRs-related mails first and see how it goes?

-- 
Alexey Kuznetsov

Re: Time to remove automated messages from the devlist?

[Dmitriy Setrakyan]

I just have a filter for Jira emails and automatically go into a different
folder for me.

On Tue, Nov 6, 2018 at 6:40 AM Dmitriy Pavlov  wrote:

> Vova, I've also started such topic about GitBox messages (
>
> https://lists.apache.org/thread.html/1870ba56e0eb9e184d055ef2c84114ea43219d7c845036566f68e880@%3Cdev.ignite.apache.org%3E
> ).
> But it seems no one reacted.
>
> I agree to move out GitHub PR notifications + GitBox messages (see a
> solution in the thread). I disagree about test failures, because a
> contributor may just disappear after a fix, and someone else should pick up
> the test fix.
>
> If we will be open, positive and welcoming we will be still in top-5 dev.
> lists, because we have something to say :)
>
> Here are some thoughts about busy lists that
> - might help to be open,
> - help everyone to feel free to discuss things
> - help to notice a useful staff
>  https://grep.codeconsult.ch/2011/12/06/stefanos-mazzocchis-busy-list-
> pattern/
> 
>
> Sincerely,
> Dmitriy Pavlov
>
> вт, 6 нояб. 2018 г. в 17:31, Vladimir Ozerov :
>
> > Igniters,
> >
> > I noted that the most common action I do on the devlist is clicking "Mark
> > As Read". All I see is JIRA and GitHub notifications. I simply counted
> last
> > 100 threads and found that 89 of them are automated messages, 2 are MTCGA
> > bot messages, and 9 are real human-created threads.
> >
> > Looks like human-created threads are drown inside generated stuff. As
> > potentially new contributor you will hardly figure out what is going on.
> > Does any info about opened tickets and PRs help anyone? Don't we want
> > instead to have a list like this [1] and move all generated stuff to
> > separate lists?
> >
> > The only drawback I see from this action is that we no longer be able to
> > brag about "Top 5 active devlist" in annual ASF summary :-)
> >
> > Thoughts?
> >
> > Vladimir.
> >
> > [1] http://apache-spark-developers-list.1001551.n3.nabble.com/
> >
>

[jira] [Created] (IGNITE-10147) CPP thin: Headers are not installed on make install

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-10147:


 Summary: CPP thin: Headers are not installed on make install
 Key: IGNITE-10147
 URL: https://issues.apache.org/jira/browse/IGNITE-10147
 Project: Ignite
  Issue Type: Bug
  Components: platforms, thin client
Reporter: Igor Sapego
Assignee: Igor Sapego


Currently, {{make install}} command from {{platforms/cpp}} does not install 
headers for C++ thin client.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Time to remove automated messages from the devlist?

[Dmitriy Pavlov]

Vova, I've also started such topic about GitBox messages (
https://lists.apache.org/thread.html/1870ba56e0eb9e184d055ef2c84114ea43219d7c845036566f68e880@%3Cdev.ignite.apache.org%3E
).
But it seems no one reacted.

I agree to move out GitHub PR notifications + GitBox messages (see a
solution in the thread). I disagree about test failures, because a
contributor may just disappear after a fix, and someone else should pick up
the test fix.

If we will be open, positive and welcoming we will be still in top-5 dev.
lists, because we have something to say :)

Here are some thoughts about busy lists that
- might help to be open,
- help everyone to feel free to discuss things
- help to notice a useful staff
 https://grep.codeconsult.ch/2011/12/06/stefanos-mazzocchis-busy-list-
pattern/

Sincerely,
Dmitriy Pavlov

вт, 6 нояб. 2018 г. в 17:31, Vladimir Ozerov :

> Igniters,
>
> I noted that the most common action I do on the devlist is clicking "Mark
> As Read". All I see is JIRA and GitHub notifications. I simply counted last
> 100 threads and found that 89 of them are automated messages, 2 are MTCGA
> bot messages, and 9 are real human-created threads.
>
> Looks like human-created threads are drown inside generated stuff. As
> potentially new contributor you will hardly figure out what is going on.
> Does any info about opened tickets and PRs help anyone? Don't we want
> instead to have a list like this [1] and move all generated stuff to
> separate lists?
>
> The only drawback I see from this action is that we no longer be able to
> brag about "Top 5 active devlist" in annual ASF summary :-)
>
> Thoughts?
>
> Vladimir.
>
> [1] http://apache-spark-developers-list.1001551.n3.nabble.com/
>

Time to remove automated messages from the devlist?

[Vladimir Ozerov]

Igniters,

I noted that the most common action I do on the devlist is clicking "Mark
As Read". All I see is JIRA and GitHub notifications. I simply counted last
100 threads and found that 89 of them are automated messages, 2 are MTCGA
bot messages, and 9 are real human-created threads.

Looks like human-created threads are drown inside generated stuff. As
potentially new contributor you will hardly figure out what is going on.
Does any info about opened tickets and PRs help anyone? Don't we want
instead to have a list like this [1] and move all generated stuff to
separate lists?

The only drawback I see from this action is that we no longer be able to
brag about "Top 5 active devlist" in annual ASF summary :-)

Thoughts?

Vladimir.

[1] http://apache-spark-developers-list.1001551.n3.nabble.com/

[GitHub] ignite pull request #4770: Ignite 7793

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4770


---

[GitHub] ignite pull request #5286: Ignite 1.7.22

[Max-Pudov]

GitHub user Max-Pudov opened a pull request:

https://github.com/apache/ignite/pull/5286

Ignite 1.7.22



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-1.7.22

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5286.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5286


commit 066691098797be8c01daa0e8dc2ba94d4ad73561
Author: sboikov 
Date:   2016-12-01T14:16:28Z

ignite-4344 Do not create offheap map on client nodes.

commit e9ace7730773a6d4a1d30b271854f1fe8a7ba632
Author: Alexey Kuznetsov 
Date:   2016-12-02T09:06:41Z

Improved exception handling.

commit 12bdd6a031a33eda004a66e73cee9628f073ed68
Author: Alexey Kuznetsov 
Date:   2016-12-02T09:09:29Z

Updated classnames.properties for running nodes in IDE.

commit 33dda46061aae73e5c138851cfdd5f49a1c254cb
Author: sboikov 
Date:   2016-12-02T09:13:38Z

ignite-4285 For serializable txs allow multiple threads to get read lock 
for the same key

commit cc13d9d155f70e22e08ef203ac64e5cc0aa0a50f
Author: dkarachentsev 
Date:   2016-11-28T08:30:14Z

IGNITE-4026: Fixed BinaryObjectBuilder.build() can fail if one of the 
fields is Externalizable, enum from binary object. This closes #1281. This 
closes #1289.

(cherry picked from commit 0b7c62d)

commit b4aedfd5350b4a318f1608596a171789513835a4
Author: Igor Sapego 
Date:   2016-12-02T17:10:09Z

IGNITE-4347: Fixed NPE.

commit acf20b32d8fb68e42b904b091fb2b943f4558cef
Author: sboikov 
Date:   2016-12-05T11:01:28Z

ignite-4296 Optimize GridDhtPartitionsSingleMessage processing
- optimized processing of GridDhtPartitionsSingleMessage
- minor optimizations for RendezvousAffinityFunction
 - fixed heartbeats sending in tcp discovery

commit 6ba1711a1fa10d8276974227491136070c3ed43a
Author: Anton Vinogradov 
Date:   2016-12-06T09:55:41Z

IGNITE-4242 ExchangeManager should wait for cache rebalancing in async way

commit 0d4a1b7381fece47ee480f3a06bff7c51a7fead4
Author: Alexey Kuznetsov 
Date:   2016-12-07T11:02:49Z

Improved exception handling for failed queries.

commit ac8602dbdf2bbf5b16a611eaf6d520a0a7b0010b
Author: Sergi Vladykin 
Date:   2016-08-15T13:46:54Z

ignite-3685 - fixed

commit bbaa79af8ef526b5d2684db0e3d71d60a8f1ebe7
Author: agura 
Date:   2016-12-07T16:36:11Z

IGNITE-3770 GridLogThrottle.warn ignores the exception

commit 18598574bb2992aa193eed1d72ca333a1e21ad72
Author: Andrey V. Mashenkov 
Date:   2016-12-08T09:36:07Z

GG-11746: Backport of IGNITE-4379:  Fixed broken local SqlFieldsQuery.

commit 671a77a2d81cac401765dddf25f30fba4e4ab17f
Author: sboikov 
Date:   2016-12-08T09:56:46Z

ignite-4154 Fixed node version check for compression feature usage

commit 391f4be4c687a7f325aeec8b727c9c85ca003454
Author: agura 
Date:   2016-12-07T17:11:50Z

ignite-2358 toString() method for cache store implementations

commit bc977d3211906ef94e1f7d3f0f988efbed65034f
Author: Alexey Kuznetsov 
Date:   2016-12-09T09:11:31Z

IGNITE-4350 Reworked JdbcTypesDefaultTransformed logic. Improved improved 
error messages in CacheJdbcPojoStore.

commit b83ec8e57c7c48f2baa4780cf3b2e46df075f3df
Author: sboikov 
Date:   2016-12-09T11:32:42Z

IGNITE-500 CacheLoadingConcurrentGridStartSelfTest fails: prevent 
'localUpdate' execution while top read lock is held.

commit 6e485637e2738a7e809eac1a802f0964dc12383d
Author: Andrey V. Mashenkov 
Date:   2016-12-09T12:42:40Z

IGNITE-4379: Fixed local query execution. This closes #1323.

commit 6fd8bf6338470275e687a686044c7d935d3714ff
Author: Andrey V. Mashenkov 
Date:   2016-12-07T15:49:06Z

Fixed tests for IGNITE-4379 commit.

commit c143bc1a77baa13f61d6ba00509fa1fcb33757b1
Author: tledkov-gridgain 
Date:   2016-12-09T13:05:03Z

IGNITE-4063:  Preserved order of fields in the metadata according with 
schema. This closes #1270.

commit 6616a878598b8ed74b71558290a22b266a8ac03e
Author: devozerov 
Date:   2016-12-09T13:05:24Z

Merge remote-tracking branch 'upstream/ignite-1.7.4' into ignite-1.7.4

commit f087b661c466c9fd27d049efa8e55a2d7bdf9834
Author: Andrey V. Mashenkov 
Date:   2016-12-09T14:45:33Z

IGNITE-4264: Fixed cluster wide cache metrics. This closes #1336.

commit ceb60d27d38782d82ec5275a56a6f77851b6
Author: Andrey V. Mashenkov 
Date:   2016-12-09T14:46:21Z

Merge remote-tracking branch 'origin/ignite-1.7.4' into ignite-1.7.4

commit 6d744db27111c68e13b06ec99428a4c4148d97b6
Author: dkarachentsev 
Date:   2016-12-12T08:44:57Z

IGNITE-4231 - Hangs on compute result serialization error. Fix

commit eeb2f2a38fb792b711eb665e380d14bc00f6e078
Author: dkarachentsev 
Date:   2016-12-12T09:14:01Z

IGNITE-3862 - GridServiceProxy invocation never times out. Fix

commit 8dd4ada6287af49a243aba1e58daffa7e44f39a9
Author: sboikov 
Date

[GitHub] ignite pull request #5284: IGNITE-7955: MVCC TX: cache peek for key-value AP...

[pavlukhin]

GitHub user pavlukhin opened a pull request:

https://github.com/apache/ignite/pull/5284

IGNITE-7955: MVCC TX: cache peek for key-value API



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-7955

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5284.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5284


commit 0359a3ad885c869a6d492af23e84fa8507bac848
Author: ipavlukhin 
Date:   2018-11-02T15:32:56Z

mvcc-compatible peek draft

commit 514b793910a88ab4718829d1f77055f45740e349
Author: ipavlukhin 
Date:   2018-11-06T11:09:40Z

do "peek" operation similarly to SQL query (use mvcc tracker)

commit 751048bed4012be6608bb01fdc42a2ab58ef5395
Author: ipavlukhin 
Date:   2018-11-06T11:13:23Z

add todo

commit 067782a81e7851f3c84455fdfb281a537fd142a3
Author: ipavlukhin 
Date:   2018-11-06T11:28:25Z

Merge branch 'master' into mvcc-peek

commit 1b2a19969039c9a53da9de9b5802c7aa751a6a7c
Author: ipavlukhin 
Date:   2018-11-06T11:29:56Z

cleanup

commit c1f774ee78b46587cb42010782b8b435df640159
Author: ipavlukhin 
Date:   2018-11-06T14:02:45Z

use special MAX snapshot which can see all committed versions for mvccPeek




---

Re: IGNITE-2.7. New Features

[Vladimir Ozerov]

Igniters,

Any more comments on release notes?

On Tue, Nov 6, 2018 at 9:01 AM Nikolay Izhikov  wrote:

> Vladimir, Thank you so much for this list!
>
> пн, 5 нояб. 2018 г., 23:25 Vladimir Ozerov voze...@gridgain.com:
>
> > Igniters,
> >
> > I assembled information about new features I am aware of. Please find the
> > list below and review it, so that we do not miss anything important. Note
> > that normally we do not include information about every single fix or
> minor
> > feature, as it will make release notes too big. Instead, we strive to
> keep
> > only the most prominent features/fixes in release notes. Minor things are
> > grouped into generic points such as "Stability and performance
> > improvements". Also we typically try to place the most important features
> > first, to catch user's attention as quickly as possible.
> >
> > Ignite:
> > * Added experimental support for multi-version concurrency control with
> > snapshot isolation
> >   - available for both cache API and SQL
> >   - use CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT to enable it
> >   - not production ready, data consistency is not guaranteed in case of
> > node failures
> > * Implemented Transparent Data Encryption based on JKS certificates
> > * Implemented Node.JS Thin Client
> > * Implemented Python Thin Client
> > * Implemented PHP Thin Client
> > * Ignite start scripts now support Java 9 and higher
> > * Added ability to set WAL history size in bytes
> > * Added SslContextFactory.protocols and SslContextFactory.cipherSuites
> > properties to control which SSL encryption algorithms can be used
> > * Added JCache 1.1 compliance
> > * Added IgniteCompute.withNoResultCache method with semantics similar to
> > ComputeTaskNoResultCache annotation
> > * Spring Data 2.0 is now supported in separate module
> > 'ignite-spring-data_2.0'
> > * Added monitoring of critical system workers
> > * Added ability to provide custom implementations of ExceptionListener
> for
> > JmsStreamer
> > * Ignite KafkaStreamer was upgraded to use new KafkaConsmer configuration
> > * S3 IP Finder now supports subfolder usage instead of bucket root
> > * Improved dynamic cache start speed
> > * Improved checkpoint performance by decreasing mark duration.
> > * Added ability to manage compression level for compressed WAL archives.
> > * Added metrics for Entry Processor invocations.
> > * Added JMX metrics: ClusterMetricsMXBean.getTotalBaselineNodes and
> > ClusterMetricsMXBean.getActiveBaselineNodes
> > * Node uptime metric now includes days count
> > * Exposed info about thin client connections through JMX
> > * Inrtoduced new system property IGNITE_REUSE_MEMORY_ON_DEACTIVATE to
> > enable reuse of allocated memory on node deactivation (disabled by
> default)
> > * Optimistic transaction now will be properly rolled back if waiting too
> > long for new topology on remap
> > * ScanQuery with setLocal flag now checks if partition is actually
> present
> > on local node
> > * Improved cluster behavior when left node does not cause partition
> > affinity assignment changes
> > * Interrupting user thread during partition initialization will no longer
> > cause node to stop
> > * Fixed problem when partition lost event were not triggered if multiple
> > nodes left cluster
> > * Fixed massive node drop from cluster on temporary network issues
> > * Fixed service redeployment on cluster reactivation
> > * Fixed client node stability under ZooKeeper discovery
> > * Massive performance and stability improvements
> >
> > Ignite .Net:
> > * Add .NET Core 2.1 support
> > * Added thin client connection failover
> >
> > Ignite C++:
> > * Implemented Thin Client with base cache operations
> > * Implemented smart affinity routing for Thin Client to send requests
> > directly to nodes containing data when possible
> > * Added Clang compiler support
> >
> > SQL:
> > * Added experimental support for fully ACID transactional SQL with
> snapshot
> > isolation:
> >   - use CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT to enable it
> >   - transaction can be started through native API (IgniteTransactions),
> > thin JDBC driver or ODBC driver
> >   - not production ready, data consistency is not guaranteed in case of
> > node failures
> > * Added a set of system views located in "IGNITE" schema to view cluster
> > information (NODES, NODE_ATTRIBUTES, NODE_METRICS, BASELINE_NODES)
> > * Added ability to create predefined SQL schemas
> > * Added GROUP_CONCAT function support
> > * Added string length constraint
> > * Custom Java objects are now inlined into primary and secondary indexes
> > what may significantly improve performance when AFFINITY_KEY is used
> > * Added timeout to fail query execution in case it cannot be mapped to
> > topology
> > * Restricted number of cores allocated for CREATE INDEX by default to 4
> to
> > avoid contention on index tree
> > Fixed transaction hanging during runtime error on commit.
> > * Fixed possible memory leak when result set size is multiple of pag

[GitHub] ignite pull request #5268: IGNITE-9840

[ilantukh]

GitHub user ilantukh opened a pull request:

https://github.com/apache/ignite/pull/5268

IGNITE-9840



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-9840

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5268.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5268


commit 8423138902a4e58f98b7e49bd6df19c07b07df88
Author: Ilya Lantukh 
Date:   2018-10-31T15:03:51Z

IGNITE-9840 : Possible fix.

commit 980689f57fca00ee0bbd675fd64d8328079ee1bd
Author: Ilya Lantukh 
Date:   2018-11-06T13:27:18Z

IGNITE-9840 : Cosmetic changes




---

[GitHub] ignite pull request #5213: Sock timeout

[SpiderRus]

Github user SpiderRus closed the pull request at:

https://github.com/apache/ignite/pull/5213


---

[GitHub] SomeFire commented on a change in pull request #40: IGNITE-9939 [Tc Bot] Add visas caсhing and monitoring

[GitBox]

SomeFire commented on a change in pull request #40: IGNITE-9939 [Tc Bot] Add 
visas caсhing and monitoring
URL: https://github.com/apache/ignite-teamcity-bot/pull/40#discussion_r231087806
 
 

 ##
 File path: 
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildObserver.java
 ##
 @@ -58,10 +63,16 @@ public void stop() {
 /**
  * @param srvId Server id.
  * @param prov Credentials.
+ * @param ticket Ticket.
+ * @param branchForTc Branch for TC.
  * @param ticket JIRA ticket name.
  */
-public void observe(String srvId, ICredentialsProv prov, String ticket, 
Build... builds) {
-observerTask.addBuild(new BuildsInfo(srvId, prov, ticket, builds));
+public void observe(String srvId, ICredentialsProv prov, String ticket, 
String branchForTc, Build... builds) {
+BuildsInfo buildsInfo = new BuildsInfo(srvId, prov, ticket, 
branchForTc, builds);
+
+   visasStorage.put(new VisaRequest(buildsInfo));
 
 Review comment:
   Wrong indentation.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] SomeFire commented on a change in pull request #40: IGNITE-9939 [Tc Bot] Add visas caсhing and monitoring

[GitBox]

SomeFire commented on a change in pull request #40: IGNITE-9939 [Tc Bot] Add 
visas caсhing and monitoring
URL: https://github.com/apache/ignite-teamcity-bot/pull/40#discussion_r231112646
 
 

 ##
 File path: 
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/VisaRequest.java
 ##
 @@ -0,0 +1,55 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.web.model;
+
+import org.apache.ignite.ci.observer.BuildsInfo;
+import org.jetbrains.annotations.Nullable;
+
+/**
+ *
+ */
+public class VisaRequest {
+/** */
+private BuildsInfo info;
+
+/** */
+private Visa visa;
+
+/** */
+public VisaRequest(BuildsInfo info) {
+this.info = info;
+this.visa = Visa.emptyVisa();
+}
+
+/** */
+@Nullable public BuildsInfo getInfo() {
+return info;
+}
+
+/** */
+@Nullable public Visa getRes() {
 
 Review comment:
   Use full words for methods.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] SomeFire commented on a change in pull request #40: IGNITE-9939 [Tc Bot] Add visas caсhing and monitoring

[GitBox]

SomeFire commented on a change in pull request #40: IGNITE-9939 [Tc Bot] Add 
visas caсhing and monitoring
URL: https://github.com/apache/ignite-teamcity-bot/pull/40#discussion_r231112615
 
 

 ##
 File path: 
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/VisaRequest.java
 ##
 @@ -0,0 +1,55 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.web.model;
+
+import org.apache.ignite.ci.observer.BuildsInfo;
+import org.jetbrains.annotations.Nullable;
+
+/**
+ *
+ */
+public class VisaRequest {
+/** */
+private BuildsInfo info;
+
+/** */
+private Visa visa;
+
+/** */
+public VisaRequest(BuildsInfo info) {
+this.info = info;
+this.visa = Visa.emptyVisa();
+}
+
+/** */
+@Nullable public BuildsInfo getInfo() {
+return info;
+}
+
+/** */
+@Nullable public Visa getRes() {
+return visa;
+}
+
+/** */
+public VisaRequest setRes(Visa res) {
 
 Review comment:
   Use full words for methods.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] SomeFire commented on a change in pull request #40: IGNITE-9939 [Tc Bot] Add visas caсhing and monitoring

[GitBox]

SomeFire commented on a change in pull request #40: IGNITE-9939 [Tc Bot] Add 
visas caсhing and monitoring
URL: https://github.com/apache/ignite-teamcity-bot/pull/40#discussion_r231087525
 
 

 ##
 File path: 
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildObserver.java
 ##
 @@ -58,10 +63,16 @@ public void stop() {
 /**
  * @param srvId Server id.
  * @param prov Credentials.
+ * @param ticket Ticket.
 
 Review comment:
   Param duplication.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] SomeFire commented on a change in pull request #40: IGNITE-9939 [Tc Bot] Add visas caсhing and monitoring

[GitBox]

SomeFire commented on a change in pull request #40: IGNITE-9939 [Tc Bot] Add 
visas caсhing and monitoring
URL: https://github.com/apache/ignite-teamcity-bot/pull/40#discussion_r231103961
 
 

 ##
 File path: 
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/Visa.java
 ##
 @@ -0,0 +1,84 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.web.model;
+
+import org.apache.ignite.ci.jira.IJiraIntegration;
+import org.jetbrains.annotations.Nullable;
+
+/**
+ *
+ */
+public class Visa {
+/** */
+public static final String EMPTY_VISA_STATUS = "emptyVisa";
+
+/** */
+public final String status;
+
+/** */
+@Nullable public final JiraCommentResponse jiraCommentRes;
+
+/** */
+public final int blockers;
+
+/** */
+public static Visa emptyVisa() {
+return new Visa(EMPTY_VISA_STATUS);
+}
+
+/** */
+public Visa(String status) {
+this.status = status;
+this.jiraCommentRes = null;
+this.blockers = 0;
+}
+
+/** */
+public Visa(String status, JiraCommentResponse res, Integer blockers) {
+this.status = status;
+this.jiraCommentRes = res;
+this.blockers = blockers;
+}
+
+/** */
+@Nullable public JiraCommentResponse getJiraCommentResponse() {
+return jiraCommentRes;
+}
+
+/** */
+@Nullable public int getBlockers() {
+return blockers;
+}
+
+/** */
+public boolean isSuccess() {
+return IJiraIntegration.JIRA_COMMENTED.equals(status)
+&& jiraCommentRes != null;
+}
+
+/** */
+public boolean isEmpty() {
+return Visa.EMPTY_VISA_STATUS.equals(status);
 
 Review comment:
   Redundant class call.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Splitting cache and basic TC configuration on pure in-memory and persistent one

[Stanislav Lukyanov]

Hi all,

I'm reviving this thread because it seems to me that it might be better to
go back to the combined in-memory and PDS suites now.
As usual, it is a long one, so feel free to skip to the TLDR.

The decision for the split was mostly driven by the desire to have shorter
time of suite runs.
It seems that the decision (and related change
https://issues.apache.org/jira/browse/IGNITE-9100) was quite reasonable at
the time.
But as Vladimir said, the time required by the tests with persistence was
impacted by HDD, and we do have SSDs now.

Having to split the tests is a burden on all developers. Persistence is the
core functionality, and core tests would mostly want to check it.
Forcing to have a clone of a test just to manage the execution time of a
suite seems to be an overkill.

I see a potential benefit in having a test suite that doesn't require a
fast disk, but for now it is just that - potential, while the additional
work
to split the tests is quite real.

Finally, it is hard to make sense from how exactly to split the tests,
which suites to them in, etc.
I believe it makes more difficult for new community members to join - which
is the last thing we want.

TLDR
I propose to allow adding persistence tests to any suite, remove
the PERSISTENCE_IN_TESTS_IS_ALLOWED_PROPERTY property
and related functionality added by
https://issues.apache.org/jira/browse/IGNITE-9100.
Instead of that, to manage the execution time of the suites we can take a
habit of splitting the suites that take more than an hour
as it is being done now in https://issues.apache.org/jira/browse/IGNITE-8849
.

WDYT?

Thanks,
Stan

On Fri, Jul 27, 2018 at 3:46 PM Eduard Shangareev 
wrote:

> Vladimir,
>
> I am talking only about Run Cache and Basic.
> I don't see any objection why we couldn't do so.
> Even with extra SSD, it could be worth to split configuration to have
> control over their impact on the disk system.
>
>
> On Fri, Jul 27, 2018 at 3:28 PM, Vladimir Ozerov 
> wrote:
>
> > Ed,
> >
> > We already discussed this some time ago. AFAIK SSD disks do not have this
> > problem, so all we need is to replace HDD with SSD.
> >
> > On Fri, Jul 27, 2018 at 3:26 PM Eduard Shangareev <
> > eduard.shangar...@gmail.com> wrote:
> >
> > > Igniters,
> > >
> > > I am working on the stability of our TC test runs.
> > >
> > > Some of our execution timeouts (hangings, unexpected stops) happen
> > because
> > > of issues in source code: test itself, test runners, configurations,
> bug,
> > > Linux OOM killer and so on.
> > >
> > > We could fix them by changing code.
> > >
> > > But almost all of the last issues with timeouts have happened because
> > many
> > > tests ran disk-intensive operations on one machine.
> > >
> > > Examples:
> > >
> > >
> > > https://ci.ignite.apache.org/viewLog.html?buildId=1543562&;
> > tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_ZooKeeperDiscovery2
> > >
> > > https://ci.ignite.apache.org/viewLog.html?buildId=1543518&;
> > tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Basic1
> > >
> > > and so on.
> > >
> > > To fix this problem I propose to extract from "Run Basic" and "Run
> Cache"
> > > new
> > > dedicated ones for persistent tests TC configurations.
> > >
> > > Also, I would add some checking to not allow add new tests with
> > persistent
> > > to other TC configurations in future.
> > >
> > > It would allow us to run almost all TC configuration on any agent while
> > > configurations with persistent would have agent rules to not get a
> > timeout.
> > >
> > > Thoughts?
> > >
> >
>
>
>
> --
> Best regards,
> Eduard.
>

[jira] [Created] (IGNITE-10146) [TC Bot] Refresh missing prs while full reindex

[PetrovMikhail (JIRA)]

PetrovMikhail created IGNITE-10146:
--

 Summary: [TC Bot] Refresh missing prs while full reindex
 Key: IGNITE-10146
 URL: https://issues.apache.org/jira/browse/IGNITE-10146
 Project: Ignite
  Issue Type: Task
Reporter: PetrovMikhail
Assignee: PetrovMikhail






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10145) [ML] ROC AUC score

[Yury Babak (JIRA)]

Yury Babak created IGNITE-10145:
---

 Summary: [ML] ROC AUC score
 Key: IGNITE-10145
 URL: https://issues.apache.org/jira/browse/IGNITE-10145
 Project: Ignite
  Issue Type: New Feature
  Components: ml
Reporter: Yury Babak
 Fix For: 2.8


Compute Area Under the Receiver Operating Characteristic Curve (ROC AUC) from 
prediction scores.

We want to implement this score for our models.

Some links:
* [wiki|https://en.wikipedia.org/wiki/Receiver_operating_characteristic]
* [google 
dev|https://developers.google.com/machine-learning/crash-course/classification/roc-and-auc]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #5255: Ignite 2.4.13

[aealeksandrov]

GitHub user aealeksandrov opened a pull request:

https://github.com/apache/ignite/pull/5255

Ignite 2.4.13

Created for team city run. Should not be merged.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.13

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5255.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5255


commit 149802a3be82ba1f88770dbff75d74b892bb0a94
Author: Alexey Kuznetsov 
Date:   2018-03-07T17:17:20Z

IGNITE-7803 Fixed regression in tests.

(cherry picked from commit 90c0af8)

commit 5b5571adc7282a29cdecd8ab2e945a446ea709fc
Author: Alexey Kuznetsov 
Date:   2018-03-23T02:55:13Z

IGNITE-8002 REST: Added support of new authentication via new API.

(cherry picked from commit 921f0cf)

commit 128fdfcd874286f4a358546c0f43b6ef082a064b
Author: devozerov 
Date:   2018-04-02T10:11:16Z

IGNITE-7884: Sample data set for JDBC. This closes #3702.

commit 247a9ef5a68de198106a866b277f1bee596c3633
Author: devozerov 
Date:   2018-04-02T10:16:00Z

Merge branch 'ignite-2.4.4' into ignite-2.4-master

commit 3949df02128e3003c409e0169ad0c80948ba134c
Author: Aleksey Plekhanov 
Date:   2018-02-13T13:43:49Z

IGNITE-5265 Eviction Rate memory metric to be implemented

Signed-off-by: Anton Vinogradov 

commit 7bc6c1ad3bacaf5e354d2710931eb398c346c06c
Author: Tim Onyschak 
Date:   2018-03-31T12:58:25Z

IGNITE-7090 Semaphore Stuck when no acquirers to assign permit - Fixes 
#3443.

Signed-off-by: dspavlov 

(cherry picked from commit 3fc5d57)

commit c854ad86f4c64260171085c8c7cce97ba1ad2530
Author: Pavel Kovalenko 
Date:   2018-02-22T09:02:31Z

IGNITE-7749 Fixed testDiscoCacheReuseOnNodeJoin test. - Fixes #3540.

Signed-off-by: Alexey Goncharuk 

commit b2e94b36bddebbf7b3ff40631e099939d16926d2
Author: Alexey Goncharuk 
Date:   2018-02-13T15:53:23Z

IGNITE-7692 Corrected test to not fail when SQL is executed on backup

commit 852425d4170ed1871c79f5ac26bfb3d03cc36a6f
Author: Алексей Стельмак 
Date:   2018-04-06T15:28:22Z

IGNITE-8049 Limit the number of operation cycles in B+Tree - Fixes #3769.

Signed-off-by: dpavlov 
(cherry picked from commit e491f10)

commit 42f529f0a04ce22786bb4a23032a64f93e214233
Author: Alexey Kuznetsov 
Date:   2018-04-09T02:25:50Z

IGNITE-8159 control.sh: Fixed NPE on adding nodes on empty baseline and not 
active cluster.

(cherry picked from commit 834869c)

commit b5f180838246f895d36846ea707790c1ff7fe70a
Author: Stanislav Lukyanov 
Date:   2018-04-09T11:33:13Z

IGNITE-7904: Changed IgniteUtils::cast not to trim exception chains. This 
closes #3683.

(cherry picked from commit 3a4f23b)

commit 1ce8e1a8fd48469073592e2fb77e2881a168a219
Author: Roman Guseinov 
Date:   2018-04-09T11:45:44Z

IGNITE-7944: Disconnected client node tries to send JOB_CANCEL message. 
Applied fix:
- Skip sending message if client disconnected;
- Throw IgniteCheckedException if a client node is disconnected and 
communication client is null.
This closes #3737.

(cherry picked from commit d70477b)

commit 840e193b3e604e8b0d90be5fac16cf11d8c832e6
Author: Ilya Lantukh 
Date:   2018-04-06T10:49:10Z

ignite-8087 : Backported ignite-8018.

(cherry picked from commit 175edf3)

commit 94e857c94ce5e7998fc39e38deee69f389ddbc5b
Author: Alexey Goncharuk 
Date:   2018-04-10T17:33:47Z

IGNITE-6430 Complete failing test early

commit 770f7469d4b86ce9af61e9e43c7262d86ee05b54
Author: Eduard Shangareev 
Date:   2018-04-06T16:22:07Z

IGNITE-8114 Add fail recovery mechanism to tracking pages

commit 549d6e3de86a22697577f77a2ebab3d0dca7338d
Author: Alexey Kukushkin 
Date:   2018-04-11T13:29:07Z

IGNITE-8221: Security for thin clients.

commit 94c0f56ef78e6c61f0e753c8aa0185c611630d45
Author: devozerov 
Date:   2018-04-11T13:44:33Z

IGNITE-8148: JDBC thin: semicolon as delimiter for properties. This closes 
#3794.

commit d99a50ccd6923aa48da78955207fe747b287ea81
Author: mcherkasov 
Date:   2018-04-11T00:23:29Z

IGNITE-8153 Nodes fail to connect each other when SSL is enabled - Fixes 
#3773.

Signed-off-by: Valentin Kulichenko 

commit 03285e953d005a18fb88a35d21701100f58f7a29
Author: devozerov 
Date:   2018-04-12T07:37:36Z

IGNITE-8042: .NET thin client: authentication support. This closes #3790.

commit 8e740164e8a0102a94f408d72b41f73df675cfb1
Author: Ilya Kasnacheev 
Date:   2018-04-05T09:55:36Z

IGNITE-7712: SQL: system property to force lazy query execution.

Cherry-picked from 064c816c177d31f18af2954175ca3ad0f3eee957

commit df405d439d461d3576cd3b22d53716cd324b3ef7
Author: Alexander Paschenko 
Date:   2018-04-11T14:03:16Z

IGNITE-8204: SQL: fixed hangs when 

[jira] [Created] (IGNITE-10144) Optimize bagging upstream transformer

[Artem Malykh (JIRA)]

Artem Malykh created IGNITE-10144:
-

 Summary: Optimize bagging upstream transformer
 Key: IGNITE-10144
 URL: https://issues.apache.org/jira/browse/IGNITE-10144
 Project: Ignite
  Issue Type: Improvement
  Components: ml
Reporter: Artem Malykh


For now BaggingUpstreamTransformer makes upstream sequential to make 
transformation deterministic. Maybe we should do it other way, for example use 
mapping of the form (entryIdx, en) -> Stream.generate(() -> en).limit(new 
PoissonDistribution(Well19937c(entryIdx + seed), ...).sample())



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10143) Cache operations hang after the cluster becomes disabled

[Alexander (JIRA)]

Alexander created IGNITE-10143:
--

 Summary: Cache operations hang after the cluster becomes disabled
 Key: IGNITE-10143
 URL: https://issues.apache.org/jira/browse/IGNITE-10143
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.6
Reporter: Alexander


Cache operations hang after the cluster becomes disabled (method has been 
called ignite.cluster().active(false))

If I call cache.isClosed method I got "true" immediately, but if I call cache 
operation (for example cache.put method) it hangs

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #5254: IGNITE-10141: Cache 3 tests optimization

[avplatonov]

GitHub user avplatonov opened a pull request:

https://github.com/apache/ignite/pull/5254

IGNITE-10141: Cache 3 tests optimization



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10141

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5254.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5254


commit d8ea4fd282050f6a83ccfca4f40fae67f022b088
Author: Alexey Platonov 
Date:   2018-11-06T11:39:15Z

init commit




---

[GitHub] ignite pull request #5253: IGNITE-10142 Cache 8 tests optimization

[ibessonov]

GitHub user ibessonov opened a pull request:

https://github.com/apache/ignite/pull/5253

IGNITE-10142 Cache 8 tests optimization



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10142

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5253.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5253


commit 33e5402ca23757f7f341ec94e3b6fda22156d0d8
Author: ibessonov 
Date:   2018-11-06T11:27:48Z

IGNITE-10142 Scale factor added to several tests from Cache 8 suite.




---

[jira] [Created] (IGNITE-10142) Cache 8 tests optimization

[Ivan Bessonov (JIRA)]

Ivan Bessonov created IGNITE-10142:
--

 Summary: Cache 8 tests optimization
 Key: IGNITE-10142
 URL: https://issues.apache.org/jira/browse/IGNITE-10142
 Project: Ignite
  Issue Type: Improvement
Reporter: Ivan Bessonov
Assignee: Ivan Bessonov


These tests run over 1 minute each:

CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime
GridCacheRebalancingAsyncSelfTest.testComplexRebalancing
GridCacheRebalancingAsyncSelfTest.testSimpleRebalancing
GridCacheRebalancingSyncSelfTest.testSimpleRebalancing
GridCacheRebalancingSyncSelfTest.testComplexRebalancing
GridCacheRebalancingSyncSelfTest.testLoadRebalancing
GridCacheConcurrentEvictionsSelfTest.testConcurrentPutsFifoLocal
GridCacheConcurrentEvictionsSelfTest.testConcurrentPutsLruLocal
GridCacheConcurrentEvictionsSelfTest.testConcurrentPutsSortedLocal
IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator
IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup

They should be either optimized or moved into overnight build (or both).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #5234: IGNITE-10107 Cache 7 tests optimization

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/5234


---

[GitHub] ignite pull request #5235: IGNITE-10115 Remove excessive "setAccessible(oldA...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/5235


---

Re: destroy cache holding residual metadata in memory (2.7)

[Yakov Zhdanov]

Wayne, can you please share a reproducer for this problem that can be
launched from IDE?

--Yakov

Re: destroy cache holding residual metadata in memory (2.7)

[Yakov Zhdanov]

Wayne, can you please share a reproducer for this problem that can be
launched from IDE?

--Yakov

[jira] [Created] (IGNITE-10141) Cache 3 tests optimization

[Alexey Platonov (JIRA)]

Alexey Platonov created IGNITE-10141:


 Summary: Cache 3 tests optimization
 Key: IGNITE-10141
 URL: https://issues.apache.org/jira/browse/IGNITE-10141
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Platonov
Assignee: Alexey Platonov


We need to investigate how to optimize these tests:

 

GridCacheInterceptorTransactionalRebalanceTest.testRebalanceUpdate
GridCacheInterceptorTransactionalRebalanceTest.testRebalanceRemoveInvoke
GridCacheInterceptorTransactionalRebalanceTest.testPutIfAbsent
GridCacheInterceptorTransactionalRebalanceTest.testRebalanceUpdateInvoke
IgniteCacheGroupsTest.testRestartsAndCacheCreateDestroy
GridCacheInterceptorTransactionalRebalanceTest.testRebalanceRemove
GridCacheInterceptorTransactionalRebalanceTest.testGetAndPut
IgniteCacheGroupsTest.testStartManyCaches
GridCacheVersionTopologyChangeTest.testVersionIncreaseTx
GridCacheVersionTopologyChangeTest.testVersionIncreaseAtomic
GridCacheValueConsistencyTransactionalSelfTest.testPutRemoveConsistencyMultithreaded
GridCacheInterceptorAtomicRebalanceTest.testRebalanceUpdateInvoke
GridCacheInterceptorAtomicRebalanceTest.testGetAndPut

 

and optimize them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #5252: IGNITE-10106: Cache 5 test suite optimization

[avplatonov]

GitHub user avplatonov opened a pull request:

https://github.com/apache/ignite/pull/5252

IGNITE-10106: Cache 5 test suite optimization



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10106

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5252.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5252


commit 4e85c11c3a5781b88cf2e3ae2a70b033f66e6e5d
Author: Alexey Platonov 
Date:   2018-10-29T13:59:05Z

init commit

commit 45076feec0dc4a26172eb79acb9dabcd1a8bab73
Author: Alexey Platonov 
Date:   2018-10-30T09:37:14Z

add scale factor

commit 907b19320d1bffbfbb9b3997201fd4b28718b2ee
Author: Alexey Platonov 
Date:   2018-10-30T09:41:21Z

remode useless code

commit 8107297ea092d46c097b4575213deb593d7a0db4
Author: Alexey Platonov 
Date:   2018-10-30T10:08:55Z

remove garbage

commit 3ff73df5a016dcd6ea03d23ee4a2c8f0b37b0c2a
Author: Alexey Platonov 
Date:   2018-10-30T10:18:56Z

fix comments in code

commit ec30ebb6b2a455d609f27d62715a876f113572d1
Author: ibessonov 
Date:   2018-10-31T12:16:30Z

IGNITE-10084 Added scale factor in 
IgniteCacheStarvationOnRebalanceTest.testLoadSystemWithPutAndStartRebalancing

commit a23b20d7f03374522e710efff2944796bfd719b7
Author: Alexey Platonov 
Date:   2018-11-01T12:35:55Z

init commit

commit b4244fc6c7664d8688aff2fe3810ad448d679684
Author: Alexey Platonov 
Date:   2018-11-02T07:46:14Z

fixes after review

commit 86ca2389d4d4aee314209942589b4f17cc12f25d
Author: Alexey Platonov 
Date:   2018-11-02T08:17:34Z

add comment

commit fcadf111cc3f1a6fb38d81a27c75173a2027b5ad
Author: Alexey Platonov 
Date:   2018-11-02T11:32:32Z

Merge branch 'ignite-10037' of https://github.com/gridgain/apache-ignite 
into ignite-10106

commit 4b3e0b4daf5f55afd1cacc0783d82df5223038d2
Author: Alexey Platonov 
Date:   2018-11-02T11:36:58Z

use SF-class

commit 4a5726f3074e7d996799fc3bd51f3403f2f667b1
Author: Alexey Platonov 
Date:   2018-11-02T11:43:49Z

Merge branch 'ignite-10084' of https://github.com/gridgain/apache-ignite 
into ignite-10106

commit 7def39c6655de3b6bc156b2f7af15df5f352c10f
Author: Alexey Platonov 
Date:   2018-11-02T11:47:15Z

merge with other branch

commit 0d056c3cde56bc16fba09594f2238cdd8231e131
Author: Alexey Platonov 
Date:   2018-11-06T08:49:36Z

Merge branch 'master' of https://github.com/apache/ignite into ignite-10106

# Conflicts:
#   
modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/CacheLoadingConcurrentGridStartSelfTest.java
#   
modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/GridCachePartitionNotLoadedEventSelfTest.java
#   
modules/core/src/test/java/org/apache/ignite/testframework/GridTestUtils.java




---

[GitHub] zzzadruga opened a new pull request #59: IGNITE-10137 Add button 'Expand all' on 'PR failures' page

[GitBox]

zzzadruga opened a new pull request #59: IGNITE-10137 Add button 'Expand all' 
on 'PR failures' page
URL: https://github.com/apache/ignite-teamcity-bot/pull/59
 
 
   Add button 'Expand all' on 'PR failures' page. The button should show 
additional information for all available lines.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services