[GitHub] ignite pull request #5617: IGNITE-10189 Added support for SSL Ciphers for co...

[akuznetsov-gridgain]

GitHub user akuznetsov-gridgain opened a pull request:

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

IGNITE-10189 Added support for SSL Ciphers for control.sh



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

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

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

https://github.com/apache/ignite/pull/5617.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 #5617


commit 45263e2bb9f4bdfd77b09ccb88c510d2118bae2f
Author: Alexey Kuznetsov 
Date:   2018-12-03T10:27:42Z

IGNITE-10189 WIP.

commit d9d62bea34eeb2df568471cd53ac153394b3052a
Author: Alexey Kuznetsov 
Date:   2018-12-05T07:30:13Z

Merge branches 'ignite-10189' and 'master' of 
https://git-wip-us.apache.org/repos/asf/ignite into ignite-10189

commit 83f786943f6812daf91fb774393ff9499ff7058f
Author: Alexey Kuznetsov 
Date:   2018-12-05T09:22:39Z

IGNITE-10189 WIP.

commit 4472ae936729562083dacc17aa7770b0ed2a964e
Author: Alexey Kuznetsov 
Date:   2018-12-05T10:48:21Z

Merge branches 'ignite-10189' and 'master' of 
https://git-wip-us.apache.org/repos/asf/ignite into ignite-10189

commit 5a0c517877768755cb8fa1fd6d26764712ce43cb
Author: Alexey Kuznetsov 
Date:   2018-12-05T12:11:29Z

IGNITE-10189 WIP.

commit 6ae44a775ecd807ee1e84aa1fb1403e8c13d6e04
Author: Alexey Kuznetsov 
Date:   2018-12-10T06:29:17Z

Merge branches 'ignite-10189' and 'master' of 
https://git-wip-us.apache.org/repos/asf/ignite into ignite-10189

commit e5908dc8ca595ddce3bfa9b769709ea88edc7075
Author: Alexey Kuznetsov 
Date:   2018-12-10T07:35:57Z

Merge branches 'ignite-10189' and 'master' of 
https://git-wip-us.apache.org/repos/asf/ignite into ignite-10189

commit c77e82e3705e2c76d055a3fc40822866c963bbdc
Author: Alexey Kuznetsov 
Date:   2018-12-10T07:52:06Z

IGNITE-10189 Added SSL tests.




---

[GitHub] ignite pull request #5392: IGNITE-10189 Added SSL ciphers suites support for...

[akuznetsov-gridgain]

Github user akuznetsov-gridgain closed the pull request at:

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


---

[jira] [Created] (IGNITE-10615) Ignite Compatibility: fix arguments' checking in the node runner

[Vyacheslav Daradur (JIRA)]

Vyacheslav Daradur created IGNITE-10615:
---

 Summary: Ignite Compatibility: fix arguments' checking in the node 
runner
 Key: IGNITE-10615
 URL: https://issues.apache.org/jira/browse/IGNITE-10615
 Project: Ignite
  Issue Type: Improvement
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
 Fix For: 2.8


There is the checking of arguments number In 
{{IgniteCompatibilityNodeRunner#main}}, which expected at least 3 arguments, 
but in actual code at least 5 arguments are required.
The checking should be fixed.



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

Re: Support service on inactive cluster

[Vyacheslav Daradur]

Alexey,

Have a look at the 'PluginProvider' interface, if you implemented a
telemetry service as a plugin:
* plugin may be placed in the 'web-console' module;
* plugin is initialized at node startup and is stopped at node shutdown;
* plugin have access to all Ignite's internals through context;
* listening of discovery topologies events allows you implementing
some kind of cluster singleton, to be able to deploy telemetry-service
in case previous one failed.


On Mon, Dec 10, 2018 at 6:28 AM Alexey Kuznetsov  wrote:
>
> Vyacheslav,
>
> Thanks for detailed explanation.
>
> As far as I see, we CAN support services on deactivated cluster, but it
> does not seems a good idea from end user perspective.
>
> I'm thinking that in my case (sending telemetry from cluster) I will go
> another way.
>
> --
> Alexey Kuznetsov



-- 
Best Regards, Vyacheslav D.

[GitHub] ignite pull request #5618: IGNITE-10615 Ignite Compatibility: fix arguments'...

[daradurvs]

GitHub user daradurvs opened a pull request:

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

IGNITE-10615 Ignite Compatibility: fix arguments' checking in the node 
runner



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

$ git pull https://github.com/daradurvs/ignite ignite-10615

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

https://github.com/apache/ignite/pull/5618.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 #5618


commit 55f63d329a79fd537adc7687a04a73c8a6194fae
Author: Vyacheslav Daradur 
Date:   2018-12-10T08:42:18Z

Fixed.




---

[GitHub] ignite pull request #5574: Ignite-10534

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #5429: IGNITE-8432: Test for column name case in PK and ...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #5539: IGNITE-4841: Improve javadoc for Ignite Query cla...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Created] (IGNITE-10616) Web console: new security token must be applied immediately

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-10616:
---

 Summary: Web console: new security token must be applied 
immediately 
 Key: IGNITE-10616
 URL: https://issues.apache.org/jira/browse/IGNITE-10616
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov
 Fix For: 2.8


I found that after changing of user's security token it not applied immediately
- expected: web agent must lose connection
- actually: web agent still be connected



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

[GitHub] SomeFire opened a new pull request #96: fix typo in schedulers

[GitBox]

SomeFire opened a new pull request #96: fix typo in schedulers
URL: https://github.com/apache/ignite-teamcity-bot/pull/96
 
 
   


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: Ignite cloud readiness and as a managed service

[Vyacheslav Daradur]

>From my point of view, it's important to further develop the thin client.

Users should be able to use most of Ignite's components via thin
client, as far as possible, just for example:
* transactional CRUD operations over data in the cluster;
* deploy/undeploy and monitor services in the Service Grid;
* run and manage the compute tasks;
* work with ML component;
* data streaming and so on...

The thin client allows end-user to place application and Ignite
cluster in a different environment and avoid impact on cluster's
topology.



On Fri, Dec 7, 2018 at 11:24 PM Denis Magda  wrote:
>
> Igniters,
>
> Presently, there are no any doubts that the private/public cloud
> deployments would be dominating soon. Personally, I already see even
> conservative companies moving from on-prem to clouds. That migration is
> impossible w/o essential support and integrations with tools/environments
> like Kubernetes, Docker, AWS, Azure, OpenShift, VMWare to name few.
>
> Luckily, Ignite is pretty well-equipped at the moment. However, there are
> some gaps which I would encourage us to highlight. What should the
> community do to make Ignite 100% ready for cloud deployments the next year?
> For instance, that's my list of gaps:
>
>- Pivotal Cloud Foundry support
>- Helm integration - https://helm.sh
>- Prometheus integration - https://prometheus.io
>
> Moreover, some of the companies moved forward and began using Ignite as a
> managed service. There is nothing we can do on the community side except
> for listing where Ignite users can get the service, which might be helpful.
> I'm thinking to create a webpage that would list all the known solutions
> like 2 below. Any recommendations on this?
>
>- https://www.nexaops.com/managed-services/managed-services-apache-ignite
>- https://gridgain.cloud
>
> --
> Denis



-- 
Best Regards, Vyacheslav D.

Re: java.lang.IllegalAccessError: tried to access field org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class org.apache.ignite.internal.processors.query.h2.H2DatabaseType

[Павлухин Иван]

Hi Ken,

It looks like you have a dependency to different h2 version in your
project. Ignite requires com.h2database:h2 version 1.4.197.
пн, 10 дек. 2018 г. в 07:08, kcheng.mvp :
>
>
> There are total 82 unite test for my system.
>
> this unit test works well in ignite 2.6.
>
> when I switch to ignite 2.7, I got below error for my unit tests
>
> I logged a ticket here https://issues.apache.org/jira/browse/IGNITE-10612
>
>
>
> java.lang.IllegalAccessError: tried to access field
> org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class
> org.apache.ignite.internal.processors.query.h2.H2DatabaseType
> at
> org.apache.ignite.internal.processors.query.h2.H2DatabaseType.fromClass(H2DatabaseType.java:147)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.dbTypeFromClass(IgniteH2Indexing.java:2972)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createTable(IgniteH2Indexing.java:2869)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:2809)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.registerCache0(GridQueryProcessor.java:1633)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:805)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:866)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1330)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:2165)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processCacheStartRequests(CacheAffinitySharedManager.java:898)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:798)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1231)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:738)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2667)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2539)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> 2018-12-10 11:47:21 INFO  o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture
> - Finish exchange future [startVer=AffinityTopologyVersion [topVer=1,
> minorTopVer=2], resVer=null, err=java.lang.IllegalAccessError: tried to
> access field org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class
> org.apache.ignite.internal.processors.query.h2.H2DatabaseType]
> 2018-12-10 11:47:21 ERROR  - Critical system error detected. Will be handled
> accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler
> [tryStop=false, timeout=0, super=AbstractFailureHandler
> [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.AssertionError: Missing user
> future for cache: GIFT]]
> java.lang.AssertionError: Missing user future for cache: GIFT
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.rebuildIndexesIfNeeded(GridCacheDatabaseSharedManager.java:1364)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2151)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:138)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:860)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2667)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2539)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
>
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/



-- 
Best regards,
Ivan Pavlukhin

[jira] [Created] (IGNITE-10617) Web console: Invalid class name in frontend/app/components/connected-clusters-dialog/components/list/controller.js

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-10617:
--

 Summary: Web console: Invalid class name in 
frontend/app/components/connected-clusters-dialog/components/list/controller.js
 Key: IGNITE-10617
 URL: https://issues.apache.org/jira/browse/IGNITE-10617
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko


Rename class to ConnectedClustersListCtrl.



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

[jira] [Created] (IGNITE-10618) Web console: exclude daemon node from cluster size on Connected Clusters modal

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-10618:
---

 Summary: Web console: exclude daemon node from cluster size on 
Connected Clusters modal
 Key: IGNITE-10618
 URL: https://issues.apache.org/jira/browse/IGNITE-10618
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov
 Attachments: image-2018-12-10-17-37-10-334.png

 !image-2018-12-10-17-37-10-334.png! 



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

[jira] [Created] (IGNITE-10619) Add support for ReadableByteChannel, WritableByteChannel over CommunicationSpi

[Maxim Muzafarov (JIRA)]

Maxim Muzafarov created IGNITE-10619:


 Summary: Add support for ReadableByteChannel, WritableByteChannel 
over CommunicationSpi
 Key: IGNITE-10619
 URL: https://issues.apache.org/jira/browse/IGNITE-10619
 Project: Ignite
  Issue Type: Sub-task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov


To benefit from zero copy we must delegate the file transferring to 
FileChannel#transferTo(long, long, java.nio.channels.WritableByteChannel) 
because the fast path of transferTo method is only executed if the destination 
buffer inherits from an internal JDK class.

The {{CommunicationSpi}} needs to support pipe connections between two nodes;
* The WritableByteChannel needs to be accessed on the supplier side;
* The ReadableByteChannel needs to be read on the demander side;
* The CommunicationListener must be extended to respond on new incoming pipe 
connections;



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

[GitHub] ignite pull request #5619: IGNITE-10619: CommunicationSpi support channels i...

[Mmuzaf]

GitHub user Mmuzaf opened a pull request:

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

IGNITE-10619: CommunicationSpi support channels initial commit

