Re: Ignite not friendly for Monitoring

Hello Alexey, Thanks for the detailed input. Assuming that Ignite supported the suggested events based model, how can it be integrated with mentioned tools like DynaTrace or Nagios? Is this all we need? — Denis > On Aug 14, 2017, at 5:02 AM, Alexey Kukushkin >

Re: Failure to deserialize simple model object

Cross-posting to dev Folks, I'm confused by the issue discussed in this thread. Here is the scenario: - Start server node with a cache with POJO store configured. There is one type declared, read-through enabled. - Start client node and execute get() for a key that exists in underlying DB. -

Re: Control.sh script and cluster activation

Agree that this is confusing. I think this functionality should be a part of Visor CLI tool (likely a new command there). -Val On Mon, Aug 14, 2017 at 4:21 PM, Denis Magda wrote: > Dmitriy, > > I see you contributed control.sh script that activates a cluster after a >

Control.sh script and cluster activation

Dmitriy, I see you contributed control.sh script that activates a cluster after a restart. Honestly, I’m a bit confused by it: 1. How to use it? I could find out that there are some of the parameters but the ‘help’ is not implemented. Please fix this and provide a description for every

[GitHub] ignite pull request #2442: Ignite 1.8.10

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

Re: Request for contributor permission

Hello Zhang Yuan, Welcome to the Ignite community! Added you to the list. Below you can find useful information. Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute can be found

Re: Hello

Hello, Welcome to the Ignite community! Added you to the list. Below you can find useful information. Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute can be found here:

[jira] [Created] (IGNITE-6059) Use any distributed matrix in K-Means

Yury Babak created IGNITE-6059: -- Summary: Use any distributed matrix in K-Means Key: IGNITE-6059 URL: https://issues.apache.org/jira/browse/IGNITE-6059 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-6058) Test fail testTransformResourceInjection broken

Dmitriy Govorukhin created IGNITE-6058: -- Summary: Test fail testTransformResourceInjection broken Key: IGNITE-6058 URL: https://issues.apache.org/jira/browse/IGNITE-6058 Project: Ignite

[GitHub] ignite pull request #2441: IGNITE-6033 Add sorted and multithreaded modes in...

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2441 IGNITE-6033 Add sorted and multithreaded modes in checkpoint algorithm You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Hello

Hi all, I am new here. My jira login: alexzaitzev. Please, give me access rights to contribute to Ignite. I hope I can help irreparably improve this product.

Re: Batch service deployment

Hi Denis, I agree, we should have an API for batch service deployment. My comments are inline... On Mon, Aug 14, 2017 at 2:22 AM, Denis Mekhanikov wrote: > Hi Igniters! > > Currently Ignite doesn't have support for batch service deployment, but it > may be a very useful

[GitHub] ignite pull request #2439: IGNITE-6052 request cluster state from daemon nod...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2439 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-6057) SQL: Full scan should be performed through data pages bypassing primary index

Vladimir Ozerov created IGNITE-6057: --- Summary: SQL: Full scan should be performed through data pages bypassing primary index Key: IGNITE-6057 URL: https://issues.apache.org/jira/browse/IGNITE-6057

[jira] [Created] (IGNITE-6056) Grid hangs on partition map exhcange during failover test with 500 logical and 26 physical caches

Ksenia Rybakova created IGNITE-6056: --- Summary: Grid hangs on partition map exhcange during failover test with 500 logical and 26 physical caches Key: IGNITE-6056 URL:

[jira] [Created] (IGNITE-6055) SQL: Add String length constraint

Vladimir Ozerov created IGNITE-6055: --- Summary: SQL: Add String length constraint Key: IGNITE-6055 URL: https://issues.apache.org/jira/browse/IGNITE-6055 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-6054) SQL: Add option to store primitive keys in plain form for CREATE TABLE

Vladimir Ozerov created IGNITE-6054: --- Summary: SQL: Add option to store primitive keys in plain form for CREATE TABLE Key: IGNITE-6054 URL: https://issues.apache.org/jira/browse/IGNITE-6054

[GitHub] ignite pull request #2347: IGNITE-5843 Ignite PDS: We don't save cache confi...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2347 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-6053) IgniteCache.clear clears local cache with same names on all server nodes

Evgenii Zhuravlev created IGNITE-6053: - Summary: IgniteCache.clear clears local cache with same names on all server nodes Key: IGNITE-6053 URL: https://issues.apache.org/jira/browse/IGNITE-6053

[GitHub] ignite pull request #2440: IGNITE-5416: add Kafka-specific builder for Strea...

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/2440 IGNITE-5416: add Kafka-specific builder for StreamSingleTupleExtractor You can merge this pull request into a Git repository by running: $ git pull https://github.com/endian675/ignite

[GitHub] ignite pull request #2329: IGNITE-5741

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2329 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: SQL usability issues

On Mon, Aug 14, 2017 at 2:52 AM, Igor Sapego wrote: > Dmitriy, > > But what would we put in such generic section? > - JAR in Ignite that contains JDBC driver - connection string - port (with explanation how to change it) - username/password with explanation why Ignite does

Ignite not friendly for Monitoring

Igniters, While preparing some Ignite materials for Administrators I found Ignite is not friendly for such a critical DevOps practice as monitoring.  TL;DRI think Ignite misses structured descriptions of abnormal events with references to event IDs in the logs not changing as new versions are

[jira] [Created] (IGNITE-6052) Check cluster state from daemon node return incorrect cluster state

Dmitriy Govorukhin created IGNITE-6052: -- Summary: Check cluster state from daemon node return incorrect cluster state Key: IGNITE-6052 URL: https://issues.apache.org/jira/browse/IGNITE-6052

[jira] [Created] (IGNITE-6051) Improve future listeners model in DataStreamerImpl

Igor Seliverstov created IGNITE-6051: Summary: Improve future listeners model in DataStreamerImpl Key: IGNITE-6051 URL: https://issues.apache.org/jira/browse/IGNITE-6051 Project: Ignite

[GitHub] ignite pull request #2428: IGNITE-4991 Do not print out system properties wh...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2428 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2386: IGNITE-5890 Estimated time to rebalance completio...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2386 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2438: IGNITE-4172 SQL: Add support for Java 8 Time API ...

GitHub user asfedotov opened a pull request: https://github.com/apache/ignite/pull/2438 IGNITE-4172 SQL: Add support for Java 8 Time API classes in date\time funcitons For CI purposes. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-6050) Eternal wait in DataStreamerTest.TestBufferSize()

Igor Seliverstov created IGNITE-6050: Summary: Eternal wait in DataStreamerTest.TestBufferSize() Key: IGNITE-6050 URL: https://issues.apache.org/jira/browse/IGNITE-6050 Project: Ignite

Batch service deployment

Hi Igniters! Currently Ignite doesn't have support for batch service deployment, but it may be a very useful feature in case of a big number of nodes in a cluster and services to be deployed. Each deployment includes write into an internal transactional cache, which is the longest part of the

[jira] [Created] (IGNITE-6049) Try to cache DataStreamer receiver

Igor Seliverstov created IGNITE-6049: Summary: Try to cache DataStreamer receiver Key: IGNITE-6049 URL: https://issues.apache.org/jira/browse/IGNITE-6049 Project: Ignite Issue Type:

[GitHub] ignite pull request #2424: IGNITE-6016 Get rid of checking topology hash in ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2424 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2437: IGNITE-5991

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

[GitHub] ignite pull request #2408: IGNITE-5941 : Fixed index name length restriction...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2408 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2436: IGNITE-5439 JDBC thin: support query cancel

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2436 IGNITE-5439 JDBC thin: support query cancel You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5439