New version of Web Console Released

Igniters! I'd like to announce that we redeployed the new version Ignite Web Console on GridGain infrastructure (https://console.gridgain.com) where you can give it a try right a way. *NOTE*: 1) You may need to refresh page (F5 or Ctrl+R) in order to reload Web Console. 2) You will need to

[jira] [Created] (IGNITE-5548) Deadlock Detection uses IgniteCheckedException instead of TransactionTimeoutException

Denis Magda created IGNITE-5548: --- Summary: Deadlock Detection uses IgniteCheckedException instead of TransactionTimeoutException Key: IGNITE-5548 URL: https://issues.apache.org/jira/browse/IGNITE-5548

Re: Transaction Deadlock Detection exception is not wrapped by the timeout exception

Here is a ticket, please fix the degradation in 2.1: https://issues.apache.org/jira/browse/IGNITE-5548 — Denis > On Jun 14, 2017, at 3:17 PM, Denis Magda wrote: > > Andrey, > >> On Jun 14, 2017, at 3:11 AM, Andrey Gura

Re: BinaryObjects and hashCode()

If the server doesn't calculate hash code how it then should work for objects which expired from cache and were pushed to persistent store? As far as persistent store methods (loadCache, load, loadAll) will be executed on server side it looks like server should have custom logic for hashCode()

Re: Cassandra configuration SO question

Igor, which Igor are you asking? (no pun intended) Perhaps it makes sense to explicitly add him to CC. D. On Mon, Jun 19, 2017 at 4:17 PM, Igor Sapego wrote: > Igor, > > Can you please take a look at this question at SO? > >

Re: IgniteCache#localEvict method

Ivan, The semantic now is very confusing, because localEvict does not evict to off-heap, it just removes it from on-heap. The off-heap cache always has the entry anyway. My vote would be to remove this method as I don't see anyone every needing it. Perhaps a more useful method would be to flush

Re: BinaryObjects and hashCode()

Igor, As far as I know, the hash code would be calculated on the client side and sent over within the binary format. Server does not calculate the hash code. D. On Tue, Jun 20, 2017 at 12:08 AM, Igor Rudyak wrote: > Hi, > > I am using simple POJO objects as key/value pair

BinaryObjects and hashCode()

Hi, I am using simple POJO objects as key/value pair for my Ignite cache. Also I would like to store objects as BinaryObjects. Thus Ignite cache was created using: *mycache = ignite.getOrCreateCache("mycache").withKeepBinary()* When I am trying to put objects in the cache I am receiving such an

Re: IgniteCache#localEvict method

Semantics in 2.0: if onheap cache enabled, method evicts entry from it. If onheap cache is disabled (default case), implementation is no-op. Probably we should keep the method and add some note in javadoc. Best Regards, Ivan Rakov On 19.06.2017 17:01, Igor Sapego wrote: What if user enables

[GitHub] ignite pull request #2161: IGNITE-5133: Examples return non-zero on error no...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2161 IGNITE-5133: Examples return non-zero on error now. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5133

Re: IGNITE-2894 - Binary object inside of Externalizable still serialized with OptimizedMarshaller

Hello everebody. I would like to clarify about some moments in marshaller about custom serialization. 1. I suggest to divide the issue into two tasks: support the Externalizable and support the Serializable. The second task is to do as a separate issue. 2. In case the Optimized marshaller when

[GitHub] ignite pull request #2160: IGNITE-2894

GitHub user NSAmelchev opened a pull request: https://github.com/apache/ignite/pull/2160 IGNITE-2894 - Add support Externalizable in BinaryMarshaller. - Use type Object(103) for Externalizable objects. You can merge this pull request into a Git repository by running: $ git

[GitHub] ignite pull request #2159: IGNITE 5529 Reworked ExchangeManager stopping mec...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/2159 IGNITE 5529 Reworked ExchangeManager stopping mechanism You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5529

[jira] [Created] (IGNITE-5547) Slow streaming and long running transactions while load test with 500 logical caches and PDS

Ksenia Rybakova created IGNITE-5547: --- Summary: Slow streaming and long running transactions while load test with 500 logical caches and PDS Key: IGNITE-5547 URL:

[jira] [Created] (IGNITE-5546) Ignite IGFS examples run configuration timeout

Dmitriy Pavlov created IGNITE-5546: -- Summary: Ignite IGFS examples run configuration timeout Key: IGNITE-5546 URL: https://issues.apache.org/jira/browse/IGNITE-5546 Project: Ignite Issue

[jira] [Created] (IGNITE-5545) Ignite PDS1: ignitePdsCheckpointSimulationTest 2 tests failed

Dmitriy Pavlov created IGNITE-5545: -- Summary: Ignite PDS1: ignitePdsCheckpointSimulationTest 2 tests failed Key: IGNITE-5545 URL: https://issues.apache.org/jira/browse/IGNITE-5545 Project: Ignite

Re: IgniteCache#localEvict method

Semantics in 2.0: if onheap cache is enabled, method evicts entry from it. If onheap cache is disabled (default case), implementation is no-op. Probably we should keep the method and add some note in javadoc. Best Regards, Ivan Rakov On 19.06.2017 17:01, Igor Sapego wrote: What if user

Cassandra configuration SO question

Igor, Can you please take a look at this question at SO? https://stackoverflow.com/questions/44589774/configure-apache-ignite-cache-with-cassandra-and-odbc/44630522 Best Regards, Igor

Re: IgniteCache#localEvict method

What if user enables on-heap cache? Best Regards, Igor On Mon, Jun 19, 2017 at 3:34 AM, Dmitriy Setrakyan wrote: > Doesn't look useful to me. > > On Mon, Jun 19, 2017 at 1:03 AM, Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > > > Folks, > > > > Does the

