[GitHub] ignite pull request #2681: IGNITE-6396: Added test for SQL state error code ...

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/2681 IGNITE-6396: Added test for SQL state error code for NOT NULL violation You can merge this pull request into a Git repository by running: $ git pull

Re: MVCC configuration

Hello, Semyon! > It seems we need introduce special 'dedicated mvcc coordinator' node role How will Ignite handle "mvcc coordinator" fail? What will happen with if coordinator fails in the middle of a transaction? Could tx be committed or rollbacked? Will we have some user notification if

[GitHub] ignite pull request #2680: IGNITE-6413

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

Re: MVCC configuration

Yakov, I would say that my example is not about adding transactions to ATOMIC cache, but rather about adding consistent snapshots to it. On Mon, Sep 18, 2017 at 1:59 PM, Yakov Zhdanov wrote: > Vladimir, I think we can ask user to switch to transactional cache to > support

Re: [VOTE] Apache Ignite 2.2.0 RC2

+1 (binding) Checked .NET - build from sources, build and run examples On Mon, Sep 18, 2017 at 2:57 PM, Vyacheslav Daradur wrote: > +1 > > On Mon, Sep 18, 2017 at 1:14 PM, Andrey Novikov > wrote: > > > +1 (binding) > > > > On Mon, Sep 18, 2017 at 4:35

Re: [VOTE] Apache Ignite 2.2.0 RC2

+1 (binding) On Mon, Sep 18, 2017 at 4:29 PM, Vladimir Ozerov wrote: > +1 (binding) > > On Mon, Sep 18, 2017 at 12:24 PM, Konstantin Dudkov wrote: > > > +1 > > > > > > 15/09/2017 17:48, Anton Vinogradov пишет: > > > > Igniters, > >> > >> We have uploaded a

[GitHub] ignite pull request #2682: IGNITE-6317 JDBC thick driver: SQLSTATE error cod...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2682 IGNITE-6317 JDBC thick driver: SQLSTATE error codes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: MVCC configuration

1. Agree. Let's disable MVCC by default. 2. Sam, if user wants to have dedicated mvcc-coordinator, then we can use configuration you suggested. However, I expect more properties will be needed. How about having MvccConfiguration bean? Once topology has no dedicated coordinators, topology should

Re: MVCC configuration

Semen, My comments: 1) I would propose to have only global flag for now - IgniteConfiguration.isMvccEnabled. One key design point we should keep in mind is that MVCC data *MSUT* be persistent. We can skip it in the first iteration, as we are focused on key-based cache updates, when typical

Re: MVCC configuration

Alex, With putAll() on ATOMIC cache all bets are off, for sure. On Mon, Sep 18, 2017 at 2:53 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Vladimir, > > I doubt it will be possible to add any meaningful guarantees to ATOMIC > caches with MVCC. Consider a case when a user does a

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

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

Re: MVCC configuration

Ouch... of course it makes sense for atomic caches. Seems I am not fully switched on after weekend =) Agree on other points. --Yakov

Re: MVCC configuration

Vladimir, I think we can ask user to switch to transactional cache to support your example. Otherwise, it seems we are turning atomic caches to tx implicitly. --Yakov 2017-09-18 13:49 GMT+03:00 Vladimir Ozerov : > Semen, > > Consider use case of some audit table where I

Re: Ignite PDS WAL analysis with human readable records

Hi Igniters, Page https://cwiki.apache.org/confluence/display/IGNITE/Ignite+WAL+reader to collect related information about this prototype was created. Sincerely, Dmitriy Pavlov пн, 18 сент. 2017 г. в 7:01, Dmitriy Setrakyan : > Can we get a sample print out from this

Re: MVCC configuration

Yakov, MVCC for atomic caches makes sense as well - we will be able to read consistent data set, which is not possible now. As I explained above, per-cache configuration might not work when we start working on transactional SQL design. Moreover, it looks like an overkill for me at the moment. We

Re: [VOTE] Apache Ignite 2.2.0 RC2

+1 (binding) On Mon, Sep 18, 2017 at 4:35 PM, Alexey Kuznetsov wrote: > +1 (binding) > > On Mon, Sep 18, 2017 at 4:29 PM, Vladimir Ozerov > wrote: > > > +1 (binding) > > > > On Mon, Sep 18, 2017 at 12:24 PM, Konstantin Dudkov >

