Re: Ignite cluster with persistent store enabled did not load from wal after restarting.

Ray, This looks odd. Sure, data has to be available for you after the restart, it's a basic capability. Then I tend to agree with the rest of the folks that you might haven encountered the issue mentioned by Yakov. To to be 100% sure about that please do the following: * Clean "work/db"

Re: Ignite cluster with persistent store enabled did not load from wal after restarting.

Dmitriy, Check up Ray’s initial message. There is no single cache.get command or SQL query that can trigger data movement from disk to RAM. Plus, the output generated after the restart suggests that the node found all the persistence directories. Thus, not sure how this issue is related to

Re: Ignite PDS WAL analysis with human readable records

Hi Denis, Thank you for your feedback. It is very important to us to understand that this tool may be useful not only for Ignite tests but for all developers. I will create wiki page. Sincerely, Dmitriy Pavlov сб, 16 сент. 2017 г. в 1:54, Denis Magda : > Dmitriy, Eduard, >

Re: Ignite cluster with persistent store enabled did not load from wal after restarting.

Hi Denis, I agree that data presence should be double-checked. In case check will show that 1) cache doesn't exist at all after restart and 2) we can find two folders with binary_meta and wal that means this question is similar with recent question

Re: Ignite PDS WAL analysis with human readable records

Dmitriy, Eduard, Sounds like a useful thing. I’ll be happy to give a feedback but need a documentation that explains how to use the tool, what’s the output format, how do decipher the output, etc (basic things). The Wiki description should be enough. — Denis > On Sep 15, 2017, at 11:36 AM,

Re: HOLE query entry in CacheContinuousQueryPartitionRecovery

I like the name. "Black holes" pop up first in my head :) The hole can absorb events and confine and digest them for billions of year. Sorry for off topic. — Denis > On Sep 15, 2017, at 10:14 AM, ALEKSEY KUZNETSOV > wrote: > > Hi, Ignters! > > > We have a strange

Re: Durable Memory and Ignite Persistence Tuning

Thanks Ivan, *no less* sounds best for me. Prachi, please do final editing of the doc: https://apacheignite.readme.io/v2.1/docs/durable-memory-tuning — Denis > On Sep 15, 2017, at 12:24 AM, Ivan Rakov wrote: > > Denis, > > Yes, Ignite page size should be *greater or

Re: Monitoring of active transactions

Hi Ilya, I can help with including this utility into build/release, I've recenty finished same steps for PDS WAL analysing tool for converting records to human readable format. Please feel free to contact me. Sincerely, Dmitriy Pavlov пт, 15 сент. 2017 г. в 6:37, Dmitriy Setrakyan

Ignite Full Description on Docker Hub

Nick, I want to fill out full description section on Docker Hub. Presently, it’s poor: https://hub.docker.com/r/apacheignite/ignite/ Is it enough to update ignite/modules/docker/README.txt and push the changes to master? Guess, there are extra steps. — Denis

Re: Ignite Benchmarking Rules

Cos, I think Apache BigTop is using servers provided by Amazon. Can you make a suggestion on how can Ignite community get a few servers from Amazon for benchmarking as well? D. On Fri, Sep 15, 2017 at 5:57 AM, Anton Vinogradov wrote: > Guys, > > I fully agree that configured

Ignite PDS WAL analysis with human readable records

Hi Igniters, Eduard Shangareev created WAL converter utility which shows WAL archive/work directory segments content in human readable form. This utility outputs all WAL records to output stream (may be redirected to file). How to use tips can be found in issue

HOLE query entry in CacheContinuousQueryPartitionRecovery

Hi, Ignters! We have a strange field HOLE in CacheContinuousQueryPartitionRecovery which compared to pending events in CacheContinuousQueryPartitionRecovery#collectEntries. And it is never equals any entry. Do we need it ? Or it can be removed. -- *Best Regards,* *Kuznetsov Aleksey*

