[GitHub] ignite pull request #4511: IGNITE-9031: SpringCacheManager throws AssertionE...

GitHub user amirakhmedov opened a pull request: https://github.com/apache/ignite/pull/4511 IGNITE-9031: SpringCacheManager throws AssertionError during Spring i… …nitialization You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #4510: Ignite 2.5.1 p11 txfix

GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/4510 Ignite 2.5.1 p11 txfix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p11-txfix Alternatively you

[GitHub] ignite pull request #4509: IGNITE-9243: G.allGrids() replaced by IgnitionEx....

GitHub user BiryukovVA opened a pull request: https://github.com/apache/ignite/pull/4509 IGNITE-9243: G.allGrids() replaced by IgnitionEx.allGridsx() You can merge this pull request into a Git repository by running: $ git pull https://github.com/BiryukovVA/ignite IGNITE-9243

[jira] [Created] (IGNITE-9243) Avoid test suit hangs on stopAllGrids

Vitaliy Biryukov created IGNITE-9243: Summary: Avoid test suit hangs on stopAllGrids Key: IGNITE-9243 URL: https://issues.apache.org/jira/browse/IGNITE-9243 Project: Ignite Issue Type:

[GitHub] ignite pull request #4508: Ignite 2.4.8.b1

GitHub user mcherkasov opened a pull request: https://github.com/apache/ignite/pull/4508 Ignite 2.4.8.b1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.8.b1 Alternatively you can review and

[GitHub] ignite pull request #4507: Ignite 8926 9200

GitHub user mcherkasov opened a pull request: https://github.com/apache/ignite/pull/4507 Ignite 8926 9200 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8926-9200 Alternatively you can review and

Re: Benchmarking

Igniters, I would like to add that it would be very nice to have prepared scenarios in packed docker images with docker-compose, to easily deploy and run it on AWS environment. This will give the possibility to benchmark any changes independently and fastly. 2018-08-09 18:51 GMT+03:00 Anton

Benchmarking

Igniters, All critical code changes should be covered by benchmarks. Currently, community have no dedicated benchmarking service. Everyone can run yandstick locally, but this seems to be useless. You have to run cluster on 4 clients and 4 servers, at least. Currently it is not possible for me

[jira] [Created] (IGNITE-9242) IgniteConfiguration.PeerAssemblyLoadingEnabled referenced in error message but doesn't exist

Ilya Kasnacheev created IGNITE-9242: --- Summary: IgniteConfiguration.PeerAssemblyLoadingEnabled referenced in error message but doesn't exist Key: IGNITE-9242 URL:

Re: C++ Thin client. JVM dependency.

Hi, This is not true, thin client does not depend on libignite. It only depends on libignite-binary and libignite-common. Neither of them depends on jvm. Best Regards, Igor On Thu, Aug 9, 2018 at 4:16 PM Nikolay Izhikov wrote: > Hello, Igniters. > > I have a question from one of an early

Re: TDE: Upgrade Team City JDK

Done > On 9 Aug 2018, at 17:44, Nikolay Izhikov wrote: > > Petr. > > Seems, now I has to put my tests in "Basic Tests With Persistence". > Can you configure Team city so I can run "Basic Tests With Persistence" on > publicagent03_9091? > > В Чт, 09/08/2018 в 16:35 +0300, Petr Ivanov пишет:

Re: Service grid redesign

Versions will complicate the implementation and will not be done in 2.7. I would vote for the hot redeployment for now and add versions in 2.8. D. On Thu, Aug 9, 2018 at 10:06 AM, Anton Vinogradov wrote: > Real case is A/B testing. > When you want to allow new service usage only to 0.1% of

Re: Service grid redesign

Real case is A/B testing. When you want to allow new service usage only to 0.1% of users. And only when you sure it works then replace all v1 with v2. So, I vote for versions. Let's do this in maven way (exact version, range, RELEASE or LATEST) чт, 9 авг. 2018 г. в 17:55, Dmitriy Setrakyan : >

