[jira] [Created] (IGNITE-6969) Move constants with influence on performance to separate config

Aleksey Zinoviev created IGNITE-6969: Summary: Move constants with influence on performance to separate config Key: IGNITE-6969 URL: https://issues.apache.org/jira/browse/IGNITE-6969 Project: Igni

[jira] [Created] (IGNITE-6968) Move similar Cache configurations in matrices and models to one Java or XML config

Aleksey Zinoviev created IGNITE-6968: Summary: Move similar Cache configurations in matrices and models to one Java or XML config Key: IGNITE-6968 URL: https://issues.apache.org/jira/browse/IGNITE-6968

Re: Ignite ML dense distributed matrices

Yury, I support one matrix with different strategies if it will have one API. Also distributed/local can be a strategy too. And yet, Artem, Yury, we could think about DenceBlockDistributedMatrix of course. Or about Matrix(boolean isDistributed, boolean isBlock, boolean isSparse) and implement all

Re: Stop Ignite opening 47500 and 47100

Hi, please see examples in org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneNoopCommunicationSpi and StandaloneNoopDiscoverySpi. also please make sure classes are annotated @IgniteSpiNoop This annotation helps Ignite ingernal stuff to identify this implementation shou

[jira] [Created] (IGNITE-6967) PME deadlock on reassigning service deployment

Alexandr Kuramshin created IGNITE-6967: -- Summary: PME deadlock on reassigning service deployment Key: IGNITE-6967 URL: https://issues.apache.org/jira/browse/IGNITE-6967 Project: Ignite I

Re: Suggestion to improve deadlock detection

It doesn’t need all txes. Instead, other nodes will send info about suspicious txes to it from time to time. вт, 21 нояб. 2017 г. в 8:04, Dmitriy Setrakyan : > How does it know about all the Txs? > > ⁣D.​ > > On Nov 20, 2017, 8:53 PM, at 8:53 PM, Vladimir Ozerov < > voze...@gridgain.com> wrote: >

Re: Suggestion to improve deadlock detection

How does it know about all the Txs? ⁣D.​ On Nov 20, 2017, 8:53 PM, at 8:53 PM, Vladimir Ozerov wrote: >Dima, > >What is wrong with coordinator approach? All it does is analyze small >number of TXes which wait for locks for too long. > >вт, 21 нояб. 2017 г. в 1:16, Dmitriy Setrakyan : > >> Vladi

Re: Suggestion to improve deadlock detection

Dima, What is wrong with coordinator approach? All it does is analyze small number of TXes which wait for locks for too long. вт, 21 нояб. 2017 г. в 1:16, Dmitriy Setrakyan : > Vladimir, > > I am not sure I like it, mainly due to some coordinator node doing some > periodic checks. For the deadlo

Fwd: getAverageGetTime/getAveragePutTime APIs of CacheMetrics always return 0

Ignite dev community, Bring this weird bug to your attention. Could you confirm it’s not a “feature” of us? Put to the IEP-6 (metrics) list. — Denis > Begin forwarded message: > > From: Denis Magda > Subject: Re: getAverageGetTime/getAveragePutTime APIs of CacheMetrics always > return 0 > Da

[jira] [Created] (IGNITE-6966) Average time metrics are not calculated for client driven operations

Denis Magda created IGNITE-6966: --- Summary: Average time metrics are not calculated for client driven operations Key: IGNITE-6966 URL: https://issues.apache.org/jira/browse/IGNITE-6966 Project: Ignite

RE: IGNITE-6745. Status

My username is cossack5. Please grant me contributor permissions. As for java 7 version, until moment it is discontinued, all the code should be java7-compatible ? -Original Message- From: Denis Magda [mailto:dma...@apache.org] Sent: Tuesday, November 21, 2017 3:15 AM To: dev@ignite.apac

Re: IGNITE-6745. Status

Cergey, What’s you JIRA account? You need to be among Ignite contributors in JIRA to assign tickets on yourself. As for Java 7, yes, we had that discussion many times. Hopefully it will be discontinued the next year. However, as for Java 8 the community is willing to support it by the end of t

Re: Data eviction/expiration from Ignite persistence

Dmitriy, That’s about TTL and eviction support for Ignite persistence. Presently if you set an expiration or eviction policy for a cache it will be applied for data stored in memory. The policy never affects the persistence layer. — Denis > On Nov 20, 2017, at 9:29 AM, Dmitry Pavlov wrote: >

Re: Facility to detect long STW pauses and other system response degradations

My 2 cents. 1. Totally for a separate native process that will handle the monitoring of an Ignite process. The watchdog process can simply start a JVM tool like jstat and parse its GC logs: https://dzone.com/articles/how-monitor-java-garbage

Re: Ignite Logger & logging file config output