[GitHub] ignite pull request #2091: IGNITE-1553 Optimize transaction prepare step whe...

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

[GitHub] ignite pull request #2332: Ignite 1094

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

[GitHub] ignite pull request #1557: IGNITE-2845 Get operation might ignore entry upda...

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

[GitHub] ignite pull request #2126: IGNITE-1094 recovery resolved

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

Re: Unintuitive error message when invalid marshaller files found

Mike, Can you show the exception that is thrown? -Val On Fri, Sep 15, 2017 at 7:12 AM, Michael Griggs wrote: > This afternoon I came across an unusual case where there were files in > my work/marshaller folder with invalid filenames. It seems that the > valid format is

[GitHub] ignite pull request #2677: ignite-5960 Sending backupQueue to node.

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2677 ignite-5960 Sending backupQueue to node. You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-5960-3 Alternatively you can

[jira] [Created] (IGNITE-6405) Deadlock is not detected if timed out on client.

Alexei Scherbakov created IGNITE-6405: - Summary: Deadlock is not detected if timed out on client. Key: IGNITE-6405 URL: https://issues.apache.org/jira/browse/IGNITE-6405 Project: Ignite

[GitHub] ignite pull request #2676: Ignite-gg-12717

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2676 Ignite-gg-12717 fix test You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12717 Alternatively you can

[jira] [Created] (IGNITE-6404) Failures in .NET test suite

Vladimir Ozerov created IGNITE-6404: --- Summary: Failures in .NET test suite Key: IGNITE-6404 URL: https://issues.apache.org/jira/browse/IGNITE-6404 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-6403) IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues fails periodically

Vladimir Ozerov created IGNITE-6403: --- Summary: IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues fails periodically Key: IGNITE-6403 URL:

[jira] [Created] (IGNITE-6402) Make yardstick delete config-db from and not copy logs to remotes

Ksenia Rybakova created IGNITE-6402: --- Summary: Make yardstick delete config-db from and not copy logs to remotes Key: IGNITE-6402 URL: https://issues.apache.org/jira/browse/IGNITE-6402 Project:

[jira] [Created] (IGNITE-6401) Change size to maxSize for memory config in ignite-base-load-config.xml

Ksenia Rybakova created IGNITE-6401: --- Summary: Change size to maxSize for memory config in ignite-base-load-config.xml Key: IGNITE-6401 URL: https://issues.apache.org/jira/browse/IGNITE-6401

[GitHub] ignite pull request #2603: IGNITE-6256: DiscoCache should always contains lo...

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

[GitHub] ignite pull request #2675: Ignite-gg-12692

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2675 Ignite-gg-12692 for tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12692 Alternatively you can

[GitHub] ignite pull request #2674: Ignite 5136 GridLogThrottle memory leak

GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/2674 Ignite 5136 GridLogThrottle memory leak You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-5136-li Alternatively you

[GitHub] ignite pull request #2673: IGNITE-6395: remove old test

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

[GitHub] ignite pull request #2671: IGNITE-6394: Can't create off-heap matrix with si...

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

Unintuitive error message when invalid marshaller files found

This afternoon I came across an unusual case where there were files in my work/marshaller folder with invalid filenames.  It seems that the valid format is -[0-9]+.classname[0-9].  However, I had files that were in the format -[0-9]+.classname - i.e., no trailing zero.  Where these files came from

[GitHub] ignite pull request #2673: IGNITE-6395: remove old test

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2673 IGNITE-6395: remove old test You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6395 Alternatively you

Re: Ignite cluster with persistent store enabled did not load from wal after restarting.

Ray, Yakov just pointed me to this thread where user had a problem with IP address changing between the cluster restarts. The persistent data directories inside work/db have names

[jira] [Created] (IGNITE-6399) .NET: support ClientConnectorConfiguration

