[GitHub] ignite pull request #1766: IGNITE-4907: Excessive service instances can be s...

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1766 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[jira] [Created] (IGNITE-4993) Distributed join on partitioned caches with segmented indices broken in master.

Andrew Mashenkov created IGNITE-4993: Summary: Distributed join on partitioned caches with segmented indices broken in master. Key: IGNITE-4993 URL: https://issues.apache.org/jira/browse/IGNITE-4993

Re: Discontinue Scalar in Ignite-2.0?

Sergi takes a lead in the chart of “let’s drop it in 2.0” :)) In general, I would support Nikita here suggesting to deprecate the module first. It’s fine to remove some APIs methods in 2.0 but a deletion of the whole module might be not a good decision. — Denis > On Apr 14, 2017, at 9:18 AM,

Re: Kubernetes deployment

Hi Irina, Looks like an issue with your MiniKube cluster. https://serverfault.com/questions/728727/kubernetes-stuck-on-containercreating Please try to use the command below to see what happens: kubectl describe po

Re: Remove or deprecate IgniteAsyncSupport?

On Fri, Apr 14, 2017 at 8:42 AM, Sergi Vladykin wrote: > That API always was a big mistake. I'm for removing it completely. > Sergi, I share your sentiment for cleaning up. But we cannot allow ourselves such radical changes given that we have a fairly large user base

Re: question: How data are stored in IgniteCache?

If a serialized object is stored in an on-heap cache then it will be wrapped by BinaryObjectImp but if it’s an off-heap cache then BinaryObjectOffHeapImpl is used instead. — Denis > On Apr 14, 2017, at 12:32 AM, Vyacheslav Daradur wrote: > >>> when it’s stored in memory

[GitHub] ignite pull request #1802: Ignite 4927

GitHub user abeliak opened a pull request: https://github.com/apache/ignite/pull/1802 Ignite 4927 WB cache without write coalescing. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4927

Re: ignite-3682 - GridFunc: move all inner anonymous classes to separate top-level classes.

Vyacheslav, all three viewReadOnly methods have many usages. And yes, some methods/classes were removed from GridFunc during other tasks. On Wed, Apr 12, 2017 at 7:24 PM, Vyacheslav Daradur wrote: > Andrey, > > I see you've merged it before I fixed merge conflict and you

[GitHub] ignite pull request #1791: Ignite 4927

Github user abeliak closed the pull request at: https://github.com/apache/ignite/pull/1791 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Discontinue Scalar in Ignite-2.0?

May be drop it in 2.0 then? Sergi 2017-04-14 19:11 GMT+03:00 Nikita Ivanov : > As the original developer/author of Scalar (and I already voiced this > opinion before) - I think we should deprecate Scalar. Ignite APIs can be > used from Scala as-is with minimal, if any,

[GitHub] ignite pull request #1776: Ignite 4587 review

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/1776 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Discontinue Scalar in Ignite-2.0?

As the original developer/author of Scalar (and I already voiced this opinion before) - I think we should deprecate Scalar. Ignite APIs can be used from Scala as-is with minimal, if any, pimping. The custom DSL introduced by Scalar proved to be not a popular option either. -- Nikita Ivanov On

Discontinue Scalar in Ignite-2.0?

There were no commits for TWO years in ignite-scalar module. Our java API is good, no need for any wrappers (IMHO). Also we even do not use it by ourselves in Visor CMD. Thoughts? -- Alexey Kuznetsov

[GitHub] ignite pull request #1801: IGNITE-4992: Fix Segmented SQL Index self tests.

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1801 IGNITE-4992: Fix Segmented SQL Index self tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4992

Re: Remove or deprecate IgniteAsyncSupport?

That API always was a big mistake. I'm for removing it completely. Sergi 2017-04-14 18:01 GMT+03:00 Dmitriy Setrakyan : > What is this obsession with breaking stuff? Let's deprecated it, it is a > big change on API. > > On Fri, Apr 14, 2017 at 7:04 AM, Vladimir Ozerov

[jira] [Created] (IGNITE-4992) Fix Segmented SQL Index self tests.