Good point. Could you create a ticket and probably contribute this improvement? — Denis > On Nov 20, 2017, at 3:12 AM, Alexey Popov wrote: > > Hi Igniters, > > Could you please advise why Ignite does not indicate > 1) the logger type it uses > 2) the logger configuration file (name) it applie

Re: SSL for ODBC connection

This configuration approach looks clearer to me. +1 for it. — Denis > On Nov 20, 2017, at 12:42 AM, Igor Sapego wrote: > > Ok, then how about the following set of options: > > ssl_enabled=[true|false] > ssl_key_file= > ssl_cert_file= > > > Best Regards, > Igor > > On Tue, Nov 14, 2017 at 5:

Invitation: RSVP now for Dec. 13 Bay Area In-Memory Computing Meetup! @ Wed Dec 13, 2017 6pm - 8pm (CST) (dev@ignite.apache.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20171214T00Z DTEND:20171214T02Z DTSTAMP:20171120T225457Z ORGANIZER;CN=GridGain Meetups (includes guest talks):mailto:gridgain.com_ci 4oqrn7b9ia4drtrurq004...

Re: Ignite Enhancement Proposal #7 (Internal problems detection)

If an Ignite operation hangs by some reason due to an internal problem or buggy application code it needs to eventual *time out*. Take atomic operations case brought by Val to our attention recently: http://apache-ignite-developers.2346864.n4.nabble.com/Timeouts-in-atomic-cache-td19839.html An a

Re: SQL warning for partitioned caches with setLocal

Sounds like a good idea. Vladimir, would be nice to hear your thoughts. D. On Mon, Nov 20, 2017 at 7:45 AM, luqmanahmad wrote: > Hi there, > > Working with SQL queries with setLocal(true) with partitioned cache, it is > very easy for someone to run SQL queries without affinityRun or > affinityC

Re: Suggestion to improve deadlock detection

Vladimir, I am not sure I like it, mainly due to some coordinator node doing some periodic checks. For the deadlock detection to work effectively, it has to be done locally on every node. This may require that every tx request will carry information about up to N previous keys it accessed, but the

RE: IGNITE-6745. Status

Hi, I can't assign the ticket to myself - seems I have no rights. Also, I see we still support java 7. Maybe it's time to cease it (especially when we have java 9 to worry about) ? -Original Message- From: Anton Vinogradov [mailto:avinogra...@gridgain.com] Sent: Monday, November 20, 201

[jira] [Created] (IGNITE-6965) affinityCall() with key mapping may not be successful with AlwaysFailoverSpi when node left

Alexandr Kuramshin created IGNITE-6965: -- Summary: affinityCall() with key mapping may not be successful with AlwaysFailoverSpi when node left Key: IGNITE-6965 URL: https://issues.apache.org/jira/browse/IGNITE

Suggestion to improve deadlock detection

Igniters, We are currently working on transactional SQL and distributed deadlocks are serious problem for us. It looks like current deadlock detection mechanism has several deficiencies: 1) It transfer keys! No go for SQL as we may have millions of keys. 2) By default we wait for a minute. Way too

[GitHub] ignite pull request #3072: IGNITE-6963: Made PhysicalMemoryPages equal to To...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3072 IGNITE-6963: Made PhysicalMemoryPages equal to TotalAllocatedPages when PDS is off You can merge this pull request into a Git repository by running: $ git pull https://github.com/an

Re: Data eviction/expiration from Ignite persistence

Hi Denis, Is this need covered by PDS + TTL? For the very first TTL test, I found some delay after applying TTL with the repository enabled: https://issues.apache.org/jira/browse/IGNITE-6964 And I'm wondering if the user's needs are covered by https://apacheignite.readme.io/docs/expiry-policies

[GitHub] ignite pull request #3068: IGNITE-6876: ODBC: Added support for SQL_ATTR_CON...

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

[jira] [Created] (IGNITE-6964) Ignite restart with PDS enabled may cause delays in TTL cleanup worker

Dmitriy Pavlov created IGNITE-6964: -- Summary: Ignite restart with PDS enabled may cause delays in TTL cleanup worker Key: IGNITE-6964 URL: https://issues.apache.org/jira/browse/IGNITE-6964 Project: I

Re: Ignite Enhancement Proposal #7 (Internal problems detection)

Dmitry, There's two cases 1) STW duration is long -> notifying monitoring via JMX metric 2) STW duration exceed N seconds -> no need to wait for something. We already know that node will be segmented or that pause bigger that N seconds will affect cluster performance. Better case is to kill node

Re: Ignite Enhancement Proposal #7 (Internal problems detection)

Hi Anton, > - GC STW duration exceed maximum possible length (node should be stopped > before STW finished) Are you sure we should kill node in case long STW? Can we produce warnings into logs and monitoring tools an wait node to become alive a little bit longer if we detect STW. In this case we

