Re: Eviction policies with persistence

Hi Valentin, As far as I know, when persistence is enabled and Ignite can't allocate new page-memory in the memory segment, then Ignite automatically evict some data from RAM to PDS using Random-2-LRU eviction algorithm. And there are no mechanisms to evict entries out when PDS is enabled. I'll b

[jira] [Created] (IGNITE-7597) visorcmd: remove cache variable (@c) after cache was stopped

Pavel Konstantinov created IGNITE-7597: -- Summary: visorcmd: remove cache variable (@c) after cache was stopped Key: IGNITE-7597 URL: https://issues.apache.org/jira/browse/IGNITE-7597 Project: Ign

Fwd: How to circumvent that a cache store adapter class needs to be on the classpath of a client node

Cross posting to dev@. Igniters, do we really require CacheStoreAdapter on the client side for non-transactional caches? D. -- Forwarded message -- From: Andrey Mashenkov Date: Wed, Jan 31, 2018 at 8:34 AM Subject: Re: How to circumvent that a cache store adapter class needs to

[jira] [Created] (IGNITE-7596) Add Functionality for data structures to be able to remove any failed node on data structure creation

Tim Onyschak created IGNITE-7596: Summary: Add Functionality for data structures to be able to remove any failed node on data structure creation Key: IGNITE-7596 URL: https://issues.apache.org/jira/browse/IGNITE-7

[GitHub] ignite pull request #3138: IGNITE-7090

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

Fwd: Ignite work directory usage?

Cross sending to dev@. Would be nice to hear from the Ignite community. How critical is this issue and does it still exist? D. -- Forwarded message -- From: Denis Magda Date: Tue, Jan 9, 2018 at 2:28 PM Subject: Re: Ignite work directory usage? To: u...@ignite.apache.org It ne

Fwd: Semaphore Stuck when no acquirers to assign permit

Hi Tim, Vlad, Any update on this ticket? I looked inside, but cannot understand the status. Thanks, D. -- Forwarded message -- From: Denis Magda Date: Fri, Jan 19, 2018 at 9:14 PM Subject: Re: Semaphore Stuck when no acquirers to assign permit To: u...@ignite.apache.org, dev@ign

Eviction policies with persistence

Folks, On "Eviction Policies" documentation page [1] we have the following callout: > Configured eviction policy has no effect if Ignite persistence is enabled > Note that if Ignite Persistence is enabled, then the page-based evictions have no effect because the oldest pages will be purged from m

Re: Stop nodes after test by default - IGNITE-6842

Hello Maxim, Granted you all the required permissions in JIRA. Feel free to assign the ticket to your account. In general, review how the testing framework works in Ignite and you’ll get why we stop all the nodes manually. It will help to get answers on most of the questions. Please propose y

Re: Move documentation from readme.io to GitHub pages

Created a ticket. I think the time to move from readme.io has come. It’s becoming too challenging to live with it: https://issues.apache.org/jira/browse/IGNITE-7595 — Denis > On Apr 13, 2017, at 8:25 AM, Dmitriy Setrakyan

[jira] [Created] (IGNITE-7595) Find and switch to alternate documentation engine

Denis Magda created IGNITE-7595: --- Summary: Find and switch to alternate documentation engine Key: IGNITE-7595 URL: https://issues.apache.org/jira/browse/IGNITE-7595 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7594) Tx performance drop after WAL optimization

Aleksey Chetaev created IGNITE-7594: --- Summary: Tx performance drop after WAL optimization Key: IGNITE-7594 URL: https://issues.apache.org/jira/browse/IGNITE-7594 Project: Ignite Issue Type

Re: Thin client failover mechanism (+ODBC, JDBC)

Pavel, I disagree. I think automatic reconnect is a very useful feature. For example, all client-side operation can throw exception anyway, so if you throw an exception due to a client reconnect, it will not require any additional exception-handling logic. On the other hand, after a few failed op

[GitHub] ignite pull request #3400: Ignite 6946: Change Ignite Logger configuration o...

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

Re: Get TTL of the specific (K,V) entry

Cross-posting to dev. Igniters, This actually makes sense to me. Why don't we add IgniteCache#ttl(K key) method that would return current TTL for the key? Looks like this is already provided by GridCacheMapEntry#ttl() method, so we only need to properly expose it to public API. Am I right? If th

Re: Annoying extra steps for enabling metrics

Alex, As a workaround, you can use boxed Boolean as a field type, and then return true from getEventsEnabled in case it's null. Will this work? -Val On Wed, Jan 31, 2018 at 7:31 AM, Alex Plehanov wrote: > Denis, there is a question about IGNITE-7346. > > CacheConfiguration fields are set to th

Fwd: ApacheCon North America 2018, September 24-28, Montreal

