[jira] [Created] (IGNITE-2697) Empty query result with binary marshaller when query argument is user object
Semen Boikov created IGNITE-2697: Summary: Empty query result with binary marshaller when query argument is user object Key: IGNITE-2697 URL: https://issues.apache.org/jira/browse/IGNITE-2697 Project: Ignite Issue Type: Bug Components: cache Reporter: Semen Boikov Assignee: Yakov Zhdanov Priority: Critical Fix For: 1.6 With binary marshaller when query argument is user object then query returns empty result, looks like comparison does not wok in this case. Added test reproducing issue: IgniteBinaryObjectQueryArgumentsTest (please include test in some suite when issue is fixed). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2696) Use another artifacvtID in POM file
Pavel Konstantinov created IGNITE-2696:
--
Summary: Use another artifacvtID in POM file
Key: IGNITE-2696
URL: https://issues.apache.org/jira/browse/IGNITE-2696
Project: Ignite
Issue Type: Sub-task
Reporter: Pavel Konstantinov
Currently we have in pom.xml the following row
{code}
ignite-generated-model
{code}
I suggest to set artifact name more related to cluster name, something like
{code}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2695) ScalarCacheQueryExample failes with BinaryInvalidTypeException
Sergey Kozlov created IGNITE-2695:
-
Summary: ScalarCacheQueryExample failes with
BinaryInvalidTypeException
Key: IGNITE-2695
URL: https://issues.apache.org/jira/browse/IGNITE-2695
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.6
Reporter: Sergey Kozlov
Priority: Critical
Remote node got following exception once ScalarCacheQueryExample run after
ScalarCachePopularNumbersExample
{noformat}
[23:19:05,834][INFO][exchange-worker-#51%null%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=88, minorTopVer=1], evt=DISCOVERY_CUSTOM_EVT,
node=43af46da-0154-4952-b8fd-fd25fe822652]
Exception in thread "pub-#8%null%" class
org.apache.ignite.binary.BinaryInvalidTypeException:
org.apache.ignite.scalar.examples.ScalarCachePopularNumbersExample$IncrementingUpdater
at
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:558)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1442)
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:295)
at
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:277)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:79)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:822)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:785)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException:
org.apache.ignite.scalar.examples.ScalarCachePopularNumbersExample$IncrementingUpdater
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:278)
at
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8195)
at
org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
at
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:549)
... 12 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Binary object inside Externalizable
Folks, I recently faced an issue which seems to be pretty critical. As you know, when binary marshaller meets an Externalizable object, it switches to optimized marshaller. And if there is a regular object inside, it's still serialized with optimized, even if its type is declared in binary configuration with custom mapper, etc. This looks wrong. It's getting even worse in compute grid, because closure processor wraps user's closures in some internal classes, which are Externalizable, so these closures are always serialized with optimized marshaller. Does anyone have ideas on what is the proper fix for this? -Val
Re: Apache Arrow and Apache Ignite
Dmitriy, that's a good question - according to [1] it seems to be a "collection of algorithms and formats" - it is not a storage engine nor is it a processing engine. Weird. [1]. http://www.zdnet.com/article/apache-arrow-unifies-in-memory-big-data-systems/ On 2/19/2016 8:56 PM, Dmitriy Setrakyan wrote: I am a bit unclear from the Apache Arrow website. Is Apache Arrow a columnar in-memory database or is it a processing engine? On Fri, Feb 19, 2016 at 6:31 PM, Dood@ODDO wrote: Hello all - are there any common points between the two? Where can they be made to work together, if at all? Thanks!
Re: Apache Arrow and Apache Ignite
I am a bit unclear from the Apache Arrow website. Is Apache Arrow a columnar in-memory database or is it a processing engine? On Fri, Feb 19, 2016 at 6:31 PM, Dood@ODDO wrote: > Hello all - are there any common points between the two? Where can they be > made to work together, if at all? > > Thanks! >
Apache Arrow and Apache Ignite
Hello all - are there any common points between the two? Where can they be made to work together, if at all? Thanks!
Re: Ignite instance hangs during restart in client mode
Crossposting to dev@. Folks, This is not the first time I see this issue. Is there a way to detect it and throw an exception? -Val On Fri, Feb 19, 2016 at 2:42 PM, vkulichenko wrote: > Hi Vinay, > > Yes, you should always create the configuration object from scratch when > starting a node. Mainly it's because it contains SPIs (e.g., > TcpDiscoverySpi) which have lifecycle and can't be reused. > > Makes sense? > > -Val > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-instance-hangs-during-restart-in-client-mode-tp3101p3106.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
Re: Ignite LinkedIn, Google Plus pages are outdated
Let me look into it and will fix it shortly.
-P
On Fri, Feb 19, 2016 at 3:06 AM, Pavel Tupitsyn
wrote:
> Igniters,
>
> There are links to social networks on ignite.apache.org, and some pages
> are
> outdated ("incubating" and all). How can we get them updated?
>
> Thanks,
>
> --
> --
> Pavel Tupitsyn
> GridGain Systems, Inc.
> www.gridgain.com
>
[jira] [Created] (IGNITE-2694) .NET: AnyCPU build
Pavel Tupitsyn created IGNITE-2694: -- Summary: .NET: AnyCPU build Key: IGNITE-2694 URL: https://issues.apache.org/jira/browse/IGNITE-2694 Project: Ignite Issue Type: Improvement Components: platforms Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Fix For: 1.6 Currently we provide separate x86 & x64 binaries. NuGet is x64-only. This is inconvenient both for us and the user. The only thing that prevents AnyCPU is unmanaged "common" project. But we load it dynamically from resources, and we may as well detect current process platform (x64 or not) and load a proper unmanaged resource. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] ignite pull request: IGNITE-2557: Added ODBC query tests.
GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/503 IGNITE-2557: Added ODBC query tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-2557 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/503.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 #503 commit 3fb85ad44106bace16c71b6f06c235c0e76b4f97 Author: isapego Date: 2016-02-05T13:14:27Z IGNITE-2557: queries test stub added. commit ad73bcf41a68da9144e8c0a6c25046170f93dc74 Author: isapego Date: 2016-02-18T12:44:12Z Merge branch 'ignite-1786' into ignite-2557 commit 8a318e5941fd33220cc29349392ec0ebced989a8 Author: stack-trace Date: 2016-02-19T16:48:59Z IGNITE-2557: Added test utility functions. commit bc7912e59a7c02dd92cfa58cc079fff8f9640f9c Author: stack-trace Date: 2016-02-19T16:49:50Z IGNITE-2557: Added several query tests. commit e1c3d3edcfc7505b7b971cf1fcacc2b61ab3cba5 Author: stack-trace Date: 2016-02-19T17:15:21Z IGNITE-2557: Added Date and Timestamp to quesires test. commit d276df01139bce58e02313bf77386367df95ad31 Author: stack-trace Date: 2016-02-19T18:12:53Z IGNITE-2557: Fix for build systems --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (IGNITE-2693) withKeepBinary and non-ninary marshallers
Sergey Kozlov created IGNITE-2693:
-
Summary: withKeepBinary and non-ninary marshallers
Key: IGNITE-2693
URL: https://issues.apache.org/jira/browse/IGNITE-2693
Project: Ignite
Issue Type: Bug
Components: general
Reporter: Sergey Kozlov
Assignee: Alexey Goncharuk
Currently the user is able to set {{.withKeepBinary()}} for any used
marshaller. But it obviously causes ClassCastException for non-binary
marshallers and should be available only for binary marshaller.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2692) Set thread local context in IgnitionEx to affect cache functions
Dmitry Karachentsev created IGNITE-2692: --- Summary: Set thread local context in IgnitionEx to affect cache functions Key: IGNITE-2692 URL: https://issues.apache.org/jira/browse/IGNITE-2692 Project: Ignite Issue Type: Sub-task Components: general Affects Versions: 1.5.0.final Reporter: Dmitry Karachentsev Assignee: Dmitry Karachentsev Priority: Critical Fix For: 1.6 For any usage of cache from single user thread must be initialized thread local context in IgnitionEx to support Ignition.localIgnite() in marshalling functions. In other words, any code that might be called during marshaling must be able to get Ignite instance from Ignition.localIgnite(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2691) Wrap all Marshaller interface usage to set thread local context in IgnitionEx
Dmitry Karachentsev created IGNITE-2691: --- Summary: Wrap all Marshaller interface usage to set thread local context in IgnitionEx Key: IGNITE-2691 URL: https://issues.apache.org/jira/browse/IGNITE-2691 Project: Ignite Issue Type: Sub-task Components: general Affects Versions: 1.5.0.final Reporter: Dmitry Karachentsev Assignee: Dmitry Karachentsev Priority: Critical Fix For: 1.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: scalar module docs
On 2/19/2016 4:53 AM, Roman Shtykh wrote: Igniters, Any reason for 'scalar' module not to be exposed on readme.io/ignite.apache.org, and no scaladoc link? -Roman Roman, in my humble opinion it is a good thing scalar is not mentioned anywhere - it is a rather "strange" method of using Ignite from Scala and it doesn't really work anyways - last time I used it there were multiple problems with it. My $.02
[GitHub] ignite pull request: Ignite 2525
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/494 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] ignite pull request: IGNITE-2600 .NET: Do not serialize object if ...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/496 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] ignite pull request: IGNITE-2679 .NET: Implement Ignition.TryGetIg...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/497 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] ignite pull request: IGNITE-1626 .Net: Create NuGet package.
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/342 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (IGNITE-2690) Format of uptime for metrics
Sergey Kozlov created IGNITE-2690:
-
Summary: Format of uptime for metrics
Key: IGNITE-2690
URL: https://issues.apache.org/jira/browse/IGNITE-2690
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.5.0.final
Reporter: Sergey Kozlov
Priority: Trivial
Milliseconds of uptime from metrics should be properly formatted (3 digits):
{noformat}
[16:35:08,994][INFO][grid-timeout-worker-#33%null%][IgniteKernal]
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=fcc9d9ca, name=null, uptime=01:04:00:996]
...
[16:36:09,011][INFO][grid-timeout-worker-#33%null%][IgniteKernal]
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=fcc9d9ca, name=null, uptime=01:05:01:14]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] ignite pull request: fix IGNITE-2650
GitHub user ruskim opened a pull request: https://github.com/apache/ignite/pull/502 fix IGNITE-2650 - Added checkClient to to IgniteSpiConsistencyChecked annotation with default value true. If it's false, than spi consistency will not be checked for client nodes. - Added IgniteSpiConsistencyChecked to NoopSwapSpaceSpi and FileSwapSpaceSpi. That guaranties, that all nodes in grid will have the same swap space provider. Client nodes ignore this check, because clients don't have any data. - Cache with swap creation will fail, if nodes in grid have NoopSwapSpaceSpi You can merge this pull request into a Git repository by running: $ git pull https://github.com/ruskim/ignite ignite-2650 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/502.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 #502 commit 4b7996ad92d452ecd0ff11e1181754e712009da0 Author: ruskim Date: 2016-02-19T12:26:37Z fix IGNITE-2650 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] ignite pull request: Ignite 2352
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/501 Ignite 2352 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-2352 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/501.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 #501 commit a652adec401dc11e6f930fcef9de9b2ee5ecdbb9 Author: iveselovskiy Date: 2016-02-10T15:54:36Z added missing file header to org.apache.ignite.hadoop.fs.KerberosHadoopFileSystemFactorySelfTest commit 48f00cac3ba7668247585ab7c257562951c4f04f Author: iveselovskiy Date: 2016-02-11T10:36:12Z Merge branch 'master' of https://github.com/apache/ignite commit a5c5ed4d5bbd61c62acfbb19610aac2f710935cd Author: iveselovskiy Date: 2016-02-15T17:58:10Z Merge branch 'master' of https://github.com/apache/ignite commit b81ee18308307dad2416f7635120a387b98bb967 Author: iveselovskiy Date: 2016-02-17T18:32:53Z Merge branch 'master' of https://github.com/apache/ignite commit 4280cbdeef94a6956ea3ebe1ae389f1db57ed249 Author: iveselovskiy Date: 2016-02-18T09:47:12Z Merge branch 'master' of https://github.com/apache/ignite commit f8a58e112f53f217dce9038efb136f6ee11eba58 Author: iveselovskiy Date: 2016-02-18T11:54:47Z WIP 3252. commit 90c68b3ec9acc1468659e3d69f1cab55cbbaab44 Author: iveselovskiy Date: 2016-02-18T17:02:32Z Merge branch 'master' of https://github.com/apache/ignite into ignite-2352 commit b433dba66a3387ecf81721e51ff9eed3dbf2e270 Author: iveselovskiy Date: 2016-02-19T07:41:50Z workable solution, but 2 hadoop tests do not work. commit 617191e3fed7beab75308b152e4b2d7639c5b6e2 Author: iveselovskiy Date: 2016-02-19T09:28:33Z Merge branch 'master' of https://github.com/apache/ignite into ignite-2352 commit fcfb882f6cc307c7fac0a23b8f542dd585a0cda5 Author: iveselovskiy Date: 2016-02-19T12:08:40Z IGNITE-2352: all known cases fixed, + cleanup, tests passed. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] ignite pull request: IGNITE-2579
GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/500 IGNITE-2579 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ilantukh/ignite ignite-2579 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/500.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 #500 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Ignite LinkedIn, Google Plus pages are outdated
Igniters,
There are links to social networks on ignite.apache.org, and some pages are
outdated ("incubating" and all). How can we get them updated?
Thanks,
--
--
Pavel Tupitsyn
GridGain Systems, Inc.
www.gridgain.com
scalar module docs
Igniters, Any reason for 'scalar' module not to be exposed on readme.io/ignite.apache.org, and no scaladoc link? -Roman
[GitHub] ignite pull request: IGNITE-2689: Marked Date/Time features as sup...
GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/499 IGNITE-2689: Marked Date/Time features as supported. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-2689 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/499.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 #499 commit 573a527ddbbba2d6e6dc690e691a5d3d48b0c17b Author: stack-trace Date: 2016-02-19T09:44:01Z IGNITE-2689: Marked Date/Time features as supported. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (IGNITE-2689) ODBC: Mark Date/Time scalar functions as supported.
Igor Sapego created IGNITE-2689:
---
Summary: ODBC: Mark Date/Time scalar functions as supported.
Key: IGNITE-2689
URL: https://issues.apache.org/jira/browse/IGNITE-2689
Project: Ignite
Issue Type: Sub-task
Components: odbc
Affects Versions: 1.5.0.final
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
Currently {{SQLGetInfo}} returns {{0}} when {{SQL_SQL92_DATETIME_FUNCTIONS}}
and {{SQL_DATETIME_LITERALS}} attributes are requested. Mark the following
features as supported:
{{SQL_SDF_CURRENT_DATE}}
{{SQL_SDF_CURRENT_TIMESTAMP}}
{{SQL_DL_SQL92_DATE}}
{{SQL_DL_SQL92_TIME}}
{{SQL_DL_SQL92_TIMESTAMP}}
{{SQL_DL_SQL92_INTERVAL_YEAR}}
{{SQL_DL_SQL92_INTERVAL_MONTH}}
{{SQL_DL_SQL92_INTERVAL_DAY}}
{{SQL_DL_SQL92_INTERVAL_HOUR}}
{{SQL_DL_SQL92_INTERVAL_MINUTE}}
{{SQL_DL_SQL92_INTERVAL_SECOND}}
{{SQL_DL_SQL92_INTERVAL_YEAR_TO_MONTH}}
{{SQL_DL_SQL92_INTERVAL_DAY_TO_HOUR}}
{{SQL_DL_SQL92_INTERVAL_DAY_TO_MINUTE}}
{{SQL_DL_SQL92_INTERVAL_DAY_TO_SECOND}}
{{SQL_DL_SQL92_INTERVAL_HOUR_TO_MINUTE}}
{{SQL_DL_SQL92_INTERVAL_HOUR_TO_SECOND}}
{{SQL_DL_SQL92_INTERVAL_MINUTE_TO_SECOND}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2688) InterruptException for segmentation issues
Sergey Kozlov created IGNITE-2688:
-
Summary: InterruptException for segmentation issues
Key: IGNITE-2688
URL: https://issues.apache.org/jira/browse/IGNITE-2688
Project: Ignite
Issue Type: Bug
Reporter: Sergey Kozlov
Assignee: Denis Magda
Priority: Minor
We're still seeing following exception for segmentation issues:
{noformat}
[18:16:31,566][WARNING][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi] Node is
out of topology (probably, due to short-time network problems).
[18:16:31,566][WARNING][disco-event-worker-#46%null%][GridDiscoveryManager]
Local node SEGMENTED: TcpDiscoveryNode
[id=19cf4b0f-d520-4915-be9f-813a99f945a5, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1,
172.22.222.44, 192.168.1.117], sockAddrs=[work-pc/172.22.222.44:47501,
/0:0:0:0:0:0:0:1:47501, /172.22.222.44:47501, /127.0.0.1:47501,
/172.22.222.44:47501, /192.168.1.117:47501], discPort=47501, order=4,
intOrder=4, lastExchangeTime=1455808591566, loc=true,
ver=1.6.0#19700101-sha1:, isClient=false]
[18:16:31,629][SEVERE][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi]
TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node in
order to prevent cluster wide instability.
java.lang.InterruptedException
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2017)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2095)
at
java.util.concurrent.LinkedBlockingDeque.pollFirst(LinkedBlockingDeque.java:519)
at
java.util.concurrent.LinkedBlockingDeque.poll(LinkedBlockingDeque.java:682)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5786)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2160)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
[18:16:31,851][WARNING][sys-#22%null%][GridDhtAtomicCache]
Failed to send near update reply to node
because it left grid: fad03851-2077-4b50-92b3-00ec6d85fa39
[18:16:31,866][WARNING][disco-event-worker-#46%null%][GridDiscoveryManager]
Stopping local node according to configured segmentation policy.
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Java proxy for .NET service
Hi Val, Currently this is not supported, but you are right, this is not very difficult to add. I've created two issues in Jira ([1], [2]). They are both Java-only, no changes are required in .NET. [1] https://issues.apache.org/jira/browse/IGNITE-2686 [2] https://issues.apache.org/jira/browse/IGNITE-2687 Thanks, On Fri, Feb 19, 2016 at 10:31 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Igniters, > > One of our users is asking me if this is possible to have a proxy on Java > client for a service implemented in .NET (and vica versa). He tried to do > this, but without success. Is it not supported or he is doing something > wrong? > > For me it sounds like a useful feature and I don't see any fundamental > reasons not to have it. > > Thoughts? > > -Val > -- -- Pavel Tupitsyn GridGain Systems, Inc. www.gridgain.com
[jira] [Created] (IGNITE-2687) Call .NET services from Java
Pavel Tupitsyn created IGNITE-2687: -- Summary: Call .NET services from Java Key: IGNITE-2687 URL: https://issues.apache.org/jira/browse/IGNITE-2687 Project: Ignite Issue Type: New Feature Components: managed services, platforms Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Fix For: 1.6 .NET services can be called via PlatformDotNetService interface, providing method name and arguments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2686) .NET: Call Java services
Pavel Tupitsyn created IGNITE-2686: -- Summary: .NET: Call Java services Key: IGNITE-2686 URL: https://issues.apache.org/jira/browse/IGNITE-2686 Project: Ignite Issue Type: New Feature Components: platforms Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Fix For: 1.6 Add support for Java service calls (see OP_DOTNET_INVOKE in PlatformServices). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] ignite pull request: gg-11016 : Fixed.
GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/498 gg-11016 : Fixed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ilantukh/ignite ignite-gg-11016 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/498.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 #498 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Cassandra cache store [IGNITE-1371]
I'm quite sure that 1.6 release won't be ready in a month. So you have a plenty of time to finish your ticket ;) On 2/19/2016 10:54 AM, irudyak wrote: Well, it just depends on how soon you are going to publish release 1.6. It will take about 1 month for me to implement PersistenceCallback. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Cassandra-cache-store-IGNITE-1371-tp6880p7466.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
Re: Cassandra cache store [IGNITE-1371]
Well, it just depends on how soon you are going to publish release 1.6. It will take about 1 month for me to implement PersistenceCallback. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Cassandra-cache-store-IGNITE-1371-tp6880p7466.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
Ignite Add-ons
Hello Everyone! Today we have added a new "Add-ons" page to the Ignite website. Ignite add-ons are projects that intend to make user experience with Ignite easier. To contribute your add-on to Ignite, send an email to dev lis Please visit this page for more details: https://ignite.apache.org/addons.html -- Alexey Kuznetsov