Re: ConcurrentLinkedHashMap works incorrectly after clear()

On Thu, Aug 9, 2018 at 8:16 AM, Alexey Goncharuk wrote: > Guys, I think we can definitely change current implementation of CLHM with > a more stable one, but as a temporal solution I see nothing wrong with > throwing an UnsupportedOperationException from clear() method. Ilya already > provided a

Re: DataFrame integration does not support ARRAY type

On Thu, Aug 9, 2018 at 8:19 AM, Nikolay Izhikov wrote: > Dmitriy, I will take care of this ticket in a few days. > Great!

Re: Data regions on client nodes

Alexey, I see your point. However, I would still argue that there are more benefits to the dynamic region allocation than not. For example, if we have this feature, users would be able to create more regions after the node and cluster start, which will allow to grow the data size indefinitely in

Re: Service grid redesign

Vyacheslav, For the case you are describing, I would take the same approach as we have for compute tasks. Keep the older version around only as long as there are active requests and then undeploy it automatically. No need to allow it linger around indefinitely. D. On Thu, Aug 9, 2018 at 9:52

Re: Service grid redesign

Dmitry, it's not only about hot redeployment. Denis, I don't see such use case, because of the answer in a different front. It relates to the best practices of SOA versioning [1] [2]. For example: * we have a cluster with service [name="MySevice", v="1"]; * I want to upgrade service to

Re: Service grid redesign

Guys, I thought this was about automatic service redeployment, which should have been a part of the current IEP, no? Can you please clarify? D. On Thu, Aug 9, 2018 at 9:26 AM, Denis Mekhanikov wrote: > Vyacheslav, > > It looks like an overcomplication to me. > Could you describe a case, that

Re: TDE: Upgrade Team City JDK

Petr. Seems, now I has to put my tests in "Basic Tests With Persistence". Can you configure Team city so I can run "Basic Tests With Persistence" on publicagent03_9091? В Чт, 09/08/2018 в 16:35 +0300, Petr Ivanov пишет: > Yeap. > > As it is disabled, it will not take tasks from queue

Re: Service grid redesign

Vyacheslav, It looks like an overcomplication to me. Could you describe a case, that can be solved using versioning, but not naming? Denis чт, 9 авг. 2018 г. в 16:56, Vyacheslav Daradur : > Denis, it's not about different users services implementations. > > A real use case is user's services

Re: Service grid redesign

Denis, it's not about different users services implementations. A real use case is user's services API versioning which is being used widely t in SOAP/REST microservices infrastructure. In my opinion, it is about services with the same name and the same full class name, but different classes

[GitHub] ignite pull request #3849: B+Tree operation may result in an infinite loop i...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3849 ---

Re: Data regions on client nodes

Once the OS gave us the pointer, no exceptions can be raised in the user code. If the OS overcommitted the memory, then the process will be halted when OOME occurs, not much we can do here. My point was that dynamic data region allocation can lead to another dynamic exception that should be

Re: Service grid redesign

I don't think, that we really need this feature. It seems to me, that if you want to use a different implementation of a service, you can assign a different name to it. What do you think? Denis чт, 9 авг. 2018 г. в 16:32, Dmitriy Setrakyan : > On Thu, Aug 9, 2018 at 4:41 AM, Vyacheslav Daradur

Re: Service grid redesign

We won't change API, user will continue to use service's name to manage it. Some kind of service id will be used internally, this allow us to distinguish services with the same name, but different version. On Thu, Aug 9, 2018 at 4:32 PM Dmitriy Setrakyan wrote: > > On Thu, Aug 9, 2018 at 4:41

Re: TDE: Upgrade Team City JDK

Yeap. As it is disabled, it will not take tasks from queue automatically, but can be assigned tasks manually. > On 9 Aug 2018, at 16:27, Nikolay Izhikov wrote: > > Hello, Petr. > > I'm able to select thi agent for build. > But it has "disabled" comment. > > Is that OK? > >

Re: Spark SQL Table Name Resolution