Ignite community, who is willing to take part in the Apache conference and present Ignite there? — Denis > Begin forwarded message: > > From: Rich Bowen > Subject: ApacheCon North America 2018, September 24-28, Montreal > Date: January 29, 2018 at 5:49:34 AM PST > To: committ...@apache.org > R

Conference talk: Microservices with Ignite in action

Igniters, If you’re around San Francisco Bay Area stop by my talk about Ignite capabilities for microservices capabilities: https://developerweeksfbayarea2018.sched.com/event/D6C7 — Denis

[jira] [Created] (IGNITE-7593) Improve data used in DecisionTreesExample

Oleg Ignatenko created IGNITE-7593: -- Summary: Improve data used in DecisionTreesExample Key: IGNITE-7593 URL: https://issues.apache.org/jira/browse/IGNITE-7593 Project: Ignite Issue Type: Ta

[GitHub] ignite pull request #3459: IGNITE-7590: Change example for decision trees

GitHub user artemmalykh opened a pull request: https://github.com/apache/ignite/pull/3459 IGNITE-7590: Change example for decision trees You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7590 Alternat

Stop nodes after test by default - IGNITE-6842

Hello everyone! I would like to take this one issue for implicating myself into Ignite community. https://issues.apache.org/jira/browse/IGNITE-6842 Can you help me with granting contributor permissons? My JIRA ID: mmuzaf e-mail: maxmu...@gmail.com So I can assign this ticket for myself, If you d

[GitHub] ignite pull request #3458: IGNITE-7584: WAL log throttle implementation

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3458 IGNITE-7584: WAL log throttle implementation You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7584 Alternatively

Re: Annoying extra steps for enabling metrics

Denis, there is a question about IGNITE-7346. CacheConfiguration fields are set to they default values when cache configuration is created by constructor. When CacheConfiguration is created by deserialization (from another node or from PDS), constructor is not called. If it was serialized by older

Backup node crash causes incorrect transaction failover recovery

Hi, Igntrs! While testing transaction failover recovery mechanisms I came across a bug. When we have multiple consequent transactions changing the same key and backup node crashes during prepare phase, not all changes are applied. This bug is flaky and arises only if there are 2 or more conseq

[jira] [Created] (IGNITE-7592) Cache with rebalanceDelay == -1 doesn't trigger late affinity assignment even after explicit rebalance is called on every node

Ilya Lantukh created IGNITE-7592: Summary: Cache with rebalanceDelay == -1 doesn't trigger late affinity assignment even after explicit rebalance is called on every node Key: IGNITE-7592 URL: https://issues.apache

[jira] [Created] (IGNITE-7591) Backup node crash causes incorrect failover

Alexey Kuznetsov created IGNITE-7591: Summary: Backup node crash causes incorrect failover Key: IGNITE-7591 URL: https://issues.apache.org/jira/browse/IGNITE-7591 Project: Ignite Issue Ty

[GitHub] ignite pull request #3457: IGNITE-7561 .NET: Add IServices.GetDynamicService...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3457 IGNITE-7561 .NET: Add IServices.GetDynamicServiceProxy Work with service proxies in dynamic fashion You can merge this pull request into a Git repository by running: $ git pull https://githu

[jira] [Created] (IGNITE-7590) Change example for decision trees

Artem Malykh created IGNITE-7590: Summary: Change example for decision trees Key: IGNITE-7590 URL: https://issues.apache.org/jira/browse/IGNITE-7590 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-7589) Grid hangs on partition map exhcange during failover test with 34 physical caches (PDS + in memory)

Ksenia Rybakova created IGNITE-7589: --- Summary: Grid hangs on partition map exhcange during failover test with 34 physical caches (PDS + in memory) Key: IGNITE-7589 URL: https://issues.apache.org/jira/browse/IGNI

Re: Should we annotate @CacheLocalStore as @Depricated?

I filed the ticket [1] and will do it soon. [1] https://issues.apache.org/jira/browse/IGNITE-7588 On Tue, Jan 30, 2018 at 2:27 PM, Anton Vinogradov wrote: > +1 > > On Tue, Jan 30, 2018 at 9:02 AM, Yakov Zhdanov wrote: > >> +1 for deprecation >> >> >> >> --Yakov >> >> 2018-01-30 1:06 GMT+03:00 V

[jira] [Created] (IGNITE-7588) Deprecate CacheLocalStore annotation

Vyacheslav Daradur created IGNITE-7588: -- Summary: Deprecate CacheLocalStore annotation Key: IGNITE-7588 URL: https://issues.apache.org/jira/browse/IGNITE-7588 Project: Ignite Issue Type:

Re: Next Steps: GA Grid: Request to contribute GA library to Apache Ignite

Denis, >From my point of view PR looks good and ready for merge. So we waiting notification from you that all paperwork is done. Regards, Yury. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-7587) SQL COPY: document the command