Andrew Mashenkov created IGNITE-4992: Summary: Fix Segmented SQL Index self tests. Key: IGNITE-4992 URL: https://issues.apache.org/jira/browse/IGNITE-4992 Project: Ignite Issue Type:

[GitHub] ignite pull request #1800: Obsolete cache metrics removed, test fixed

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1800 Obsolete cache metrics removed, test fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Remove or deprecate IgniteAsyncSupport?

What is this obsession with breaking stuff? Let's deprecated it, it is a big change on API. On Fri, Apr 14, 2017 at 7:04 AM, Vladimir Ozerov wrote: > Folks, > > As you know we reworked our async API and added paired asynchronous methods > instead of using

Re: ClusterGroup fallback

Also disagree, silent fallback is no good. If we really need this, we can introduce some way to specify "preferred locations" for service deployment, based on weights for example. But that's a whole new feature and needs to be discussed in more detail. -Val On Fri, Apr 14, 2017 at 3:59 PM,

Re: IgniteSemaphore and failoverSafe flag

It's not 100% reproducible, to get failed locally I've ran it many times in a loop (Intellij IDEA feature). N.B. This test was muted before the fix, so yes, it's could not be a cause. Thanks! 14.04.2017 17:23, Vladisav Jelisavcic пишет: Hmm, I cannot reproduce this behavior locally, my guess

[GitHub] ignite pull request #1799: Ignite 4275

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

[jira] [Created] (IGNITE-4991) Do not print out system properties when IGNITE_TO_STRING_INCLUDE_SENSITIVE is set

Valentin Kulichenko created IGNITE-4991: --- Summary: Do not print out system properties when IGNITE_TO_STRING_INCLUDE_SENSITIVE is set Key: IGNITE-4991 URL: https://issues.apache.org/jira/browse/IGNITE-4991

Kubernetes deployment

Hi, Can you help me - I try to deploy Apache Ignite cluster via Kubernetes in my automation test (using documentation https://apacheignite.readme.io /docs/kubernetes-deployment) I run minikube and next do all steps from documentation. On step Ignite Pods deploymeny, after command: kubectl get

Re: IgniteSemaphore and failoverSafe flag

Hmm, I cannot reproduce this behavior locally, my guess is interrupt flag is not always cleared properly in #GridCacheSemaphore.acquire method (but it doesn't have anything to do with latest fix) Can you make it reproducible? On Fri, Apr 14, 2017 at 2:46 PM, Dmitry Karachentsev <

Re: Adding ML to Ignite, IGNITE-4572

Thank you Denis, that sounds like a good plan. I am working on it now. I didn't reassign IGNITE-4964, just set a watch on it. Will comment on it when I have concrete details to share. Side note my build check completed successfully, although it took quite a bit of time: I cleaned my local maven

[GitHub] ignite pull request #1798: IGNITE-4182: fixed

GitHub user rfqu opened a pull request: https://github.com/apache/ignite/pull/1798 IGNITE-4182: fixed detailed diagnostics from H2 driver retained as wrapper exception's message. You can merge this pull request into a Git repository by running: $ git pull

Remove or deprecate IgniteAsyncSupport?

Folks, As you know we reworked our async API and added paired asynchronous methods instead of using IgntieAsyncSupport infrastructure. Now our API is clean and straightforward. However, we didn't remove IgntieAsyncSupport, but deprecated it as user impact might be huge. Now I think that may be

Re: ClusterGroup fallback

-1 from my side. If there are no nodes for a service this is an exceptional situation, which should be handled explicitly. Silent fallback will make things less obvious. On Fri, Apr 14, 2017 at 3:44 PM, Alexander Fedotov < alexander.fedot...@gmail.com> wrote: > Hi Igniters! > > I want to

[jira] [Created] (IGNITE-4990) Remove deprecated properties from FileSystemConfiguration

Vladimir Ozerov created IGNITE-4990: --- Summary: Remove deprecated properties from FileSystemConfiguration Key: IGNITE-4990 URL: https://issues.apache.org/jira/browse/IGNITE-4990 Project: Ignite

[GitHub] ignite pull request #1772: IGNITE-4942

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1772 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-4989) Assertion error in BPlusTree#finishTail