Re: MVCC configuration

Semen, Consider use case of some audit table where I log user actions over time. Every actions is a put to ATOMIC cache. User interacts with my application, and performs the following set of actions: 1. 08:00 MSK -> LOGIN 2. 08:10 MSK -> Update something 3. 08:20 MSK -> LOGUT If MVCC is there,

Re: MVCC configuration

Vladimir, I doubt it will be possible to add any meaningful guarantees to ATOMIC caches with MVCC. Consider a case when a user does a putAll, not a single put. In this case, updates received by multiple primary nodes are not connected in any way. Moreover, whenever a primary node fails, the put

Re: MVCC configuration

Vladimir, should it be on IgniteConfiguration or on CacheConfiguration? I think mvcc should be enabled on per cache basis and moreover it makes sense only for tx caches. --Yakov

Re: [VOTE] Apache Ignite 2.2.0 RC2

+1 On Mon, Sep 18, 2017 at 1:14 PM, Andrey Novikov wrote: > +1 (binding) > > On Mon, Sep 18, 2017 at 4:35 PM, Alexey Kuznetsov > wrote: > > > +1 (binding) > > > > On Mon, Sep 18, 2017 at 4:29 PM, Vladimir Ozerov > > wrote: > >

Re: MVCC configuration

Nikolay, thanks for comments > How will Ignite handle "mvcc coordinator" fail? > What will happen with if coordinator fails in the middle of a transaction? > Could tx be committed or rollbacked? I think coordinator failure will be handled in the same way as failure of one of transaction's

Re: [VOTE] Apache Ignite 2.2.0 RC2

+1 15/09/2017 17:48, Anton Vinogradov пишет: Igniters, We have uploaded a 2.2.0 release candidate to https://dist.apache.org/repos/dist/dev/ignite/2.2.0-rc2/ Git tag name is 2.2.0-rc2 This release includes the following changes: Ignite: * Checkpointing algorithm optimized * Default max

Re: Ignite PDS WAL analysis with human readable records

Example of output (will add to wiki): [W] InitNewPageRecord [newPageId=0001001c0067, super=PageDeltaRecord [grpId=2141373875, pageId=0001001c0067, super=WALRecord [size=41, chainSize=0, pos=FileWALPointer [idx=1, fileOffset=25406, len=41, forceFlush=false], type=INIT_NEW_PAGE_RECORD]]]

[jira] [Created] (IGNITE-6419) Thin client: pass user agent string

Pavel Tupitsyn created IGNITE-6419: -- Summary: Thin client: pass user agent string Key: IGNITE-6419 URL: https://issues.apache.org/jira/browse/IGNITE-6419 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6418) Binary: optionally write integer datatypes with varint encoding

Vladimir Ozerov created IGNITE-6418: --- Summary: Binary: optionally write integer datatypes with varint encoding Key: IGNITE-6418 URL: https://issues.apache.org/jira/browse/IGNITE-6418 Project:

MVCC configuration

Hi all, Currently I'm working on MVCC feature (IGNITE-3478) and need your opinion on related configuration options. 1. MVCC will definitely bring some performance overhead, so I think it should not be enabled by default, I'm going to add special flag on cache configuration:

Re: MVCC configuration

Guys, I do not really understand mvcc for atomic cache, could you please provide some real use case. Thank you On Mon, Sep 18, 2017 at 1:37 PM, Yakov Zhdanov wrote: > Ouch... of course it makes sense for atomic caches. Seems I am not fully > switched on after weekend =) >

Re: [VOTE] Apache Ignite 2.2.0 RC2

+1 (binding) On Mon, Sep 18, 2017 at 12:24 PM, Konstantin Dudkov wrote: > +1 > > > 15/09/2017 17:48, Anton Vinogradov пишет: > > Igniters, >> >> We have uploaded a 2.2.0 release candidate to >> https://dist.apache.org/repos/dist/dev/ignite/2.2.0-rc2/ >> >> Git tag name is >>

[RESULT] [VOTE] Apache Ignite 2.2.0 Release (RC2)

Igniters, Apache Ignite 2.2.0 release (RC2) has been accepted. 4 "+1" binding votes received: - Vladimir Ozerov - Alexey Kuznetsov - Andrey Novikov - Pavel Tupitsyn Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-2-0-RC2-td22261.html Ignite 2.2.0 will

