[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&focusedCommentId=16650536#comment-16650536 ] Andrey Gura commented on IGNITE-9737: - [~andrey-kuznetsov] I've added a few comments

[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&focusedCommentId=16650569#comment-16650569 ] Andrey Gura commented on IGNITE-9710: - [~andrey-kuznetsov] I've found a mistake a-la

[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] [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 seg

[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] [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&focusedCommentId=16679579#comment-16679579 ] Andrey Gura commented on IGNITE-10154: -- Agree, it's breaking change. Solution: add

[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&focusedCommentId=16683686#comment-16683686 ] Andrey Gura commented on IGNITE-10154: -- [~yzhdanov] Liveness checking is disabled

[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&focusedCommentId=16683725#comment-16683725 ] Andrey Gura commented on IGNITE-10154: -- [~agoncharuk] Could you please review chan

[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&focusedCommentId=16683842#comment-16683842 ] Andrey Gura commented on IGNITE-10154: -- Merged to master and ignite-2.7 branches.

[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&focusedCommentId=16686423#comment-16686423 ] Andrey Gura commented on IGNITE-10154: -- {{setIgnoreFailureTypes}} method is remove

[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&focusedCommentId=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&focusedCommentId=16686513#comment-16686513 ] Andrey Gura commented on IGNITE-10154: -- Merged to master and ignite-2.7 branches.

[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: Ig

[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-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: Improve

[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 com

[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 stil

[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] [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&focusedCommentId=16703076#comment-16703076 ] Andrey Gura commented on IGNITE-10079: -- [~andrey-kuznetsov] LGTM. Merged to master

[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] [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 prep

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

[ https://issues.apache.org/jira/browse/IGNITE-10412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703108#comment-16703108 ] Andrey Gura edited comment on IGNITE-10412 at 11/29/18 12:32 PM:

[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] [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&focusedCommentId=16723002#comment-16723002 ] Andrey Gura commented on IGNITE-10482: -- {{FaiureProcessor}} dumps all stacks. This

[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&focusedCommentId=16723002#comment-16723002 ] Andrey Gura edited comment on IGNITE-10482 at 12/17/18 2:00 PM: -

[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&focusedCommentId=16723025#comment-16723025 ] Andrey Gura commented on IGNITE-10563: -- Just thoughts: {{putAll}} will involve *a

[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&focusedCommentId=16724100#comment-16724100 ] Andrey Gura commented on IGNITE-9290: - There is no such way. You can use {{GridWorke

[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&focusedCommentId=16725808#comment-16725808 ] Andrey Gura commented on IGNITE-9903: - [~astelmak] The PR has too many merge conflic

[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&focusedCommentId=16725803#comment-16725803 ] Andrey Gura commented on IGNITE-3269: - [~oleg-ostanin] What is the intention of benc

[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&focusedCommentId=16725822#comment-16725822 ] Andrey Gura commented on IGNITE-10003: -- [~andrey-kuznetsov] [~Jokser] LGTM. Except

[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&focusedCommentId=16725866#comment-16725866 ] Andrey Gura commented on IGNITE-3269: - [~skozlov] My point here is benchmark results

[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&focusedCommentId=16725903#comment-16725903 ] Andrey Gura commented on IGNITE-10003: -- [~andrey-kuznetsov][~Jokser][~agoncharuk][

[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&focusedCommentId=16725903#comment-16725903 ] Andrey Gura edited comment on IGNITE-10003 at 12/20/18 2:39 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&focusedCommentId=16725903#comment-16725903 ] Andrey Gura edited comment on IGNITE-10003 at 12/20/18 2:40 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&focusedCommentId=16725924#comment-16725924 ] Andrey Gura commented on IGNITE-10003: -- [~andrey-kuznetsov] Timeout is more specif

[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 Type

[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] [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 worker's

[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 worker's

[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&focusedCommentId=16726692#comment-16726692 ] Andrey Gura commented on IGNITE-10003: -- [~Jokser]] Don't merge please. My comment

[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&focusedCommentId=16726692#comment-16726692 ] Andrey Gura edited comment on IGNITE-10003 at 12/21/18 12:32 PM:

[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&focusedCommentId=16728331#comment-16728331 ] Andrey Gura commented on IGNITE-10760: -- [~ilyak] This is just usability issue. It

[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&focusedCommentId=16728399#comment-16728399 ] Andrey Gura commented on IGNITE-10003: -- Ok, I have no objections. > Raise SYSTEM_

[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&focusedCommentId=16728409#comment-16728409 ] Andrey Gura commented on IGNITE-10806: -- Protocol version 1 used by Ignite <1.6 ver

[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-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&focusedCommentId=16728440#comment-16728440 ] Andrey Gura commented on IGNITE-3269: - [~oleg-ostanin] LGTM. Merged to master branch

[jira] [Updated] (IGNITE-9739) Critical exception in transaction processing in case we have nodes out of baseline and non-persisted cache

[ https://issues.apache.org/jira/browse/IGNITE-9739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-9739: Fix Version/s: 2.8 > Critical exception in transaction processing in case we have nodes out of >

[jira] [Resolved] (IGNITE-10938) After restart cluster with non-blt nodes - they left by handler

[ https://issues.apache.org/jira/browse/IGNITE-10938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura resolved IGNITE-10938. -- Resolution: Duplicate > After restart cluster with non-blt nodes - they left by handler > ---

[jira] [Updated] (IGNITE-11129) Incorrect size calculation for SWITCH_SEGMENT_RECORD for TDE

[ https://issues.apache.org/jira/browse/IGNITE-11129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-11129: - Description: Size of {{SWITCH_SEGMENT_RECORD}} will be invalid in case of encryption switched

[jira] [Created] (IGNITE-11129) Incorrect size calculation for SWITCH_SEGMENT_RECORD for TDE

Andrey Gura created IGNITE-11129: Summary: Incorrect size calculation for SWITCH_SEGMENT_RECORD for TDE Key: IGNITE-11129 URL: https://issues.apache.org/jira/browse/IGNITE-11129 Project: Ignite

[jira] [Updated] (IGNITE-11129) Incorrect size calculation for SWITCH_SEGMENT_RECORD for TDE

[ https://issues.apache.org/jira/browse/IGNITE-11129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-11129: - Description: Size of {{SWITCH_SEGMENT_RECORD}} will be invalid in case of encryption switched

[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&focusedCommentId=16755142#comment-16755142 ] Andrey Gura commented on IGNITE-9903: - [~astelmak] I've looked at your change and ha

[jira] [Comment Edited] (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&focusedCommentId=16755142#comment-16755142 ] Andrey Gura edited comment on IGNITE-9903 at 1/29/19 6:40 PM:

[jira] [Commented] (IGNITE-11129) Incorrect size calculation for SWITCH_SEGMENT_RECORD for TDE

[ https://issues.apache.org/jira/browse/IGNITE-11129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757846#comment-16757846 ] Andrey Gura commented on IGNITE-11129: -- [~mstepachev] Agree. Thanks. > Incorrect

[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&focusedCommentId=16757843#comment-16757843 ] Andrey Gura commented on IGNITE-9903: - [~astelmak] LGTM. Merged to master branch. Th

[jira] [Closed] (IGNITE-11129) Incorrect size calculation for SWITCH_SEGMENT_RECORD for TDE

[ https://issues.apache.org/jira/browse/IGNITE-11129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura closed IGNITE-11129. > Incorrect size calculation for SWITCH_SEGMENT_RECORD for TDE >

[jira] [Commented] (IGNITE-11130) BackupPostProcessingClosure should not save initial value on a backup node when cache store is not configured.

[ https://issues.apache.org/jira/browse/IGNITE-11130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757850#comment-16757850 ] Andrey Gura commented on IGNITE-11130: -- [~slava.koptilin] LGTM. But is seems that

[jira] [Commented] (IGNITE-11130) BackupPostProcessingClosure should not save initial value on a backup node when cache store is not configured.

[ https://issues.apache.org/jira/browse/IGNITE-11130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758266#comment-16758266 ] Andrey Gura commented on IGNITE-11130: -- [~slava.koptilin] Thanks. Merged to master

[jira] [Commented] (IGNITE-11253) When a node that is not part of the baseline topology joins the cluster, it may lead to a node failure.

[ https://issues.apache.org/jira/browse/IGNITE-11253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764906#comment-16764906 ] Andrey Gura commented on IGNITE-11253: -- [~slava.koptilin] Could you please add at

[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 usage

[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] [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&focusedCommentId=16584054#comment-16584054 ] Andrey Gura commented on IGNITE-9280: - LGTM. Fixed some cosmetics and merged to mast

[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&focusedCommentId=16587881#comment-16587881 ] Andrey Gura commented on IGNITE-9296: - [~macrergate] I've looked a your change. It i

[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&focusedCommentId=16587889#comment-16587889 ] Andrey Gura commented on IGNITE-8486: - I remember that fix did'nt solve the problem.

[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&focusedCommentId=16588787#comment-16588787 ] Andrey Gura commented on IGNITE-1094: - [~vozerov] It's bad idea to reopen issue that

[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 IgniteWalFlushBackgroundSelfTes

[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! > Stop

[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] [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&focusedCommentId=16593796#comment-16593796 ] Andrey Gura commented on IGNITE-8337: - [~oleg-ostanin] LGTM. Merged to master branch

[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 example-ignite

[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 s

[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 WAL

[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&focusedCommentId=16594804#comment-16594804 ] Andrey Gura commented on IGNITE-6527: - [~VitaliyB] Could you please move tickets to

[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 cl

[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-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 handler

[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&focusedCommentId=16594926#comment-16594926 ] Andrey Gura commented on IGNITE-9120: - [~a-polyakov] Is there any reproducer and ful

[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] [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] [Commented] (IGNITE-6587) Ignite watchdog service

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

[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] [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) {{PREPA

[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&focusedCommentId=16622570#comment-16622570 ] Andrey Gura commented on IGNITE-9601: - [~andrey-kuznetsov] I've looked at your chang

[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&focusedCommentId=16623719#comment-16623719 ] Andrey Gura commented on IGNITE-9657: - [~ezhuravl] LGTM. Merged to master. Thanks fo

[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-6587) Ignite watchdog service

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

[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 GridCacheDatabas

[jira] [Commented] (IGNITE-10925) Failure to submit affinity task from client node

[ https://issues.apache.org/jira/browse/IGNITE-10925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779470#comment-16779470 ] Andrey Gura commented on IGNITE-10925: -- [~ilyak] LGTM. Please merge. Thanks! > Fa

[jira] [Commented] (IGNITE-11127) GridDhtInvalidPartitionException not handled by GridCacheTtlManager

[ https://issues.apache.org/jira/browse/IGNITE-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802765#comment-16802765 ] Andrey Gura commented on IGNITE-11127: -- [~roman_s] Looks good to me too. > GridDh

[jira] [Commented] (IGNITE-9812) Explicit tests with expired SSL certificates

[ https://issues.apache.org/jira/browse/IGNITE-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802772#comment-16802772 ] Andrey Gura commented on IGNITE-9812: - [~ilyak] LGTM! Please proceed with merge. >

[jira] [Commented] (IGNITE-7883) Cluster can have inconsistent affinity configuration

[ https://issues.apache.org/jira/browse/IGNITE-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802903#comment-16802903 ] Andrey Gura commented on IGNITE-7883: - [~a-polyakov] I've took a look ti the change

[jira] [Assigned] (IGNITE-11687) Concurrent WAL replay & log may fail with CRC error on read

[ https://issues.apache.org/jira/browse/IGNITE-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura reassigned IGNITE-11687: Assignee: Andrey Gura > Concurrent WAL replay & log may fail with CRC error on read > --

[jira] [Comment Edited] (IGNITE-11687) Concurrent WAL replay & log may fail with CRC error on read

[ https://issues.apache.org/jira/browse/IGNITE-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811031#comment-16811031 ] Andrey Gura edited comment on IGNITE-11687 at 4/5/19 4:38 PM: ---

[jira] [Commented] (IGNITE-11687) Concurrent WAL replay & log may fail with CRC error on read

[ https://issues.apache.org/jira/browse/IGNITE-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811031#comment-16811031 ] Andrey Gura commented on IGNITE-11687: -- [~agoncharuk] You are right. It could be f

[jira] [Commented] (IGNITE-11687) Concurrent WAL replay & log may fail with CRC error on read

[ https://issues.apache.org/jira/browse/IGNITE-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16818481#comment-16818481 ] Andrey Gura commented on IGNITE-11687: -- [~agoncharuk] I've investigated the proble

[jira] [Commented] (IGNITE-11774) NPE TxDeadlockDetection in case of concurrent cache stop and tx.

[ https://issues.apache.org/jira/browse/IGNITE-11774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821957#comment-16821957 ] Andrey Gura commented on IGNITE-11774: -- [~zstan] Does it prevent successful node s

[jira] [Assigned] (IGNITE-11267) Print warning when keystore password arguments are used in control.sh (bat)

[ https://issues.apache.org/jira/browse/IGNITE-11267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura reassigned IGNITE-11267: Assignee: Andrey Kuznetsov (was: Andrey Gura) > Print warning when keystore password ar

[jira] [Assigned] (IGNITE-11267) Print warning when keystore password arguments are used in control.sh (bat)

[ https://issues.apache.org/jira/browse/IGNITE-11267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura reassigned IGNITE-11267: Assignee: Andrey Gura (was: Andrey Kuznetsov) > Print warning when keystore password ar

[jira] [Commented] (IGNITE-11804) Assertion error

[ https://issues.apache.org/jira/browse/IGNITE-11804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825354#comment-16825354 ] Andrey Gura commented on IGNITE-11804: -- [~ascherbakov] Could you please add assert

  1   2   3   4   5   6   7   8   9   10   >