[jira] [Created] (IGNITE-7579) NPE in GridDhtLocalPartition.cacheMapHolder()

Alexandr Kuramshin created IGNITE-7579: -- Summary: NPE in GridDhtLocalPartition.cacheMapHolder() Key: IGNITE-7579 URL: https://issues.apache.org/jira/browse/IGNITE-7579 Project: Ignite Is

[jira] [Created] (IGNITE-7578) Web console: Actualize configuration of ClientConnectorConfiguration

Vasiliy Sisko created IGNITE-7578: - Summary: Web console: Actualize configuration of ClientConnectorConfiguration Key: IGNITE-7578 URL: https://issues.apache.org/jira/browse/IGNITE-7578 Project: Ignit

[GitHub] ignite pull request #3456: IGNITE-7576 - Tweak to version check regexp to fi...

GitHub user dwimsey opened a pull request: https://github.com/apache/ignite/pull/3456 IGNITE-7576 - Tweak to version check regexp to find OpenJDK Haven't tested this extensively, it 'works for me' under OpenJDK 1.8 and OracleJDK 1.8 You can merge this pull request into a Git reposi

[GitHub] ignite pull request #3455: IGNITE-7577 Fixing public API active flag on base...

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3455 IGNITE-7577 Fixing public API active flag on baseline changes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-

Re: IGNITE_HOME for persistence

I think at this point all we can do is print a warning. However, starting with 3.0, we should require IGNITE_HOME to be set if we cannot determine it automatically. Do we print a warning already? On Tue, Jan 30, 2018 at 12:55 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Denis, Dmit

Re: IGNITE_HOME for persistence

Hi Igniters, Why it can be serious issue for end users? As far as I know IGNITE_HOME is always set using start scripts, e.g. in ignite.sh. If Ignite is started using java code from IDE, it may be required to set storage directory or work or home directory. Until that, TEMP is convinient for devel

[jira] [Created] (IGNITE-7577) GridClusterStateProcessor#publicApiActiveState returns false when baseline change is in progress

Alexey Goncharuk created IGNITE-7577: Summary: GridClusterStateProcessor#publicApiActiveState returns false when baseline change is in progress Key: IGNITE-7577 URL: https://issues.apache.org/jira/browse/IGNIT

Re: IGNITE_HOME for persistence

Denis, Dmitriy, I do not think the behavior should be in any way specific to the case when persistence is enabled. We have quite a bit of other information (such as binary marshaller metadata and marshaller class mappings) that are also stored in the work folder and may be required after the clust

Re: IGNITE_HOME for persistence

I think we should still keep System property and Environment variable check. Our product has a user base that depends on these properties and changing them at will is not an option. I do agree that the product should not start if IGNITE_HOME cannot be calculated, but I still do not understand how

Re: IGNITE_HOME for persistence

The temp dir is no way to go for the persistence. I would enforce setting paths for the storage and WAL files if IGNITE_HOME can't be calculated and we end up placing the storage files under the temp.dir. Alex G., can you join this thread? Seems that there is an oversight on our side that needs

[jira] [Created] (IGNITE-7576) ignite.sh expect only oracle jdk, not openjdk

David Wimsey created IGNITE-7576: Summary: ignite.sh expect only oracle jdk, not openjdk Key: IGNITE-7576 URL: https://issues.apache.org/jira/browse/IGNITE-7576 Project: Ignite Issue Type: Bu

[jira] [Created] (IGNITE-7575) Concurrent updates of common keys cause silent wrong update count (intermittent issue)

Pavel Kuznetsov created IGNITE-7575: --- Summary: Concurrent updates of common keys cause silent wrong update count (intermittent issue) Key: IGNITE-7575 URL: https://issues.apache.org/jira/browse/IGNITE-7575

[jira] [Created] (IGNITE-7574) Ignite Getting Started confuses developers

Denis Magda created IGNITE-7574: --- Summary: Ignite Getting Started confuses developers Key: IGNITE-7574 URL: https://issues.apache.org/jira/browse/IGNITE-7574 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-7573) IgniteOfflineBaselineNodeFullApiSelfTest.testSize fails

Alexey Goncharuk created IGNITE-7573: Summary: IgniteOfflineBaselineNodeFullApiSelfTest.testSize fails Key: IGNITE-7573 URL: https://issues.apache.org/jira/browse/IGNITE-7573 Project: Ignite

[jira] [Created] (IGNITE-7572) Local cache fails to start on local node

Mikhail Cherkasov created IGNITE-7572: - Summary: Local cache fails to start on local node Key: IGNITE-7572 URL: https://issues.apache.org/jira/browse/IGNITE-7572 Project: Ignite Issue Typ

Re: Protect Ignite clusters from Meltdown and Spectre

Apache Ignite community applied security patches against the notorious Meltdown Spectre vulnerabilities and completed performance testing of general operations and workloads that are typical for Ignite deployments. The details are under the link: https://blogs.apache.org/ignite/entry/meltdown-an

[jira] [Created] (IGNITE-7571) [Test fail]

Eduard Shangareev created IGNITE-7571: - Summary: [Test fail] Key: IGNITE-7571 URL: https://issues.apache.org/jira/browse/IGNITE-7571 Project: Ignite Issue Type: Improvement Re

[GitHub] ignite pull request #3454: IGNITE-7569 Fixed index rebuild future

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3454 IGNITE-7569 Fixed index rebuild future You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7569 Alternatively you