Re: Static code analysis for Java

Why do not use all of the tools (well at least several). They are easy to be integrateable. In this way one would be less exposed to promote one commercial vendor over the other. This would also help in finding the right quality criteria instead of analyzing what is offered by only one

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

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

[jira] [Created] (IGNITE-6426) Add support for variable length numbers in raw readers/writers.

Alexei Scherbakov created IGNITE-6426: - Summary: Add support for variable length numbers in raw readers/writers. Key: IGNITE-6426 URL: https://issues.apache.org/jira/browse/IGNITE-6426 Project:

[GitHub] ignite pull request #2686: IGNITE-6427: IgniteOOME in Cache5 test: Increase ...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/2686 IGNITE-6427: IgniteOOME in Cache5 test: Increase memory policy size You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: ContinuousQueryWithTransformer implementation questions - 2

So, resuming: 1) My solution reduces network communication. As far as I know, a lot of people want to have this feature at Ignite 2.x. It's impossible to gain perfect API right now, it will take months to gain it. My solution ready right now!, let's merge it and refactor whole Continuous Query

[jira] [Created] (IGNITE-6427) Ignite Cache 5 suite has timed out with CacheLateAffinityAssignmentTest.testRandomOperations()

Dmitriy Pavlov created IGNITE-6427: -- Summary: Ignite Cache 5 suite has timed out with CacheLateAffinityAssignmentTest.testRandomOperations() Key: IGNITE-6427 URL:

Re: Unintuitive error message when invalid marshaller files found

I agree, error message should be more informative. Mike, feel free to create a Jira ticket for this. -Val On Mon, Sep 18, 2017 at 12:25 AM, Michael Griggs wrote: > Sure > > SEVERE: Exception during start processors, node will be stopped and > close connections > class

[GitHub] ignite pull request #2687: IGNITE-6209 .NET: Build NuGet packages for Apache...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2687 IGNITE-6209 .NET: Build NuGet packages for Apache-Ignite release on CI You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite

Issues if -Djava.net.preferIPv4Stack=true is not set

Guys, I noticed there are many issues on user forum that occur of -Djava.net.preferIPv4Stack=true system property is not set. Can someone explain the nature of these issues? What exactly in Ignite requires this system property do be set? And can this be fixed/automated somehow? If fix is not

Re: MVCC configuration

Vladimir, thanks for comments > 2) I would also avoid this flag until we clearly understand it is needed. > All numbers will be assigned from a single thread. For this reason even > peak load on coordinator should not consume too much resources. I think we > can assign coordinators automatically

