Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]
Thanks, I will keep the original ticket in patch available then and leave a comment. Let us know if need any help with moving commits to the release branch. пт, 17 апр. 2020 г. в 18:18, Nikolay Izhikov : > Please, don’t cherry pick tickets to 2.8.1 > It seems I have to cherry pick many previous tickets for 2.8.1 to avoid > conflicts. > > > 17 апр. 2020 г., в 18:01, Alexey Goncharuk > написал(а): > > > > Nikolay, > > > > If I merge a ticket that is already targeted for 2.8.1 to master, do you > > prefer this ticket to be cherry-picket to 2.8.1 yourself or should I > merge > > it to the release branch? > > > > пт, 17 апр. 2020 г. в 16:55, Ivan Pavlukhin : > > > >> Great! > >> > >> Best regards, > >> Ivan Pavlukhin > >> > >> пт, 17 апр. 2020 г. в 12:48, Nikolay Izhikov : > >>> > >>> OK, let’s try it > >>> > I do not know who is a manager for 2.8.1. > >>> > >>> I am. > >>> > >>> > 17 апр. 2020 г., в 12:42, Ivan Pavlukhin > >> написал(а): > > > We didn’t it for the previous releases. > > Why we should start to do it?) > > Because it seems to be a good thing, is not it? I suppose it is > important to know who is a release manager (the current thread subject > has a "Manager" keyword). E.g. I do not know who is a manager for > 2.8.1. > > Best regards, > Ivan Pavlukhin > > пт, 17 апр. 2020 г. в 12:27, Nikolay Izhikov : > > > > Hello, > > > >> Should not we reflect on the release page [1] who is a release > >> manager? > > > > We didn’t it for the previous releases. > > Why we should start to do it?) > > > >> I suggest to include these fixes into 2.8.1 release: > > > > Thanks, included. > > > > > > > >> 17 апр. 2020 г., в 12:20, Ivan Rakov > >> написал(а): > >> > >> Hi, > >> > >> I suggest to include these fixes into 2.8.1 release: > >> https://issues.apache.org/jira/browse/IGNITE-12101 > >> https://issues.apache.org/jira/browse/IGNITE-12651 > >> > >> On Fri, Apr 17, 2020 at 11:32 AM Ivan Pavlukhin < > vololo...@gmail.com> > >> wrote: > >> > >>> Hi folks, > >>> > >>> A side note from an external spectator. Should not we reflect on > the > >>> release page [1] who is a release manager? > >>> > >>> [1] > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > >>> > >>> Best regards, > >>> Ivan Pavlukhin > >>> > >>> пт, 17 апр. 2020 г. в 11:11, Nikolay Izhikov >: > > Hello, Igniters. > > I’ve added all tickets proposed in this thread to 2.8.1 scope [1] > For now we have > > 61 resolved tickets. > 19 unresolved tickets. > > > > [1] > >>> > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > > > 17 апр. 2020 г., в 01:38, Alex Plehanov > > >>> написал(а): > > > > Hello guys, > > > > I propose to cherry-pick to 2.8.1 following bug-fixes too, which > >> are > > already in master: > > Scan query over an evicted partition can cause node failure > >>> (IGNITE-12734 > > [1]) > > Java thin client: There were problems with deserialization of > some > >>> types on > > the client-side, these types can't be used (IGNITE-12624 > > [2], IGNITE-12468 [3]) > > Java thin client: Thread doesn't stop properly on client close > >> when > > partition awareness is enabled, this prevents main() method from > >>> exiting > > (IGNITE-12743 [4]) > > > > Also, there is a performance fix for checkpoint read lock, which > I > >>> propose > > to cherry-pick too (IGNITE-12491 [5]). This fix brings > significant > > performance boost on environments with a large number of CPUs > >> (there > >>> was > > some drop on such environments introduced in 2.8.0 for all > >>> transactional > > operations after IGNITE-12593 fixing) > > > > WDYT? > > > > [1]: https://issues.apache.org/jira/browse/IGNITE-12734 > > [2]: https://issues.apache.org/jira/browse/IGNITE-12624 > > [3]: https://issues.apache.org/jira/browse/IGNITE-12468 > > [4]: https://issues.apache.org/jira/browse/IGNITE-12743 > > [5]: https://issues.apache.org/jira/browse/IGNITE-12491 > > > > чт, 16 апр. 2020 г. в 18:48, Maxim Muzafarov >: > > > >> Nikolay, > >> > >> Probably, we should not wait for all blocker issues in minor > >> bug-fix > >> releases except very special cases. I think we should release > all > >> accumulated bug-fixes `as is` and schedule the next 2.8.2 > >> release. > >> This will allow as to have shorten minor releases. > >> > >> On Thu, 16 Apr 2020 at 18:17, Nikolay I
[jira] [Created] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a value object --- and SQL enabled.
Alexander Korenshteyn created IGNITE-12911:
--
Summary: B+Tree Corrupted exception when using a key extracted
from a value object --- and SQL enabled.
Key: IGNITE-12911
URL: https://issues.apache.org/jira/browse/IGNITE-12911
Project: Ignite
Issue Type: Bug
Components: cache, sql
Reporter: Alexander Korenshteyn
Attachments: Employee.java, EmployeeId.java, ServerNode.java
If a key is part of the value like so:
class key \{ ... }
class value {
private Key key
getKey()
}
cache = ignite.cache()*.withKeepBinary()*
the following scenario yields a B+ Tree exception:
1. *Enable SQL via annotations or QueryEntities.*
key1= new Key()
value1 = new Value(key1)
cache.put(key1, value1)
BinaryObject val2 = cache.get(key1)
BinaryObject key2 = val2.field("key")
*cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree iscorrupted
...*
user list:
[http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html]
*Reproducer – attached*
Exception:
[2020-04-17 11:24:33,475][ERROR][main][root] Critical system error detected.
Will be handled accordingly to configured handler
[hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
departmentNumber=123], val: model.Employee [idHash=382762227, hash=1627745429,
firstName=John, lastName=Smith, id=model.EmployeeId [idHash=2021540695,
hash=674030145, employeeNumber=65348765, departmentNumber=123]] ][ John, Smith
class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
departmentNumber=123], val: model.Employee [idHash=382762227, hash=1627745429,
firstName=John, lastName=Smith, id=model.EmployeeId [idHash=2021540695,
hash=674030145, employeeNumber=65348765, departmentNumber=123]] ][ John, Smith
]]
at
org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
at
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:401)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2555)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1664)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1639)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:436)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2311)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2593)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:2053)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1871)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1685)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendS
Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]
Please, don’t cherry pick tickets to 2.8.1 It seems I have to cherry pick many previous tickets for 2.8.1 to avoid conflicts. > 17 апр. 2020 г., в 18:01, Alexey Goncharuk > написал(а): > > Nikolay, > > If I merge a ticket that is already targeted for 2.8.1 to master, do you > prefer this ticket to be cherry-picket to 2.8.1 yourself or should I merge > it to the release branch? > > пт, 17 апр. 2020 г. в 16:55, Ivan Pavlukhin : > >> Great! >> >> Best regards, >> Ivan Pavlukhin >> >> пт, 17 апр. 2020 г. в 12:48, Nikolay Izhikov : >>> >>> OK, let’s try it >>> I do not know who is a manager for 2.8.1. >>> >>> I am. >>> >>> 17 апр. 2020 г., в 12:42, Ivan Pavlukhin >> написал(а): > We didn’t it for the previous releases. > Why we should start to do it?) Because it seems to be a good thing, is not it? I suppose it is important to know who is a release manager (the current thread subject has a "Manager" keyword). E.g. I do not know who is a manager for 2.8.1. Best regards, Ivan Pavlukhin пт, 17 апр. 2020 г. в 12:27, Nikolay Izhikov : > > Hello, > >> Should not we reflect on the release page [1] who is a release >> manager? > > We didn’t it for the previous releases. > Why we should start to do it?) > >> I suggest to include these fixes into 2.8.1 release: > > Thanks, included. > > > >> 17 апр. 2020 г., в 12:20, Ivan Rakov >> написал(а): >> >> Hi, >> >> I suggest to include these fixes into 2.8.1 release: >> https://issues.apache.org/jira/browse/IGNITE-12101 >> https://issues.apache.org/jira/browse/IGNITE-12651 >> >> On Fri, Apr 17, 2020 at 11:32 AM Ivan Pavlukhin >> wrote: >> >>> Hi folks, >>> >>> A side note from an external spectator. Should not we reflect on the >>> release page [1] who is a release manager? >>> >>> [1] >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 >>> >>> Best regards, >>> Ivan Pavlukhin >>> >>> пт, 17 апр. 2020 г. в 11:11, Nikolay Izhikov : Hello, Igniters. I’ve added all tickets proposed in this thread to 2.8.1 scope [1] For now we have 61 resolved tickets. 19 unresolved tickets. [1] >>> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > 17 апр. 2020 г., в 01:38, Alex Plehanov >>> написал(а): > > Hello guys, > > I propose to cherry-pick to 2.8.1 following bug-fixes too, which >> are > already in master: > Scan query over an evicted partition can cause node failure >>> (IGNITE-12734 > [1]) > Java thin client: There were problems with deserialization of some >>> types on > the client-side, these types can't be used (IGNITE-12624 > [2], IGNITE-12468 [3]) > Java thin client: Thread doesn't stop properly on client close >> when > partition awareness is enabled, this prevents main() method from >>> exiting > (IGNITE-12743 [4]) > > Also, there is a performance fix for checkpoint read lock, which I >>> propose > to cherry-pick too (IGNITE-12491 [5]). This fix brings significant > performance boost on environments with a large number of CPUs >> (there >>> was > some drop on such environments introduced in 2.8.0 for all >>> transactional > operations after IGNITE-12593 fixing) > > WDYT? > > [1]: https://issues.apache.org/jira/browse/IGNITE-12734 > [2]: https://issues.apache.org/jira/browse/IGNITE-12624 > [3]: https://issues.apache.org/jira/browse/IGNITE-12468 > [4]: https://issues.apache.org/jira/browse/IGNITE-12743 > [5]: https://issues.apache.org/jira/browse/IGNITE-12491 > > чт, 16 апр. 2020 г. в 18:48, Maxim Muzafarov : > >> Nikolay, >> >> Probably, we should not wait for all blocker issues in minor >> bug-fix >> releases except very special cases. I think we should release all >> accumulated bug-fixes `as is` and schedule the next 2.8.2 >> release. >> This will allow as to have shorten minor releases. >> >> On Thu, 16 Apr 2020 at 18:17, Nikolay Izhikov < >> nizhi...@apache.org> >>> wrote: >>> >>> Hello, Igniters. >>> >>> I’m started to work on this 2.8.1 release [1] >>> >>> Resolved issues for release(28) - [2] >>> Unresolved issues for release(30) - [3] >>> >>> My next step: >>> >>> 1. I want to double-check that all commits for the tickets with >> the >> fixVersion=2.8.1 presented in corresponding release branch. >>>
Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]
Nikolay, If I merge a ticket that is already targeted for 2.8.1 to master, do you prefer this ticket to be cherry-picket to 2.8.1 yourself or should I merge it to the release branch? пт, 17 апр. 2020 г. в 16:55, Ivan Pavlukhin : > Great! > > Best regards, > Ivan Pavlukhin > > пт, 17 апр. 2020 г. в 12:48, Nikolay Izhikov : > > > > OK, let’s try it > > > > > I do not know who is a manager for 2.8.1. > > > > I am. > > > > > > > 17 апр. 2020 г., в 12:42, Ivan Pavlukhin > написал(а): > > > > > >> We didn’t it for the previous releases. > > >> Why we should start to do it?) > > > > > > Because it seems to be a good thing, is not it? I suppose it is > > > important to know who is a release manager (the current thread subject > > > has a "Manager" keyword). E.g. I do not know who is a manager for > > > 2.8.1. > > > > > > Best regards, > > > Ivan Pavlukhin > > > > > > пт, 17 апр. 2020 г. в 12:27, Nikolay Izhikov : > > >> > > >> Hello, > > >> > > >>> Should not we reflect on the release page [1] who is a release > manager? > > >> > > >> We didn’t it for the previous releases. > > >> Why we should start to do it?) > > >> > > >>> I suggest to include these fixes into 2.8.1 release: > > >> > > >> Thanks, included. > > >> > > >> > > >> > > >>> 17 апр. 2020 г., в 12:20, Ivan Rakov > написал(а): > > >>> > > >>> Hi, > > >>> > > >>> I suggest to include these fixes into 2.8.1 release: > > >>> https://issues.apache.org/jira/browse/IGNITE-12101 > > >>> https://issues.apache.org/jira/browse/IGNITE-12651 > > >>> > > >>> On Fri, Apr 17, 2020 at 11:32 AM Ivan Pavlukhin > wrote: > > >>> > > Hi folks, > > > > A side note from an external spectator. Should not we reflect on the > > release page [1] who is a release manager? > > > > [1] > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > > > > Best regards, > > Ivan Pavlukhin > > > > пт, 17 апр. 2020 г. в 11:11, Nikolay Izhikov : > > > > > > Hello, Igniters. > > > > > > I’ve added all tickets proposed in this thread to 2.8.1 scope [1] > > > For now we have > > > > > > 61 resolved tickets. > > > 19 unresolved tickets. > > > > > > > > > > > > [1] > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > > > > > >> 17 апр. 2020 г., в 01:38, Alex Plehanov > > написал(а): > > >> > > >> Hello guys, > > >> > > >> I propose to cherry-pick to 2.8.1 following bug-fixes too, which > are > > >> already in master: > > >> Scan query over an evicted partition can cause node failure > > (IGNITE-12734 > > >> [1]) > > >> Java thin client: There were problems with deserialization of some > > types on > > >> the client-side, these types can't be used (IGNITE-12624 > > >> [2], IGNITE-12468 [3]) > > >> Java thin client: Thread doesn't stop properly on client close > when > > >> partition awareness is enabled, this prevents main() method from > > exiting > > >> (IGNITE-12743 [4]) > > >> > > >> Also, there is a performance fix for checkpoint read lock, which I > > propose > > >> to cherry-pick too (IGNITE-12491 [5]). This fix brings significant > > >> performance boost on environments with a large number of CPUs > (there > > was > > >> some drop on such environments introduced in 2.8.0 for all > > transactional > > >> operations after IGNITE-12593 fixing) > > >> > > >> WDYT? > > >> > > >> [1]: https://issues.apache.org/jira/browse/IGNITE-12734 > > >> [2]: https://issues.apache.org/jira/browse/IGNITE-12624 > > >> [3]: https://issues.apache.org/jira/browse/IGNITE-12468 > > >> [4]: https://issues.apache.org/jira/browse/IGNITE-12743 > > >> [5]: https://issues.apache.org/jira/browse/IGNITE-12491 > > >> > > >> чт, 16 апр. 2020 г. в 18:48, Maxim Muzafarov : > > >> > > >>> Nikolay, > > >>> > > >>> Probably, we should not wait for all blocker issues in minor > bug-fix > > >>> releases except very special cases. I think we should release all > > >>> accumulated bug-fixes `as is` and schedule the next 2.8.2 > release. > > >>> This will allow as to have shorten minor releases. > > >>> > > >>> On Thu, 16 Apr 2020 at 18:17, Nikolay Izhikov < > nizhi...@apache.org> > > wrote: > > > > Hello, Igniters. > > > > I’m started to work on this 2.8.1 release [1] > > > > Resolved issues for release(28) - [2] > > Unresolved issues for release(30) - [3] > > > > My next step: > > > > 1. I want to double-check that all commits for the tickets with > the > > >>> fixVersion=2.8.1 presented in corresponding release branch. > > And cherry-pick losted changes. > > > > 2. I want to reduce the scope of the release and exclude tickets > > that is > > >>>
Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]
Great! Best regards, Ivan Pavlukhin пт, 17 апр. 2020 г. в 12:48, Nikolay Izhikov : > > OK, let’s try it > > > I do not know who is a manager for 2.8.1. > > I am. > > > > 17 апр. 2020 г., в 12:42, Ivan Pavlukhin написал(а): > > > >> We didn’t it for the previous releases. > >> Why we should start to do it?) > > > > Because it seems to be a good thing, is not it? I suppose it is > > important to know who is a release manager (the current thread subject > > has a "Manager" keyword). E.g. I do not know who is a manager for > > 2.8.1. > > > > Best regards, > > Ivan Pavlukhin > > > > пт, 17 апр. 2020 г. в 12:27, Nikolay Izhikov : > >> > >> Hello, > >> > >>> Should not we reflect on the release page [1] who is a release manager? > >> > >> We didn’t it for the previous releases. > >> Why we should start to do it?) > >> > >>> I suggest to include these fixes into 2.8.1 release: > >> > >> Thanks, included. > >> > >> > >> > >>> 17 апр. 2020 г., в 12:20, Ivan Rakov написал(а): > >>> > >>> Hi, > >>> > >>> I suggest to include these fixes into 2.8.1 release: > >>> https://issues.apache.org/jira/browse/IGNITE-12101 > >>> https://issues.apache.org/jira/browse/IGNITE-12651 > >>> > >>> On Fri, Apr 17, 2020 at 11:32 AM Ivan Pavlukhin > >>> wrote: > >>> > Hi folks, > > A side note from an external spectator. Should not we reflect on the > release page [1] who is a release manager? > > [1] > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > > Best regards, > Ivan Pavlukhin > > пт, 17 апр. 2020 г. в 11:11, Nikolay Izhikov : > > > > Hello, Igniters. > > > > I’ve added all tickets proposed in this thread to 2.8.1 scope [1] > > For now we have > > > > 61 resolved tickets. > > 19 unresolved tickets. > > > > > > > > [1] > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > > > >> 17 апр. 2020 г., в 01:38, Alex Plehanov > написал(а): > >> > >> Hello guys, > >> > >> I propose to cherry-pick to 2.8.1 following bug-fixes too, which are > >> already in master: > >> Scan query over an evicted partition can cause node failure > (IGNITE-12734 > >> [1]) > >> Java thin client: There were problems with deserialization of some > types on > >> the client-side, these types can't be used (IGNITE-12624 > >> [2], IGNITE-12468 [3]) > >> Java thin client: Thread doesn't stop properly on client close when > >> partition awareness is enabled, this prevents main() method from > exiting > >> (IGNITE-12743 [4]) > >> > >> Also, there is a performance fix for checkpoint read lock, which I > propose > >> to cherry-pick too (IGNITE-12491 [5]). This fix brings significant > >> performance boost on environments with a large number of CPUs (there > was > >> some drop on such environments introduced in 2.8.0 for all > transactional > >> operations after IGNITE-12593 fixing) > >> > >> WDYT? > >> > >> [1]: https://issues.apache.org/jira/browse/IGNITE-12734 > >> [2]: https://issues.apache.org/jira/browse/IGNITE-12624 > >> [3]: https://issues.apache.org/jira/browse/IGNITE-12468 > >> [4]: https://issues.apache.org/jira/browse/IGNITE-12743 > >> [5]: https://issues.apache.org/jira/browse/IGNITE-12491 > >> > >> чт, 16 апр. 2020 г. в 18:48, Maxim Muzafarov : > >> > >>> Nikolay, > >>> > >>> Probably, we should not wait for all blocker issues in minor bug-fix > >>> releases except very special cases. I think we should release all > >>> accumulated bug-fixes `as is` and schedule the next 2.8.2 release. > >>> This will allow as to have shorten minor releases. > >>> > >>> On Thu, 16 Apr 2020 at 18:17, Nikolay Izhikov > wrote: > > Hello, Igniters. > > I’m started to work on this 2.8.1 release [1] > > Resolved issues for release(28) - [2] > Unresolved issues for release(30) - [3] > > My next step: > > 1. I want to double-check that all commits for the tickets with the > >>> fixVersion=2.8.1 presented in corresponding release branch. > And cherry-pick losted changes. > > 2. I want to reduce the scope of the release and exclude tickets > that is > >>> not ready for now. > > As you may know, 2.8.1 is a bug fix release. > Therefore, I think we can wait only for a blocker issues. > > What do you think? > > [1] > >>> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > [2] > >>> > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.8.1%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20
[jira] [Created] (IGNITE-12910) SqlViewExporterSpi uses log method which must not be used in production code
Andrey N. Gura created IGNITE-12910:
---
Summary: SqlViewExporterSpi uses log method which must not be used
in production code
Key: IGNITE-12910
URL: https://issues.apache.org/jira/browse/IGNITE-12910
Project: Ignite
Issue Type: Bug
Affects Versions: 2.8
Reporter: Andrey N. Gura
Fix For: 2.8.1
{{SqlViewExporterSpi.register()}} method uses IgniteUtils.debug() method that
log on INFO level instead of DEBUG because it needs only for debug purposes.
Should be replaced by explicit log.debug() invocation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]
OK, let’s try it > I do not know who is a manager for 2.8.1. I am. > 17 апр. 2020 г., в 12:42, Ivan Pavlukhin написал(а): > >> We didn’t it for the previous releases. >> Why we should start to do it?) > > Because it seems to be a good thing, is not it? I suppose it is > important to know who is a release manager (the current thread subject > has a "Manager" keyword). E.g. I do not know who is a manager for > 2.8.1. > > Best regards, > Ivan Pavlukhin > > пт, 17 апр. 2020 г. в 12:27, Nikolay Izhikov : >> >> Hello, >> >>> Should not we reflect on the release page [1] who is a release manager? >> >> We didn’t it for the previous releases. >> Why we should start to do it?) >> >>> I suggest to include these fixes into 2.8.1 release: >> >> Thanks, included. >> >> >> >>> 17 апр. 2020 г., в 12:20, Ivan Rakov написал(а): >>> >>> Hi, >>> >>> I suggest to include these fixes into 2.8.1 release: >>> https://issues.apache.org/jira/browse/IGNITE-12101 >>> https://issues.apache.org/jira/browse/IGNITE-12651 >>> >>> On Fri, Apr 17, 2020 at 11:32 AM Ivan Pavlukhin wrote: >>> Hi folks, A side note from an external spectator. Should not we reflect on the release page [1] who is a release manager? [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 Best regards, Ivan Pavlukhin пт, 17 апр. 2020 г. в 11:11, Nikolay Izhikov : > > Hello, Igniters. > > I’ve added all tickets proposed in this thread to 2.8.1 scope [1] > For now we have > > 61 resolved tickets. > 19 unresolved tickets. > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > >> 17 апр. 2020 г., в 01:38, Alex Plehanov написал(а): >> >> Hello guys, >> >> I propose to cherry-pick to 2.8.1 following bug-fixes too, which are >> already in master: >> Scan query over an evicted partition can cause node failure (IGNITE-12734 >> [1]) >> Java thin client: There were problems with deserialization of some types on >> the client-side, these types can't be used (IGNITE-12624 >> [2], IGNITE-12468 [3]) >> Java thin client: Thread doesn't stop properly on client close when >> partition awareness is enabled, this prevents main() method from exiting >> (IGNITE-12743 [4]) >> >> Also, there is a performance fix for checkpoint read lock, which I propose >> to cherry-pick too (IGNITE-12491 [5]). This fix brings significant >> performance boost on environments with a large number of CPUs (there was >> some drop on such environments introduced in 2.8.0 for all transactional >> operations after IGNITE-12593 fixing) >> >> WDYT? >> >> [1]: https://issues.apache.org/jira/browse/IGNITE-12734 >> [2]: https://issues.apache.org/jira/browse/IGNITE-12624 >> [3]: https://issues.apache.org/jira/browse/IGNITE-12468 >> [4]: https://issues.apache.org/jira/browse/IGNITE-12743 >> [5]: https://issues.apache.org/jira/browse/IGNITE-12491 >> >> чт, 16 апр. 2020 г. в 18:48, Maxim Muzafarov : >> >>> Nikolay, >>> >>> Probably, we should not wait for all blocker issues in minor bug-fix >>> releases except very special cases. I think we should release all >>> accumulated bug-fixes `as is` and schedule the next 2.8.2 release. >>> This will allow as to have shorten minor releases. >>> >>> On Thu, 16 Apr 2020 at 18:17, Nikolay Izhikov wrote: Hello, Igniters. I’m started to work on this 2.8.1 release [1] Resolved issues for release(28) - [2] Unresolved issues for release(30) - [3] My next step: 1. I want to double-check that all commits for the tickets with the >>> fixVersion=2.8.1 presented in corresponding release branch. And cherry-pick losted changes. 2. I want to reduce the scope of the release and exclude tickets that is >>> not ready for now. As you may know, 2.8.1 is a bug fix release. Therefore, I think we can wait only for a blocker issues. What do you think? [1] >>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 [2] >>> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.8.1%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20 [3] >>> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.8.1%27))%20AND%2
Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]
> We didn’t it for the previous releases. > Why we should start to do it?) Because it seems to be a good thing, is not it? I suppose it is important to know who is a release manager (the current thread subject has a "Manager" keyword). E.g. I do not know who is a manager for 2.8.1. Best regards, Ivan Pavlukhin пт, 17 апр. 2020 г. в 12:27, Nikolay Izhikov : > > Hello, > > > Should not we reflect on the release page [1] who is a release manager? > > We didn’t it for the previous releases. > Why we should start to do it?) > > > I suggest to include these fixes into 2.8.1 release: > > Thanks, included. > > > > > 17 апр. 2020 г., в 12:20, Ivan Rakov написал(а): > > > > Hi, > > > > I suggest to include these fixes into 2.8.1 release: > > https://issues.apache.org/jira/browse/IGNITE-12101 > > https://issues.apache.org/jira/browse/IGNITE-12651 > > > > On Fri, Apr 17, 2020 at 11:32 AM Ivan Pavlukhin wrote: > > > >> Hi folks, > >> > >> A side note from an external spectator. Should not we reflect on the > >> release page [1] who is a release manager? > >> > >> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > >> > >> Best regards, > >> Ivan Pavlukhin > >> > >> пт, 17 апр. 2020 г. в 11:11, Nikolay Izhikov : > >>> > >>> Hello, Igniters. > >>> > >>> I’ve added all tickets proposed in this thread to 2.8.1 scope [1] > >>> For now we have > >>> > >>> 61 resolved tickets. > >>> 19 unresolved tickets. > >>> > >>> > >>> > >>> [1] > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > >>> > 17 апр. 2020 г., в 01:38, Alex Plehanov > >> написал(а): > > Hello guys, > > I propose to cherry-pick to 2.8.1 following bug-fixes too, which are > already in master: > Scan query over an evicted partition can cause node failure > >> (IGNITE-12734 > [1]) > Java thin client: There were problems with deserialization of some > >> types on > the client-side, these types can't be used (IGNITE-12624 > [2], IGNITE-12468 [3]) > Java thin client: Thread doesn't stop properly on client close when > partition awareness is enabled, this prevents main() method from > >> exiting > (IGNITE-12743 [4]) > > Also, there is a performance fix for checkpoint read lock, which I > >> propose > to cherry-pick too (IGNITE-12491 [5]). This fix brings significant > performance boost on environments with a large number of CPUs (there > >> was > some drop on such environments introduced in 2.8.0 for all > >> transactional > operations after IGNITE-12593 fixing) > > WDYT? > > [1]: https://issues.apache.org/jira/browse/IGNITE-12734 > [2]: https://issues.apache.org/jira/browse/IGNITE-12624 > [3]: https://issues.apache.org/jira/browse/IGNITE-12468 > [4]: https://issues.apache.org/jira/browse/IGNITE-12743 > [5]: https://issues.apache.org/jira/browse/IGNITE-12491 > > чт, 16 апр. 2020 г. в 18:48, Maxim Muzafarov : > > > Nikolay, > > > > Probably, we should not wait for all blocker issues in minor bug-fix > > releases except very special cases. I think we should release all > > accumulated bug-fixes `as is` and schedule the next 2.8.2 release. > > This will allow as to have shorten minor releases. > > > > On Thu, 16 Apr 2020 at 18:17, Nikolay Izhikov > >> wrote: > >> > >> Hello, Igniters. > >> > >> I’m started to work on this 2.8.1 release [1] > >> > >> Resolved issues for release(28) - [2] > >> Unresolved issues for release(30) - [3] > >> > >> My next step: > >> > >> 1. I want to double-check that all commits for the tickets with the > > fixVersion=2.8.1 presented in corresponding release branch. > >> And cherry-pick losted changes. > >> > >> 2. I want to reduce the scope of the release and exclude tickets > >> that is > > not ready for now. > >> > >> As you may know, 2.8.1 is a bug fix release. > >> Therefore, I think we can wait only for a blocker issues. > >> > >> What do you think? > >> > >> [1] > > > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > >> [2] > > > >> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.8.1%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > >> [3] > > > >> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.8.1%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%2
Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]
Hello, > Should not we reflect on the release page [1] who is a release manager? We didn’t it for the previous releases. Why we should start to do it?) > I suggest to include these fixes into 2.8.1 release: Thanks, included. > 17 апр. 2020 г., в 12:20, Ivan Rakov написал(а): > > Hi, > > I suggest to include these fixes into 2.8.1 release: > https://issues.apache.org/jira/browse/IGNITE-12101 > https://issues.apache.org/jira/browse/IGNITE-12651 > > On Fri, Apr 17, 2020 at 11:32 AM Ivan Pavlukhin wrote: > >> Hi folks, >> >> A side note from an external spectator. Should not we reflect on the >> release page [1] who is a release manager? >> >> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 >> >> Best regards, >> Ivan Pavlukhin >> >> пт, 17 апр. 2020 г. в 11:11, Nikolay Izhikov : >>> >>> Hello, Igniters. >>> >>> I’ve added all tickets proposed in this thread to 2.8.1 scope [1] >>> For now we have >>> >>> 61 resolved tickets. >>> 19 unresolved tickets. >>> >>> >>> >>> [1] >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 >>> 17 апр. 2020 г., в 01:38, Alex Plehanov >> написал(а): Hello guys, I propose to cherry-pick to 2.8.1 following bug-fixes too, which are already in master: Scan query over an evicted partition can cause node failure >> (IGNITE-12734 [1]) Java thin client: There were problems with deserialization of some >> types on the client-side, these types can't be used (IGNITE-12624 [2], IGNITE-12468 [3]) Java thin client: Thread doesn't stop properly on client close when partition awareness is enabled, this prevents main() method from >> exiting (IGNITE-12743 [4]) Also, there is a performance fix for checkpoint read lock, which I >> propose to cherry-pick too (IGNITE-12491 [5]). This fix brings significant performance boost on environments with a large number of CPUs (there >> was some drop on such environments introduced in 2.8.0 for all >> transactional operations after IGNITE-12593 fixing) WDYT? [1]: https://issues.apache.org/jira/browse/IGNITE-12734 [2]: https://issues.apache.org/jira/browse/IGNITE-12624 [3]: https://issues.apache.org/jira/browse/IGNITE-12468 [4]: https://issues.apache.org/jira/browse/IGNITE-12743 [5]: https://issues.apache.org/jira/browse/IGNITE-12491 чт, 16 апр. 2020 г. в 18:48, Maxim Muzafarov : > Nikolay, > > Probably, we should not wait for all blocker issues in minor bug-fix > releases except very special cases. I think we should release all > accumulated bug-fixes `as is` and schedule the next 2.8.2 release. > This will allow as to have shorten minor releases. > > On Thu, 16 Apr 2020 at 18:17, Nikolay Izhikov >> wrote: >> >> Hello, Igniters. >> >> I’m started to work on this 2.8.1 release [1] >> >> Resolved issues for release(28) - [2] >> Unresolved issues for release(30) - [3] >> >> My next step: >> >> 1. I want to double-check that all commits for the tickets with the > fixVersion=2.8.1 presented in corresponding release branch. >> And cherry-pick losted changes. >> >> 2. I want to reduce the scope of the release and exclude tickets >> that is > not ready for now. >> >> As you may know, 2.8.1 is a bug fix release. >> Therefore, I think we can wait only for a blocker issues. >> >> What do you think? >> >> [1] > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 >> [2] > >> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.8.1%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20 >> [3] > >> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.8.1%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20 >> >> >>> 8 апр. 2020 г., в 20:15, Вячеслав Коптилин < >> slava.kopti...@gmail.com> > написал(а): >>> >>> Folks, >>> >>> I'd like to add ticket IGNITE-12805 "NullPointerException on node > restart >>> when 3rd party persistence and Ignite native persistence are used" >> to >>> ignite-2.8.1 scope. >>> >>> [1] https://issues.apache.org/jira/browse/IGNITE-12805 >>> >>> Thanks, >>> S. >>> >>> вт, 7 апр. 2020 г. в 19:57, Ilya Kasnacheev < >> ilya.kasnach...@gmail.com >> : >>>
Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]
Hi, I suggest to include these fixes into 2.8.1 release: https://issues.apache.org/jira/browse/IGNITE-12101 https://issues.apache.org/jira/browse/IGNITE-12651 On Fri, Apr 17, 2020 at 11:32 AM Ivan Pavlukhin wrote: > Hi folks, > > A side note from an external spectator. Should not we reflect on the > release page [1] who is a release manager? > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > > Best regards, > Ivan Pavlukhin > > пт, 17 апр. 2020 г. в 11:11, Nikolay Izhikov : > > > > Hello, Igniters. > > > > I’ve added all tickets proposed in this thread to 2.8.1 scope [1] > > For now we have > > > > 61 resolved tickets. > > 19 unresolved tickets. > > > > > > > > [1] > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > > > > > 17 апр. 2020 г., в 01:38, Alex Plehanov > написал(а): > > > > > > Hello guys, > > > > > > I propose to cherry-pick to 2.8.1 following bug-fixes too, which are > > > already in master: > > > Scan query over an evicted partition can cause node failure > (IGNITE-12734 > > > [1]) > > > Java thin client: There were problems with deserialization of some > types on > > > the client-side, these types can't be used (IGNITE-12624 > > > [2], IGNITE-12468 [3]) > > > Java thin client: Thread doesn't stop properly on client close when > > > partition awareness is enabled, this prevents main() method from > exiting > > > (IGNITE-12743 [4]) > > > > > > Also, there is a performance fix for checkpoint read lock, which I > propose > > > to cherry-pick too (IGNITE-12491 [5]). This fix brings significant > > > performance boost on environments with a large number of CPUs (there > was > > > some drop on such environments introduced in 2.8.0 for all > transactional > > > operations after IGNITE-12593 fixing) > > > > > > WDYT? > > > > > > [1]: https://issues.apache.org/jira/browse/IGNITE-12734 > > > [2]: https://issues.apache.org/jira/browse/IGNITE-12624 > > > [3]: https://issues.apache.org/jira/browse/IGNITE-12468 > > > [4]: https://issues.apache.org/jira/browse/IGNITE-12743 > > > [5]: https://issues.apache.org/jira/browse/IGNITE-12491 > > > > > > чт, 16 апр. 2020 г. в 18:48, Maxim Muzafarov : > > > > > >> Nikolay, > > >> > > >> Probably, we should not wait for all blocker issues in minor bug-fix > > >> releases except very special cases. I think we should release all > > >> accumulated bug-fixes `as is` and schedule the next 2.8.2 release. > > >> This will allow as to have shorten minor releases. > > >> > > >> On Thu, 16 Apr 2020 at 18:17, Nikolay Izhikov > wrote: > > >>> > > >>> Hello, Igniters. > > >>> > > >>> I’m started to work on this 2.8.1 release [1] > > >>> > > >>> Resolved issues for release(28) - [2] > > >>> Unresolved issues for release(30) - [3] > > >>> > > >>> My next step: > > >>> > > >>> 1. I want to double-check that all commits for the tickets with the > > >> fixVersion=2.8.1 presented in corresponding release branch. > > >>> And cherry-pick losted changes. > > >>> > > >>> 2. I want to reduce the scope of the release and exclude tickets > that is > > >> not ready for now. > > >>> > > >>> As you may know, 2.8.1 is a bug fix release. > > >>> Therefore, I think we can wait only for a blocker issues. > > >>> > > >>> What do you think? > > >>> > > >>> [1] > > >> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > > >>> [2] > > >> > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.8.1%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > > >>> [3] > > >> > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.8.1%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > > >>> > > >>> > > 8 апр. 2020 г., в 20:15, Вячеслав Коптилин < > slava.kopti...@gmail.com> > > >> написал(а): > > > > Folks, > > > > I'd like to add ticket IGNITE-12805 "NullPointerException on node > > >> restart > > when 3rd party persistence and Ignite native persistence are used" > to > > ignite-2.8.1 scope. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12805 > > > > Thanks, > > S. > > > > вт, 7 апр. 2020 г. в 19:57, Ilya Kasnacheev < > ilya.kasnach...@gmail.com > > >>> : > > > > > Hello! > > > > > > Done! > > > > > > Regards, > > > -- > > > Ilya Kasnacheev > > > > > > > > > вт, 7 апр. 2020 г. в 12:31, Sergey : > > > > > >> Hi, > > >> > > >> I'm proposing to add > > >> https://issues.apache.org/jira/bro
Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]
Hi folks, A side note from an external spectator. Should not we reflect on the release page [1] who is a release manager? [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 Best regards, Ivan Pavlukhin пт, 17 апр. 2020 г. в 11:11, Nikolay Izhikov : > > Hello, Igniters. > > I’ve added all tickets proposed in this thread to 2.8.1 scope [1] > For now we have > > 61 resolved tickets. > 19 unresolved tickets. > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > > > 17 апр. 2020 г., в 01:38, Alex Plehanov > > написал(а): > > > > Hello guys, > > > > I propose to cherry-pick to 2.8.1 following bug-fixes too, which are > > already in master: > > Scan query over an evicted partition can cause node failure (IGNITE-12734 > > [1]) > > Java thin client: There were problems with deserialization of some types on > > the client-side, these types can't be used (IGNITE-12624 > > [2], IGNITE-12468 [3]) > > Java thin client: Thread doesn't stop properly on client close when > > partition awareness is enabled, this prevents main() method from exiting > > (IGNITE-12743 [4]) > > > > Also, there is a performance fix for checkpoint read lock, which I propose > > to cherry-pick too (IGNITE-12491 [5]). This fix brings significant > > performance boost on environments with a large number of CPUs (there was > > some drop on such environments introduced in 2.8.0 for all transactional > > operations after IGNITE-12593 fixing) > > > > WDYT? > > > > [1]: https://issues.apache.org/jira/browse/IGNITE-12734 > > [2]: https://issues.apache.org/jira/browse/IGNITE-12624 > > [3]: https://issues.apache.org/jira/browse/IGNITE-12468 > > [4]: https://issues.apache.org/jira/browse/IGNITE-12743 > > [5]: https://issues.apache.org/jira/browse/IGNITE-12491 > > > > чт, 16 апр. 2020 г. в 18:48, Maxim Muzafarov : > > > >> Nikolay, > >> > >> Probably, we should not wait for all blocker issues in minor bug-fix > >> releases except very special cases. I think we should release all > >> accumulated bug-fixes `as is` and schedule the next 2.8.2 release. > >> This will allow as to have shorten minor releases. > >> > >> On Thu, 16 Apr 2020 at 18:17, Nikolay Izhikov wrote: > >>> > >>> Hello, Igniters. > >>> > >>> I’m started to work on this 2.8.1 release [1] > >>> > >>> Resolved issues for release(28) - [2] > >>> Unresolved issues for release(30) - [3] > >>> > >>> My next step: > >>> > >>> 1. I want to double-check that all commits for the tickets with the > >> fixVersion=2.8.1 presented in corresponding release branch. > >>> And cherry-pick losted changes. > >>> > >>> 2. I want to reduce the scope of the release and exclude tickets that is > >> not ready for now. > >>> > >>> As you may know, 2.8.1 is a bug fix release. > >>> Therefore, I think we can wait only for a blocker issues. > >>> > >>> What do you think? > >>> > >>> [1] > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > >>> [2] > >> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.8.1%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > >>> [3] > >> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.8.1%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > >>> > >>> > 8 апр. 2020 г., в 20:15, Вячеслав Коптилин > >> написал(а): > > Folks, > > I'd like to add ticket IGNITE-12805 "NullPointerException on node > >> restart > when 3rd party persistence and Ignite native persistence are used" to > ignite-2.8.1 scope. > > [1] https://issues.apache.org/jira/browse/IGNITE-12805 > > Thanks, > S. > > вт, 7 апр. 2020 г. в 19:57, Ilya Kasnacheev >>> : > > > Hello! > > > > Done! > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > вт, 7 апр. 2020 г. в 12:31, Sergey : > > > >> Hi, > >> > >> I'm proposing to add > >> https://issues.apache.org/jira/browse/IGNITE-12549 (fix > >> iterators/scan > >> queries for replicated caches) > >> to 2.8.1. > >> > >> Best regards, > >> Sergey Kosarev. > >> > >> > >> вс, 5 апр. 2020 г. в 01:22, Saikat Maitra : > >> > >>> Hi, > >>> > >>> I observed that we already have release 2.8.1 branch > >>> https://github.com/apache/ignite/tree/ignite-2.8.1 > >>> > >>> In that case we should be ok to merge these 2 open PRs in master to > > make > >> it > >>> available for 2.9.0 release. > >>>
Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]
Hello, Igniters. I’ve added all tickets proposed in this thread to 2.8.1 scope [1] For now we have 61 resolved tickets. 19 unresolved tickets. [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > 17 апр. 2020 г., в 01:38, Alex Plehanov написал(а): > > Hello guys, > > I propose to cherry-pick to 2.8.1 following bug-fixes too, which are > already in master: > Scan query over an evicted partition can cause node failure (IGNITE-12734 > [1]) > Java thin client: There were problems with deserialization of some types on > the client-side, these types can't be used (IGNITE-12624 > [2], IGNITE-12468 [3]) > Java thin client: Thread doesn't stop properly on client close when > partition awareness is enabled, this prevents main() method from exiting > (IGNITE-12743 [4]) > > Also, there is a performance fix for checkpoint read lock, which I propose > to cherry-pick too (IGNITE-12491 [5]). This fix brings significant > performance boost on environments with a large number of CPUs (there was > some drop on such environments introduced in 2.8.0 for all transactional > operations after IGNITE-12593 fixing) > > WDYT? > > [1]: https://issues.apache.org/jira/browse/IGNITE-12734 > [2]: https://issues.apache.org/jira/browse/IGNITE-12624 > [3]: https://issues.apache.org/jira/browse/IGNITE-12468 > [4]: https://issues.apache.org/jira/browse/IGNITE-12743 > [5]: https://issues.apache.org/jira/browse/IGNITE-12491 > > чт, 16 апр. 2020 г. в 18:48, Maxim Muzafarov : > >> Nikolay, >> >> Probably, we should not wait for all blocker issues in minor bug-fix >> releases except very special cases. I think we should release all >> accumulated bug-fixes `as is` and schedule the next 2.8.2 release. >> This will allow as to have shorten minor releases. >> >> On Thu, 16 Apr 2020 at 18:17, Nikolay Izhikov wrote: >>> >>> Hello, Igniters. >>> >>> I’m started to work on this 2.8.1 release [1] >>> >>> Resolved issues for release(28) - [2] >>> Unresolved issues for release(30) - [3] >>> >>> My next step: >>> >>> 1. I want to double-check that all commits for the tickets with the >> fixVersion=2.8.1 presented in corresponding release branch. >>> And cherry-pick losted changes. >>> >>> 2. I want to reduce the scope of the release and exclude tickets that is >> not ready for now. >>> >>> As you may know, 2.8.1 is a bug fix release. >>> Therefore, I think we can wait only for a blocker issues. >>> >>> What do you think? >>> >>> [1] >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 >>> [2] >> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.8.1%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20 >>> [3] >> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.8.1%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20 >>> >>> 8 апр. 2020 г., в 20:15, Вячеслав Коптилин >> написал(а): Folks, I'd like to add ticket IGNITE-12805 "NullPointerException on node >> restart when 3rd party persistence and Ignite native persistence are used" to ignite-2.8.1 scope. [1] https://issues.apache.org/jira/browse/IGNITE-12805 Thanks, S. вт, 7 апр. 2020 г. в 19:57, Ilya Kasnacheev >> : > Hello! > > Done! > > Regards, > -- > Ilya Kasnacheev > > > вт, 7 апр. 2020 г. в 12:31, Sergey : > >> Hi, >> >> I'm proposing to add >> https://issues.apache.org/jira/browse/IGNITE-12549 (fix >> iterators/scan >> queries for replicated caches) >> to 2.8.1. >> >> Best regards, >> Sergey Kosarev. >> >> >> вс, 5 апр. 2020 г. в 01:22, Saikat Maitra : >> >>> Hi, >>> >>> I observed that we already have release 2.8.1 branch >>> https://github.com/apache/ignite/tree/ignite-2.8.1 >>> >>> In that case we should be ok to merge these 2 open PRs in master to > make >> it >>> available for 2.9.0 release. >>> >>> https://github.com/apache/ignite/pull/7240 >>> https://github.com/apache/ignite/pull/7227 >>> >>> Can you please review and confirm? >>> >>> Regards, >>> Saikat >>> >>> On Fri, Mar 20, 2020 at 8:19 AM Maxim Muzafarov >> wrote: >>> Igniters, I support Nikolay Izhikov as the release manager of 2.8.1 Apache Ignite release. Since no one else of committers, PMCs expressed a desire to lead this release I think