Ignite Enhancement Proposal #7 (Internal problems detection)

Igniters, Internal problems may and, unfortunately, cause unexpected cluster behavior. We should determine behavior in case any of internal problem happened. Well known internal problems can be split to: 1) OOM or any other reason cause node crash 2) Situations required graceful node shutdown wi

[GitHub] ignite pull request #3029: enforceJoinOrder flag for Thick JDBC Driver to 1....

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

[GitHub] ignite pull request #3028: Support enforceJoinOrder flag for Thick JDBC Driv...

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

[jira] [Created] (IGNITE-6963) TotalAllocatedPages metric does not match PhysicalMemoryPages when persistence is disabled

Andrey Kuznetsov created IGNITE-6963: Summary: TotalAllocatedPages metric does not match PhysicalMemoryPages when persistence is disabled Key: IGNITE-6963 URL: https://issues.apache.org/jira/browse/IGNITE-6963

SQL warning for partitioned caches with setLocal

Hi there, Working with SQL queries with setLocal(true) with partitioned cache, it is very easy for someone to run SQL queries without affinityRun or affinityCall computations which are the preferred ways of running queries on partition cache, as described in [1]. Now what I was thinking whenever

[GitHub] ignite pull request #3062: Backport IGNITE-6818, fix test

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

[GitHub] ignite pull request #3026: 5195 DataStreamer can fails if non-data node ente...

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

Re: Ignite ML dense distributed matrices