Alexey Goncharuk created IGNITE-4989: Summary: Assertion error in BPlusTree#finishTail Key: IGNITE-4989 URL: https://issues.apache.org/jira/browse/IGNITE-4989 Project: Ignite Issue Type:

[GitHub] ignite pull request #1734: IGNITE-4915 Remove deprecated methods at the publ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1734 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: IgniteSemaphore and failoverSafe flag

Vladislav, One more thing, This test [1] started failing on semaphore close when this fix [2] was introduced. Could you check it please? [1] http://ci.ignite.apache.org/viewLog.html?buildId=547151=buildResultsDiv=IgniteTests_IgniteDataStrucutures#testNameId-979977708202725050 [2]

ClusterGroup fallback

Hi Igniters! I want to discuss if it possible to implement ClusterGroup fallback, i.e. create a chained cluster group ClusterGroup1->ClusterGroup2 that will refer to nodes satisfying conditions for ClusterGroup1 while there are such nodes and if no such nodes become available then the nodes

[jira] [Created] (IGNITE-4988) Web Console: Cleanup and refactor VisorXxx tasks and DTO for ignite-2.0

Alexey Kuznetsov created IGNITE-4988: Summary: Web Console: Cleanup and refactor VisorXxx tasks and DTO for ignite-2.0 Key: IGNITE-4988 URL: https://issues.apache.org/jira/browse/IGNITE-4988

[GitHub] ignite pull request #1797: IGNITE-3689 .NET: Remove IgniteProxy

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1797 IGNITE-3689 .NET: Remove IgniteProxy You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-3689 Alternatively you can

Re: IgniteSemaphore and failoverSafe flag

Vladislav, Yep, you're right. I'll fix it. Thanks! 14.04.2017 15:18, Vladisav Jelisavcic пишет: Hi Dmitry, it looks to me that this test is not valid - after the semaphore 2 fails the permits are redistributed so the expected number of permits should really be 20 not 10. Do you agree? I

[GitHub] ignite pull request #1796: IGNITE-4694

GitHub user gvvinblade opened a pull request: https://github.com/apache/ignite/pull/1796 IGNITE-4694 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4694 Alternatively you can review and apply

Re: IgniteSemaphore and failoverSafe flag

Hi Dmitry, it looks to me that this test is not valid - after the semaphore 2 fails the permits are redistributed so the expected number of permits should really be 20 not 10. Do you agree? I guess before latest fix this test was (incorrectly) passing because permits weren't released properly.

[GitHub] ignite pull request #1694: IGNITE-3548 .NET: Rename ILifecycleBean

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1694 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1795: Ignite 1.7.10

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

[GitHub] ignite pull request #1794: swap-related functionality removed in ignite-2.0

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1794 swap-related functionality removed in ignite-2.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-4987) .NET-based cache plugins

Pavel Tupitsyn created IGNITE-4987: -- Summary: .NET-based cache plugins Key: IGNITE-4987 URL: https://issues.apache.org/jira/browse/IGNITE-4987 Project: Ignite Issue Type: New Feature

[GitHub] ignite pull request #1793: IGNITE-4938

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1793 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1793: IGNITE-4938

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/1793 IGNITE-4938 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4938-1 Alternatively you can review and apply

[jira] [Created] (IGNITE-4986) .NET possible affinity resource leak

Alexey Goncharuk created IGNITE-4986: Summary: .NET possible affinity resource leak Key: IGNITE-4986 URL: https://issues.apache.org/jira/browse/IGNITE-4986 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-4985) Atomic cache operations acquire backpressure semaphore on retries

Alexey Goncharuk created IGNITE-4985: Summary: Atomic cache operations acquire backpressure semaphore on retries Key: IGNITE-4985 URL: https://issues.apache.org/jira/browse/IGNITE-4985 Project:

[jira] [Created] (IGNITE-4984) AssertionError GridNearAtomicSingleUpdateFuture.onAllReceived on node left