Kirill Shirokov created IGNITE-7587: --- Summary: SQL COPY: document the command Key: IGNITE-7587 URL: https://issues.apache.org/jira/browse/IGNITE-7587 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-7586) SQL COPY: add code examples

Kirill Shirokov created IGNITE-7586: --- Summary: SQL COPY: add code examples Key: IGNITE-7586 URL: https://issues.apache.org/jira/browse/IGNITE-7586 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-7585) GridDhtLockFuture related memory leak

Alexei Scherbakov created IGNITE-7585: - Summary: GridDhtLockFuture related memory leak Key: IGNITE-7585 URL: https://issues.apache.org/jira/browse/IGNITE-7585 Project: Ignite Issue Type:

Re: Thin client failover mechanism (+ODBC, JDBC)

Pavel, I completely agree with you. No need of "black magic", just throw appropriate Exception, for example, IgniteThinClientConnectionLostException. But it will be very useful to "reconnect to next alive node" just to not reinvent the wheel in every user app. On Wed, Jan 31, 2018 at 7:21 PM, Ig

Re: Thin client failover mechanism (+ODBC, JDBC)

Well, I agree with Pavel here. To me looks like this feature gives a little to a user, as they need to write all the same amount of code as they would need to if there was no this feature. It also will produce some new issues with the "hanging" of operations, while thin client tries and fails to re

[jira] [Created] (IGNITE-7584) Smooth decrease WAL write speed if low work segments left

Dmitriy Pavlov created IGNITE-7584: -- Summary: Smooth decrease WAL write speed if low work segments left Key: IGNITE-7584 URL: https://issues.apache.org/jira/browse/IGNITE-7584 Project: Ignite

[jira] [Created] (IGNITE-7583) SQL TX: Change secondary indexes structure

Igor Seliverstov created IGNITE-7583: Summary: SQL TX: Change secondary indexes structure Key: IGNITE-7583 URL: https://issues.apache.org/jira/browse/IGNITE-7583 Project: Ignite Issue Typ

Re: Thin client failover mechanism (+ODBC, JDBC)

Alexey, retrieving addresses from topology makes sense, but in this thread I'm trying to understand whether any kind of built-in failover makes sense at all at the Ignite API level. I mean, on the business logic level failover certainly makes sense: if Web Agent has failed to execute some operatio

Re: Thin client failover mechanism (+ODBC, JDBC)

Pavel, I hope, that at some point Web agent (connector to Web Console) will be refactored from REST to thin client. It will be nice if thin client will support following modes: 1) Specify several addresses in thin client connection config. Thin client will use ONLY this addresses (hardcoded list)

[jira] [Created] (IGNITE-7582) Document 'No Archiver' WAL mode

Dmitriy Pavlov created IGNITE-7582: -- Summary: Document 'No Archiver' WAL mode Key: IGNITE-7582 URL: https://issues.apache.org/jira/browse/IGNITE-7582 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #3244: IGNITE-7182: throttle only changes

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

Thin client failover mechanism (+ODBC, JDBC)

Igniters, I'm working on client-side failover logic for .NET Thin Client. This will probably apply to ODBC and JDBC thin clients as well in future. Currently all thin clients connect to a single specified Ignite node. The idea is to have multiple known nodes (host:port pairs) and reconnect to ano

[GitHub] ignite pull request #3407: IGNITE-7475 Improve VerifyBackupPartitionsTask to...

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

[jira] [Created] (IGNITE-7581) TxPessimisticDeadlockDetectionTest.testDeadlocksLocal hangs on TC

Alexey Goncharuk created IGNITE-7581: Summary: TxPessimisticDeadlockDetectionTest.testDeadlocksLocal hangs on TC Key: IGNITE-7581 URL: https://issues.apache.org/jira/browse/IGNITE-7581 Project: Ig

[GitHub] ignite pull request #3456: IGNITE-7576 - Tweak to version check regexp to fi...

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

[GitHub] ignite pull request #3455: IGNITE-7577 Fixing public API active flag on base...

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

[GitHub] ignite pull request #3454: IGNITE-7569 Fixed index rebuild future

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

[jira] [Created] (IGNITE-7580) compatibilityMode flag consistency

Sergey Chugunov created IGNITE-7580: --- Summary: compatibilityMode flag consistency Key: IGNITE-7580 URL: https://issues.apache.org/jira/browse/IGNITE-7580 Project: Ignite Issue Type: Bug

Re: cache operation failed after transaction rolled back due to deadlock

Aleksey, thanks, we will take a look at this ticket and fix it in 2.5. 2018-01-23 19:57 GMT+03:00 Yakov Zhdanov : > Alex Goncharuk, can you please take a look and comment? Test seems to be > valid from my standpoint. > > Yakov Zhdanov, > www.gridgain.com > > 2018-01-22 23:14 GMT-08:00 ALEKSEY KUZ