- GridNioServer supports channel creation from GridNioSession
- rework createTcpClient method
- new GridIoManager channel creation listener
- updated HandshakeMessage2 to support new connections
- new connection Builder'ы

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

$ git pull https://github.com/Mmuzaf/ignite ignite-10619

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

https://github.com/apache/ignite/pull/5619.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 #5619


commit ae7e5f6e10b23caf98830e349286bcf4ea059cff
Author: Maxim Muzafarov 
Date:   2018-12-10T11:01:44Z

IGNITE-10619: CommunicationSpi support channels initial commit




---

Re: Default failure handler was changed for tests

[Anton Vinogradov]

Dmitriy,

You confirmed that fix should be reverted and reworked last Friday.
Why it still not reverted?

On Mon, Dec 10, 2018 at 12:46 AM Dmitrii Ryabov 
wrote:

> Agree, it is reasonable to revert.
> пт, 7 дек. 2018 г. в 18:44, Dmitriy Pavlov :
> >
> > Hi Ilya,
> >
> > thank you for noticing.
> >
> > Calling to fail is equal to re-throw,
> >
> > throw new AssertionFailedError(message);
> >
> > So, yes, for now it is absolutely valid reason to revert and rework fix
> >
> > - as Nikolay suggested to reduce method override ocurrences.
> > - and with transferring this exception into GridAbstractTest and
> > correctly failing test.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> >
> > пт, 7 дек. 2018 г. в 18:38, Ilya Lantukh :
> >
> > > Unfortunately, this FailureHandler doesn't seem to work. I wrote a test
> > > that reproduces a bug and should fail. It prints the following text
> into
> > > log, but the test still passes "successfully":
> > >
> > > [2018-12-07
> > >
> > >
> 18:28:23,800][ERROR][sys-stripe-1-#345%recovery.GridPointInTimeRecoveryCacheNoAffinityExchangeTest1%][IgniteTestResources]
> > > Critical system error detected. Will be handled accordingly to
> configured
> > > handler [hnd=TestFailingFailureHandler [], failureCtx=FailureContext
> > > [type=CRITICAL_ERROR, err=java.lang.IllegalStateException: Unable to
> find
> > > consistentId by UUID [nodeId=80dd2ec6-1913-4a5c-a839-630315c3,
> > > topVer=AffinityTopologyVersion [topVer=12, minorTopVer=0
> > > java.lang.IllegalStateException: Unable to find consistentId by UUID
> > > [nodeId=80dd2ec6-1913-4a5c-a839-630315c3,
> > > topVer=AffinityTopologyVersion [topVer=12, minorTopVer=0]]
> > > at
> > >
> > >
> org.apache.ignite.internal.managers.discovery.ConsistentIdMapper.mapToCompactId(ConsistentIdMapper.java:62)
> > > at
> > >
> > >
> org.apache.ignite.internal.managers.discovery.ConsistentIdMapper.mapToCompactIds(ConsistentIdMapper.java:123)
> > > at
> > >
> > >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.newTxRecord(IgniteTxManager.java:2507)
> > > at
> > >
> > >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.logTxRecord(IgniteTxManager.java:2483)
> > > at
> > >
> > >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.state(IgniteTxAdapter.java:1226)
> > > at
> > >
> > >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.state(IgniteTxAdapter.java:1054)
> > > at
> > >
> > >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.startRemoteTx(IgniteTxHandler.java:1836)
> > > at
> > >
> > >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxPrepareRequest(IgniteTxHandler.java:1180)
> > > at
> > >
> > >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$400(IgniteTxHandler.java:118)
> > > at
> > >
> > >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$5.apply(IgniteTxHandler.java:222)
> > > at
> > >
> > >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$5.apply(IgniteTxHandler.java:220)
> > > at
> > >
> > >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1059)
> > > at
> > >
> > >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:584)
> > > at
> > >
> > >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:383)
> > > at
> > >
> > >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:309)
> > > at
> > >
> > >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:100)
> > > at
> > >
> > >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:299)
> > > at
> > >
> > >
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
> > > at
> > >
> > >
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
> > > at
> > >
> > >
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> > > at
> > >
> > >
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
> > > at
> > >
> > >
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
> > > at
> > >
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> > > at java.lang.Thread.run(Thread.java:748)
> > >
> > >
> > > On Thu, Dec 6, 2018 at 4:01 PM Anton Vinogradov  wrote:
> > >
> > > > >> We stop, for now, then you will chill a
> > > > >> little bit, then you will have an absolutely fantastic weekend,
> and
> > > then
> >

Re: [RESULT] [VOTE] Apache Ignite 2.7.0 Release (RC2)

[Petr Ivanov]

AFAIK, there is no such procedure yet and it definitely requires introduction.
I guess, thin client developers should share the process of updating official 
repositories.


> On 10 Dec 2018, at 09:49, Nikolay Izhikov  wrote:
> 
> Hello, Roman.
> 
> Do we have release procedure for this pacakage?
> Let's develop one.
> 
> Thin client developers, please,let me know, which artifacts should be 
> uploaded to which package manager system.
> 
> 
> В Пн, 10/12/2018 в 04:30 +, Roman Shtykh пишет:
>> Nikolay,
>> Do you know when npm (and other thin client) package will be uploaded?
>> 
>>   - $ npm i apache-ignite-client --save
>>   - npm ERR! code E404
>>   - npm ERR! 404 Not Found: apache-ignite-client@lates
>> 
>> 
>> -- Roman
>> 
>> 
>>On Thursday, December 6, 2018, 7:20:33 a.m. GMT+9, Prachi Garg 
>>  wrote:  
>> 
>> Hello Igniters,
>> 
>> The documentation for Apache Ignite 2.7.0 is now public on readme.io
>> .
>> 
>> -Prachi
>> 
>> On Wed, Dec 5, 2018 at 9:35 AM Nikolay Izhikov  wrote:
>> 
>>> Yes, Denis.
>>> 
>>> I will do my best to complete release steps today.
>>> The only things that blocks me is bintray permissions.
>>> They required to upload rpm and deb packages to corresponding repository.
>>> 
>>> I've created ticket to the INFRA [1]
>>> Seems, they, resolve it eventually.
>>> 
>>> We discussed this issue with other Igniters and decided to do release
>>> without rpm and deb. When I got permissions, I release them too.
>>> 
>>> [1] https://issues.apache.org/jira/browse/INFRA-17354
>>> 
>>> ср, 5 дек. 2018 г., 20:25 Denis Magda dma...@apache.org:
>>> 
 When are going to complete the post-release steps and announce the
>>> 
>>> release?
 Once the binaries are available on the website we need to release the
>>> 
>>> docs.
 
 
 I'm ready to prepare a blog post for blogs.apache.org.
 
 --
 Denis
 
 On Mon, Dec 3, 2018 at 11:14 PM Nikolay Izhikov 
 wrote:
 
> Sorry, Alex.
> 
> I miss your +1.
> Thank you, very much for checking RC artifacts.
> 
> вт, 4 дек. 2018 г., 7:10 Alexey Kuznetsov akuznet...@apache.org:
> 
>> Nikolay,
>> 
>> Actually 4 "+1"  binding.
>> 
>> You did not count my "+1".
>> 
>> :)
>> 
>> 
>> On Tue, Dec 4, 2018 at 4:28 AM Nikolay Izhikov 
>> wrote:
>> 
>>> Igniters,
>>> 
>>> Apache Ignite 2.7.0 release (RC2) has been accepted.
>>> 
>>> 3 "+1" binding votes received:
>>> 
>>> - Pavel Tupitsyn
>>> - Dmitriy Pavlov
>>> - Nikolay Izhikov
>>> 
>>> Vote thread:
>>> 
>>> 
>>> 
>>> 
>>> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-7-0-RC2-td38788.html
>>> 
>> 
>> 
>> --
>> Alexey Kuznetsov
>> 
>>> 
>>> 

[GitHub] ignite pull request #5357: IGNITE-10167: MVCC-compatible IgniteCache.localEn...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: About readme.io's latest docs

[李玉珏]

Prachi,


Can you help to export all the latest version of all documents to me?
I am ready to make a synchronization of the chinese version of the document.

thanks!


在 2018/6/2 上午4:38, Prachi Garg 写道:

Please see attached.

On Fri, Jun 1, 2018 at 9:22 AM, 李玉珏@163 <18624049...@163.com 
> wrote:


Prachi,


Can you help to export all the latest version of all documents to me?
I am ready to make a synchronization of the chinese version of the
document.

thanks!


在 2017/11/24 下午1:33, Prachi Garg 写道:

Attached.

On Wed, Nov 15, 2017 at 4:41 AM, 李玉珏@163 <18624049...@163.com
> wrote:

Prachi,


Can you help me to export all the latest version of all
documents to me?
I am ready to make a synchronization of the chinese version
of the document.

thanks!

在 2017/8/17 上午2:05, Prachi Garg 写道:

Please see attached.

-P

On Wed, Aug 9, 2017 at 11:19 AM, Denis Magda
mailto:dma...@gridgain.com>> wrote:

Hi!

Prachi is on vacation and will send you the latest
version as soon as she is back to work.

—
Denis


On Aug 7, 2017, at 5:33 AM, 李玉珏@163
<18624049...@163.com > wrote:


Prachi,


Can you help me to export all the latest version of all
documents to me?
I am ready to make a synchronization of the chinese
version of the document.

thanks!


在 2017/5/13 上午12:48, Prachi Garg 写道:

See attached for cpp, .net and integrations
documentation.

-P

On Fri, May 12, 2017 at 9:47 AM, Prachi Garg
mailto:pg...@gridgain.com>> wrote:

See attached for java, file-system, and tools
documentation.

-P

On Fri, May 12, 2017 at 5:39 AM, 李玉珏@163
<18624049...@163.com >
wrote:

Prachi,


Can you help me to export all the latest
version of all documents to me?
I am ready to make a synchronization of the
chinese version of the document.

thanks!


在 2017/3/18 04:54, Prachi Garg 写道:

Hi,

Please see attached.

-P

On Fri, Mar 17, 2017 at 4:56 AM, 李玉珏@163
<18624049...@163.com
> wrote:

Prachi,


Can you help me to export all the latest
version of all documents to me?
I am ready to make a synchronization of
the chinese version of the document.


在 2016/12/21 00:55, Prachi Garg 写道:

Hi,
I have attached the documentation for
Hadoop/Spark and Integrations.

-Prachi

On Tue, Dec 20, 2016 at 6:50 AM, 李玉珏@163
<18624049...@163.com
> wrote:

Hi,


Hadoop Accelerator，about MapR env's
install and config,is this part of
the document missing?


在 2016/12/19 11:24, Denis Magda 写道:

Hi,

Yes, the documentation is stable.
Prachi, could you help out with the
exporting?

—
Denis


On Dec 18, 2016, at 7:09 AM,
李玉珏@163 <18624049...@163.com
> wrote:

Prachi,

I would like to ask, 1.8 version
of the document, is now in a
stable state?
If it is stable, can you help me
to export the latest version of
all documents to me?
I am ready to make a
synchronization of the chinese
version of the document.

thanks！


在 2016/8/23 02:25, Prachi Garg 写道:

Hi,

I've attached the latest version
of Ignite and Hadoop/Spark
documentation. Let me know if
   

[GitHub] ignite pull request #5500: IGNITE-10366: MVCC: Create "Cache 1" test suite f...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #5585: IGNITE-10367: MVCC: Create "Cache 8" test suite f...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Created] (IGNITE-10620) [TC Bot] Implement Tracked Branches processor and IssueDetector unit tests

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-10620:
---

 Summary: [TC Bot] Implement Tracked Branches processor and 