Vladimir Ozerov created IGNITE-6399: --- Summary: .NET: support ClientConnectorConfiguration Key: IGNITE-6399 URL: https://issues.apache.org/jira/browse/IGNITE-6399 Project: Ignite Issue

[jira] [Created] (IGNITE-6400) Document ClientConnectorConfiguration

Vladimir Ozerov created IGNITE-6400: --- Summary: Document ClientConnectorConfiguration Key: IGNITE-6400 URL: https://issues.apache.org/jira/browse/IGNITE-6400 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6398) WebConsole: support ClientConnectorConfiguration

Vladimir Ozerov created IGNITE-6398: --- Summary: WebConsole: support ClientConnectorConfiguration Key: IGNITE-6398 URL: https://issues.apache.org/jira/browse/IGNITE-6398 Project: Ignite

[GitHub] ignite pull request #2672: IGNITE-6327

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

Re: Ignite cluster with persistent store enabled did not load from wal after restarting.

Guys, it seems that we have the same issue that was described in thread - Specifying location of persistent storage location I filed a ticket some time ago - https://issues.apache.org/jira/browse/IGNITE-6285, Alex G, can you take a look if this ticket makes sense? --Yakov

Re: Ignite Benchmarking Rules

Guys, I fully agree that configured servers at Amazon is the best choice. But when you need to check that your changes has no performance drop you're able to use your own PC or PCs to checks that. All you need is to benchmark already released version vs version with your fix at same environment.

[GitHub] ignite pull request #2542: IGNITE-5905 .NET: Thin client: cache.Get for prim...

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

[GitHub] ignite pull request #2625: IGNITE-6244 .NET: Thin client: ScanQuery

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

[GitHub] ignite pull request #2580: IGNITE-6236 .NET: Thin client: cache.Get and Put ...

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

[jira] [Created] (IGNITE-6397) .NET thin client: implement base cache operations

Vladimir Ozerov created IGNITE-6397: --- Summary: .NET thin client: implement base cache operations Key: IGNITE-6397 URL: https://issues.apache.org/jira/browse/IGNITE-6397 Project: Ignite

[GitHub] ignite pull request #2562: IGNITE-6225: Improve tests of WAL iterator with c...

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

[GitHub] ignite pull request #2671: IGNITE-6394: Can't create off-heap matrix with si...

GitHub user ybabak opened a pull request: https://github.com/apache/ignite/pull/2671 IGNITE-6394: Can't create off-heap matrix with size over 2 Gb Fixed int overflow. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2620: Ignite 6235: Add ability to handle CacheObject fr...

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

[jira] [Created] (IGNITE-6396) SQL: Support SQLSTATE error code for "NOT NULL" constraint

Vladimir Ozerov created IGNITE-6396: --- Summary: SQL: Support SQLSTATE error code for "NOT NULL" constraint Key: IGNITE-6396 URL: https://issues.apache.org/jira/browse/IGNITE-6396 Project: Ignite

[jira] [Created] (IGNITE-6395) Uncomment JdbcThinStatementSelfTest.testCloseOnCompletion

Vladimir Ozerov created IGNITE-6395: --- Summary: Uncomment JdbcThinStatementSelfTest.testCloseOnCompletion Key: IGNITE-6395 URL: https://issues.apache.org/jira/browse/IGNITE-6395 Project: Ignite

[jira] [Created] (IGNITE-6394) Can't create off-heap matrix with size over 2 Gb (int overflow in DenseOffHeapMatrixStorage.allocateMemory)

Oleg Ignatenko created IGNITE-6394: -- Summary: Can't create off-heap matrix with size over 2 Gb (int overflow in DenseOffHeapMatrixStorage.allocateMemory) Key: IGNITE-6394 URL:

[jira] [Created] (IGNITE-6393) ODBC: need to cleanup server cursors on client disconnect

Vladimir Ozerov created IGNITE-6393: --- Summary: ODBC: need to cleanup server cursors on client disconnect Key: IGNITE-6393 URL: https://issues.apache.org/jira/browse/IGNITE-6393 Project: Ignite