[jira] [Created] (IGNITE-6420) Time metrics (CacheMetrics.getAverage###Time) should be calculated on primary node in case of ATOMIC cache

Vyacheslav Koptilin created IGNITE-6420: --- Summary: Time metrics (CacheMetrics.getAverage###Time) should be calculated on primary node in case of ATOMIC cache Key: IGNITE-6420 URL:

[GitHub] ignite pull request #2683: Ignite-6420 Time metrics (CacheMetrics.getAverage...

GitHub user sk0x50 opened a pull request: https://github.com/apache/ignite/pull/2683 Ignite-6420 Time metrics (CacheMetrics.getAverage###Time) should be calculated on primary node in case of ATOMIC cache You can merge this pull request into a Git repository by running: $ git

[jira] [Created] (IGNITE-6421) Ignite WAL reader: add shell script to start converter

Dmitriy Pavlov created IGNITE-6421: -- Summary: Ignite WAL reader: add shell script to start converter Key: IGNITE-6421 URL: https://issues.apache.org/jira/browse/IGNITE-6421 Project: Ignite

Re: Ignite PDS WAL analysis with human readable records

Dmitriy, Thank you for your feedback I've created IGNITE-6421 for this change. Is it common practice to use property file in Ignite utils? I'd like to support parse and display data entries and its fields, but it is required to configure several folders: 'binary_meta' and 'marshaller' folders.

[jira] [Created] (IGNITE-6422) In visorcmd "cache on nodes" statistics mixes together primary and backup entries

Ilya Kasnacheev created IGNITE-6422: --- Summary: In visorcmd "cache on nodes" statistics mixes together primary and backup entries Key: IGNITE-6422 URL: https://issues.apache.org/jira/browse/IGNITE-6422

Re: ContinuousQueryWithTransformer implementation questions - 2

Vladimir, Here is a short summary what is wrong with continuous query OK. I agree - this is problems of current API. How we can fix it by not merging ContinuousQueryWIthTransformer? How we can quickly design, discuss and implement new API? Because at the moment there is no any ticket to

[jira] [Created] (IGNITE-6424) .NET: IgniteConfiguration.ServiceConfiguration

Pavel Tupitsyn created IGNITE-6424: -- Summary: .NET: IgniteConfiguration.ServiceConfiguration Key: IGNITE-6424 URL: https://issues.apache.org/jira/browse/IGNITE-6424 Project: Ignite Issue

[GitHub] ignite pull request #2684: IGNITE-6391 JDBC thin driver: remove unused JdbcT...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2684 IGNITE-6391 JDBC thin driver: remove unused JdbcThinTcpIo.srvProtocolVer You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2682: IGNITE-6317 JDBC thick driver: SQLSTATE error cod...

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

Re: Ignite PDS WAL analysis with human readable records

Thanks! After looking at the ticket, the way to launch this utility seems complex. Does this utility have a shell script? If not, we should add one with proper command line options, like we do for other scripts. D. On Mon, Sep 18, 2017 at 4:05 AM, Eduard Shangareev <

[GitHub] ignite pull request #2578: IGNITE-6014 Transaction records in WAL.

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

Re: MVCC configuration

Semyon, How about to have node attribute "COORDINATOR_RANK" or "COORDINATOR_ORDER"? This attribute can be 1, 2, 3 And node with minimal number will become coordinator. If it failed, node with next rank/order will be elected as new coordinator. Make sense? On Mon, Sep 18, 2017 at 4:39 PM,

Re: ContinuousQueryWithTransformer implementation questions - 2

Nikolay, Here is a short summary what is wrong with continuous query: 1) It should not have "initialQuery" 2) It should not be called through IgniteCache.query() method, as it has nothing in common with other "query" types 3) Main thing: our listeners are *ALWAYS* executed on a node which

[GitHub] ignite pull request #2647: IGNITE-6355 Calculating cache size during cache s...

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

[GitHub] ignite pull request #2536: IGNITE-6210 Size of the checkpoint buffer is limi...

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

[jira] [Created] (IGNITE-6423) LFD could be corrupted if partition have been evicted and returned to node

Eduard Shangareev created IGNITE-6423: - Summary: LFD could be corrupted if partition have been evicted and returned to node Key: IGNITE-6423 URL: https://issues.apache.org/jira/browse/IGNITE-6423

[GitHub] ignite pull request #2685: Ignite 6355

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

[jira] [Created] (IGNITE-6425) Races during transaction finalization

Eduard Shangareev created IGNITE-6425: - Summary: Races during transaction finalization Key: IGNITE-6425 URL: https://issues.apache.org/jira/browse/IGNITE-6425 Project: Ignite Issue Type:

Re: ContinuousQueryWithTransformer implementation questions - 2

Igniters, I discussed API of ContinuousQuery and ContinuousQueryWithTransformer with Anton Vinogradov one more time. Since users who use regular ContinuousQuery already knows pros. and cons of using initialQuery and to not to complicate API more and more until 3.0 we agreed that best choice is

[GitHub] ignite pull request #2365: Ignite 5813 1.7

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

[GitHub] ignite pull request #2690: IGNITE 6428: IgniteOOME in PDS Indexing test:

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/2690 IGNITE 6428: IgniteOOME in PDS Indexing test: Experimental branch with Increase memory policy size Don't merge, only for testing You can merge this pull request into a Git repository by

[jira] [Created] (IGNITE-6428) Timed out test IgnitePdsAtomicCacheRebalancingTest.testTopologyChangesWithConstantLoad

Dmitriy Pavlov created IGNITE-6428: -- Summary: Timed out test IgnitePdsAtomicCacheRebalancingTest.testTopologyChangesWithConstantLoad Key: IGNITE-6428 URL: https://issues.apache.org/jira/browse/IGNITE-6428

Fwd: Fetched result set too large

