Re: Ignite spring-session-ext release
Yes, I see sucessfull build with JDK 17: https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_SpringSession/8128400?buildTab=overview=false=false=false чт, 23 мая 2024 г. в 12:46, Ilya Shishkov : > > Hi, > Have you tested PR [1] on CI [2, 3]? > > 1. https://github.com/apache/ignite-extensions/pull/262 > 2. https://ci.ignite.apache.org/ > 3. https://ci2.ignite.apache.org/ > > чт, 23 мая 2024 г. в 09:45, Nusrat Shakarov : > > > > Thank you! > > > > чт, 23 мая 2024 г. в 06:17, Andrey Novikov : > > > > > It looks like only committers can prepare the release. > > > > > > I can be a release manager for these if nobody minds. > > > > > > On Wed, May 22, 2024 at 2:55 PM Nusrat Shakarov > > > wrote: > > > > > > > Hello! > > > > > > > > I want to release the spring-session-ext from Ignite Extensions. > > > > The main changes are: > > > > > > > >- StackOverflow issue fix > > > >- Spring 6 support > > > > > > > > > > > > Any objections? > > > > > > >
Re: Ignite spring-session-ext release
Hi, Have you tested PR [1] on CI [2, 3]? 1. https://github.com/apache/ignite-extensions/pull/262 2. https://ci.ignite.apache.org/ 3. https://ci2.ignite.apache.org/ чт, 23 мая 2024 г. в 09:45, Nusrat Shakarov : > > Thank you! > > чт, 23 мая 2024 г. в 06:17, Andrey Novikov : > > > It looks like only committers can prepare the release. > > > > I can be a release manager for these if nobody minds. > > > > On Wed, May 22, 2024 at 2:55 PM Nusrat Shakarov > > wrote: > > > > > Hello! > > > > > > I want to release the spring-session-ext from Ignite Extensions. > > > The main changes are: > > > > > >- StackOverflow issue fix > > >- Spring 6 support > > > > > > > > > Any objections? > > > > >
Re: New Apache Ignite PMC member: Nikita Amelchev
Congratulations, Nikita! ср, 22 нояб. 2023 г. в 14:53, Maksim Timonin : > > Congratulations! > > On Wed, Nov 22, 2023 at 2:29 PM Anton Vinogradov wrote: > > > Welcome aboard :) > > > > On Wed, Nov 22, 2023 at 2:11 PM Maxim Muzafarov wrote: > > > > > My congratulations, Nikita! > > > > > > On Tue, 21 Nov 2023 at 15:20, Dmitriy Pavlov wrote: > > > > > > > > Hello Igniters, > > > > > > > > The Project Management Committee (PMC) for Apache Ignite > > > > has invited Nikita Amelchev to become a member of PMC and we are > > pleased > > > > to announce that he has accepted. > > > > > > > > We appreciate his constant efforts in improving Apache Ignite code, as > > > well > > > > as efforts in preparing 2 major releases. > > > > > > > > A PMC member helps manage and guide the direction of the project. > > > > > > > > Congratulations on your new role! Keep the pace! > > > > > > > > Best Regards > > > > Dmitriy Pavlov > > > > on behalf of Apache Ignite PMC > > > > >
Re: [VOTE] Release Apache Ignite 2.15.0 RC0
+ 1
Started 2 node in-memory cluster: first node from binary distribution,
second one from debian package.
Started and successfully connected application, based on spring-data
extension examples, but with Ignite dependencies from the staging.
сб, 29 апр. 2023 г. в 10:17, Maxim Muzafarov :
>
> +1
>
> On Fri, 28 Apr 2023 at 09:54, Vladimir Steshin wrote:
> >
> > + 1
> >
> > 26.04.2023 22:51, Alex Plehanov пишет:
> > > Dear Community,
> > >
> > > The release candidate is ready.
> > >
> > > I have uploaded release candidate to
> > > https://dist.apache.org/repos/dist/dev/ignite/2.15.0-rc0/
> > > https://dist.apache.org/repos/dist/dev/ignite/packages_2.15.0-rc0/
> > >
> > > The following staging can be used for testing:
> > > https://repository.apache.org/content/repositories/orgapacheignite-1558/
> > >
> > > Tag name is 2.15.0-rc0:
> > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.15.0-rc0
> > >
> > > 2.15.0 most important changes:
> > > * Implemented incremental snapshots.
> > > * Java thin client improvements (logging, connections balancing, events
> > > listening, endpoints discovery)
> > > * Calcite based SQL engine improvements (memory quotas, index scans
> > > optimisations).
> > > * Reworked permission management for system tasks.
> > > * Removed deprecated functionality (daemon nodes, visorcmd, legacy JMX
> > > beans).
> > >
> > > RELEASE NOTES:
> > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.15
> > >
> > > Complete list of resolved issues:
> > > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20'Ignite'%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20('2.15'))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20('CLOSED'%2C%20'RESOLVED')%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
> > >
> > >
> > >
> > > DEVNOTES
> > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.15
> > >
> > > The vote is formal, see voting guidelines
> > > https://www.apache.org/foundation/
> > > voting.html
> > >
> > > +1 - to accept Apache Ignite 2.15.0-rc0
> > > 0 - don't care either way
> > > -1 - DO NOT accept Apache Ignite Ignite 2.15.0-rc0 (explain why)
> > >
> > > See notes on how to verify release here
> > > https://www.apache.org/info/verification.html
> > > and
> > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> > >
> > > This vote will be open till Tue May 2, 2023, 07:00 UTC.
> > > https://www.timeanddate.com/countdown/vote?iso=20230502T07=0=VOTE+on+the+Apache+Ignite+Release+2.15.0+RC0=sanserif
> > >
Re: [ANNOUNCE] Welcome Mikhail Petrov as a new Committer
Congratulations, Mikhail! пн, 14 нояб. 2022 г. в 11:36, Mikhail Petrov : > Thank you all. I appreciate it. > > On 11.11.2022 12:48, Anton Vinogradov wrote: > > Great news! > > Welcome aboard > > > > On Fri, Nov 11, 2022 at 12:03 PM Nikita Amelchev > > wrote: > > > >> My congratulations, Mikhail! > >> > >> пт, 11 нояб. 2022 г. в 11:55, Maksim Timonin : > >>> Hi Mikhail! Congratulations! > >>> > >>> On Fri, Nov 11, 2022 at 11:30 AM Vladimir Steshin > >>> wrote: > >>> > Mikhail, congratulations! > > 11.11.2022 11:20, Maxim Muzafarov пишет: > > The Project Management Committee (PMC) for Apache Ignite has invited > > Mikhail Petrov to become a committer and we are pleased to announce > > that they have accepted. > > > > Mikhail Petrov is an active contributor and community member, he made > > significant additions to Ignite and Ignite Extensions code bases, > >> this > > client support for Spring Data, Spring Transactions, tracing of SQL > > queries etc. > > > > Being a committer enables easier contribution to the project since > > there is no need to go via the patch submission process. This should > > enable better productivity. > > > > Please join in welcoming Mikhail Petrov, and congratulating him on > >> the > > new role in the Apache Ignite Community! > > > > > > Best Regards, > > Maxim Muzafarov > > on behalf of Apache Ignite PMC > >> > >> > >> -- > >> Best wishes, > >> Amelchev Nikita > >> >
Re: [VOTE] Release pyignite 0.6.0.rc1
Hi,
+1 from me.
Checked out pyignite-0.6.0.zip with
pyignite-0.6.0-cp310-cp310-win_amd64.whl:
1. Whl package installed via pip.
2. All examples tested (with supplied docker-compose.yml).
3. SHA512 hashes checked for both files (zip & whl).
вт, 15 нояб. 2022 г. в 09:58, Ivan Daschinsky :
> +1 (binding) Checked signature, hashsums, checked client on all 5 pythons
> on all available platforms (mac x86_64, ubuntu x86_84 and windows 10
> x86_64).
> Checked docs (readthedocs).
>
> вт, 15 нояб. 2022 г. в 09:10, Zhenya Stanilovsky
> >:
>
> >
> > +1, thanks Ivan !
> >
> >
> > >Dear Igniters!
> > >
> > >Release candidate binaries for subj are uploaded and ready for vote
> > >You can find them here:
> > >https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.6.0.rc1
> > >
> > >If you follow the link above, you will find source packages (*.zip)
> > >and binary packages (wheels) for windows (amd64), mac os x (amd64) and
> > >linux (x86_64)
> > >for pythons 37, 38, 39, 310 and 311. Also, there are sha512 and gpg
> > >signatures.
> > >Code signing keys can be found here --
> > >https://downloads.apache.org/ignite/KEYS
> > >Here you can find instructions how to verify packages
> > >https://www.apache.org/info/verification.html
> > >
> > >You can install binary package for specific version of python using pip
> > >For example do this on linux for python 3.8
> > >>> pip
> > >install
> >
> pyignite-0.6.0-cp38-cp38-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
> > >
> > >You can build and install package from source using this command:
> > >>> pip install pyignite-0.6.0.zip
> > >You can build wheel on your platform using this command:
> > >>> pip wheel --no-deps pyignite-0.6.0.zip
> > >
> > >For building C module, you should have python headers and C compiler
> > >installed.
> > >(i.e. for ubuntu sudo apt install build-essential python3-dev)
> > >In Mac OS X xcode-tools and python from homebrew are the best option.
> > >
> > >In order to check whether C module works, use following:
> > >>> from pyignite import _cutils
> > >>> print(_cutils.hashcode('test'))
> > >>> 3556498
> > >
> > >You can find documentation here:
> > >
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.6.0.rc1/
> > >
> > >You can find examples here (to check them, you should start ignite
> > locally):
> > >
> >
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.6.0.rc0/examples.html
> > >Also, examples can be found in source archive in examples subfolder.
> > >docker-compose.yml is supplied in order to start ignite quickly. (Use
> > >`docker-compose up -d` to start 3 nodes cluster and `docker-compose
> > >down` to shut down it)
> > >
> > >Release notes:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=995bda81780402116e89d76523949da88136f260
> > >
> > >Git release tag was created:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=tag;h=ea3f180a0300abf25c992ed8c241defdc2b4bd4b
> > >
> > >The vote is formal, see voting guidelines
> > >https://www.apache.org/foundation/voting.html
> > >
> > >+1 - to accept pyignite-0.6.0.rc0
> > >0 - don't care either way
> > >-1 - DO NOT accept pyignite-0.6.0.rc0
> > >
> > >The vote finishes at 11/15/2022 15:00 UTC
> >
> >
> >
> >
>
Re: [ANNOUNCE] New PMC member: Taras Ledkov
Congratulations, Taras! вс, 21 авг. 2022 г. в 09:52, Pavel Tupitsyn : > Congrats! > > Pavel > > On Sun, Aug 21, 2022 at 9:07 AM Ivan Pavlukhin > wrote: > > > Congratulations, Taras! > > > > Best regards, > > Ivan Pavlukhin > > > > сб, 20 авг. 2022 г. в 00:18, Dmitriy Pavlov : > > > > > > Hi Igniters! > > > > > > The Project Management Committee (PMC) for Apache Ignite has invited > > > Taras Ledkov to become a member of the PMC and we are pleased to > > > announce that he has accepted. > > > > > > Taras is a veteran committer, and it is needless to say how long > > > and successfully he is contributing to the Apache Ignite. > > > Taras is responsible for a solid bulk of SQL and JDBC code. > > > > > > Please join me in congratulating Taras on his new role. > > > > > > Best Regards, > > > Dmitriy Pavlov > > > on behalf of Apache Ignite PMC > > >
Re: [ANNOUNCE] New PMC member: Vyacheslav Koptilin
Congratulations, Slava! сб, 20 авг. 2022 г. в 00:20, Dmitriy Pavlov : > Congrats, Slava! Keep the pace! > > пт, 19 авг. 2022 г. в 12:45, Petr Ivanov : > > > Congrats! > > Well deserved! > > > > > On 17 Aug 2022, at 17:34, Kseniya Romanova > > wrote: > > > > > > Hi Igniters! > > > > > > The Project Management Committee (PMC) for Apache Ignite has invited > > > Vyacheslav Koptilin to become a member of the PMC and we are pleased to > > > announce that he has accepted. > > > > > > Vyacheslav is a veteran committer and contributes a lot to the Ignite > > > storage https://github.com/sk0x50. > > > > > > Please join me in congratulating Vyacheslav on his new role. > > > > > > Best Regards, > > > Kseniya Romanova > > > on behalf of Apache Ignite PMC > > > > >
Re: TeamCity #1: Problem with 'ZooKeeper (Discovery) 1'
Thanks a lot, Ivan! I have prepared a ticket [1] and will check suggested changes soon. 1. https://issues.apache.org/jira/browse/IGNITE-16793 пн, 4 апр. 2022 г. в 18:04, Ivan Daschinsky : > Seems that after update of zookeeper and curator, behaviour of testing > cluster have been slightly changed. I've tried to > increase zookeeper.electionPortBindRetry for testing zk ensemble > nodes and seems all issues are resolved now. > > пн, 4 апр. 2022 г. в 17:37, Ilya Shishkov : > > > Hi all, > > > > As I see TC#1 (ci.ignite.apache.org) experiences problems with > 'ZooKeeper > > (Discovery) 1' test suite execution (master branch). > > There are such errors in logs as below [1, 2]: > > [2022-04-04 03:37:09,971][ERROR][QuorumPeerListener][ServiceUtils] > > Exiting JVM with code 14 > > Process exited with code 14 > > > > I checked TC#2 (ci2.ignite.apache.org) and found out that the amount of > > test runs on TC2 [3, 4] is more than those on TC1 [5, 6]. And, BTW, > > there are no problems with exit code on TC#2. > > > > It seems to be an infrastructure problem, because as I understand, > > Zookeeper can't bind to a port. This line is from Zookeeper ExitCode > class > > [7]: > > /** Unable to bind to the quorum (election) port after multiple retry > > */ > > UNABLE_TO_BIND_QUORUM_PORT(14); > > > > Please, can anyone take a look at possible misconfiguration on TC#1? > > > > Links: > > 1. > > > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery1/6500597?showLog=6500597_230432_890.962.230567.230604=debug > > 2. > > > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery1/6501316?showLog=6501316_228931_890.962.228942=debug > > 4. > > > > > https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery1/6376069?buildTab=tests=classes > > 5 . > > > > > https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery1/6377319?buildTab=tests=classes > > > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery1/6500597?buildTab=tests=passed=classes > > 6. > > > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery1/6501316?buildTab=tests=classes=all > > 7. > > > > > https://github.com/apache/zookeeper/blob/master/zookeeper-server/src/main/java/org/apache/zookeeper/server/ExitCode.java#L51 > > > > > -- > Sincerely yours, Ivan Daschinskiy >
TeamCity #1: Problem with 'ZooKeeper (Discovery) 1'
Hi all, As I see TC#1 (ci.ignite.apache.org) experiences problems with 'ZooKeeper (Discovery) 1' test suite execution (master branch). There are such errors in logs as below [1, 2]: [2022-04-04 03:37:09,971][ERROR][QuorumPeerListener][ServiceUtils] Exiting JVM with code 14 Process exited with code 14 I checked TC#2 (ci2.ignite.apache.org) and found out that the amount of test runs on TC2 [3, 4] is more than those on TC1 [5, 6]. And, BTW, there are no problems with exit code on TC#2. It seems to be an infrastructure problem, because as I understand, Zookeeper can't bind to a port. This line is from Zookeeper ExitCode class [7]: /** Unable to bind to the quorum (election) port after multiple retry */ UNABLE_TO_BIND_QUORUM_PORT(14); Please, can anyone take a look at possible misconfiguration on TC#1? Links: 1. https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery1/6500597?showLog=6500597_230432_890.962.230567.230604=debug 2. https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery1/6501316?showLog=6501316_228931_890.962.228942=debug 4. https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery1/6376069?buildTab=tests=classes 5 . https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery1/6377319?buildTab=tests=classes https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery1/6500597?buildTab=tests=passed=classes 6. https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery1/6501316?buildTab=tests=classes=all 7. https://github.com/apache/zookeeper/blob/master/zookeeper-server/src/main/java/org/apache/zookeeper/server/ExitCode.java#L51
Re: Empty test report for 'Control-utility' and 'Zookeeper
Maxim, Ivan, thanks a lot for your help! чт, 31 мар. 2022 г. в 15:38, Maksim Timonin : > Igniters JFYI, > > I fixed this, but for the last month TC didn't run test suites for > Zookeeper, Control Utility. So, no stats for MTCGA for the master branch > for those suites. Then some of the flaky tests in those suites can appear > as blockers for a while (while statistics of flaky tests won't be built). > > > > On Mon, Mar 28, 2022 at 4:46 PM Ivan Daschinsky > wrote: > > > Great job Maxim! > > > > пн, 28 мар. 2022 г. в 15:51, Maksim Timonin : > > > > > Hi, guys! > > > > > > I investigated the issue. This is due to commit: fe95954c. It updated > the > > > curator-test version in the control-utility module (from 4.2.0 to > 5.2.0). > > > It led to changed transitive dependencies (jar-hell) of junit and tests > > > just don't start due to different junit version (5 instead of 4). > > > > > > I'll fix it today. > > > > > > On Mon, Mar 28, 2022 at 11:50 AM Ivan Daschinsky > > > wrote: > > > > > > > Problem was introduced in 2b74474b7220df046c5c6d7a12a23ba90a697025. > > Suite > > > > has not been run since that commit. > > > > > > > > чт, 24 мар. 2022 г. в 19:01, Shishkov Ilya : > > > > > > > > > Hi everyone, > > > > > > > > > > As I see, both 'Control Utility' and 'Control Utility (Zookeeper)' > > test > > > > > suites have empty test results and there are messages in a build > log > > as > > > > > below: > > > > > > > > > > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > > > > > > > > > > Above problem occurs both on TC1 and TC2 [1-4] for the master > branch, > > > but > > > > > does not on the 'ignite-2.12' [5-8]. > > > > > > > > > > Can anyone take a look, please? > > > > > > > > > > Links: > > > > > 1. > > > > > > > > > > > > > > > > > > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtility/6480112?showLog=6480112_1061_895 > > > > > 2. > > > > > > > > > > > > > > > > > > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtilityZookeeper/6480111?showLog=6480111_1060_894 > > > > > 3. > > > > > > > > > > > > > > > > > > > > https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtility/6359892?showRootCauses=true=6359892_1003_909 > > > > > 4. > > > > > > > > > > > > > > > > > > > > https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtilityZookeeper/6359893?showRootCauses=true=6359893_1003_909 > > > > > . > > > > > 5. > > > > > > > > > > > > > > > > > > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtility/6479329 > > > > > 6. > > > > > > > > > > > > > > > > > > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtilityZookeeper/6479328 > > > > > 7. > > > > > > > > > > > > > > > > > > > > https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtility/6359189?showRootCauses=true=true > > > > > 8. > > > > > > > > > > > > > > > > > > > > https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtilityZookeeper/6359190?showRootCauses=true=true > > > > > > > > > > > > > > > > > -- > > > > Sincerely yours, Ivan Daschinskiy > > > > > > > > > > > > > -- > > Sincerely yours, Ivan Daschinskiy > > >
[jira] [Created] (IGNITE-13809) Add SpringCache support for thin client
Ilya Shishkov created IGNITE-13809: -- Summary: Add SpringCache support for thin client Key: IGNITE-13809 URL: https://issues.apache.org/jira/browse/IGNITE-13809 Project: Ignite Issue Type: New Feature Components: spring, thin client Affects Versions: 2.10 Reporter: Ilya Shishkov It would be perfect, if we add this feature, because now it is supported only for client nodes, but not for thin clients. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13553) Node failure with ClassNotFoundException when indexed field of QueryEntity differs from type used in put operation
Ilya Shishkov created IGNITE-13553:
--
Summary: Node failure with ClassNotFoundException when indexed
field of QueryEntity differs from type used in put operation
Key: IGNITE-13553
URL: https://issues.apache.org/jira/browse/IGNITE-13553
Project: Ignite
Issue Type: Bug
Components: sql, thin client
Affects Versions: 2.8.1, 2.9, 2.10
Reporter: Ilya Shishkov
Failures occur under these conditions:
# Data classes are not present in server classpaths, peer-classloading is not
used because thin client is used.
# Manual construction of QueryEntity via #setFields, #setIndexes etc. is used
instead of constructor of QueryEntity in conjunction with @QuerySqlField for
data clases.
# One of the indexed fields of QueryEntity has type different from type of
corresponding field of data object instance, eg:
{code:java|title=QueryEntity}
fields.put("name", "java.lang.String");
fields.put("wrongTypeEmbeddable", "java.lang.String"); /* This is wrong type */
QueryEntity qryEntity = new QueryEntity()
.setKeyType("java.lang.Integer")
.setValueType("org.apache.ignite.wrongtype.WrongTypeEntity") /* FQDN
should be used */
.setFields(fields)
.setIndexes(Collections.singleton(
new QueryIndex("wrongTypeEmbeddable") /* Wrong type field is
indexed */));
{code}
{code:java|title=Embedded field type in put operation is different}
cache.put(0, new WrongTypeEntity("name",
new WrongTypeEmbeddable(256, "testField") /* wrongTypeEmbeddable field
*/));
{code}
How to reproduce:
# Start server nodes with default condig via ignite.sh
# Run reproducer:
For Apache Ignite 2.8.1 failures are identical for atomic and transactional
caches:
{code:java}
[17:45:23,108][SEVERE][sys-stripe-0-#1][] JVM will be halted immediately due to
the failure: [failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
o.a.i.binary.BinaryInvalidTypeException: o.a.i.wrongtype.WrongTypeEmbeddable]]
{code}
For AI, built and assemblied from master, failure is supressed for atomic and
occur only for transactional caches:
{code:java}
[17:39:09,305][SEVERE][sys-stripe-10-#11][] JVM will be halted immediately due
to the failure: [failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
o.a.i.i.transactions.IgniteTxHeuristicCheckedException: Committing a
transaction has produced runtime exception]]
{code}
Root cause for all failures is:
{code:java}
Caused by: java.lang.ClassNotFoundException:
org.apache.ignite.wrongtype.WrongTypeEmbeddable
{code}
Logs:
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12831) Invoking destroy of local cache on one node destroys local caches with the same name on all other nodes
Ilya Shishkov created IGNITE-12831: -- Summary: Invoking destroy of local cache on one node destroys local caches with the same name on all other nodes Key: IGNITE-12831 URL: https://issues.apache.org/jira/browse/IGNITE-12831 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.7.6, 2.8 Reporter: Ilya Shishkov Attachments: MyLocalCacheDestroyReproducer.java If you create caches with cache mode CacheMode.LOCAL and same name, but on different nodes, then all those caches will be destroyed after invoking destroy of cache on one of the cluster nodes. Expected behaviour: local cache should be destroyed only on the node invoking destroy. Reproducer in attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12454) Cache stop, destroy and clear status metrics
Ilya Shishkov created IGNITE-12454: -- Summary: Cache stop, destroy and clear status metrics Key: IGNITE-12454 URL: https://issues.apache.org/jira/browse/IGNITE-12454 Project: Ignite Issue Type: Improvement Components: cache Reporter: Ilya Shishkov In case of long lasting data removing processes, for example, stopping of big caches, particularly if highly uneven data distribution across partitions takes place, it would be perfect to have a tool, providing monitoring of cache data removal progress. I suppose, it should be metrics, representing status of caches stop, destroy and clear processes. This metrics should be available at least via JMX, and should be periodically printed into logs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