Hi Nikolay, yes would be happy to - will likely be early next week. I’ll go with the approach of adding a new optional field to the Spark data source provider unless there are any objections. Stuart. > On 9 Aug 2018, at 14:20, Nikolay Izhikov wrote: > > Stuart, do you want to work on this

Re: Service grid redesign

On Thu, Aug 9, 2018 at 4:41 AM, Vyacheslav Daradur wrote: > Hi, Igniters! > > I found a ticket about a service’s versioning [1]. > > It’s out of scope IEP-17, but if we are going to implement this > feature we should build a base in the first iteration of IEP-17 > because of change messages

Re: TDE: Upgrade Team City JDK

Hello, Petr. I'm able to select thi agent for build. But it has "disabled" comment. Is that OK? https://ci.ignite.apache.org/viewQueued.html?itemId=1620053:0:153=queuedBuildOverviewTab В Ср, 08/08/2018 в 17:44 +0300, Petr Ivanov пишет: > Nikolay, > > > I’ve updated publicagent03_9091 and

Re: Deprecate force server mode for clients.

+1 from me. В Чт, 09/08/2018 в 12:51 +0300, Pavel Kovalenko пишет: > Andrey, > > Huge +1 for that. > "Force server mode" increases the complexity of understanding how cluster > in ring mode works without real benefits. > If a user wants to start client node first before server nodes have >

Re: Spark SQL Table Name Resolution

Stuart, do you want to work on this ticket? В Вт, 07/08/2018 в 11:13 -0700, Stuart Macdonald пишет: > Thanks Val, here’s the ticket: > > https://issues.apache.org/jira/projects/IGNITE/issues/IGNITE-9228 > >

Re: DataFrame integration does not support ARRAY type

Dmitriy, I will take care of this ticket in a few days. В Ср, 08/08/2018 в 18:06 -0500, Dmitriy Setrakyan пишет: > Would be nice if someone in the community would pick this ticket up. > > On Wed, Aug 8, 2018 at 1:19 AM, Nikolay Izhikov wrote: > > > Hello, Valentin. > > > > Yes, this is a bug.

[GitHub] ignite pull request #4506: IGNITE-9231 improvement throttle implementation

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/4506 IGNITE-9231 improvement throttle implementation …Buf condition. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: ConcurrentLinkedHashMap works incorrectly after clear()

Guys, I think we can definitely change current implementation of CLHM with a more stable one, but as a temporal solution I see nothing wrong with throwing an UnsupportedOperationException from clear() method. Ilya already provided a patch which replaces all clear() calls with a new map creation,

C++ Thin client. JVM dependency.

Hello, Igniters. I have a question from one of an early adopter of Ignite C++ thin client. Seems, that our C++ thin client depends on JVM lib. thin-client [1] depends on libignite, and libignite depends on jvm libs [2]. Is that correct? Why do we need it? I thought that a thin client is a

Re: Is there a partial document missing in the section of the data grid?

Oh, sorry, found it. 在 2018/8/9 下午8:39, Ilya Kasnacheev 写道: Hello! I am able to find all of those under https://apacheignite.readme.io/docs/cache-configuration subsection in "Key-Value Data Grid" section. Regards,

TDE Implementation details.

Hello, Igniters. I want to share with you TDE implementation details. I think it can simplify review and acception of TDE implementation. This mail is copy of wiki page [1]. Please, share your thoughts. TDE is ready for review [2]. Please, let me know, who is able to make final review. This

[GitHub] ignite pull request #4505: IGNITE-9196 Fix memory leak in MapNodeResults

GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/4505 IGNITE-9196 Fix memory leak in MapNodeResults You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9196

Re: Is there a partial document missing in the section of the data grid?

Hello! I am able to find all of those under https://apacheignite.readme.io/docs/cache-configuration subsection in "Key-Value Data Grid" section. Regards, -- Ilya Kasnacheev 2018-08-09 14:56 GMT+03:00 李玉珏@163 <18624049...@163.com>: > Hi, > > Some pages are missing in the latest version of the