[jira] [Created] (IGNITE-6392) JDBC thin driver: need to cleanup server cursors on client disconnect

Vladimir Ozerov created IGNITE-6392: --- Summary: JDBC thin driver: need to cleanup server cursors on client disconnect Key: IGNITE-6392 URL: https://issues.apache.org/jira/browse/IGNITE-6392 Project:

[GitHub] ignite pull request #2670: IGNITE-6368 .NET: Separate interfaces for Ignite ...

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

[GitHub] ignite pull request #2496: IGNITE-6137: CAS logic fix in async commit.

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

[GitHub] ignite pull request #2605: Ignite 6277

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

[jira] [Created] (IGNITE-6390) Implement usable component cluster-selector on dependence pages

Dmitriy Shabalin created IGNITE-6390: Summary: Implement usable component cluster-selector on dependence pages Key: IGNITE-6390 URL: https://issues.apache.org/jira/browse/IGNITE-6390 Project:

[GitHub] ignite pull request #2670: IGNITE-6368 .NET: Separate interfaces for Ignite ...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2670 IGNITE-6368 .NET: Separate interfaces for Ignite and Cache facades for thin client You can merge this pull request into a Git repository by running: $ git pull

Re: Expiry policy for Cache.invoke

I filed a ticket for this issue: https://issues.apache.org/jira/browse/IGNITE-6388 Also I stumbled upon another bug, trying to reproduce the previous one. Here is a ticket: https://issues.apache.org/jira/browse/IGNITE-6389 Denis пт, 15 сент. 2017 г. в 3:07, Valentin Kulichenko <

Re: Ignite Benchmarking Rules

Hello, Dmitriy. I think experienced members of community have specific number for benchmarking. Can we start from reference hardware configuration: Num of CPU, RAM and HDD(SDD?) configuration, network configs, etc. Can someone share that kind of knowledge - Which hardware is best for

[jira] [Created] (IGNITE-6389) Cache.invoke fails on atomic cache with configured AccessedExpiryPolicy

Denis Mekhanikov created IGNITE-6389: Summary: Cache.invoke fails on atomic cache with configured AccessedExpiryPolicy Key: IGNITE-6389 URL: https://issues.apache.org/jira/browse/IGNITE-6389

[jira] [Created] (IGNITE-6388) ExpiryPolicy is used incorrectly during invoke

Denis Mekhanikov created IGNITE-6388: Summary: ExpiryPolicy is used incorrectly during invoke Key: IGNITE-6388 URL: https://issues.apache.org/jira/browse/IGNITE-6388 Project: Ignite

[jira] [Created] (IGNITE-6387) SQL: NOT NULL fields validation with read-through cache store

Sergey Kalashnikov created IGNITE-6387: -- Summary: SQL: NOT NULL fields validation with read-through cache store Key: IGNITE-6387 URL: https://issues.apache.org/jira/browse/IGNITE-6387 Project:

[GitHub] ignite pull request #2669: Ignite 1.9.6 b4

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

[GitHub] ignite pull request #2609: ignite-6289 Remove "allOrNone" flag from IgniteSe...

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

[GitHub] ignite pull request #2590: IGNITE-5817 Changed checksum calculation methods

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

[GitHub] ignite pull request #2535: IGNITE-6182

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

[GitHub] ignite pull request #2586: IGNITE-6237 created script for signing and upload...

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

Re: Durable Memory and Ignite Persistence Tuning

Denis, Yes, Ignite page size should be *greater or equal* than OS page cache size and SSD page size. I mentioned it in advice list: page size of Ignite shouldn't be less than SSD page size Page size of Ignite shouldn't be less than OS page size Sorry for vague wording. We should fix this

[GitHub] ignite pull request #2668: ignite-5960 race fixed

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2668 ignite-5960 race fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-5960-final Alternatively you can review and apply