[jira] [Created] (IGNITE-6305) Need to add update checker to Ignite

Dmitriy Setrakyan created IGNITE-6305: - Summary: Need to add update checker to Ignite Key: IGNITE-6305 URL: https://issues.apache.org/jira/browse/IGNITE-6305 Project: Ignite Issue Type:

Re: [DISCUSS] Ignite Update Checker

I think it is safe to assume at this point that everyone is in general agreement, since there are no active objections. I have filed a ticket for the 2.3 release. Let's try to make it happen: https://issues.apache.org/jira/browse/IGNITE-6305 D. On Sat, Aug 26, 2017 at 3:06 PM, Dmitriy Setrakyan

Re: Annoying extra steps for enabling metrics

First of all, these are events, not metrics, and to my knowledge Ignite itself does not expose any metrics that depend on events. The fact that Web Console (or any other tool) uses events to track and show something is a different story. Events API has two parts: listening (one simply registers a

[jira] [Created] (IGNITE-6304) Visor CMD: Failed script execution after throttling interval

Vasiliy Sisko created IGNITE-6304: - Summary: Visor CMD: Failed script execution after throttling interval Key: IGNITE-6304 URL: https://issues.apache.org/jira/browse/IGNITE-6304 Project: Ignite

Fwd: 2.1.4 visor console - activate/deactivate command?

Cross-sending to dev@ Igniters, can we try to include the fixes to the cluster activation command into 2.3 release, including the renaming suggestion? https://issues.apache.org/jira/browse/IGNITE-6064 D. -- Forwarded message -- From: Denis Magda Date: Thu,

Re: Annoying extra steps for enabling metrics

On Thu, Sep 7, 2017 at 7:30 PM, Denis Magda wrote: > My point is different. Before I had to do this only assuming that “Ignite > will spend 99%” sending events: > > > > > > > > >

Re: Annoying extra steps for enabling metrics

My point is different. Before I had to do this only assuming that “Ignite will spend 99%” sending events: Now the platform forces me to do that (probably thinking

Re: Annoying extra steps for enabling metrics

On Thu, Sep 7, 2017 at 7:19 PM, Denis Magda wrote: > Any metric from of org.apache.ignite.events.EventType (cache operations, > compute, etc.) > If you enable them all, Ignite will spend 99% of its time doing event notifications. > > — > Denis > > > On Sep 7, 2017, at 7:15

Re: Hello

Hello Maxim, Granted and welcome to the Ignite community! Please subscribe to both dev and user lists: https://ignite.apache.org/community/resources.html#mail-lists Get familiar with Ignite development process described here:

Re: Annoying extra steps for enabling metrics

Any metric from of org.apache.ignite.events.EventType (cache operations, compute, etc.) — Denis > On Sep 7, 2017, at 7:15 PM, Dmitriy Setrakyan wrote: > > Denis, which metrics are you talking about? > > On Thu, Sep 7, 2017 at 7:12 PM, Denis Magda

Re: [Meetup] Apache Spark and Ignite for IoT scenarious

Hello Anjaneya, Marco, Honestly, I’m not aware if the video broadcasting or recording is planned. Could you go to the meetup page [1] and raise the question there? Just in case, here is you can find a list of all upcoming Ignite related events [2]. Probably some of them will be in close

Re: Annoying extra steps for enabling metrics

Denis, which metrics are you talking about? On Thu, Sep 7, 2017 at 7:12 PM, Denis Magda wrote: > Igniters, > > It was a surprise for me to reveal that even if the default config is used > [1] I still will not see the metrics in Web Console or in a custom app. > However, the

Annoying extra steps for enabling metrics

Igniters, It was a surprise for me to reveal that even if the default config is used [1] I still will not see the metrics in Web Console or in a custom app. However, the config was left unchanged for a while and from the first look encompassed everything we need to start getting metrics. But,

RE: Massive commit sizes for processes with local Ignite Grid servers

Hi Alexey, The server itself is pretty simple, it runs up and waits for requests without preloading aything. Once the process has initialized everything (except for activating the Ignite server node), the Commit Size is around 750Mb in size. It then stalls waiting for Active to become true,

Re: [Meetup] Apache Spark and Ignite for IoT scenarious

Hi Will there be a podcast to view afterwards for remote EMEA users? Kr On Sep 7, 2017 12:15 AM, "Denis Magda" wrote: > Folks, > > Those who are craving for mind food this weekend come over the meetup - > Santa Clara, Sept 9, 9.30 AM: >

Re: Ignite Benchmarking page on readme.io

Actually, it can be contributed directly to readme.io. Alexey, I just sent you an invite. You can create a new page for benchmarking and make it invisible for now, while you are working on it. If you need us to review it, please send a direct link to it here. D. On Thu, Sep 7, 2017 at 8:26 AM,

Re: Disable compute job results cache by default

On Thu, Sep 7, 2017 at 8:52 AM, Yakov Zhdanov wrote: > Guys, according to this - > http://apache-ignite-users.70518.x6.nabble.com/Task-manageme > nt-MapReduce-amp-ForkJoin-performance-penalty-td16542.html > - I would think that we need to disable result caching by default.0

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

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/2620 Ignite 6235: Add ability to handle CacheObject from DataRecord in standalone WAL iterator You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2619: IGNITE-2092 Switched to the up-to-date java image...

GitHub user max-neverov opened a pull request: https://github.com/apache/ignite/pull/2619 IGNITE-2092 Switched to the up-to-date java image which has build-in … …functionality to detect container CPU limitation You can merge this pull request into a Git repository by running:

Hello

Hello Igniters! Could you please grant me the permissions so I can contribute to this project? My jira account: Maxim Neverov -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: IGNITE-2092: upgrade java

Hello, It sounds common sense. Can you create pull request for this ticket? On Thu, Sep 7, 2017 at 8:03 AM, Maxim Neverov wrote: > Hi Igniters! > > I've investigated the ticket > and found out that > it > can be

[GitHub] ignite pull request #2618: IGNITE-6046 Multiple SQL statements in one JDBC c...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2618 IGNITE-6046 Multiple SQL statements in one JDBC command do not work You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2617: IGNITE-6288 NPE on SQL query with parameters on c...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2617 IGNITE-6288 NPE on SQL query with parameters on custom schema name You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2616: Ignite-gg-12707

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

Disable compute job results cache by default

Guys, according to this - http://apache-ignite-users.70518.x6.nabble.com/Task-management-MapReduce-amp-ForkJoin-performance-penalty-td16542.html - I would think that we need to disable result caching by default. Or at least find out why it is so costly. --Yakov

[jira] [Created] (IGNITE-6303) .NET: GetAll should close query cursor

Pavel Tupitsyn created IGNITE-6303: -- Summary: .NET: GetAll should close query cursor Key: IGNITE-6303 URL: https://issues.apache.org/jira/browse/IGNITE-6303 Project: Ignite Issue Type:

[GitHub] ignite pull request #2593: Ignite-gg-12699

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

[GitHub] ignite pull request #2615: Ignite-gg-12695

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

Re: Ignite Benchmarking page on readme.io

Aleksei, Good idea. Could you please prepare page in MD format and attach link to branch containing it to the issue to review before publication? On Thu, Sep 7, 2017 at 1:45 PM, Aleksei Zaitsev wrote: > Hi, guys. > > Issue[1] stated that we have not any information

[jira] [Created] (IGNITE-6302) Client heap starts constantly growing when server offheap memory gets full

Ksenia Rybakova created IGNITE-6302: --- Summary: Client heap starts constantly growing when server offheap memory gets full Key: IGNITE-6302 URL: https://issues.apache.org/jira/browse/IGNITE-6302

Re: [DISCUSSION] Urgent Ignite bug fix release

We created the release build procedure on Apache CI server according to this ticket: https://issues.apache.org/jira/browse/IGNITE-5249 We also changed the checksum calculation method: https://issues.apache.org/jira/browse/IGNITE-5817 Oleg On Thu, Sep 7, 2017 at 9:49 AM, 李玉珏@163

RE: Massive commit sizes for processes with local Ignite Grid servers

I tried an experiment where I ran only two instances of the server locally, this is the result in the Task Manager: *From:* Raymond Wilson [mailto:raymond_wil...@trimble.com] *Sent:* Thursday, September 7, 2017 9:21 PM *To:* u...@ignite.apache.org; 'dev@ignite.apache.org'

Massive commit sizes for processes with local Ignite Grid servers

I’m running a set of four server applications on a local system to simulate a cluster. Each of the servers has the following memory configurations set: public override void ConfigureRaptorGrid(IgniteConfiguration cfg) { cfg.JvmInitialMemoryMb = 512; // Set to

[GitHub] ignite pull request #2614: IGNITE-5829 on 2.1.5

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/2614 IGNITE-5829 on 2.1.5 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-pitr-2.1.5-ignite-5829 Alternatively

[jira] [Created] (IGNITE-6301) CacheConfiguration.indexedTypes never initialized and can be removed

Nikolay Izhikov created IGNITE-6301: --- Summary: CacheConfiguration.indexedTypes never initialized and can be removed Key: IGNITE-6301 URL: https://issues.apache.org/jira/browse/IGNITE-6301 Project:

[jira] [Created] (IGNITE-6300) BinaryObject's set size estimator

Anton Vinogradov created IGNITE-6300: Summary: BinaryObject's set size estimator Key: IGNITE-6300 URL: https://issues.apache.org/jira/browse/IGNITE-6300 Project: Ignite Issue Type: New

[GitHub] ignite pull request #2613: IGNITE-6297

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

[jira] [Created] (IGNITE-6298) SQL: Print names of created tables on node startup

Vladimir Ozerov created IGNITE-6298: --- Summary: SQL: Print names of created tables on node startup Key: IGNITE-6298 URL: https://issues.apache.org/jira/browse/IGNITE-6298 Project: Ignite

[jira] [Created] (IGNITE-6297) JDBC: consistent driver names

Vladimir Ozerov created IGNITE-6297: --- Summary: JDBC: consistent driver names Key: IGNITE-6297 URL: https://issues.apache.org/jira/browse/IGNITE-6297 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #2613: IGNITE-6297

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

[jira] [Created] (IGNITE-6295) SQL: Get rid of "replicatedOnly" flag

Vladimir Ozerov created IGNITE-6295: --- Summary: SQL: Get rid of "replicatedOnly" flag Key: IGNITE-6295 URL: https://issues.apache.org/jira/browse/IGNITE-6295 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6294) ODBC: Propagate SQLSTATE error codes

Vladimir Ozerov created IGNITE-6294: --- Summary: ODBC: Propagate SQLSTATE error codes Key: IGNITE-6294 URL: https://issues.apache.org/jira/browse/IGNITE-6294 Project: Ignite Issue Type: Task

RE: Massive commit sizes for processes with local Ignite Grid servers

Hi Dmitry, Thanks for the pointer to the MemoryPolicy. I added the following: cfg.MemoryConfiguration = new MemoryConfiguration() { SystemCacheMaxSize = (long)1 * 1024 * 1024 * 1024, DefaultMemoryPolicyName = "defaultPolicy",

[jira] [Created] (IGNITE-6293) SQL: Support FOREIGN KEY constraint

Vladimir Ozerov created IGNITE-6293: --- Summary: SQL: Support FOREIGN KEY constraint Key: IGNITE-6293 URL: https://issues.apache.org/jira/browse/IGNITE-6293 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-6292) SQL: Support CHECK constraint

Vladimir Ozerov created IGNITE-6292: --- Summary: SQL: Support CHECK constraint Key: IGNITE-6292 URL: https://issues.apache.org/jira/browse/IGNITE-6292 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #2612: IGNITE-6282: Implemented lazy initialization of I...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2612 IGNITE-6282: Implemented lazy initialization of IgniteImpl members. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2611: Ignite 2.1.3 p2

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

[jira] [Created] (IGNITE-6291) JDBC thin protocol compatibility

Taras Ledkov created IGNITE-6291: Summary: JDBC thin protocol compatibility Key: IGNITE-6291 URL: https://issues.apache.org/jira/browse/IGNITE-6291 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #2610: Fix Licenses & Javadoc tests.

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/2610 Fix Licenses & Javadoc tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/alamar/ignite ignite-licjd Alternatively you can review and

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

GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/2609 ignite-6289 Remove "allOrNone" flag from IgniteServices#deployAll method You can merge this pull request into a Git repository by running: $ git pull

Re: Massive commit sizes for processes with local Ignite Grid servers

OK, please ignore - I see you might have found a cause in the other thread. On Thu, Sep 7, 2017 at 2:45 PM, Alexey Kukushkin wrote: > Raymond, > > So you see 3 "extra" GB that your server app takes. Is it possible your > app really loads additional 3GB of referenced

Re: Massive commit sizes for processes with local Ignite Grid servers

Raymond, So you see 3 "extra" GB that your server app takes. Is it possible your app really loads additional 3GB of referenced libraries and data besides Ignite? Did you try temporarily changing the code to NOT start Ignite and see how much memory such an app takes? On Thu, Sep 7, 2017 at 1:49

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

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

Ignite Benchmarking page on readme.io

Hi, guys. Issue[1] stated that we have not any information about Apache Ignite benchmarking on our site https://apacheignite.readme.io. I want to add such a page, but I can’t find appropriate section for it. I suggest to make new section named ‘Tests and Benchmarking’ and put all information

Re: Massive commit sizes for processes with local Ignite Grid servers

Hi Raymond, Total memory usage since 2.0 version is determined as sum of heap size and memory policies MaxSizes (overall segment sizes). If it is not configured there is 80% of physical RAM is used for each node (before 2.2). In 2.2 this behaviour will be changed. To run several nodes at one PC

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

I also agree that we should try to use Externalizable without deserialization on servers. I will do it in a way suggested in the review. The Externalizable will marshal through type GridBinaryMarshaller.OBJ, in addition, I’ll add a flag in BinaryConfiguration which will be used to turn on the old

[jira] [Created] (IGNITE-6290) Data loss in case of manual rebalance

Andrey Gura created IGNITE-6290: --- Summary: Data loss in case of manual rebalance Key: IGNITE-6290 URL: https://issues.apache.org/jira/browse/IGNITE-6290 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #2604: IGNITE-6193 ML profile is missing in 2.1 binary r...

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

[GitHub] ignite pull request #2608: IGNITE-6190: Let pass collections as arguments to...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/2608 IGNITE-6190: Let pass collections as arguments to SQL queries. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite IGNITE-6190

[jira] [Created] (IGNITE-6289) Remove "allOrNone" flag from IgniteServices#deployAll method

Denis Mekhanikov created IGNITE-6289: Summary: Remove "allOrNone" flag from IgniteServices#deployAll method Key: IGNITE-6289 URL: https://issues.apache.org/jira/browse/IGNITE-6289 Project: Ignite

[jira] [Created] (IGNITE-6288) NPE on SQL query with parameters on custom schema name

Taras Ledkov created IGNITE-6288: Summary: NPE on SQL query with parameters on custom schema name Key: IGNITE-6288 URL: https://issues.apache.org/jira/browse/IGNITE-6288 Project: Ignite

[GitHub] ignite pull request #2607: tests unmuted

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

Re: [DISCUSSION] Urgent Ignite bug fix release

Currently,the latest version is apache-ignite-fabric-2.1.0-bin.zip . and in http://www.gridgainsystems.com/nexus/content/repositories/external/org/apache/ignite/ignite-core/ the latest version is 2.1.4, As I

[GitHub] ignite pull request #2607: tests unmuted

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2607 tests unmuted You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-4931-on-2.1 Alternatively you can review and apply these