[jira] [Created] (IGNITE-5544) Ignite Cache: floating failure in testBackupRestore

Dmitriy Pavlov created IGNITE-5544: -- Summary: Ignite Cache: floating failure in testBackupRestore Key: IGNITE-5544 URL: https://issues.apache.org/jira/browse/IGNITE-5544 Project: Ignite

[GitHub] ignite pull request #2158: Ignite 5399 Manual cache rebalancing fix

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/2158 Ignite 5399 Manual cache rebalancing fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5399 Alternatively

[jira] [Created] (IGNITE-5543) Partition map update timeout in IgniteCacheP2pUnmarshallingTxErrorTest testResponseMessageOnUnmarshallingFailed

Dmitriy Pavlov created IGNITE-5543: -- Summary: Partition map update timeout in IgniteCacheP2pUnmarshallingTxErrorTest testResponseMessageOnUnmarshallingFailed Key: IGNITE-5543 URL:

[jira] [Created] (IGNITE-5542) Assertion failure in IgniteBasic test IgniteCacheP2pUnmarshallingRebalanceErrorTest.testResponseMessageOnUnmarshallingFailed

Dmitriy Pavlov created IGNITE-5542: -- Summary: Assertion failure in IgniteBasic test IgniteCacheP2pUnmarshallingRebalanceErrorTest.testResponseMessageOnUnmarshallingFailed Key: IGNITE-5542 URL:

[jira] [Created] (IGNITE-5541) PutIfAbsent may return wrong result when primary node fails.

Andrew Mashenkov created IGNITE-5541: Summary: PutIfAbsent may return wrong result when primary node fails. Key: IGNITE-5541 URL: https://issues.apache.org/jira/browse/IGNITE-5541 Project: Ignite

Fwd: Transaction Boundary - Data Streamer

Crossposting to dev. Igniters, Would someone please update documentation that IgniteDataStreamer is not designed to be used inside transactions? -- Forwarded message -- From: Andrey Mashenkov Date: Mon, Jun 19, 2017 at 3:37 PM Subject: Re: Transaction

Re: TeamCity triggers change proposal

Hi Semyon, As far as I know, build Priorities (Build Priority classes) may be created and configured only in relation to specific run (build) configuration, but not in relation to trigger (cause this build was started). Second option which may provide prioritization is agent pools, but still run

[jira] [Created] (IGNITE-5540) Ignite Cache 2 FailoverTest failures: Timeout of waiting for topology map update

Dmitriy Pavlov created IGNITE-5540: -- Summary: Ignite Cache 2 FailoverTest failures: Timeout of waiting for topology map update Key: IGNITE-5540 URL: https://issues.apache.org/jira/browse/IGNITE-5540

Re: TeamCity triggers change proposal

Hi Dmitry, Is it possible instead to set priority for manually started builds higher than for builds triggered by git? Thanks On Fri, Jun 16, 2017 at 2:37 PM, Dmitry Pavlov wrote: > Hi Igniters, > > > > Most of us at least once have faced with situation that we have

[GitHub] ignite pull request #2157: Ignite 2.1.2

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

[jira] [Created] (IGNITE-5539) MemoryMetrics.getTotalAllocatedPages return 0 when persistence is enabled

Alexey Kuznetsov created IGNITE-5539: Summary: MemoryMetrics.getTotalAllocatedPages return 0 when persistence is enabled Key: IGNITE-5539 URL: https://issues.apache.org/jira/browse/IGNITE-5539

Re: IGNITE-532 ready for review

Hi Alex, could you review the integration then? -- Best regards Kozlov Maksim > 24 мая 2017 г., в 22:31, Denis Magda написал(а): > > Got you. Alex K., could you review the integration then? You are an > experienced Scala developer as I know. > > — > Denis > >> On May

[jira] [Created] (IGNITE-5538) NPE (PersistentStoreExample)

Ilya Suntsov created IGNITE-5538: Summary: NPE (PersistentStoreExample) Key: IGNITE-5538 URL: https://issues.apache.org/jira/browse/IGNITE-5538 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-5537) bin/control.sh add validation of input parameters

Ilya Suntsov created IGNITE-5537: Summary: bin/control.sh add validation of input parameters Key: IGNITE-5537 URL: https://issues.apache.org/jira/browse/IGNITE-5537 Project: Ignite Issue

[GitHub] ignite pull request #2094: IGNITE-5306 persist sql flag

Github user kdudkov closed the pull request at: https://github.com/apache/ignite/pull/2094 --- 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 #2146: Ignite 5512

Github user kdudkov closed the pull request at: https://github.com/apache/ignite/pull/2146 --- 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 #2142: fixing tests

Github user kdudkov closed the pull request at: https://github.com/apache/ignite/pull/2142 --- 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 #1657: ignite-4844 remove async queue

Github user kdudkov closed the pull request at: https://github.com/apache/ignite/pull/1657 --- 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 #1671: ignite-4626 topologyImpl

Github user kdudkov closed the pull request at: https://github.com/apache/ignite/pull/1671 --- 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-5535) BLAS support for offheap vector/matrix

Yury Babak created IGNITE-5535: -- Summary: BLAS support for offheap vector/matrix Key: IGNITE-5535 URL: https://issues.apache.org/jira/browse/IGNITE-5535 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-5534) Enable yardstick to activate grid

Ksenia Rybakova created IGNITE-5534: --- Summary: Enable yardstick to activate grid Key: IGNITE-5534 URL: https://issues.apache.org/jira/browse/IGNITE-5534 Project: Ignite Issue Type: Wish