Re: Ignite Usability: Deadlocks and Starvation

On Thu, Aug 24, 2017 at 10:09 AM, Yakov Zhdanov wrote: > > I think as a first step, the deadlock detection should kick off after a > > certain timeout, even if the transaction timeout was not set. > > > What do you think? > > Dmitry, I thought that was what I suggested, no?

Re: [DISCUSSION] Urgent Ignite bug fix release

+1 on the release, let's do it ASAP. On Thu, Aug 24, 2017 at 12:32 PM, Denis Magda wrote: > Igniters, > > Presently every Apache Ignite node requests 80% of RAM from an operating > system. We debated a lot about this default [1] and as a practice shows > those who voted for

[DISCUSSION] Urgent Ignite bug fix release

Igniters, Presently every Apache Ignite node requests 80% of RAM from an operating system. We debated a lot about this default [1] and as a practice shows those who voted for the lower value (20%-25%) were right. Our users started reporting about bizarre issues ([2], [3], [4]) when a cluster

Re: [DISCUSS] Ignite Update Checker

I see nothing wrong with this approach. Cos, Roman, Raul, as Apache veterans, what do you think? Is it good to go? — Denis > On Aug 23, 2017, at 11:17 PM, Dmitriy Setrakyan wrote: > > Is everyone OK with this approach? Should I file a ticket on it? > > On Mon, Aug 21,

Re: Adding Apache Ignite to Kubernetes Example

Dani, I’m totally for this! This is an easy way to spread a word about Ignite. Do you want to take a lead in this activity and add the example to Kube repo? You can rely on me if any technical assistance is needed. — Denis > On Aug 23, 2017, at 7:32 PM, Dani Traphagen

Re: Expanding Apache Ignite Use Case

Good catch, Dmitriy! Didn’t know the pages existed. Made them up-to-date. — Denis > On Aug 23, 2017, at 7:14 PM, Dmitriy Setrakyan wrote: > > Denis, great progress. > > I think you forgot to update these pages: > https://ignite.apache.org/features.html >

[GitHub] ignite pull request #2513: Ignite 6180

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2513 Ignite 6180 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6180 Alternatively you can review and

[jira] [Created] (IGNITE-6182) Change default max memory size from 80% to 20%

Vladimir Ozerov created IGNITE-6182: --- Summary: Change default max memory size from 80% to 20% Key: IGNITE-6182 URL: https://issues.apache.org/jira/browse/IGNITE-6182 Project: Ignite Issue

Re: Ignite Usability: Deadlocks and Starvation

> I think as a first step, the deadlock detection should kick off after a > certain timeout, even if the transaction timeout was not set. > What do you think? Dmitry, I thought that was what I suggested, no? =) --Yakov

[jira] [Created] (IGNITE-6181) Tx is not rolled back on timeout leading to potential whole grid hang

Alexei Scherbakov created IGNITE-6181: - Summary: Tx is not rolled back on timeout leading to potential whole grid hang Key: IGNITE-6181 URL: https://issues.apache.org/jira/browse/IGNITE-6181

[jira] [Created] (IGNITE-6180) Marshaller mappings are not restored from disk on node start

Sergey Chugunov created IGNITE-6180: --- Summary: Marshaller mappings are not restored from disk on node start Key: IGNITE-6180 URL: https://issues.apache.org/jira/browse/IGNITE-6180 Project: Ignite

[GitHub] ignite pull request #2512: IGNITE-5855 Type-safe parameters setting fixes cr...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/2512 IGNITE-5855 Type-safe parameters setting fixes crash when querying BigInteger key You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-6179) Test fail DynamicIndexReplicatedAtomicConcurrentSelfTest.testClientReconnectWithCacheRestart

Dmitriy Govorukhin created IGNITE-6179: -- Summary: Test fail DynamicIndexReplicatedAtomicConcurrentSelfTest.testClientReconnectWithCacheRestart Key: IGNITE-6179 URL:

[GitHub] ignite pull request #2511: IGNITE-6178 Make CheckpointWriteOrder.SEQUENTIAL ...

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2511 IGNITE-6178 Make CheckpointWriteOrder.SEQUENTIAL and checkpointingThreads=4 default in persistent store confguration You can merge this pull request into a Git repository by running: $ git

[jira] [Created] (IGNITE-6178) Make CheckpointWriteOrder.SEQUENTIAL and checkpointingThreads=4 default in persistent store confguration

Ivan Rakov created IGNITE-6178: -- Summary: Make CheckpointWriteOrder.SEQUENTIAL and checkpointingThreads=4 default in persistent store confguration Key: IGNITE-6178 URL:

[GitHub] ignite pull request #2510: IGNITE-6130 JDBC Thin: JdbcThinResultSet must sup...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2510 IGNITE-6130 JDBC Thin: JdbcThinResultSet must support types conversions You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-6177) Update docs for integration with Apache Zeppelin

Ilya Suntsov created IGNITE-6177: Summary: Update docs for integration with Apache Zeppelin Key: IGNITE-6177 URL: https://issues.apache.org/jira/browse/IGNITE-6177 Project: Ignite Issue

[jira] [Created] (IGNITE-6176) Request to BinaryMetadataTransport may cause deadlock on grid stop

Ivan Rakov created IGNITE-6176: -- Summary: Request to BinaryMetadataTransport may cause deadlock on grid stop Key: IGNITE-6176 URL: https://issues.apache.org/jira/browse/IGNITE-6176 Project: Ignite

[GitHub] ignite pull request #2509: For testing

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2509 For testing You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.1.4-5682 Alternatively you can review and apply

Re: [DISCUSS] Ignite Update Checker

Is everyone OK with this approach? Should I file a ticket on it? On Mon, Aug 21, 2017 at 2:07 PM, Dmitriy Setrakyan wrote: > Igniters, > > There has been lots of talk of proposals about various usage metrics for > Ignite and nothing came of it. I would like to resurrect