Vladimir, Seems the usage hints of the flag below have to go to the performance & troubleshooting doc: https://apacheignite-sql.readme.io/docs/performance-and-debugging Could you properly add it there? — Denis > Begin forwarded message: > > From: Вячеслав Коптилин

[GitHub] ignite pull request #2691: IGNITE-6403

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

[jira] [Created] (IGNITE-6430) CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails periodically.

Andrey Gura created IGNITE-6430: --- Summary: CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails periodically. Key: IGNITE-6430 URL: https://issues.apache.org/jira/browse/IGNITE-6430

[GitHub] ignite pull request #2684: IGNITE-6391 JDBC thin driver: remove unused JdbcT...

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

[jira] [Created] (IGNITE-6429) GridCachePreloadingEvictionsSelfTest.testEvictions test fails periodically

Andrey Gura created IGNITE-6429: --- Summary: GridCachePreloadingEvictionsSelfTest.testEvictions test fails periodically Key: IGNITE-6429 URL: https://issues.apache.org/jira/browse/IGNITE-6429 Project:

[GitHub] ignite pull request #2688: IGNITE-6403 SchemaOperationManager fix

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/2688 IGNITE-6403 SchemaOperationManager fix …tiated operation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2689: IGNITE-6099: Fully implemented SQLGetInfo in ODBC...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2689 IGNITE-6099: Fully implemented SQLGetInfo in ODBC driver. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6099

[GitHub] ignite pull request #2691: IGNITE-6403

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

Re: Ignite PDS WAL analysis with human readable records

Dmitriy, can you please describe your idea in the ticket? Here is the link for easier access: https://issues.apache.org/jira/browse/IGNITE-6421 D. On Mon, Sep 18, 2017 at 7:02 AM, Dmitry Pavlov wrote: > Dmitriy, > > Thank you for your feedback I've created IGNITE-6421

[GitHub] ignite pull request #2688: IGNITE-6403 SchemaOperationManager fix

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

Re: Issues if -Djava.net.preferIPv4Stack=true is not set

Any comments here? Do we really require IPv4 for some reason? On Mon, Sep 18, 2017 at 9:51 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Guys, > > I noticed there are many issues on user forum that occur > of -Djava.net.preferIPv4Stack=true system property is not set. > > Can

Re: MVCC configuration

On Mon, Sep 18, 2017 at 4:57 AM, Vladimir Ozerov wrote: > Alex, > > With putAll() on ATOMIC cache all bets are off, for sure. > Are we all in agreement that MVCC should only be enabled for transactional caches then?

[GitHub] ignite pull request #2692: Ignite gg 12788

GitHub user sk0x50 opened a pull request: https://github.com/apache/ignite/pull/2692 Ignite gg 12788 You can merge this pull request into a Git repository by running: $ git pull https://github.com/sk0x50/ignite ignite-gg-12788 Alternatively you can review and apply these

Re: MVCC configuration

On Mon, Sep 18, 2017 at 2:39 AM, Semyon Boikov wrote: > > 1. MVCC will definitely bring some performance overhead, so I think it > should not be enabled by default, I'm going to add special flag on cache > configuration: CacheConfiguration.isMvccEnabled. > Is it possible for

[jira] [Created] (IGNITE-6417) Missed binary type configuration in VisorGridConfiguration.

Vasiliy Sisko created IGNITE-6417: - Summary: Missed binary type configuration in VisorGridConfiguration. Key: IGNITE-6417 URL: https://issues.apache.org/jira/browse/IGNITE-6417 Project: Ignite

Re: Unintuitive error message when invalid marshaller files found

Sure SEVERE: Exception during start processors, node will be stopped and close connections class org.apache.ignite.IgniteCheckedException: Failed to start processor: GridProcessorAdapter []     at org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1813)     at

[GitHub] ignite pull request #2680: IGNITE-6413

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

Re: [VOTE] Apache Ignite 2.2.0 RC2

+1 Checked md5, sha512 Build from sources Build examples 2017-09-16 10:45 GMT+03:00 Andrey Gura : > +1 > > 15 сент. 2017 г. 5:48 PM пользователь "Anton Vinogradov" > написал: > > > Igniters, > > > > We have uploaded a 2.2.0 release candidate to > >

[GitHub] ignite pull request #2666: IGNITE-6385 Offheap page eviction doesn't work if...

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