Artem, I think It`s a good idea. We could implement dense matrix as separate matrix, but what do you think about common distributed matrix with multiple possible storage strategies? Regards, Yury -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #3071: ignite-2.1.7-p2

GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/3071 ignite-2.1.7-p2 Ignite-2.1.7-p2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.1.7-p2 Alternatively you c

[GitHub] ignite pull request #3070: Ignite wal freelist disable

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/3070 ---

Re: Facility to detect long STW pauses and other system response degradations

Yakov, Issue is https://issues.apache.org/jira/browse/IGNITE-6171 We split issue to #1 STW duration metrics #2 External monitoring allows to stop node during STW > Testing GC pause with java thread is > a bit strange and can give info only after GC pause finishes. That's ok since it's #1 On Mo

Re: Facility to detect long STW pauses and other system response degradations

I have tested solution with java-thread and GC logs had contain same pause values of thread stopping which was detected by java-thread. My log (contains pauses > 100ms): [2017-11-20 17:33:28,822][WARN ][Thread-1][root] Possible too long STW pause: 507 milliseconds. [2017-11-20 17:33:34,522][WARN

[jira] [Created] (IGNITE-6962) Reduce ExchangeHistory memory consumption

Alexander Belyak created IGNITE-6962: Summary: Reduce ExchangeHistory memory consumption Key: IGNITE-6962 URL: https://issues.apache.org/jira/browse/IGNITE-6962 Project: Ignite Issue Type

Re: Facility to detect long STW pauses and other system response degradations

Guys, how about having 2 native threads - one calling some java method, another one monitoring that the first one is active and is not stuck on safepoint (which points to GC pause)? Testing GC pause with java thread is a bit strange and can give info only after GC pause finishes. Native threads can

Re: Facility to detect long STW pauses and other system response degradations

Yes, we need some timestamp from Java code. But I think JVM thread could update TS with delays not related to GC and will have same effect with IgniteUtils#currentTimeMillis(). Is this new test compares result from java timestamps difference with GC logs? пн, 20 нояб. 2017 г. в 16:39, Anton Vinog

[jira] [Created] (IGNITE-6961) Internal Problems should be covered by Monitoring tool

Anton Vinogradov created IGNITE-6961: Summary: Internal Problems should be covered by Monitoring tool Key: IGNITE-6961 URL: https://issues.apache.org/jira/browse/IGNITE-6961 Project: Ignite

[GitHub] ignite pull request #3070: Ignite wal freelist disable

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/3070 Ignite wal freelist disable You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-wal-freelist-disable Alter

[GitHub] ignite pull request #3069: Ignite 6872 1

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

Ignite ML dense distributed matrices

Hi all, currently we do not have dense distributed matices in ML module, but I think we should add them. Obviously, not every big ML dataset has sparse structure. Of course, we can put it into a sparse distributed matrix, but this will have performance hits. Any ideas/objections about it? -- Se

Re: Facility to detect long STW pauses and other system response degradations

Dmitriy, > Sleeping Java Thread IMO is not an option, because thread can be in > Timed_Watiting logner than timeout. That's the only one idea we have, and, according to tests, it works! > Did I understand correctly that the native stream is proposed? And our goal > now is to select best framewor

[jira] [Created] (IGNITE-6960) ContinuousQuery failed if set deploymentMode to Private

Mikhail Cherkasov created IGNITE-6960: - Summary: ContinuousQuery failed if set deploymentMode to Private Key: IGNITE-6960 URL: https://issues.apache.org/jira/browse/IGNITE-6960 Project: Ignite

Re: Facility to detect long STW pauses and other system response degradations

Sleeping Java Thread IMO is not an option, because thread can be in Timed_Watiting logner than timeout. Did I understand correctly that the native stream is proposed? And our goal now is to select best framework for this? Can we limit this oppotunity with several popular OS (Win,Linux), and do no

[jira] [Created] (IGNITE-6959) Split a ttl index tree by partition

Sergey Puchnin created IGNITE-6959: -- Summary: Split a ttl index tree by partition Key: IGNITE-6959 URL: https://issues.apache.org/jira/browse/IGNITE-6959 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #3068: IGNITE-6876: ODBC: Added support for SQL_ATTR_CON...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/3068 IGNITE-6876: ODBC: Added support for SQL_ATTR_CONNECTION_TIMEOUT You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-

Re: Facility to detect long STW pauses and other system response degradations

Igniters, Since no one rejected proposal, let's start from part one. > I propose to add a special thread that will record current time every N > milliseconds and check the difference with the latest recorded value. > The maximum and total pause values for a certain period can be published in > th

Ignite Logger & logging file config output

Hi Igniters, Could you please advise why Ignite does not indicate 1) the logger type it uses 2) the logger configuration file (name) it applies during startup? Can we add such output to IgniteLogger implementations? Thanks, Alexey -- Sent from: http://apache-ignite-developers.2346864.n4.nabb

Re: IGNITE-6745. Status

Cergey, Please assign https://issues.apache.org/jira/browse/IGNITE-6745 to yourself and change status to Patch Available. Also, before asking review, please check that TeamCity status is ok, see https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-SubmittingforRevie

[jira] [Created] (IGNITE-6958) Reduce FilePageStore allocation on start

Alexander Belyak created IGNITE-6958: Summary: Reduce FilePageStore allocation on start Key: IGNITE-6958 URL: https://issues.apache.org/jira/browse/IGNITE-6958 Project: Ignite Issue Type:

[GitHub] ignite pull request #3067: IGNITE-6955 Update com.google.code.simple-spring-...

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/3067 IGNITE-6955 Update com.google.code.simple-spring-memcached:spymemcach… …ed to 2.8.4 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgai

[jira] [Created] (IGNITE-6957) Reduce excessive int boxing when accessing cache by ID

Alexey Goncharuk created IGNITE-6957: Summary: Reduce excessive int boxing when accessing cache by ID Key: IGNITE-6957 URL: https://issues.apache.org/jira/browse/IGNITE-6957 Project: Ignite

[jira] [Created] (IGNITE-6956) Reduce excessive iterator allocations during GridDhtPartitionMap instantiation

Alexey Goncharuk created IGNITE-6956: Summary: Reduce excessive iterator allocations during GridDhtPartitionMap instantiation Key: IGNITE-6956 URL: https://issues.apache.org/jira/browse/IGNITE-6956

[jira] [Created] (IGNITE-6955) Update com.google.code.simple-spring-memcached:spymemcached to 2.8.4

Alexey Popov created IGNITE-6955: Summary: Update com.google.code.simple-spring-memcached:spymemcached to 2.8.4 Key: IGNITE-6955 URL: https://issues.apache.org/jira/browse/IGNITE-6955 Project: Ignite

[jira] [Created] (IGNITE-6954) Baseline should throw appropriate exception in case of --baseline version OLD_VERSION

Alexey Kuznetsov created IGNITE-6954: Summary: Baseline should throw appropriate exception in case of --baseline version OLD_VERSION Key: IGNITE-6954 URL: https://issues.apache.org/jira/browse/IGNITE-6954

Re: SSL for ODBC connection

Ok, then how about the following set of options: ssl_enabled=[true|false] ssl_key_file= ssl_cert_file= Best Regards, Igor On Tue, Nov 14, 2017 at 5:21 PM, Vladimir Ozerov wrote: > I think it would be enough to have a single switch for now. > > On Tue, Nov 7, 2017 at 10:04 PM, Denis Magda wro

[GitHub] ignite pull request #2974: Ignite 2.1.7.b1

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

Re: Stop Ignite opening 47500 and 47100

I have been trying to implement my own discovery spi and communication spi. But i am unable achieve it without errors. I just need Ignite Cache. It will be helpful if you can you provide the code or at least mention what classes and where i need to make changes. Thanks in advance. -- Sent from:

[GitHub] ignite pull request #2774: IGNITE-6416

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