IssueDetector unit tests
 Key: IGNITE-10620
 URL: https://issues.apache.org/jira/browse/IGNITE-10620
 Project: Ignite
  Issue Type: Task
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov


Implement actual tests for tracked branches processing and issue detectors. 
Skeletons:

org.apache.ignite.ci.tcbot.issue.IssueDetectorTest#testDetector

org.apache.ignite.ci.tcbot.chain.TrackedBranchProcessorTest#testTrackedBranchChainsProcessor

The actual challenge is refactoring of configuration to use not singletons, but 
some injected interfaces with mock-able alternatives, refactor scheduler, and 
any other refactorings needed to cover issue detection by test. 



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

[GitHub] ignite pull request #5409: IGNITE-10263: MVCC: Concurrent cache stop can cau...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] asfgit closed pull request #96: fix typo in schedulers

[GitBox]

asfgit closed pull request #96: fix typo in schedulers
URL: https://github.com/apache/ignite-teamcity-bot/pull/96
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/di/scheduler/NoOpSheduler.java
 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/di/scheduler/NoOpScheduler.java
similarity index 96%
rename from 
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/di/scheduler/NoOpSheduler.java
rename to 
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/di/scheduler/NoOpScheduler.java
index c4cae202..18d4362f 100644
--- 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/di/scheduler/NoOpSheduler.java
+++ 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/di/scheduler/NoOpScheduler.java
@@ -21,7 +21,7 @@
 /**
  * Sheduler which never waits
  */
