[jira] [Commented] (IGNITE-3269) Benchmark driver stops working when one of servers left grid and backupcount 0

[ https://issues.apache.org/jira/browse/IGNITE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728440#comment-16728440 ] Andrey Gura commented on IGNITE-3269: - [~oleg-ostanin] LGTM. Merged to master branch. Thanks for

[jira] [Resolved] (IGNITE-10806) Test failure on Big Endian

[ https://issues.apache.org/jira/browse/IGNITE-10806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura resolved IGNITE-10806. -- Resolution: Won't Fix > Test failure on Big Endian > -- > >

[jira] [Commented] (IGNITE-10806) Test failure on Big Endian

[ https://issues.apache.org/jira/browse/IGNITE-10806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728409#comment-16728409 ] Andrey Gura commented on IGNITE-10806: -- Protocol version 1 used by Ignite <1.6 versions only and

[jira] [Commented] (IGNITE-10760) Confusing message about system worker blocking

[ https://issues.apache.org/jira/browse/IGNITE-10760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728331#comment-16728331 ] Andrey Gura commented on IGNITE-10760: -- [~ilyak] This is just usability issue. It isn't related

[jira] [Comment Edited] (IGNITE-10003) Raise SYSTEM_WORKER_BLOCKED instead of CRITICAL_ERROR when checkpoint read lock timeout detected

[ https://issues.apache.org/jira/browse/IGNITE-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726692#comment-16726692 ] Andrey Gura edited comment on IGNITE-10003 at 12/21/18 12:32 PM: -

[jira] [Commented] (IGNITE-10003) Raise SYSTEM_WORKER_BLOCKED instead of CRITICAL_ERROR when checkpoint read lock timeout detected

[ https://issues.apache.org/jira/browse/IGNITE-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726692#comment-16726692 ] Andrey Gura commented on IGNITE-10003: -- [~Jokser]] Don't merge please. My comment about

[jira] [Updated] (IGNITE-10760) Confusing message about system worker blocking

[ https://issues.apache.org/jira/browse/IGNITE-10760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-10760: - Description: System workers blocking monitoring message can confuse because print out

[jira] [Updated] (IGNITE-10760) Confusing message about system worker blocking

[ https://issues.apache.org/jira/browse/IGNITE-10760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-10760: - Description: System workers blocking monitoring message can confuse because print out

[jira] [Updated] (IGNITE-10760) Confusing message about system worker blocking

[ https://issues.apache.org/jira/browse/IGNITE-10760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-10760: - Labels: newbie (was: ) > Confusing message about system worker blocking >

[jira] [Created] (IGNITE-10760) Confusing message about system worker blocking

Andrey Gura created IGNITE-10760: Summary: Confusing message about system worker blocking Key: IGNITE-10760 URL: https://issues.apache.org/jira/browse/IGNITE-10760 Project: Ignite Issue

[jira] [Commented] (IGNITE-10003) Raise SYSTEM_WORKER_BLOCKED instead of CRITICAL_ERROR when checkpoint read lock timeout detected

[ https://issues.apache.org/jira/browse/IGNITE-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725924#comment-16725924 ] Andrey Gura commented on IGNITE-10003: -- [~andrey-kuznetsov] Timeout is more specific failure. So

[jira] [Comment Edited] (IGNITE-10003) Raise SYSTEM_WORKER_BLOCKED instead of CRITICAL_ERROR when checkpoint read lock timeout detected

[ https://issues.apache.org/jira/browse/IGNITE-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725903#comment-16725903 ] Andrey Gura edited comment on IGNITE-10003 at 12/20/18 2:40 PM:

[jira] [Comment Edited] (IGNITE-10003) Raise SYSTEM_WORKER_BLOCKED instead of CRITICAL_ERROR when checkpoint read lock timeout detected

[ https://issues.apache.org/jira/browse/IGNITE-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725903#comment-16725903 ] Andrey Gura edited comment on IGNITE-10003 at 12/20/18 2:39 PM:

[jira] [Commented] (IGNITE-10003) Raise SYSTEM_WORKER_BLOCKED instead of CRITICAL_ERROR when checkpoint read lock timeout detected

[ https://issues.apache.org/jira/browse/IGNITE-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725903#comment-16725903 ] Andrey Gura commented on IGNITE-10003: -- [~andrey-kuznetsov][~Jokser][~agoncharuk][~ivan.glukos]

[jira] [Commented] (IGNITE-3269) Benchmark driver stops working when one of servers left grid and backupcount 0

[ https://issues.apache.org/jira/browse/IGNITE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725866#comment-16725866 ] Andrey Gura commented on IGNITE-3269: - [~skozlov] My point here is benchmark results will not have

[jira] [Commented] (IGNITE-10003) Raise SYSTEM_WORKER_BLOCKED instead of CRITICAL_ERROR when checkpoint read lock timeout detected

[ https://issues.apache.org/jira/browse/IGNITE-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725822#comment-16725822 ] Andrey Gura commented on IGNITE-10003: -- [~andrey-kuznetsov] [~Jokser] LGTM. Except of unused

[jira] [Commented] (IGNITE-3269) Benchmark driver stops working when one of servers left grid and backupcount 0

[ https://issues.apache.org/jira/browse/IGNITE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725803#comment-16725803 ] Andrey Gura commented on IGNITE-3269: - [~oleg-ostanin] What is the intention of benchmarking cluster

[jira] [Commented] (IGNITE-9903) Copy only actual amount of data during archiving of WAL segment

[ https://issues.apache.org/jira/browse/IGNITE-9903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725808#comment-16725808 ] Andrey Gura commented on IGNITE-9903: - [~astelmak] The PR has too many merge conflicts after

[jira] [Commented] (IGNITE-9290) Make remove explicit locks async when node left.

[ https://issues.apache.org/jira/browse/IGNITE-9290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724100#comment-16724100 ] Andrey Gura commented on IGNITE-9290: - There is no such way. You can use

[jira] [Commented] (IGNITE-10563) Allow manual fsync for WAL

[ https://issues.apache.org/jira/browse/IGNITE-10563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723025#comment-16723025 ] Andrey Gura commented on IGNITE-10563: -- Just thoughts: {{putAll}} will involve *at least* one

[jira] [Resolved] (IGNITE-10482) Print stacktrace of the blocked thread in failure handler.

[ https://issues.apache.org/jira/browse/IGNITE-10482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura resolved IGNITE-10482. -- Resolution: Won't Fix > Print stacktrace of the blocked thread in failure handler. >

[jira] [Comment Edited] (IGNITE-10482) Print stacktrace of the blocked thread in failure handler.

[ https://issues.apache.org/jira/browse/IGNITE-10482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723002#comment-16723002 ] Andrey Gura edited comment on IGNITE-10482 at 12/17/18 2:00 PM:

[jira] [Commented] (IGNITE-10482) Print stacktrace of the blocked thread in failure handler.

[ https://issues.apache.org/jira/browse/IGNITE-10482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723002#comment-16723002 ] Andrey Gura commented on IGNITE-10482: -- {{FaiureProcessor}} dumps all stacks. This behaviour is

[jira] [Closed] (IGNITE-10412) Transaction tries to prepare after rollback

[ https://issues.apache.org/jira/browse/IGNITE-10412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura closed IGNITE-10412. > Transaction tries to prepare after rollback > --- > >

[jira] [Resolved] (IGNITE-10412) Transaction tries to prepare after rollback

[ https://issues.apache.org/jira/browse/IGNITE-10412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura resolved IGNITE-10412. -- Resolution: Won't Fix PRPC is valid case for changing topology. > Transaction tries to

[jira] [Closed] (IGNITE-10400) Server node stop by handler IgniteException: Failed to resolve node topology

[ https://issues.apache.org/jira/browse/IGNITE-10400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura closed IGNITE-10400. > Server node stop by handler IgniteException: Failed to resolve node topology >

[jira] [Commented] (IGNITE-10079) FileWriteAheadLogManager may return invalid lastCompactedSegment

[ https://issues.apache.org/jira/browse/IGNITE-10079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16703076#comment-16703076 ] Andrey Gura commented on IGNITE-10079: -- [~andrey-kuznetsov] LGTM. Merged to master branch. Thanks

[jira] [Updated] (IGNITE-10412) Transaction tries to prepare after rollback

[ https://issues.apache.org/jira/browse/IGNITE-10412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-10412: - Fix Version/s: 2.8 > Transaction tries to prepare after rollback >

[jira] [Updated] (IGNITE-10412) Transaction tries to prepare after rollback

[ https://issues.apache.org/jira/browse/IGNITE-10412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-10412: - Description: Transaction could be rolled back due to a changing baseline topology. But it

[jira] [Updated] (IGNITE-10412) Transaction tries to prepare after rollback

[ https://issues.apache.org/jira/browse/IGNITE-10412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-10412: - Summary: Transaction tries to prepare after rollback (was: Transaction tries prepare after

[jira] [Created] (IGNITE-10412) Transaction tries prepare after commit

Andrey Gura created IGNITE-10412: Summary: Transaction tries prepare after commit Key: IGNITE-10412 URL: https://issues.apache.org/jira/browse/IGNITE-10412 Project: Ignite Issue Type:

[jira] [Closed] (IGNITE-10327) Claster take NPE due cache stop and stop by handler

[ https://issues.apache.org/jira/browse/IGNITE-10327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura closed IGNITE-10327. > Claster take NPE due cache stop and stop by handler >

[jira] [Created] (IGNITE-10352) Cache get request can be mapped to node while partition in MOVING state

Andrey Gura created IGNITE-10352: Summary: Cache get request can be mapped to node while partition in MOVING state Key: IGNITE-10352 URL: https://issues.apache.org/jira/browse/IGNITE-10352 Project:

[jira] [Commented] (IGNITE-10154) Critical worker liveness check configuration is non-trivial and inconsistent

[ https://issues.apache.org/jira/browse/IGNITE-10154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686513#comment-16686513 ] Andrey Gura commented on IGNITE-10154: -- Merged to master and ignite-2.7 branches. > Critical

[jira] [Comment Edited] (IGNITE-10154) Critical worker liveness check configuration is non-trivial and inconsistent

[ https://issues.apache.org/jira/browse/IGNITE-10154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686423#comment-16686423 ] Andrey Gura edited comment on IGNITE-10154 at 11/14/18 12:08 PM: -

[jira] [Commented] (IGNITE-10154) Critical worker liveness check configuration is non-trivial and inconsistent

[ https://issues.apache.org/jira/browse/IGNITE-10154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686423#comment-16686423 ] Andrey Gura commented on IGNITE-10154: -- {{setIgnoreFailureTypes}} method is removed from

[jira] [Commented] (IGNITE-10154) Critical worker liveness check configuration is non-trivial and inconsistent

[ https://issues.apache.org/jira/browse/IGNITE-10154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683842#comment-16683842 ] Andrey Gura commented on IGNITE-10154: -- Merged to master and ignite-2.7 branches. > Critical

[jira] [Commented] (IGNITE-10154) Critical worker liveness check configuration is non-trivial and inconsistent

[ https://issues.apache.org/jira/browse/IGNITE-10154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683725#comment-16683725 ] Andrey Gura commented on IGNITE-10154: -- [~agoncharuk] Could you please review change? > Critical

[jira] [Commented] (IGNITE-10154) Critical worker liveness check configuration is non-trivial and inconsistent

[ https://issues.apache.org/jira/browse/IGNITE-10154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683686#comment-16683686 ] Andrey Gura commented on IGNITE-10154: -- [~yzhdanov] Liveness checking is disabled only if checking

[jira] [Commented] (IGNITE-10154) Critical worker liveness check configuration is non-trivial and inconsistent

[ https://issues.apache.org/jira/browse/IGNITE-10154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16679579#comment-16679579 ] Andrey Gura commented on IGNITE-10154: -- Agree, it's breaking change. Solution: add

[jira] [Assigned] (IGNITE-10154) Critical worker liveness check configuration is non-trivial and inconsistent

[ https://issues.apache.org/jira/browse/IGNITE-10154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura reassigned IGNITE-10154: Assignee: Andrey Gura > Critical worker liveness check configuration is non-trivial and

[jira] [Updated] (IGNITE-9903) Copy only actual amount of data during archiving of WAL segment

[ https://issues.apache.org/jira/browse/IGNITE-9903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-9903: Ignite Flags: (was: Docs Required) > Copy only actual amount of data during archiving of WAL

[jira] [Created] (IGNITE-9903) Copy only actual amount of data during archiving of WAL segment

Andrey Gura created IGNITE-9903: --- Summary: Copy only actual amount of data during archiving of WAL segment Key: IGNITE-9903 URL: https://issues.apache.org/jira/browse/IGNITE-9903 Project: Ignite

[jira] [Commented] (IGNITE-9710) Ignite watchdog service handles longrunning cache creation

[ https://issues.apache.org/jira/browse/IGNITE-9710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650569#comment-16650569 ] Andrey Gura commented on IGNITE-9710: - [~andrey-kuznetsov] I've found a mistake a-la copy See

[jira] [Commented] (IGNITE-9737) Ignite WatchDog service should be configurable

[ https://issues.apache.org/jira/browse/IGNITE-9737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650536#comment-16650536 ] Andrey Gura commented on IGNITE-9737: - [~andrey-kuznetsov] I've added a few comments to upsource

[jira] [Updated] (IGNITE-9723) Critial section should be wrapped correctly for GridCacheDatabaseSharedManager

[ https://issues.apache.org/jira/browse/IGNITE-9723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-9723: Priority: Blocker (was: Major) > Critial section should be wrapped correctly for

[jira] [Commented] (IGNITE-6587) Ignite watchdog service

[ https://issues.apache.org/jira/browse/IGNITE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625766#comment-16625766 ] Andrey Gura commented on IGNITE-6587: - [~andrey-kuznetsov] And finally merged to master branch!

[jira] [Updated] (IGNITE-6587) Ignite watchdog service

[ https://issues.apache.org/jira/browse/IGNITE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-6587: Ignite Flags: Docs Required > Ignite watchdog service > --- > >

[jira] [Commented] (IGNITE-9657) socket leak in TcpDiscoverySpi

[ https://issues.apache.org/jira/browse/IGNITE-9657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16623719#comment-16623719 ] Andrey Gura commented on IGNITE-9657: - [~ezhuravl] LGTM. Merged to master. Thanks for contribution!

[jira] [Commented] (IGNITE-9601) Write rollover WAL record as the last record in current segment

[ https://issues.apache.org/jira/browse/IGNITE-9601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16622570#comment-16622570 ] Andrey Gura commented on IGNITE-9601: - [~andrey-kuznetsov] I've looked at your change and have the

[jira] [Updated] (IGNITE-9384) Transaction state PREPARED may be set too early or too late

[ https://issues.apache.org/jira/browse/IGNITE-9384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-9384: Description: I see the following issues in the {{GridDhtTxPrepareFutureAdapter}} class: 1)

[jira] [Assigned] (IGNITE-9384) Transaction state PREPARED may be set too early or too late

[ https://issues.apache.org/jira/browse/IGNITE-9384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura reassigned IGNITE-9384: --- Assignee: Andrey Gura > Transaction state PREPARED may be set too early or too late >

[jira] [Commented] (IGNITE-6587) Ignite watchdog service

[ https://issues.apache.org/jira/browse/IGNITE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602284#comment-16602284 ] Andrey Gura commented on IGNITE-6587: - [~andrey-kuznetsov] I've looked at your changes and I

[jira] [Updated] (IGNITE-6587) Ignite watchdog service

[ https://issues.apache.org/jira/browse/IGNITE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-6587: Fix Version/s: (was: 2.8) 2.7 > Ignite watchdog service >

[jira] [Assigned] (IGNITE-9438) StandaloneWalRecordsIterator file descriptors leak

[ https://issues.apache.org/jira/browse/IGNITE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura reassigned IGNITE-9438: --- Assignee: Sergey Antonov > StandaloneWalRecordsIterator file descriptors leak >

[jira] [Commented] (IGNITE-9120) Metadata writer does not propagate error to failure handler

[ https://issues.apache.org/jira/browse/IGNITE-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594926#comment-16594926 ] Andrey Gura commented on IGNITE-9120: - [~a-polyakov] Is there any reproducer and full stack trace?

[jira] [Updated] (IGNITE-9120) Metadata writer does not propagate error to failure handler

[ https://issues.apache.org/jira/browse/IGNITE-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-9120: Ignite Flags: (was: Docs Required) > Metadata writer does not propagate error to failure

[jira] [Updated] (IGNITE-8642) Failure processor should dump state of all threads

[ https://issues.apache.org/jira/browse/IGNITE-8642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8642: Ignite Flags: Docs Required > Failure processor should dump state of all threads >

[jira] [Updated] (IGNITE-6405) Deadlock is not detected if timed out on client.

[ https://issues.apache.org/jira/browse/IGNITE-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-6405: Fix Version/s: (was: 2.7) 2.8 > Deadlock is not detected if timed out on

[jira] [Commented] (IGNITE-6527) Deadlock detection works incorrectly with some timeouts that haven't caused by deadlocks.

[ https://issues.apache.org/jira/browse/IGNITE-6527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594804#comment-16594804 ] Andrey Gura commented on IGNITE-6527: - [~VitaliyB] Could you please move tickets to the "Path

[jira] [Updated] (IGNITE-7820) Investigate and fix perfromance drop of WAL for FSYNC mode

[ https://issues.apache.org/jira/browse/IGNITE-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-7820: Fix Version/s: (was: 2.7) 2.8 > Investigate and fix perfromance drop of

[jira] [Updated] (IGNITE-6527) Deadlock detection works incorrectly with some timeouts that haven't caused by deadlocks.

[ https://issues.apache.org/jira/browse/IGNITE-6527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-6527: Fix Version/s: (was: 2.7) 2.8 > Deadlock detection works incorrectly with

[jira] [Updated] (IGNITE-8641) SpringDataExample should use example-ignite.xml config

[ https://issues.apache.org/jira/browse/IGNITE-8641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8641: Fix Version/s: (was: 2.7) 2.8 > SpringDataExample should use

[jira] [Commented] (IGNITE-8337) Java ThinClient benchmark for yardstick

[ https://issues.apache.org/jira/browse/IGNITE-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593796#comment-16593796 ] Andrey Gura commented on IGNITE-8337: - [~oleg-ostanin] LGTM. Merged to master branch. Thanks for

[jira] [Resolved] (IGNITE-8337) Java ThinClient benchmark for yardstick

[ https://issues.apache.org/jira/browse/IGNITE-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura resolved IGNITE-8337. - Resolution: Fixed > Java ThinClient benchmark for yardstick >

[jira] [Resolved] (IGNITE-9296) Stopping node by Failure Handler hangs up in IgniteWalFlushBackgroundSelfTest

[ https://issues.apache.org/jira/browse/IGNITE-9296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura resolved IGNITE-9296. - Resolution: Fixed [~macrergate] LGTM! Merged to master branch. Thanks for contribution! >

[jira] [Updated] (IGNITE-9296) Stopping node by Failure Handler hangs up in IgniteWalFlushBackgroundSelfTest

[ https://issues.apache.org/jira/browse/IGNITE-9296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-9296: Fix Version/s: 2.7 > Stopping node by Failure Handler hangs up in

[jira] [Commented] (IGNITE-1094) Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

[ https://issues.apache.org/jira/browse/IGNITE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16588787#comment-16588787 ] Andrey Gura commented on IGNITE-1094: - [~vozerov] It's bad idea to reopen issue that was included in

[jira] [Commented] (IGNITE-8486) Update ConcurrentLinkedDeque in Ignite's master repository to the latest JDK version

[ https://issues.apache.org/jira/browse/IGNITE-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16587889#comment-16587889 ] Andrey Gura commented on IGNITE-8486: - I remember that fix did'nt solve the problem. So path is

[jira] [Commented] (IGNITE-9296) Stopping node by Failure Handler hangs up in IgniteWalFlushBackgroundSelfTest

[ https://issues.apache.org/jira/browse/IGNITE-9296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16587881#comment-16587881 ] Andrey Gura commented on IGNITE-9296: - [~macrergate] I've looked a your change. It is odd fix from

[jira] [Commented] (IGNITE-9280) Decrease WAL archive compaction latency

[ https://issues.apache.org/jira/browse/IGNITE-9280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584054#comment-16584054 ] Andrey Gura commented on IGNITE-9280: - LGTM. Fixed some cosmetics and merged to master branch.

[jira] [Resolved] (IGNITE-9280) Decrease WAL archive compaction latency

[ https://issues.apache.org/jira/browse/IGNITE-9280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura resolved IGNITE-9280. - Resolution: Fixed > Decrease WAL archive compaction latency >

[jira] [Updated] (IGNITE-9100) Split Basic and Cache TC configurations on pure in-memory and with disk usage one

[ https://issues.apache.org/jira/browse/IGNITE-9100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-9100: Fix Version/s: 2.7 > Split Basic and Cache TC configurations on pure in-memory and with disk

[jira] [Commented] (IGNITE-7967) DataRegionMetrics#totalAllocatedPages is invalid if metrics were enabled at runtime

[ https://issues.apache.org/jira/browse/IGNITE-7967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16548224#comment-16548224 ] Andrey Gura commented on IGNITE-7967: - [~cyberdemon] I've looked to your change and I believe it is

[jira] [Commented] (IGNITE-9025) "PDS 1" TC configuration could hang because of SegmentedRingByteBufferTest

[ https://issues.apache.org/jira/browse/IGNITE-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546932#comment-16546932 ] Andrey Gura commented on IGNITE-9025: - [~EdShangGG] LGTM. Merged to master branch. Thanks for

[jira] [Updated] (IGNITE-9025) "PDS 1" TC configuration could hang because of SegmentedRingByteBufferTest

[ https://issues.apache.org/jira/browse/IGNITE-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-9025: Fix Version/s: 2.7 > "PDS 1" TC configuration could hang because of SegmentedRingByteBufferTest >

[jira] [Commented] (IGNITE-1094) Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

[ https://issues.apache.org/jira/browse/IGNITE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545223#comment-16545223 ] Andrey Gura commented on IGNITE-1094: - Thanks! Merged to master branch. >

[jira] [Commented] (IGNITE-8875) Add JMX methods to block\unblock new incoming connections from thin clients.

[ https://issues.apache.org/jira/browse/IGNITE-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538729#comment-16538729 ] Andrey Gura commented on IGNITE-8875: - [~amashenkov] Could you please add issue description. Idea,

[jira] [Updated] (IGNITE-8898) rename command argument '--force' to '--yes' for control.sh

[ https://issues.apache.org/jira/browse/IGNITE-8898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8898: Fix Version/s: 2.7 > rename command argument '--force' to '--yes' for control.sh >

[jira] [Commented] (IGNITE-8869) PartitionsExchangeOnDiscoveryHistoryOverflowTest hangs on TeamCity

[ https://issues.apache.org/jira/browse/IGNITE-8869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537179#comment-16537179 ] Andrey Gura commented on IGNITE-8869: - Thanks! Merged to master branch. >

[jira] [Updated] (IGNITE-7777) Thin Client lib: Node.js

[ https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-: Fix Version/s: (was: 2.6) 2.7 > Thin Client lib: Node.js >

[jira] [Commented] (IGNITE-7823) Separate cache for non collocated IgniteSet.

[ https://issues.apache.org/jira/browse/IGNITE-7823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16536979#comment-16536979 ] Andrey Gura commented on IGNITE-7823: - Compatibility based on version is fragile and this approach

[jira] [Comment Edited] (IGNITE-7823) Separate cache for non collocated IgniteSet.

[ https://issues.apache.org/jira/browse/IGNITE-7823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16536891#comment-16536891 ] Andrey Gura edited comment on IGNITE-7823 at 7/9/18 1:13 PM: - [~xtern] It

[jira] [Comment Edited] (IGNITE-7823) Separate cache for non collocated IgniteSet.

[ https://issues.apache.org/jira/browse/IGNITE-7823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16536891#comment-16536891 ] Andrey Gura edited comment on IGNITE-7823 at 7/9/18 1:12 PM: - [~xtern] It

[jira] [Updated] (IGNITE-8776) Eviction policy MBeans are never registered if evictionPolicyFactory is used

[ https://issues.apache.org/jira/browse/IGNITE-8776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8776: Fix Version/s: (was: 2.6) 2.7 > Eviction policy MBeans are never

[jira] [Updated] (IGNITE-8942) In some cases grid cannot be deactivated because of hanging CQ internal cleanup.

[ https://issues.apache.org/jira/browse/IGNITE-8942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8942: Fix Version/s: (was: 2.6) 2.7 > In some cases grid cannot be deactivated

[jira] [Updated] (IGNITE-8929) WAL should not disable for the group if none a partition is not assigned to a local node

[ https://issues.apache.org/jira/browse/IGNITE-8929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8929: Fix Version/s: (was: 2.6) 2.7 > WAL should not disable for the group if

[jira] [Commented] (IGNITE-7823) Separate cache for non collocated IgniteSet.

[ https://issues.apache.org/jira/browse/IGNITE-7823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16536891#comment-16536891 ] Andrey Gura commented on IGNITE-7823: - [~xtern] It is't the best idea to use version in

[jira] [Updated] (IGNITE-8754) Node outside of baseline does not start when service configured

[ https://issues.apache.org/jira/browse/IGNITE-8754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8754: Fix Version/s: 2.7 > Node outside of baseline does not start when service configured >

[jira] [Updated] (IGNITE-8620) Remove intOrder and loc keys from node info in control.sh --tx utility

[ https://issues.apache.org/jira/browse/IGNITE-8620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8620: Fix Version/s: 2.7 > Remove intOrder and loc keys from node info in control.sh --tx utility >

[jira] [Created] (IGNITE-8938) file-decompressor thread termination should be handled with Failure handler

Andrey Gura created IGNITE-8938: --- Summary: file-decompressor thread termination should be handled with Failure handler Key: IGNITE-8938 URL: https://issues.apache.org/jira/browse/IGNITE-8938 Project:

[jira] [Updated] (IGNITE-8797) Error during writeCheckpointEntry is not passed to failure handler during checkpoint finish

[ https://issues.apache.org/jira/browse/IGNITE-8797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8797: Fix Version/s: 2.7 > Error during writeCheckpointEntry is not passed to failure handler during >

[jira] [Commented] (IGNITE-8780) File I/O operations must be retried if buffer hasn't read/written completely

[ https://issues.apache.org/jira/browse/IGNITE-8780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533000#comment-16533000 ] Andrey Gura commented on IGNITE-8780: - Merged to master branch. > File I/O operations must be

[jira] [Updated] (IGNITE-8780) File I/O operations must be retried if buffer hasn't read/written completely

[ https://issues.apache.org/jira/browse/IGNITE-8780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8780: Fix Version/s: (was: 2.6) 2.7 > File I/O operations must be retried if

[jira] [Updated] (IGNITE-8769) JVM crash in Basic1 suite in master branch on TC

[ https://issues.apache.org/jira/browse/IGNITE-8769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8769: Fix Version/s: (was: 2.7) 2.6 > JVM crash in Basic1 suite in master branch

[jira] [Updated] (IGNITE-8910) PagesList.takeEmptyPage may fail with AssertionError: type = 1

[ https://issues.apache.org/jira/browse/IGNITE-8910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8910: Fix Version/s: (was: 2.7) 2.6 > PagesList.takeEmptyPage may fail with

[jira] [Commented] (IGNITE-4210) CacheLoadingConcurrentGridStartSelfTest.testLoadCacheFromStore() test lose data.

[ https://issues.apache.org/jira/browse/IGNITE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532671#comment-16532671 ] Andrey Gura commented on IGNITE-4210: - [~Alexey Kuznetsov] I don't see any arguments for blocking

[jira] [Updated] (IGNITE-8902) GridDhtTxRemote sometimes not rolled back in one phase commit scenario.

[ https://issues.apache.org/jira/browse/IGNITE-8902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8902: Fix Version/s: (was: 2.6) 2.7 > GridDhtTxRemote sometimes not rolled back

[jira] [Updated] (IGNITE-8921) Add control.sh --cache affinity command to output current and ideal assignment and optionally show diff between them

[ https://issues.apache.org/jira/browse/IGNITE-8921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8921: Fix Version/s: (was: 2.6) 2.7 > Add control.sh --cache affinity command to

[jira] [Created] (IGNITE-8823) Incorrect transaction state in tx manager

Andrey Gura created IGNITE-8823: --- Summary: Incorrect transaction state in tx manager Key: IGNITE-8823 URL: https://issues.apache.org/jira/browse/IGNITE-8823 Project: Ignite Issue Type: Bug

<    1   2   3   4   5   6   7   8   9   10   >