[jira] [Created] (IGNITE-7570) Client nodes failed with "Failed to process invalid partitions response" during failover

Ksenia Rybakova created IGNITE-7570: --- Summary: Client nodes failed with "Failed to process invalid partitions response" during failover Key: IGNITE-7570 URL: https://issues.apache.org/jira/browse/IGNITE-7570

[jira] [Created] (IGNITE-7569) Index rebuild future is created too late

Alexey Goncharuk created IGNITE-7569: Summary: Index rebuild future is created too late Key: IGNITE-7569 URL: https://issues.apache.org/jira/browse/IGNITE-7569 Project: Ignite Issue Type:

[GitHub] ignite pull request #3453: IGNITE-7567: Fixed bug with datasest in examples

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

Abandoned Patch Available JIRA tickets

Igniters, We have *almost 60* of PATCH AVAILABLE tickets that are inactive for more than a month: https://issues.apache.org/jira/issues/?filter=12333285&jql=project%3Dignite%20AND%20status%3D%22Patch%20Available%22%20AND%20updated%20%3C%20-30d (JQL: project=ignite AND status="Patch Available" AND

Re: Apache Ignite 2.4 release

Igniters, I will handle 2.4 release if there are no objections. Let's take a bit more time for testing and start vote by the end of this week. Pavel On Sat, Jan 27, 2018 at 3:32 AM, Denis Magda wrote: > Hi Vyacheslav, > > According to the previous review notes the impact of the changes might be

Re: Unresolved Ignite 2.4 tickets

Hi Dmitry, Thanks for the heads up, I've moved all 2.4 tickets (except site and documentation related) to 2.5. Pavel On Tue, Jan 30, 2018 at 3:36 PM, Dmitry Sherstobitov wrote: > Hi! > > We are still having issues for ignite-2.4 release in PATCH AVAILABLE or > OPEN state: > > >1. IGNITE-72

Unresolved Ignite 2.4 tickets

Hi! We are still having issues for ignite-2.4 release in PATCH AVAILABLE or OPEN state: 1. IGNITE-7216 Refactor examples project 1. IGNITE-6630 Incorrect time units of average t

[jira] [Created] (IGNITE-7568) Product version increment script

Pavel Tupitsyn created IGNITE-7568: -- Summary: Product version increment script Key: IGNITE-7568 URL: https://issues.apache.org/jira/browse/IGNITE-7568 Project: Ignite Issue Type: Improvement

[GitHub] ignite pull request #3361: IGNITE-6810: SSL support for ODBC

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

[GitHub] ignite pull request #3453: IGNITE-7567: Fixed bug with datasest in examples

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/3453 IGNITE-7567: Fixed bug with datasest in examples You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7567 Alternati

Re: Should we annotate @CacheLocalStore as @Depricated?

+1 On Tue, Jan 30, 2018 at 9:02 AM, Yakov Zhdanov wrote: > +1 for deprecation > > > > --Yakov > > 2018-01-30 1:06 GMT+03:00 Valentin Kulichenko < > valentin.kuliche...@gmail.com > >: > > > +1 > > > > On Mon, Jan 29, 2018 at 8:31 AM, Andrey Mashenkov < > > andrey.mashen...@gmail.com> wrote: > > >

RE: IGNITE_HOME for persistence

I checked the code handling the IGNITE_HOME and persistent storage paths, and here is what the algorithm looks like. For IGNITE_HOME the following is checked in order; if on any step a value is found then we use it. - IgniteHome in IgniteConfiguration - IGNITE_HOME system property - IGNITE_HOME

Re: Ignite Semaphore Bug 7090

Tim, I added you as Ignite contributor. You can assign tickets to yourself now. On Sun, Jan 28, 2018 at 5:24 PM, Tim Onyschak wrote: > Jira Username: Timay > > On Sat, Jan 27, 2018 at 1:43 AM, Dmitriy Setrakyan > wrote: > >> Tim, can you please send your Apache Jira ID here, so I could add you

[jira] [Created] (IGNITE-7567) ML example datasets should be moved in resoirce directory

Sergey Kozlov created IGNITE-7567: - Summary: ML example datasets should be moved in resoirce directory Key: IGNITE-7567 URL: https://issues.apache.org/jira/browse/IGNITE-7567 Project: Ignite

[GitHub] ignite pull request #3452: Ignite 2.3.2.b1

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

[GitHub] ignite pull request #3451: Service reassign with merge exchanges (TC run).

GitHub user xtern opened a pull request: https://github.com/apache/ignite/pull/3451 Service reassign with merge exchanges (TC run). You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-7366 Alternatively you can r

Re: .NET development on Linux & macOS is now possible

Yakov, thanks for trying this out. Good point about build script, I've filed a ticket: https://issues.apache.org/jira/browse/IGNITE-7566 As for tests - yes, these two seem to be flaky on TC as well, I'll have a look. Pavel On Tue, Jan 30, 2018 at 8:34 AM, Yakov Zhdanov wrote: > Pavel, > > I tr

[jira] [Created] (IGNITE-7566) .NET: Build scripts: stop build when one of the steps fails

Pavel Tupitsyn created IGNITE-7566: -- Summary: .NET: Build scripts: stop build when one of the steps fails Key: IGNITE-7566 URL: https://issues.apache.org/jira/browse/IGNITE-7566 Project: Ignite