-public class NoOpSheduler implements IScheduler {
+public class NoOpScheduler implements IScheduler {
 /** {@inheritDoc} */
 @Override public void invokeLater(Runnable cmd, long delay, TimeUnit unit) 
{
 
diff --git 
a/ignite-tc-helper-web/src/test/java/org/apache/ignite/ci/di/scheduler/DirectExecNoWaitSheduler.java
 
b/ignite-tc-helper-web/src/test/java/org/apache/ignite/ci/di/scheduler/DirectExecNoWaitScheduler.java
similarity index 95%
rename from 
ignite-tc-helper-web/src/test/java/org/apache/ignite/ci/di/scheduler/DirectExecNoWaitSheduler.java
rename to 
ignite-tc-helper-web/src/test/java/org/apache/ignite/ci/di/scheduler/DirectExecNoWaitScheduler.java
index a7f8904b..0b034fa4 100644
--- 
a/ignite-tc-helper-web/src/test/java/org/apache/ignite/ci/di/scheduler/DirectExecNoWaitSheduler.java
+++ 
b/ignite-tc-helper-web/src/test/java/org/apache/ignite/ci/di/scheduler/DirectExecNoWaitScheduler.java
@@ -21,7 +21,7 @@
 /**
  * Sheduler which never waits
  */
-public class DirectExecNoWaitSheduler implements IScheduler {
+public class DirectExecNoWaitScheduler implements IScheduler {
 /** {@inheritDoc} */
 @Override public void invokeLater(Runnable cmd, long delay, TimeUnit unit) 
{
 cmd.run();
diff --git 
a/ignite-tc-helper-web/src/test/java/org/apache/ignite/ci/teamcity/ignited/IgnitedTcInMemoryIntegrationTest.java
 
b/ignite-tc-helper-web/src/test/java/org/apache/ignite/ci/teamcity/ignited/IgnitedTcInMemoryIntegrationTest.java
index 1a7d64cb..51403a47 100644
--- 
a/ignite-tc-helper-web/src/test/java/org/apache/ignite/ci/teamcity/ignited/IgnitedTcInMemoryIntegrationTest.java
+++ 
b/ignite-tc-helper-web/src/test/java/org/apache/ignite/ci/teamcity/ignited/IgnitedTcInMemoryIntegrationTest.java
@@ -39,9 +39,9 @@
 import org.apache.ignite.ci.analysis.SuiteInBranch;
 import org.apache.ignite.ci.analysis.TestInBranch;
 import org.apache.ignite.ci.db.TcHelperDb;
-import org.apache.ignite.ci.di.scheduler.DirectExecNoWaitSheduler;
+import org.apache.ignite.ci.di.scheduler.DirectExecNoWaitScheduler;
 import org.apache.ignite.ci.di.scheduler.IScheduler;
-import org.apache.ignite.ci.di.scheduler.NoOpSheduler;
+import org.apache.ignite.ci.di.scheduler.NoOpScheduler;
 import org.apache.ignite.ci.tcbot.chain.PrChainsProcessorTest;
 import org.apache.ignite.ci.tcmodel.changes.ChangesList;
 import org.apache.ignite.ci.tcmodel.conf.BuildType;
@@ -170,7 +170,7 @@ public void saveAndLoadBuildReference() throws IOException {
 Injector injector = Guice.createInjector(module, new AbstractModule() {
 @Override protected void configure() {
 bind(Ignite.class).toInstance(ignite);
-bind(IScheduler.class).to(DirectExecNoWaitSheduler.class);
+bind(IScheduler.class).to(DirectExecNoWaitScheduler.class);
 }
 });
 
@@ -240,7 +240,7 @@ public void saveAndLoadBuildTypes() throws IOException, 
JAXBException {
 Injector injector = Guice.createInjector(module, new AbstractModule() {
 @Override protected void configure() {
 bind(Ignite.class).toInstance(ignite);
-bind(IScheduler.class).to(DirectExecNoWaitSheduler.class);
+bind(IScheduler.class).to(DirectExecNoWaitScheduler.class);
 }
 });
 
@@ -341,7 +341,7 @@ public void 
incrementalActualizationOfBuildsContainsQueued() throws IOException
 Injector injector = Guice.createInjector(module, new AbstractModule() {
 @Override protected void configure() {
 bind(Ignite.class).toInstance(ignite);
-bind(IScheduler.class).to(NoOpSheduler.class);
+bind(IScheduler.class).to(NoOpScheduler.class);
 }
 });
 
@@ -481,7 +481,7 @@ private void saveTmpFile(Object obj, String name) throws 
IOException, JAXBExcept
 
 @Test
 public void testRunHistSaveLoad() {
-  

[GitHub] asfgit closed pull request #94: Visa History page fix

[GitBox]

asfgit closed pull request #94: Visa History page fix
URL: https://github.com/apache/ignite-teamcity-bot/pull/94
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildObserver.java
 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildObserver.java
index 3de27fad..88a858e6 100644
--- 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildObserver.java
+++ 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildObserver.java
@@ -20,9 +20,11 @@
 import java.util.Objects;
 import java.util.Timer;
 import javax.inject.Inject;
-import org.apache.ignite.ci.IAnalyticsEnabledTeamcity;
 import org.apache.ignite.ci.ITcHelper;
 import org.apache.ignite.ci.tcmodel.result.Build;
+import org.apache.ignite.ci.teamcity.ignited.IStringCompactor;
+import org.apache.ignite.ci.teamcity.ignited.ITeamcityIgnited;
+import org.apache.ignite.ci.teamcity.ignited.ITeamcityIgnitedProvider;
 import org.apache.ignite.ci.user.ICredentialsProv;
 import org.apache.ignite.ci.web.model.ContributionKey;
 import org.slf4j.Logger;
@@ -48,6 +50,12 @@
 /** Helper. */
 @Inject private ITcHelper tcHelper;
 
+/** */
+@Inject private ITeamcityIgnitedProvider teamcityIgnitedProvider;
+
+/** */
+@Inject private IStringCompactor strCompactor;
+
 /**
  */
 @Inject
@@ -109,11 +117,11 @@ public String getObservationStatus(ContributionKey key) {
 
 ICredentialsProv creds = tcHelper.getServerAuthorizerCreds();
 
-IAnalyticsEnabledTeamcity teamcity = tcHelper.server(key.srvId, creds);
+ITeamcityIgnited teamcity = teamcityIgnitedProvider.server(key.srvId, 
creds);
 
 if (Objects.nonNull(buildsInfo)) {
 sb.append(buildsInfo.ticket).append(" to be commented, waiting for 
builds. ");
-sb.append(buildsInfo.finishedBuildsCount(teamcity));
+sb.append(buildsInfo.finishedBuildsCount(teamcity, strCompactor));
 sb.append(" builds done from ");
 sb.append(buildsInfo.buildsCount());
 }
diff --git 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildsInfo.java
 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildsInfo.java
index ad1b548c..bbd01daa 100644
--- 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildsInfo.java
+++ 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildsInfo.java
@@ -24,9 +24,10 @@
 import java.util.Date;
 import java.util.List;
 import java.util.Objects;
-import org.apache.ignite.ci.IAnalyticsEnabledTeamcity;
 import org.apache.ignite.ci.tcmodel.result.Build;
 import org.apache.ignite.ci.teamcity.ignited.IStringCompactor;
+import org.apache.ignite.ci.teamcity.ignited.ITeamcityIgnited;
+import org.apache.ignite.ci.teamcity.ignited.fatbuild.FatBuildCompacted;
 import org.apache.ignite.ci.user.ICredentialsProv;
 import org.apache.ignite.ci.web.model.ContributionKey;
 
@@ -103,20 +104,21 @@ public BuildsInfo(String srvId, ICredentialsProv prov, 
String ticket, String bra
 
 /**
  * @param teamcity Teamcity.
+ * @param strCompactor {@link IStringCompactor} instance.
  *
  * @return One of {@link #FINISHED_STATUS}, {@link #CANCELLED_STATUS} or
  * {@link #RUNNING_STATUS} statuses.
  */
-public String getStatus(IAnalyticsEnabledTeamcity teamcity) {
+public String getStatus(ITeamcityIgnited teamcity, IStringCompactor 
strCompactor) {
 boolean isFinished = true;
 
 for (Integer id : builds) {
-Build build = teamcity.getBuild(id);
+FatBuildCompacted build = teamcity.getFatBuild(id);
 
-if (build.isUnknown())
+if (build.isFakeStub() || build.isCancelled(strCompactor))
 return CANCELLED_STATUS;
 
-if (!build.isFinished())
+if (!build.isFinished(strCompactor))
 isFinished = false;
 }
 
@@ -125,16 +127,18 @@ public String getStatus(IAnalyticsEnabledTeamcity 
teamcity) {
 
 /**
  * @param teamcity Teamcity.
+ * @param strCompactor {@link IStringCompactor} instance.
  */
-public boolean isFinished(IAnalyticsEnabledTeamcity teamcity) {
-return FINISHED_STATUS.equals(getStatus(teamcity));
+public boolean isFinished(ITeamcityIgnited teamcity, IStringCompactor 
strCompactor) {
+return FINISHED_STATUS.equals(getStatus(teamcity, strCompactor));
 }
 
 /**
  * @param teamcity Teamcity.
+ * @param strCompactor {@link IStringCompactor} instance.
  */
-public boolean isCancelled(IAnalyticsEnabledTeamcity teamcity) {
-return CANCELLED_STATUS.equals(getStatus(teamcity));
+   

[jira] [Created] (IGNITE-10621) Track all running queries

[Yury Gerzhedovich (JIRA)]

Yury Gerzhedovich created IGNITE-10621:
--

 Summary: Track all running queries
 Key: IGNITE-10621
 URL: https://issues.apache.org/jira/browse/IGNITE-10621
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Yury Gerzhedovich
Assignee: Yury Gerzhedovich
 Fix For: 2.8


As of now Ignite track running queries in few places and use 
GridRunningQueryInfo to keep information about each of running query.

Unfortunately we track not all running queries. Need to track all DML and 
Select queries. Be able to distinguish user initial queries and system 
auxiliary queries, e.g. map/reduce queries or select for DML operations.

 



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

[GitHub] ignite pull request #4685: IGNITE-4111

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #5572: IGNITE-9630

[devozerov]

Github user devozerov closed the pull request at:

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


---

[GitHub] ignite pull request #5593: IGNITE-10578

[devozerov]

Github user devozerov closed the pull request at:

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


---

[GitHub] ignite pull request #5590: IGNITE-8626: ODBC and C++ thin now support OpenSS...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #5620: IGNITE-10621

[ygerzhedovich]

GitHub user ygerzhedovich opened a pull request:

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

IGNITE-10621



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

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

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

https://github.com/apache/ignite/pull/5620.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 #5620


commit 6f8dd8726b7bf0039a038491f384c346222d37be
Author: Yury Gerzhedovich 
Date:   2018-12-10T12:57:39Z

IGNITE-10621: Start work on tracking all running queries




---

Re: Default failure handler was changed for tests

[Dmitriy Pavlov]

Anton, I was expecting that you revert, because you wanted to do it.

Provided that I agree that fix could be reverted because of both functional
and style possible improvements, does not mean I believe it is the only
option and it should be reverted.

Even if I agree to revert doesn't mean all community agrees, so reverting
just 1 minute after writing to dev list would be strange. I believe we
should be courteous enough to give a couple of days for people to come and
give feedback.

So if you have a spare minute, please go ahead. If not, I can do it later.

пн, 10 дек. 2018 г. в 14:23, Anton Vinogradov :

> Dmitriy,
>
> You confirmed that fix should be reverted and reworked last Friday.
> Why it still not reverted?
>
> On Mon, Dec 10, 2018 at 12:46 AM Dmitrii Ryabov 
> wrote:
>
> > Agree, it is reasonable to revert.
> > пт, 7 дек. 2018 г. в 18:44, Dmitriy Pavlov :
> > >
> > > Hi Ilya,
> > >
> > > thank you for noticing.
> > >
> > > Calling to fail is equal to re-throw,
> > >
> > > throw new AssertionFailedError(message);
> > >
> > > So, yes, for now it is absolutely valid reason to revert and rework fix
> > >
> > > - as Nikolay suggested to reduce method override ocurrences.
> > > - and with transferring this exception into GridAbstractTest and
> > > correctly failing test.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > >
> > > пт, 7 дек. 2018 г. в 18:38, Ilya Lantukh :
> > >
> > > > Unfortunately, this FailureHandler doesn't seem to work. I wrote a
> test
> > > > that reproduces a bug and should fail. It prints the following text
> > into
> > > > log, but the test still passes "successfully":
> > > >
> > > > [2018-12-07
> > > >
> > > >
> >
> 18:28:23,800][ERROR][sys-stripe-1-#345%recovery.GridPointInTimeRecoveryCacheNoAffinityExchangeTest1%][IgniteTestResources]
> > > > Critical system error detected. Will be handled accordingly to
> > configured
> > > > handler [hnd=TestFailingFailureHandler [], failureCtx=FailureContext
> > > > [type=CRITICAL_ERROR, err=java.lang.IllegalStateException: Unable to
> > find
> > > > consistentId by UUID [nodeId=80dd2ec6-1913-4a5c-a839-630315c3,
> > > > topVer=AffinityTopologyVersion [topVer=12, minorTopVer=0
> > > > java.lang.IllegalStateException: Unable to find consistentId by UUID
> > > > [nodeId=80dd2ec6-1913-4a5c-a839-630315c3,
> > > > topVer=AffinityTopologyVersion [topVer=12, minorTopVer=0]]
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.managers.discovery.ConsistentIdMapper.mapToCompactId(ConsistentIdMapper.java:62)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.managers.discovery.ConsistentIdMapper.mapToCompactIds(ConsistentIdMapper.java:123)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.newTxRecord(IgniteTxManager.java:2507)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.logTxRecord(IgniteTxManager.java:2483)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.state(IgniteTxAdapter.java:1226)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.state(IgniteTxAdapter.java:1054)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.startRemoteTx(IgniteTxHandler.java:1836)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxPrepareRequest(IgniteTxHandler.java:1180)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$400(IgniteTxHandler.java:118)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$5.apply(IgniteTxHandler.java:222)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$5.apply(IgniteTxHandler.java:220)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1059)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:584)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:383)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:309)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:100)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:299)
> > > > at
> > > >
> > > >
> >
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(Grid

[jira] [Created] (IGNITE-10622) Undelivered ensure message to some nodes

[Anton Kalashnikov (JIRA)]

Anton Kalashnikov created IGNITE-10622:
--

 Summary: Undelivered ensure message to some nodes
 Key: IGNITE-10622
 URL: https://issues.apache.org/jira/browse/IGNITE-10622
 Project: Ignite
  Issue Type: Bug
Reporter: Anton Kalashnikov
Assignee: Anton Kalashnikov


We have follow case:
* Grid from 5 nodes(node1, node2, node3, node4, node5)
* node1 detect that node4 was failed and send NodeFailed message to node2
* node2 send NodeFailedNode3 message to node3
* node3 accepted message but does not handle because it also failed
* node1 detect that node3 was failed and send NodeFailed message to node2
* node2 select new next node(node4) and send NodeFailedNode3 message to node4

As result node4 received only NodeFailedNode3 but don't received 
NodeFailedNode3.

This case also valid for other ensure message which sending  one after another.



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

[GitHub] ignite pull request #5563: IGNITE-10511 removeExplicitNodeLocks() removed.

[voropava]

Github user voropava closed the pull request at:

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


---

[GitHub] ignite pull request #5425: IGNITE-10300 Fixed correct message in case of use...

[voropava]

Github user voropava closed the pull request at:

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


---

[GitHub] ignite pull request #5621: Ignite 2.5.1 p162

[voropava]

GitHub user voropava opened a pull request:

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

Ignite 2.5.1 p162



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

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

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

https://github.com/apache/ignite/pull/5621.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 #5621


commit 2528435ec946c479f6bf4eb7eaeabf092a0536a3
Author: devozerov 
Date:   2018-07-31T14:15:49Z

IGNITE-9114: SQL: use query time in retry timeout calculation. This closes 
#4460.

commit 98d0ccc729e647a4ad8876e2d29423904e6fa6ca
Author: devozerov 
Date:   2018-07-31T14:18:49Z

Merge remote-tracking branch 'upstream/ignite-2.5.1-master' into 
ignite-2.5.1-master

commit c78a7f215699f65983edfcc0c9014d9e3108f381
Author: Anton Kalashnikov 
Date:   2018-08-01T09:23:03Z

IGNITE-8757 idle_verify utility doesn't show both update counter and hash 
conflicts

(cherry picked from commit 9131e4d)

commit 66369583096b04d71c3f82e1ebfd1922ae6b0b6a
Author: Anton Kalashnikov 
Date:   2018-07-31T13:13:27Z

IGNITE-8973 Calculate partition hash and print into standard output

Signed-off-by: Andrey Gura 

(cherry picked from commit 8309cef)

commit e92788d392d4c60f76c4fd0f38c52669f4e3e772
Author: Evgeny Stanilovskiy 
Date:   2018-08-01T11:05:58Z

IGNITE-8939 Catch and proper propagate transaction string reprsentation - 
Fixes #4454.

Signed-off-by: Dmitriy Pavlov 
(cherry picked from commit 458480c5b0520aa8e28935361a37ab49e1e65ff6)

commit 60155cb55ca35790da7f80ae167dd7fb3f3793fd
Author: Andrey V. Mashenkov 
Date:   2018-08-01T10:23:32Z

IGNITE-9154: Fixed conflict version passed to events for ATOMIC cache. This 
closes #4463.

(cherry picked from commit 3ea3a56)

commit 15d72fc022f64939fee336438256460024ca59c0
Author: Andrey V. Mashenkov 
Date:   2018-08-01T12:58:22Z

Merge remote-tracking branch 'origin/ignite-2.5.1-master' into 
ignite-2.5.1-master

commit 158f36de551e860176ac7f3bcf92e9751039a35c
Author: ilantukh 
Date:   2018-08-01T13:31:15Z

IGNITE-8900 SqlFieldsQuery provides incorrect result when item size exceeds 
page size.

(cherry picked from commit f1ecbbc)

commit ef331f3ba58da49746f34546f1972cf65c083b3d
Author: Maxim Muzafarov 
Date:   2018-08-01T15:39:54Z

IGNITE-7165 Re-balancing is cancelled if client node joins

Signed-off-by: Anton Vinogradov 
(cherry picked from commit 137dd06aaee9cc84104e6b4bf48306b050341e3a)

commit cfe95a1b1762501dd9ac48a1a24228ac0bc3b5c3
Author: Pavel Kovalenko 
Date:   2018-08-02T12:51:17Z

IGNITE-9111 Do not wait for deactivation.

Signed-off-by: agura 

(cherry picked from commit 8811a14)

commit 2e43db33e09e1ed456ccaf3e9361e9b2f07f99a7
Author: Pavel Kovalenko 
Date:   2018-08-02T13:18:44Z

IGNITE-9129 P2P class deployment with ZK discovery fixed.

Signed-off-by: agura 

(cherry picked from commit 0e9bb1c)

commit d1ae06b8a2adbb1890b7e0605708dddb52cd0d29
Author: Ivan Daschinskiy 
Date:   2018-08-02T15:57:22Z

IGNITE-8869 PartitionsExchangeOnDiscoveryHistoryOverflowTest hangs on 
TeamCity. - Fixes #4277.

Signed-off-by: Dmitriy Pavlov 
(cherry picked from commit b718e4438e469ad0341f1bf9a605c2fe3ab5970c)

commit c9ebbb2c2b8f1a1ebaac21586fa56ea6f57a7bb0
Author: Vitaliy Biryukov 
Date:   2018-07-30T17:33:04Z

IGNITE-9127 ZooKeeper (Discovery) 1 suite hang, JMX logging disabled for ZK 
- Fixes #4450.

Signed-off-by: Dmitriy Pavlov 
(cherry picked from commit 774ed773a6786cbcd4e6ca7f12290211f4f52201)

commit c191c75e67be4819b3c5b243dfdfb58f2e8240e2
Author: Sergey Chugunov 
Date:   2018-04-28T13:52:44Z

IGNITE-8252 NPE is replaced with IgniteException with meaningful message - 
Fixes #3908.

Signed-off-by: dspavlov 
(cherry picked from commit 5135f82f3f53eddef9ab91da2e647e14488b2d5a)

commit 63b4c4d2a479b957b6aa5cb00ac31c749e40cdfe
Author: Anton Vinogradov 
Date:   2018-07-23T10:18:16Z

IGNITE-8783 Failover tests periodically cause hanging of the whole Data 
Structures suite on TC

Signed-off-by: Anton Vinogradov 
(cherry picked from commit 6582b084943ac63c36b062c8ae66b43883ef6c19)

commit aa4a9b09dfd25a628cef62a92decd6c583141025
Author: Anton Kalashnikov 
Date:   2018-07-23T13:48:18Z

IGNITE-8998 Send reconnect exception without partitions - Fixes #4358.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit 78e0bb7efbc53e969c4c4918b6c6272c7b98dc36)

commit 7e89cf89088f11d282f79c331897d17d7db00ed2
Author: EdShangGG 
Date:   2018-07-17T14:19:36Z

IGNITE-9012 Fixed exchange await logic in GridServiceProcessor - Fixes 
#4367.

(cherry picked from commit 66e547a9eebf3e8354135b3300619754294a805d)

commit 52cf2809a759071d44071

Re: Default failure handler was changed for tests

[Dmitriy Pavlov]

Reverted.

https://issues.apache.org/jira/browse/IGNITE-8227 reopened

пн, 10 дек. 2018 г. в 16:23, Dmitriy Pavlov :

> Anton, I was expecting that you revert, because you wanted to do it.
>
> Provided that I agree that fix could be reverted because of both
> functional and style possible improvements, does not mean I believe it is
> the only option and it should be reverted.
>
> Even if I agree to revert doesn't mean all community agrees, so reverting
> just 1 minute after writing to dev list would be strange. I believe we
> should be courteous enough to give a couple of days for people to come and
> give feedback.
>
> So if you have a spare minute, please go ahead. If not, I can do it later.
>
> пн, 10 дек. 2018 г. в 14:23, Anton Vinogradov :
>
>> Dmitriy,
>>
>> You confirmed that fix should be reverted and reworked last Friday.
>> Why it still not reverted?
>>
>> On Mon, Dec 10, 2018 at 12:46 AM Dmitrii Ryabov 
>> wrote:
>>
>> > Agree, it is reasonable to revert.
>> > пт, 7 дек. 2018 г. в 18:44, Dmitriy Pavlov :
>> > >
>> > > Hi Ilya,
>> > >
>> > > thank you for noticing.
>> > >
>> > > Calling to fail is equal to re-throw,
>> > >
>> > > throw new AssertionFailedError(message);
>> > >
>> > > So, yes, for now it is absolutely valid reason to revert and rework
>> fix
>> > >
>> > > - as Nikolay suggested to reduce method override ocurrences.
>> > > - and with transferring this exception into GridAbstractTest and
>> > > correctly failing test.
>> > >
>> > > Sincerely,
>> > > Dmitriy Pavlov
>> > >
>> > >
>> > > пт, 7 дек. 2018 г. в 18:38, Ilya Lantukh :
>> > >
>> > > > Unfortunately, this FailureHandler doesn't seem to work. I wrote a
>> test
>> > > > that reproduces a bug and should fail. It prints the following text
>> > into
>> > > > log, but the test still passes "successfully":
>> > > >
>> > > > [2018-12-07
>> > > >
>> > > >
>> >
>> 18:28:23,800][ERROR][sys-stripe-1-#345%recovery.GridPointInTimeRecoveryCacheNoAffinityExchangeTest1%][IgniteTestResources]
>> > > > Critical system error detected. Will be handled accordingly to
>> > configured
>> > > > handler [hnd=TestFailingFailureHandler [], failureCtx=FailureContext
>> > > > [type=CRITICAL_ERROR, err=java.lang.IllegalStateException: Unable to
>> > find
>> > > > consistentId by UUID [nodeId=80dd2ec6-1913-4a5c-a839-630315c3,
>> > > > topVer=AffinityTopologyVersion [topVer=12, minorTopVer=0
>> > > > java.lang.IllegalStateException: Unable to find consistentId by UUID
>> > > > [nodeId=80dd2ec6-1913-4a5c-a839-630315c3,
>> > > > topVer=AffinityTopologyVersion [topVer=12, minorTopVer=0]]
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.managers.discovery.ConsistentIdMapper.mapToCompactId(ConsistentIdMapper.java:62)
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.managers.discovery.ConsistentIdMapper.mapToCompactIds(ConsistentIdMapper.java:123)
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.newTxRecord(IgniteTxManager.java:2507)
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.logTxRecord(IgniteTxManager.java:2483)
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.state(IgniteTxAdapter.java:1226)
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.state(IgniteTxAdapter.java:1054)
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.startRemoteTx(IgniteTxHandler.java:1836)
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxPrepareRequest(IgniteTxHandler.java:1180)
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$400(IgniteTxHandler.java:118)
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$5.apply(IgniteTxHandler.java:222)
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$5.apply(IgniteTxHandler.java:220)
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1059)
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:584)
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:383)
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:309)
>> > > > at
>> > > >
>> > > >
>> >
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoM

[jira] [Created] (IGNITE-10623) Possible JVM crash in case of stopping node with errors

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-10623:
--

 Summary: Possible JVM crash in case of stopping node with errors
 Key: IGNITE-10623
 URL: https://issues.apache.org/jira/browse/IGNITE-10623
 Project: Ignite
  Issue Type: Bug
Reporter: Eduard Shangareev
Assignee: Eduard Shangareev


{noformat}
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x03a23bde, pid=5444, 
tid=0x18d0
#
# JRE version: Java(TM) SE Runtime Environment (8.0_102-b14) (build 
1.8.0_102-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.102-b14 mixed mode 
windows-amd64 compressed oops)
# Problematic frame:
# J 25052 C2 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(IJZ)J
 (1421 bytes) @ 0x03a23bde [0x03a23800+0x3de]
#
# Core dump written. Default location: 
C:\BuildAgent\work\81a8bed9f07f3feb\ggprivate\hs_err_pid5444.mdmp
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
{noformat}

Seems that it was caused by an erroneous stop on a node which left 
checkpoint-thread alive.



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

[GitHub] ignite pull request #5622: IGNITE-10472: MVCC: Add Dependency Injection supp...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-10472: MVCC: Add Dependency Injection support for EntryProcessor.



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

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

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

https://github.com/apache/ignite/pull/5622.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 #5622


commit 7a04e55babb9fdfc7d489319bb09149e6f874519
Author: Andrey V. Mashenkov 
Date:   2018-12-10T14:38:05Z

IGNITE-10472: Add Dependency Injection support for EntryProcessor in mvcc 
mode.




---

[GitHub] ignite pull request #5623: IGNITE-10623 Possible JVM crash when node stopped...

[EdShangGG]

GitHub user EdShangGG opened a pull request:

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

IGNITE-10623 Possible JVM crash when node stopped with errors



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

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

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

https://github.com/apache/ignite/pull/5623.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 #5623


commit 5b3a7333173af73212bc63978976bdb6dfc30857
Author: EdShangGG 
Date:   2018-12-10T14:43:29Z

IGNITE-10623 Possible JVM crash when node stopped with errors




---

[GitHub] ignite pull request #5624: IGNITE-10556 Skip records deserialization on reco...

[Jokser]

GitHub user Jokser opened a pull request:

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

IGNITE-10556 Skip records deserialization on recovery



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

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

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

https://github.com/apache/ignite/pull/5624.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 #5624


commit 64f2f9c1c4ef5f60545fd211ef1abb4297284f0e
Author: Pavel Kovalenko 
Date:   2018-12-07T14:03:38Z

IGNITE-10556 Remove metastoreOnly flag

Signed-off-by: Pavel Kovalenko 

commit db4ce1a2ede33421624b8d0a71b21fb6f736c573
Author: Pavel Kovalenko 
Date:   2018-12-07T15:45:08Z

IGNITE-10556 WIP

Signed-off-by: Pavel Kovalenko 

commit 476077be82bb42bfbdf545b2cf9137d7780d432f
Author: Pavel Kovalenko 
Date:   2018-12-10T14:43:33Z

IGNITE-10556 WIP

Signed-off-by: Pavel Kovalenko 

commit c4a305b3109812f68e2431c4818bf11dd2720c03
Author: Pavel Kovalenko 
Date:   2018-12-10T14:44:55Z

Merge branch 'master' into ignite-10556

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/GridCacheDatabaseSharedManager.java




---

[GitHub] ignite pull request #5625: IGNITE-8717 Cache configuration was moved to meta...

[antonovsergey93]

GitHub user antonovsergey93 opened a pull request:

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

IGNITE-8717 Cache configuration was moved to metastore



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

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

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

https://github.com/apache/ignite/pull/5625.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 #5625


commit d95e8a78f1e71174c130b3b9bbc89f686e6f35ff
Author: Sergey Antonov 
Date:   2018-11-20T13:42:46Z

IGNITE-8717 Move cache configuration to metastore.

commit 22dc40f634e502cef32c72512db7647cfcdf1e9e
Author: Sergey Antonov 
Date:   2018-11-20T13:43:39Z

IGNITE-8717 Move cache configuration to metastore.

commit be9ea5710d680bb7be791ee0c3be4abedc575309
Author: Sergey Antonov 
Date:   2018-11-20T15:20:48Z

IGNITE-8717 Add GridCacheConfigurationVersion and tests for it.

commit c2441d1ae63ec6f86f7a0089c5c03df483d858a3
Author: Sergey Antonov 
Date:   2018-12-10T14:53:17Z

Merge branch 'master' into ignite-8717




---

[GitHub] ignite pull request #5425: IGNITE-10300 Fixed correct message in case of use...

[voropava]

GitHub user voropava reopened a pull request:

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

IGNITE-10300 Fixed correct message in case of user/password retries e…

…xceeded.

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

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

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

https://github.com/apache/ignite/pull/5425.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 #5425


commit 82c57cbf0a42057c9c4a7aea26dbdf7da8542a3e
Author: Pavel Voronkin 
Date:   2018-11-09T12:00:03Z

IGNITE-10300 Fixed correct message in case of user/password retries 
exceeded.

commit 5b81779cf40aff39c4ef865f7e73af59ca2a0d93
Author: Pavel Voronkin 
Date:   2018-10-10T08:57:11Z

IGNITE-10300 Fixed review comments.




---

[GitHub] ignite pull request #5626: IGNITE-10359: Add deployment feature for EntryPro...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-10359: Add deployment feature for EntryProcessor.



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

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

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

https://github.com/apache/ignite/pull/5626.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 #5626


commit a55946f374c8fbfb358e3219ed0b4bcf842afa5b
Author: Andrey V. Mashenkov 
Date:   2018-12-10T15:13:56Z

IGNITE-10359: Add deployment feature for EntryProcessor.




---

[GitHub] ignite pull request #5627: IGNITE-10464: MVCC: Create "PDS 4" test suite for...

[rkondakov]

GitHub user rkondakov opened a pull request:

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

IGNITE-10464: MVCC: Create "PDS 4" test suite for MVCC mode.



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

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

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

https://github.com/apache/ignite/pull/5627.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 #5627


commit f76b5497eec9c8026ee65fc49c21aedc4df265f4
Author: rkondakov 
Date:   2018-12-07T15:04:52Z

IGNITE-10464: MVCC: Create "PDS 4" test suite for MVCC mode.




---

[GitHub] ignite pull request #5628: IGNITE-10622 to sent pending messages when new ne...

[akalash]

GitHub user akalash opened a pull request:

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

IGNITE-10622 to sent pending messages when new next node was selected



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

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

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

https://github.com/apache/ignite/pull/5628.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 #5628


commit 2f301f3ebed56c787e23e9aeaf7b77c730ef4345
Author: Anton Kalashnikov 
Date:   2018-12-10T15:41:25Z

IGNITE-10622 to sent pending messages when new next node was selected




---

Clean up of our PRs and IEPs before 2019

[Dmitriy Pavlov]

Hi Igniters,

Newcomers to Apache Ignite sometimes became concerned about many open PRs
in the project. Apache Ignite TC Bot also performs runs checks with a PR
open. Apache Ignite pulls list https://github.com/apache/ignite/pulls contains
1442 PRs open while only 84 issues are waiting for review.

Could you please verify the list of your PRs in Apache Ignite
https://github.com/pulls  and close every not needed/already merged change?

The same proposal is related to IEP statuses. If you were involved in an
IEP, please validate its status here
https://cwiki.apache.org/confluence/display/IGNITE/Active+Proposals  Please
set a correct state for your IEP, as well.

Should you have any questions, please don't hesitate to ask here. Thank you
in advance!

Sincerely,
Dmitriy Pavlov

[GitHub] ignite pull request #3919: Ignite 2.4.2 p10

[zstan]

Github user zstan closed the pull request at:

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


---

[GitHub] ignite pull request #4239: IGNITE-8849

[EdShangGG]

Github user EdShangGG closed the pull request at:

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


---

[GitHub] ignite pull request #1481: IGNITE-4552 support eviction for dhtLocalPartitio...

[zstan]

Github user zstan closed the pull request at:

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


---

[GitHub] ignite pull request #1522: IGNITE-4484 fix not compliant with tx isolation s...

[zstan]

Github user zstan closed the pull request at:

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


---

[GitHub] zzzadruga commented on a change in pull request #95: IGNITE-9542: new run history stripe

[GitBox]

zzzadruga commented on a change in pull request #95: IGNITE-9542: new run 
history stripe
URL: https://github.com/apache/ignite-teamcity-bot/pull/95#discussion_r240279974
 
 

 ##
 File path: 
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/issue/IssueDetector.java
 ##
 @@ -446,9 +463,9 @@ protected String checkFailuresEx(String brachName) {
 backgroundOpsCreds
 );
 
-registerIssuesAndNotifyLater(failures, backgroundOpsCreds);
+String issResult = registerIssuesAndNotifyLater(failures, 
backgroundOpsCreds);
 
 Review comment:
   if #registerIssuesAndNotifyLater returns null (if creds == null), method 
return string like "Tests 4 Suites 3 were checked. **null**"


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] ignite pull request #2779: IGNITE-6437: DataStructure can not be obtained on...

[zstan]

Github user zstan closed the pull request at:

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


---

[GitHub] dspavlov commented on a change in pull request #95: IGNITE-9542: new run history stripe

[GitBox]

dspavlov commented on a change in pull request #95: IGNITE-9542: new run 
history stripe
URL: https://github.com/apache/ignite-teamcity-bot/pull/95#discussion_r240287246
 
 

 ##
 File path: 
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/issue/IssueDetector.java
 ##
 @@ -446,9 +463,9 @@ protected String checkFailuresEx(String brachName) {
 backgroundOpsCreds
 );
 
-registerIssuesAndNotifyLater(failures, backgroundOpsCreds);
+String issResult = registerIssuesAndNotifyLater(failures, 
backgroundOpsCreds);
 
 Review comment:
   Yes, I agree, but this string will go to the monitoring, so it is better to 
see null showing there is some unexpected behavior there.


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] ignite pull request #3144: IGNITE-7112 More informative: Failed to wait PME

[zstan]

Github user zstan closed the pull request at:

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


---

[GitHub] ignite pull request #1493: IGNITE-4654 GridMarshallerPerformanceTest#testGri...

[zstan]

Github user zstan closed the pull request at:

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


---

[GitHub] ignite pull request #1544: IGNITE-4710: extended optimistic tx lock conflict...

[zstan]

Github user zstan closed the pull request at:

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


---

[GitHub] ignite pull request #1922: IGNITE-5125, improve logging in case of hang whil...

[zstan]

Github user zstan closed the pull request at:

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


---

[GitHub] ignite pull request #1955: IGNITE-5100 don`t remove active exchange events f...

[zstan]

Github user zstan closed the pull request at:

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


---

[GitHub] ignite pull request #2482: IGNITE-5869 client hangs infinitely while binary ...

[zstan]

Github user zstan closed the pull request at:

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


---

[GitHub] asfgit closed pull request #95: IGNITE-9542: new run history stripe

[GitBox]

asfgit closed pull request #95: IGNITE-9542: new run history stripe
URL: https://github.com/apache/ignite-teamcity-bot/pull/95
 
 
   


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] ignite pull request #2986: IGNITE-5955: IgniteCacheContinuousQueryClientReco...

[zstan]

Github user zstan closed the pull request at:

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


---

[GitHub] ignite pull request #3190: IGNITE-3935: Switch to the peer-class-loading loa...

[zstan]

Github user zstan closed the pull request at:

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


---

Re: Clean up of our PRs and IEPs before 2019

[Nikolay Izhikov]

Hello, Dmitriy.

What, exactly concerns newcomers?
What is wrong with opened PR?
How project will benefit from closed PR?

> The same proposal is related to IEP statuses. If you were involved in an
IEP, please validate its status

+1. We should maintain IEP description up to date.

пн, 10 дек. 2018 г., 19:15 Dmitriy Pavlov dpav...@apache.org:

> Hi Igniters,
>
> Newcomers to Apache Ignite sometimes became concerned about many open PRs
> in the project. Apache Ignite TC Bot also performs runs checks with a PR
> open. Apache Ignite pulls list https://github.com/apache/ignite/pulls
> contains
> 1442 PRs open while only 84 issues are waiting for review.
>
> Could you please verify the list of your PRs in Apache Ignite
> https://github.com/pulls  and close every not needed/already merged
> change?
>
> The same proposal is related to IEP statuses. If you were involved in an
> IEP, please validate its status here
> https://cwiki.apache.org/confluence/display/IGNITE/Active+Proposals
> Please
> set a correct state for your IEP, as well.
>
> Should you have any questions, please don't hesitate to ask here. Thank you
> in advance!
>
> Sincerely,
> Dmitriy Pavlov
>

[GitHub] ignite pull request #2121: IGNITE-1583: fix test, removeNode partition id up...

[zstan]

Github user zstan closed the pull request at:

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


---

[jira] [Created] (IGNITE-10624) Cache deployment id may be different that cluster-wide after recovery

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-10624:


 Summary: Cache deployment id may be different that cluster-wide 
after recovery
 Key: IGNITE-10624
 URL: https://issues.apache.org/jira/browse/IGNITE-10624
 Project: Ignite
  Issue Type: Bug
  Components: cache, sql
Affects Versions: 2.8
Reporter: Pavel Kovalenko
Assignee: Pavel Kovalenko
 Fix For: 2.8


When schema for a cache is changing 
(GridQueryProcessor#processSchemaOperationLocal),
it may produce false-negative "CACHE_NOT_FOUND" message if a cache was started 
during recovery while cluster-wide descriptor was changed.

{noformat}
if (cacheInfo == null || !F.eq(depId, cacheInfo.dynamicDeploymentId()))
throw new 
SchemaOperationException(SchemaOperationException.CODE_CACHE_NOT_FOUND, 
cacheName); 
{noformat}




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

[GitHub] ignite pull request #5629: IGNITE-10624 Update deployment id for recovered c...

[Jokser]

GitHub user Jokser opened a pull request:

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

IGNITE-10624 Update deployment id for recovered cache after join to topology



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

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

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

https://github.com/apache/ignite/pull/5629.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 #5629


commit 009c617d2fa9c23e58bd0cad18dfdd7d92ebb363
Author: Pavel Kovalenko 
Date:   2018-12-10T17:00:39Z

IGNITE-10624 Update deployment id for recovered cache after join to topology

Signed-off-by: Pavel Kovalenko 




---

Re: Clean up of our PRs and IEPs before 2019

[Dmitriy Pavlov]

The main concern is related to chances that newcomer will have to obtain a
review support from the community.

Actually, a lot of people doing their best to provide a feedback to
newcomers, and count of issues still in PA state goes down (84 is a
relatively small count of issues in PA state). But 1428 PRs may imply we
don't review here, as we have tons of incomplete PRs. Actually, most of
these PRs were merged (but not using ./apply-pull-request.sh script, but
manually, without reference to PRs).

Another benefit of revising this list, if there are any changes which
were not accomplished with a proper ticket with PA status, we will identify
a number of additional contributions to be applied to the codebase.


пн, 10 дек. 2018 г. в 19:53, Nikolay Izhikov :

> Hello, Dmitriy.
>
> What, exactly concerns newcomers?
> What is wrong with opened PR?
> How project will benefit from closed PR?
>
> > The same proposal is related to IEP statuses. If you were involved in an
> IEP, please validate its status
>
> +1. We should maintain IEP description up to date.
>
> пн, 10 дек. 2018 г., 19:15 Dmitriy Pavlov dpav...@apache.org:
>
> > Hi Igniters,
> >
> > Newcomers to Apache Ignite sometimes became concerned about many open PRs
> > in the project. Apache Ignite TC Bot also performs runs checks with a PR
> > open. Apache Ignite pulls list https://github.com/apache/ignite/pulls
> > contains
> > 1442 PRs open while only 84 issues are waiting for review.
> >
> > Could you please verify the list of your PRs in Apache Ignite
> > https://github.com/pulls  and close every not needed/already merged
> > change?
> >
> > The same proposal is related to IEP statuses. If you were involved in an
> > IEP, please validate its status here
> > https://cwiki.apache.org/confluence/display/IGNITE/Active+Proposals
> > Please
> > set a correct state for your IEP, as well.
> >
> > Should you have any questions, please don't hesitate to ask here. Thank
> you
> > in advance!
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
>

[GitHub] ignite pull request #2276: Ignite 5515

[dspavlov]

Github user dspavlov closed the pull request at:

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


---

[GitHub] ignite pull request #1892: Ignite 5078: Pull request for partition lost even...

[dspavlov]

Github user dspavlov closed the pull request at:

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


---

[jira] [Created] (IGNITE-10625) Do first checkpoint on node start before join to topology

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-10625:


 Summary: Do first checkpoint on node start before join to topology
 Key: IGNITE-10625
 URL: https://issues.apache.org/jira/browse/IGNITE-10625
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 2.4
Reporter: Pavel Kovalenko
 Fix For: 2.8


If a node joins to active cluster we do the first checkpoint during PME when 
partition states have restored here 
{code:java}
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopology#afterStateRestored
 
{code}
In IGNITE-9420 we moved logical recovery phase before joining to topology and 
currently when a node joins to active cluster it already has all recovered 
partitions. It means that we can safely do the first checkpoint after all 
logical updates are applied. This change will accelerate PME process if there 
were a lot of applied updates during recovery.




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

Re: Is it time to move forward to JUnit4 (5)?

[Eduard Shangareev]

Ivan,

So, suggested actions with the new approach:
1. Add @Test annotation on test methods.
2. Add @RunWith(JUnit4.class) annotation on test class.
3. Add @Before, @After on methods which should run before, after a
test (setUp, tearDown in current approach).
4. Add your test-class to a suite using suite.addTest(new
JUnit4TestAdapter(YourTestClass.class));
5. Use @Ignore instead fail(); for muting test.
6. You could start using @Parametrized instead of inheritance.


On Mon, Dec 3, 2018 at 1:15 PM Павлухин Иван  wrote:

> Hi Oleg,
>
> I noticed that GridAbstractTest is now capable to run junit4 tests.
> What are the current recommendations for writing new tests? Can we use
> junit4 annotation for new tests?
> пн, 12 нояб. 2018 г. в 19:58, oignatenko :
> >
> > Hi Ivan,
> >
> > I am currently testing approach you used in pull/5354 in the "pilot"
> > sub-task with examples tests (IGNITE-10174).
> >
> > So far it looks more and more like the way to go. The most promising
> thing I
> > observed is that after I changed classes in our test framework the way
> you
> > did, execution of (unchanged) examples tests went exactly the same as it
> was
> > before changes.
> >
> > This indicates that existing tests won't be affected making it indeed low
> > risk.
> >
> > After that I converted examples tests to Junit 4 by adding @RunWith and
> > @Test annotations and tried a few, and these looked okay.
> >
> > Currently I am running full examples test suite and after it is over I
> will
> > compare results to the reference list I made by running it prior to
> > migration.
> >
> > regards, Oleg
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>

Re: Is it time to move forward to JUnit4 (5)?

[Vladimir Ozerov]

Ed,

Several questions from my side:
1) When the change is expected to be merged?
2) What contributors with opened PRs and new or updated JUnit3 tests are
supposed to do? Rewrite to JUnit4?

If yes, then we should give them time to have a chance to get used to new
approach and resolve possible conflicts.

Vladimir.

пн, 10 дек. 2018 г. в 20:32, Eduard Shangareev :

> Ivan,
>
> So, suggested actions with the new approach:
> 1. Add @Test annotation on test methods.
> 2. Add @RunWith(JUnit4.class) annotation on test class.
> 3. Add @Before, @After on methods which should run before, after a
> test (setUp, tearDown in current approach).
> 4. Add your test-class to a suite using suite.addTest(new
> JUnit4TestAdapter(YourTestClass.class));
> 5. Use @Ignore instead fail(); for muting test.
> 6. You could start using @Parametrized instead of inheritance.
>
>
> On Mon, Dec 3, 2018 at 1:15 PM Павлухин Иван  wrote:
>
> > Hi Oleg,
> >
> > I noticed that GridAbstractTest is now capable to run junit4 tests.
> > What are the current recommendations for writing new tests? Can we use
> > junit4 annotation for new tests?
> > пн, 12 нояб. 2018 г. в 19:58, oignatenko :
> > >
> > > Hi Ivan,
> > >
> > > I am currently testing approach you used in pull/5354 in the "pilot"
> > > sub-task with examples tests (IGNITE-10174).
> > >
> > > So far it looks more and more like the way to go. The most promising
> > thing I
> > > observed is that after I changed classes in our test framework the way
> > you
> > > did, execution of (unchanged) examples tests went exactly the same as
> it
> > was
> > > before changes.
> > >
> > > This indicates that existing tests won't be affected making it indeed
> low
> > > risk.
> > >
> > > After that I converted examples tests to Junit 4 by adding @RunWith and
> > > @Test annotations and tried a few, and these looked okay.
> > >
> > > Currently I am running full examples test suite and after it is over I
> > will
> > > compare results to the reference list I made by running it prior to
> > > migration.
> > >
> > > regards, Oleg
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >
> >
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
> >
>

Re: Is it time to move forward to JUnit4 (5)?

[Eduard Shangareev]

Vovan,

1) Tomorrow in core-module.
2) I believe that nothing, old JUnit3 would work if they are a new one.
Otherwise, they need to fix merge conflict and add @Test on their new test.
And I think that it's unavoidable, we couldn't ask all people to finish
their current activity and not start a new one. So, it's no matter when we
would merge it.

On Mon, Dec 10, 2018 at 8:38 PM Vladimir Ozerov 
wrote:

> Ed,
>
> Several questions from my side:
> 1) When the change is expected to be merged?
> 2) What contributors with opened PRs and new or updated JUnit3 tests are
> supposed to do? Rewrite to JUnit4?
>
> If yes, then we should give them time to have a chance to get used to new
> approach and resolve possible conflicts.
>
> Vladimir.
>
> пн, 10 дек. 2018 г. в 20:32, Eduard Shangareev <
> eduard.shangar...@gmail.com
> >:
>
> > Ivan,
> >
> > So, suggested actions with the new approach:
> > 1. Add @Test annotation on test methods.
> > 2. Add @RunWith(JUnit4.class) annotation on test class.
> > 3. Add @Before, @After on methods which should run before, after a
> > test (setUp, tearDown in current approach).
> > 4. Add your test-class to a suite using suite.addTest(new
> > JUnit4TestAdapter(YourTestClass.class));
> > 5. Use @Ignore instead fail(); for muting test.
> > 6. You could start using @Parametrized instead of inheritance.
> >
> >
> > On Mon, Dec 3, 2018 at 1:15 PM Павлухин Иван 
> wrote:
> >
> > > Hi Oleg,
> > >
> > > I noticed that GridAbstractTest is now capable to run junit4 tests.
> > > What are the current recommendations for writing new tests? Can we use
> > > junit4 annotation for new tests?
> > > пн, 12 нояб. 2018 г. в 19:58, oignatenko :
> > > >
> > > > Hi Ivan,
> > > >
> > > > I am currently testing approach you used in pull/5354 in the "pilot"
> > > > sub-task with examples tests (IGNITE-10174).
> > > >
> > > > So far it looks more and more like the way to go. The most promising
> > > thing I
> > > > observed is that after I changed classes in our test framework the
> way
> > > you
> > > > did, execution of (unchanged) examples tests went exactly the same as
> > it
> > > was
> > > > before changes.
> > > >
> > > > This indicates that existing tests won't be affected making it indeed
> > low
> > > > risk.
> > > >
> > > > After that I converted examples tests to Junit 4 by adding @RunWith
> and
> > > > @Test annotations and tried a few, and these looked okay.
> > > >
> > > > Currently I am running full examples test suite and after it is over
> I
> > > will
> > > > compare results to the reference list I made by running it prior to
> > > > migration.
> > > >
> > > > regards, Oleg
> > > >
> > > >
> > > >
> > > > --
> > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Ivan Pavlukhin
> > >
> >
>

Re: Is it time to move forward to JUnit4 (5)?

[Dmitriy Pavlov]

Vladimir, AFAIK there will be no single change for overall migration. All
migration will be in a step-by-step manner and mostly transparent for
contributors.

Both approaches 3&4 will be available for some time.

First of all, we need an opportunity to run existing integration tests in
JUnit4.

пн, 10 дек. 2018 г. в 20:38, Vladimir Ozerov :

> Ed,
>
> Several questions from my side:
> 1) When the change is expected to be merged?
> 2) What contributors with opened PRs and new or updated JUnit3 tests are
> supposed to do? Rewrite to JUnit4?
>
> If yes, then we should give them time to have a chance to get used to new
> approach and resolve possible conflicts.
>
> Vladimir.
>
> пн, 10 дек. 2018 г. в 20:32, Eduard Shangareev <
> eduard.shangar...@gmail.com
> >:
>
> > Ivan,
> >
> > So, suggested actions with the new approach:
> > 1. Add @Test annotation on test methods.
> > 2. Add @RunWith(JUnit4.class) annotation on test class.
> > 3. Add @Before, @After on methods which should run before, after a
> > test (setUp, tearDown in current approach).
> > 4. Add your test-class to a suite using suite.addTest(new
> > JUnit4TestAdapter(YourTestClass.class));
> > 5. Use @Ignore instead fail(); for muting test.
> > 6. You could start using @Parametrized instead of inheritance.
> >
> >
> > On Mon, Dec 3, 2018 at 1:15 PM Павлухин Иван 
> wrote:
> >
> > > Hi Oleg,
> > >
> > > I noticed that GridAbstractTest is now capable to run junit4 tests.
> > > What are the current recommendations for writing new tests? Can we use
> > > junit4 annotation for new tests?
> > > пн, 12 нояб. 2018 г. в 19:58, oignatenko :
> > > >
> > > > Hi Ivan,
> > > >
> > > > I am currently testing approach you used in pull/5354 in the "pilot"
> > > > sub-task with examples tests (IGNITE-10174).
> > > >
> > > > So far it looks more and more like the way to go. The most promising
> > > thing I
> > > > observed is that after I changed classes in our test framework the
> way
> > > you
> > > > did, execution of (unchanged) examples tests went exactly the same as
> > it
> > > was
> > > > before changes.
> > > >
> > > > This indicates that existing tests won't be affected making it indeed
> > low
> > > > risk.
> > > >
> > > > After that I converted examples tests to Junit 4 by adding @RunWith
> and
> > > > @Test annotations and tried a few, and these looked okay.
> > > >
> > > > Currently I am running full examples test suite and after it is over
> I
> > > will
> > > > compare results to the reference list I made by running it prior to
> > > > migration.
> > > >
> > > > regards, Oleg
> > > >
> > > >
> > > >
> > > > --
> > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Ivan Pavlukhin
> > >
> >
>

[jira] [Created] (IGNITE-10626) Save authenticated Webconsole session for more than one page refresh

[Evgenii Zhuravlev (JIRA)]

Evgenii Zhuravlev created IGNITE-10626:
--

 Summary: Save authenticated Webconsole session for more than one 
page refresh
 Key: IGNITE-10626
 URL: https://issues.apache.org/jira/browse/IGNITE-10626
 Project: Ignite
  Issue Type: Improvement
Reporter: Evgenii Zhuravlev


Now, it's needed to enter login and password after each page refresh



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

[GitHub] ignite pull request #5584: IGNITE-8227: Proper NoOpHandler injection.

[nizhikov]

Github user nizhikov closed the pull request at:

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


---

Re: Schema in CacheConfig is not updated after DDL commands(Add/drop column, Create/drop index)

[Nikolay Izhikov]

Vladimir.

Since we are talking about internal component(Spark Data Frame integration)
can we use same technique as JdbcRequestHandler to obtain columns metadata?
Seems, code above will fetch up to date columns info:

org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler#getColumnsMeta
```

for (String cacheName : ctx.cache().publicCacheNames()) {
for (GridQueryTypeDescriptor table :
ctx.query().types(cacheName)) {
if (!matches(table.schemaName(), req.schemaName()))
continue;

if (!matches(table.tableName(), req.tableName()))
continue;
//Process column here

```

пн, 19 нояб. 2018 г. в 18:54, Vladimir Ozerov :

> There is no public API currently. This information can be extracted using
> JDBC metadata requests.
>
> On Mon, Nov 19, 2018 at 6:50 PM Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Vladimir,
> >
> > What is the best way to get current schema information (list of tables,
> > columns, etc.)?
> >
> > -Val
> >
> > On Mon, Nov 19, 2018 at 1:21 AM Vladimir Ozerov 
> > wrote:
> >
> > > Hi,
> > >
> > > In this case Spark integration should be fixed. as we never stated that
> > DDL
> > > updates will be reflected in IgniteCache.getConfiguration().
> > >
> > >
> > > On Mon, Nov 19, 2018 at 11:58 AM Ray  wrote:
> > >
> > > > When user performs column and index modification operation in SQL(ex
> > > create
> > > > index, drop index, add column, drop column),  QueryEntity in
> > > > CacheConfiguration for the modified cache is not updated.
> > > >
> > > > Here's my analysis
> > > >
> > > > QueryEntity in QuerySchema is a local copy of the original
> QueryEntity,
> > > so
> > > > the original QueryEntity is not updated when modification happens.
> > > >
> > > > I have created a ticket for this issue
> > > > https://issues.apache.org/jira/browse/IGNITE-10314
> > > >
> > > > But as Vlad said in the comments "public configuration is immutable,
> it
> > > > represents initial cache parameters. So it is expected that
> > configuration
> > > > will not be updated after DDL commands. Real changes are accumulated
> in
> > > > separate query entity which is hidden from user and used internally"
> > > >
> > > > But I think it's only reasonable to return the newest QueryEntity to
> > > user.
> > > >
> > > > For example, a user adds a column to a table then he reads data using
> > > Spark
> > > > data frame API which currently relies on QueryEntity to construct
> data
> > > > frame
> > > > schema, so user will get wrong schema.
> > > >
> > > > What do you guys think?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > > >
> > >
> >
>

Re: Is it time to move forward to JUnit4 (5)?

[Vladimir Ozerov]

Got it. Thank you.

пн, 10 дек. 2018 г. в 20:52, Dmitriy Pavlov :

> Vladimir, AFAIK there will be no single change for overall migration. All
> migration will be in a step-by-step manner and mostly transparent for
> contributors.
>
> Both approaches 3&4 will be available for some time.
>
> First of all, we need an opportunity to run existing integration tests in
> JUnit4.
>
> пн, 10 дек. 2018 г. в 20:38, Vladimir Ozerov :
>
> > Ed,
> >
> > Several questions from my side:
> > 1) When the change is expected to be merged?
> > 2) What contributors with opened PRs and new or updated JUnit3 tests are
> > supposed to do? Rewrite to JUnit4?
> >
> > If yes, then we should give them time to have a chance to get used to new
> > approach and resolve possible conflicts.
> >
> > Vladimir.
> >
> > пн, 10 дек. 2018 г. в 20:32, Eduard Shangareev <
> > eduard.shangar...@gmail.com
> > >:
> >
> > > Ivan,
> > >
> > > So, suggested actions with the new approach:
> > > 1. Add @Test annotation on test methods.
> > > 2. Add @RunWith(JUnit4.class) annotation on test class.
> > > 3. Add @Before, @After on methods which should run before, after a
> > > test (setUp, tearDown in current approach).
> > > 4. Add your test-class to a suite using suite.addTest(new
> > > JUnit4TestAdapter(YourTestClass.class));
> > > 5. Use @Ignore instead fail(); for muting test.
> > > 6. You could start using @Parametrized instead of inheritance.
> > >
> > >
> > > On Mon, Dec 3, 2018 at 1:15 PM Павлухин Иван 
> > wrote:
> > >
> > > > Hi Oleg,
> > > >
> > > > I noticed that GridAbstractTest is now capable to run junit4 tests.
> > > > What are the current recommendations for writing new tests? Can we
> use
> > > > junit4 annotation for new tests?
> > > > пн, 12 нояб. 2018 г. в 19:58, oignatenko :
> > > > >
> > > > > Hi Ivan,
> > > > >
> > > > > I am currently testing approach you used in pull/5354 in the
> "pilot"
> > > > > sub-task with examples tests (IGNITE-10174).
> > > > >
> > > > > So far it looks more and more like the way to go. The most
> promising
> > > > thing I
> > > > > observed is that after I changed classes in our test framework the
> > way
> > > > you
> > > > > did, execution of (unchanged) examples tests went exactly the same
> as
> > > it
> > > > was
> > > > > before changes.
> > > > >
> > > > > This indicates that existing tests won't be affected making it
> indeed
> > > low
> > > > > risk.
> > > > >
> > > > > After that I converted examples tests to Junit 4 by adding @RunWith
> > and
> > > > > @Test annotations and tried a few, and these looked okay.
> > > > >
> > > > > Currently I am running full examples test suite and after it is
> over
> > I
> > > > will
> > > > > compare results to the reference list I made by running it prior to
> > > > > migration.
> > > > >
> > > > > regards, Oleg
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Ivan Pavlukhin
> > > >
> > >
> >
>

[jira] [Created] (IGNITE-10627) Support custom preferences like date format and other similar features

[Evgenii Zhuravlev (JIRA)]

Evgenii Zhuravlev created IGNITE-10627:
--

 Summary: Support custom preferences like date format and other 
similar features
 Key: IGNITE-10627
 URL: https://issues.apache.org/jira/browse/IGNITE-10627
 Project: Ignite
  Issue Type: Improvement
Reporter: Evgenii Zhuravlev






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

[GitHub] ignite pull request #5541: IGNITE-10386 Add mode when WAL won't be disabled ...

[andrey-kuznetsov]

Github user andrey-kuznetsov closed the pull request at:

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


---

[GitHub] ignite pull request #5219: IGNITE-10079 Fixed inconsistent lastCompactedSegm...

[andrey-kuznetsov]

Github user andrey-kuznetsov closed the pull request at:

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


---

[GitHub] ignite pull request #5092: TDR-93 Several WAL compressor fixes.

[andrey-kuznetsov]

Github user andrey-kuznetsov closed the pull request at:

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


---

[GitHub] ignite pull request #4547: Tdr 26

[andrey-kuznetsov]

Github user andrey-kuznetsov closed the pull request at:

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


---

[jira] [Created] (IGNITE-10628) Add support for nightly RunAll

[Nikolai Kulagin (JIRA)]

Nikolai Kulagin created IGNITE-10628:


 Summary: Add support for nightly RunAll
 Key: IGNITE-10628
 URL: https://issues.apache.org/jira/browse/IGNITE-10628
 Project: Ignite
  Issue Type: Sub-task
Reporter: Nikolai Kulagin
Assignee: Nikolai Kulagin


Add support for nightly RunAll, fix divisions on the y-axis of duration chart



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

[GitHub] zzzadruga opened a new pull request #97: IGNITE-10628 Add support for nightly RunAll

[GitBox]

zzzadruga opened a new pull request #97: IGNITE-10628 Add support for nightly 
RunAll
URL: https://github.com/apache/ignite-teamcity-bot/pull/97
 
 
   


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: Is it time to move forward to JUnit4 (5)?

[oignatenko]

Hello,

I would like add few minor clarifications to what Ed wrote.

1. After transition to JUnit4 is fully over (ETA this week) there won't be a
need to use @RunWith(JUnit4.class) anymore, so you will be writing test
classes as a normal JUnit 4 user, without any special scaffolding.
1.1. Please keep in mind that tests that don't inherit from GridAbstractTest
can (and I think should) be written full Junit 4 and don't need anything
special at all - these are essentially out of scope of this discussion.

2. Note that "full JUnit 4 experience" doesn't apply to part of testsuites
that currently use suite() method because in these you would still have to
use JUnit4TestAdapter. Unless of course you will choose to rewrite
particular suite Junit 4 style (which I would encourage everyone to do,
after we complete migration).

3. As a bit of further perspective, we also considering next migration -
after all tests will be uniform Junit 4 (instead of current mix of Junit 3
and 4) we will look into whether it is worth migrating to most recent
version - JUnit5. Those interested can keep an eye on respective JIRA
ticket:
  https://issues.apache.org/jira/browse/IGNITE-10180
  
regards, Oleg


Eduard Shangareev wrote
> Ivan,
> 
> So, suggested actions with the new approach:
> 1. Add @Test annotation on test methods.
> 2. Add @RunWith(JUnit4.class) annotation on test class.
> 3. Add @Before, @After on methods which should run before, after a
> test (setUp, tearDown in current approach).
> 4. Add your test-class to a suite using suite.addTest(new
> JUnit4TestAdapter(YourTestClass.class));
> 5. Use @Ignore instead fail(); for muting test.
> 6. You could start using @Parametrized instead of inheritance.
> 
> 
> On Mon, Dec 3, 2018 at 1:15 PM Павлухин Иван <

> vololo100@

> > wrote:
> 
>> Hi Oleg,
>>
>> I noticed that GridAbstractTest is now capable to run junit4 tests.
>> What are the current recommendations for writing new tests? Can we use
>> junit4 annotation for new tests?
>> пн, 12 нояб. 2018 г. в 19:58, oignatenko <

> oignatenko@

> >:
>> >
>> > Hi Ivan,
>> >
>> > I am currently testing approach you used in pull/5354 in the "pilot"
>> > sub-task with examples tests (IGNITE-10174).
>> >
>> > So far it looks more and more like the way to go. The most promising
>> thing I
>> > observed is that after I changed classes in our test framework the way
>> you
>> > did, execution of (unchanged) examples tests went exactly the same as
>> it
>> was
>> > before changes.
>> >
>> > This indicates that existing tests won't be affected making it indeed
>> low
>> > risk.
>> >
>> > After that I converted examples tests to Junit 4 by adding @RunWith and
>> > @Test annotations and tried a few, and these looked okay.
>> >
>> > Currently I am running full examples test suite and after it is over I
>> will
>> > compare results to the reference list I made by running it prior to
>> > migration.
>> >
>> > regards, Oleg
>> >
>> >
>> >
>> > --
>> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>>
>>
>>
>> --
>> Best regards,
>> Ivan Pavlukhin
>>





--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-10629) Migration follow up: check for old style tests that could be slipped through in transition period

[Oleg Ignatenko (JIRA)]

Oleg Ignatenko created IGNITE-10629:
---

 Summary: Migration follow up: check for old style tests that could 
be slipped through in transition period
 Key: IGNITE-10629
 URL: https://issues.apache.org/jira/browse/IGNITE-10629
 Project: Ignite
  Issue Type: Sub-task
Affects Versions: 2.8
Reporter: Oleg Ignatenko


We need to account for risk that while tests are migrating some commits may by 
mistake slip in old style test cases - that will be ignored by JUnit 4.

In order to address possible issues of that kind, do the following a week or 
two after IGNITE-10177 is merged to master: run the IntelliJ inspection called 
"old style Junit test method in JUnit 4 class", review report and fix 
discovered problems if there are any.

For the reference, my version of IDE explains this inspection as follows:
 {quote}Reports JUnit 3 style test methods which are located inside a class 
which does not extend the abstract JUnit 3 class TestCase and contains JUnit 
4/JUnit 5 @Test annotated methods.{quote}

 (note concerns mentioned in this ticket were originally raised at dev list: 
[here|http://apache-ignite-developers.2346864.n4.nabble.com/Is-it-time-to-move-forward-to-JUnit4-5-tp29608p39300.html])



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

[GitHub] ignite pull request #3413: Ignite system views (prototype)

[alex-plekhanov]

Github user alex-plekhanov closed the pull request at:

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


---

[GitHub] ignite pull request #3433: IGNITE-7527 SQL system views: local transactions

[alex-plekhanov]

Github user alex-plekhanov closed the pull request at:

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


---

[GitHub] ignite pull request #3664: IGNITE-7969 Fixed failure of failure of IgniteTop...

[alex-plekhanov]

Github user alex-plekhanov closed the pull request at:

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


---

[GitHub] ignite pull request #3855: IGNITE-8191 Print out information when cluster is...

[alex-plekhanov]

Github user alex-plekhanov closed the pull request at:

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


---

[GitHub] ignite pull request #3866: IGNITE-8192 Print out information on how many nod...

[alex-plekhanov]

Github user alex-plekhanov closed the pull request at:

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


---

[GitHub] ignite pull request #3875: IGNITE-8190 Print out an information message when...

[alex-plekhanov]

Github user alex-plekhanov closed the pull request at:

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


---

[GitHub] ignite pull request #3906: IGNITE-8191 Hotfix (don't wait for transition)

[alex-plekhanov]

Github user alex-plekhanov closed the pull request at:

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


---

[GitHub] ignite pull request #3963: IGNITE-8443 Transaction hangs when some error occ...

[alex-plekhanov]

Github user alex-plekhanov closed the pull request at:

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


---

[GitHub] ignite pull request #3922: IGNITE-8400 IgniteTopologyValidatorGridSplitCache...

[alex-plekhanov]

Github user alex-plekhanov closed the pull request at:

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


---

[GitHub] ignite pull request #3930: IGNITE-8400 IgniteTopologyValidatorGridSplitCache...

[alex-plekhanov]

Github user alex-plekhanov closed the pull request at:

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


---

[GitHub] ignite pull request #3964: IGNITE-8443 Transaction hangs when some error occ...

[alex-plekhanov]

Github user alex-plekhanov closed the pull request at:

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


---