Semen Boikov created IGNITE-4984: Summary: AssertionError GridNearAtomicSingleUpdateFuture.onAllReceived on node left Key: IGNITE-4984 URL: https://issues.apache.org/jira/browse/IGNITE-4984 Project:

Re: IgniteSemaphore and failoverSafe flag

Hi Vladislav, It looks like after fix was merged these tests [1] started failing. Could you please take a look? [1] http://ci.ignite.apache.org/viewLog.html?buildId=544238=buildResultsDiv=IgniteTests_IgniteBinaryObjectsDataStrucutures Thanks! -Dmitry. 13.04.2017 16:15, Dmitry

[jira] [Created] (IGNITE-4983) .NET: Cache plugins do not work

Pavel Tupitsyn created IGNITE-4983: -- Summary: .NET: Cache plugins do not work Key: IGNITE-4983 URL: https://issues.apache.org/jira/browse/IGNITE-4983 Project: Ignite Issue Type: Bug

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

Because expiry time is 10 seconds, while loop iterates every 5 seconds пт, 14 апр. 2017 г. в 11:32, ALEKSEY KUZNETSOV : > No, the bug is in SQL query, not key-value storage. > > пт, 14 апр. 2017 г. в 11:11, Vladislav Pyatkov : > >> Denis, Aleksey,

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

No, the bug is in SQL query, not key-value storage. пт, 14 апр. 2017 г. в 11:11, Vladislav Pyatkov : > Denis, Aleksey, > > It is correct, remember I have already said something like[1]. > I have no idea, why this happened in this case with SQL. > > [1]: > >

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

Denis, Aleksey, It is correct, remember I have already said something like[1]. I have no idea, why this happened in this case with SQL. [1]: http://apache-ignite-developers.2346864.n4.nabble.com/TouchedExpiryPolicy-works-incorrect-in-some-cases-IGNITE-4401-td16349.html#a16356 On Fri, Apr 14,

[GitHub] ignite pull request #1792: ignite-4982

GitHub user kdudkov opened a pull request: https://github.com/apache/ignite/pull/1792 ignite-4982 GridCacheAbstractRemoveFailureTest (and some child tests) fix You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-4982) GridCacheAbstractRemoveFailureTest fail

Konstantin Dudkov created IGNITE-4982: - Summary: GridCacheAbstractRemoveFailureTest fail Key: IGNITE-4982 URL: https://issues.apache.org/jira/browse/IGNITE-4982 Project: Ignite Issue

Re: question: How data are stored in IgniteCache?

>> when it’s stored in memory in a specific cache partition Does that mean that any serialized object is always stored IN MEMORY as is wrapped by BinaryObjectImpl? 2017-04-14 3:42 GMT+03:00 Denis Magda : > A serialized object is always wrapped by BinaryObjectImpl when it’s

[GitHub] ignite pull request #1595: IGNITE-4758 multiple PageMemory instances were im...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1595 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1279: gg-8.0.1.ea7

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1279 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1119: GG-11547 - RWLock tags

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1119 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1415: Ignite gg 11414

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1415 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1749: IGNITE-4524: Index direct lookup for SQL MIN() an...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1749 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1723: ignite-4851 : made GridDhtLocalPartition state ch...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1723 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1379: gg 8.0.2.ea1

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1379 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1154: gg-8.0.0.ea4

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1154 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-4981) .NET: SQL functions in LINQ

Pavel Tupitsyn created IGNITE-4981: -- Summary: .NET: SQL functions in LINQ Key: IGNITE-4981 URL: https://issues.apache.org/jira/browse/IGNITE-4981 Project: Ignite Issue Type: New Feature

[jira] [Created] (IGNITE-4980) .NET: NuGet packages do not work with PackageReference in VS2017

Pavel Tupitsyn created IGNITE-4980: -- Summary: .NET: NuGet packages do not work with PackageReference in VS2017 Key: IGNITE-4980 URL: https://issues.apache.org/jira/browse/IGNITE-4980 Project: Ignite