[GitHub] ignite pull request #4485: ignite-8888 write fix

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4485 ---

[GitHub] ignite pull request #4504: IGNITE-9219 Uncomment tests in IgniteCacheTestSui...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/4504 IGNITE-9219 Uncomment tests in IgniteCacheTestSuite4, minor fixes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #4503: Ignite 9238

GitHub user xtern opened a pull request: https://github.com/apache/ignite/pull/4503 Ignite 9238 You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-9238 Alternatively you can review and apply these changes as

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

Dmitry, Sure, I've already informed author about this issue. Hope he will have time to look at. I see no problems fixing it myself if fix will be simple. In other cases I doubt my ability of fixing complex .NET tests. On Wed, 8 Aug 2018 at 19:08 Dmitriy Pavlov wrote: > This change will

[GitHub] ignite pull request #3315: IGNITE-7251 Remove term "fabric" from Ignite deli...

Github user vveider closed the pull request at: https://github.com/apache/ignite/pull/3315 ---

[jira] [Created] (IGNITE-9241) TcpClusterNode.isClient semantic is broken.

Andrew Mashenkov created IGNITE-9241: Summary: TcpClusterNode.isClient semantic is broken. Key: IGNITE-9241 URL: https://issues.apache.org/jira/browse/IGNITE-9241 Project: Ignite Issue

[GitHub] ignite pull request #4497: IGNITE-9225

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4497 ---

Re: Deprecate force server mode for clients.

Andrey, Huge +1 for that. "Force server mode" increases the complexity of understanding how cluster in ring mode works without real benefits. If a user wants to start client node first before server nodes have started, he can adjust timeouts on connection and spin till a client is connected.

[jira] [Created] (IGNITE-9240) Web console: plus sign not clickable on low resolution

Stepan Pilschikov created IGNITE-9240: - Summary: Web console: plus sign not clickable on low resolution Key: IGNITE-9240 URL: https://issues.apache.org/jira/browse/IGNITE-9240 Project: Ignite

Re: Service grid redesign

Hi, Igniters! I found a ticket about a service’s versioning [1]. It’s out of scope IEP-17, but if we are going to implement this feature we should build a base in the first iteration of IEP-17 because of change messages formats. In case of the versioning which assumes that we are able to host

Deprecate force server mode for clients.

Hi Igniters, I've found that KernalContext.clientNode() and TcpDusciveryNode.isClient() means different and it looks confusing. 1. The first one return true if "node is configured as client" and false otherwise, 2. The second one can return false if server mode is forced for client (via

[jira] [Created] (IGNITE-9239) [ML] KMeansTrainer crashed if amount of possible clusters more than amount of partitions in dataset

Aleksey Zinoviev created IGNITE-9239: Summary: [ML] KMeansTrainer crashed if amount of possible clusters more than amount of partitions in dataset Key: IGNITE-9239 URL:

[GitHub] ignite pull request #4313: IGNITE-8714

Github user NSAmelchev closed the pull request at: https://github.com/apache/ignite/pull/4313 ---

[GitHub] ignite pull request #3815: IGNITE-7024

Github user NSAmelchev closed the pull request at: https://github.com/apache/ignite/pull/3815 ---

[GitHub] ignite pull request #4501: IGNITE-8493 GridToStringBuilder arrayToString ref...

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/4501 IGNITE-8493 GridToStringBuilder arrayToString refactoring. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8493

[GitHub] ignite pull request #3999: IGNITE-8493: refactor arrayToString, decrease hea...

Github user zstan closed the pull request at: https://github.com/apache/ignite/pull/3999 ---

[GitHub] ignite pull request #4500: #ignite example - Readme.txt typo fix

GitHub user k4utech opened a pull request: https://github.com/apache/ignite/pull/4500 #ignite example - Readme.txt typo fix I believe there is typo error (he instead of the) in README.txt inside example folder. Please look into this if pull request stand correct take necessary