Code Contribution Request - Kin (Nathan) Chan
Hello everyone, I hope you are having a good day. My name is Kin Chan, and I go by Nathan. I am writing this email to wonder if I have any chance to contribute my work to Ignite project. I am currently a Junior Software Developer in Minneapolis, MN, USA. I graduated from University of Minnesota as a Bachelor degree in computer science, and I focused on system. I have few years experience mainly using C and Java during my college and research, but I am with C# right now since it is the main language in my company. Currently I am trying to explore my career, and I found it interesting in the Ignite project at APACHE, especially on how it can help application run faster using the in-memory data grid. I have created a Jira account - nathanchan2020. I really I hope I can get involved into the project. Please let me know if there is anything I can help or provide. Thanks, Kin (Nathan) Chan
Re: [Micronaut] pubsub support
Hi Michael, Denis I did an initial review of the PR and wanted to share my thoughts. I observed that currently the implementation is using Ignite messaging apis and I am thinking if we should change the implementation to use Ignite data streaming apis. The reason for change is to ensure that it will be better aligned to Ignite 3.0 release as we are planning to deprecate Ignite Messaging apis in Ignite 3.0 [1] My recommendation to use Ignite data streaming apis is also due to the fact that we have multiple integration like Google Pub/Sub[2] and Kafka Streamer[3] that uses Data streaming apis for integration and it will keep micronaut implementation consistent with other extensions. Here is an example[4] of how Kafka Streamer can be used to stream data into Ignite nodes. [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0 [2] https://github.com/apache/ignite-extensions/blob/master/modules/pub-sub-ext/src/main/java/org/apache/ignite/stream/pubsub/PubSubStreamer.java [3] https://github.com/apache/ignite-extensions/blob/master/modules/kafka-ext/src/main/java/org/apache/ignite/stream/kafka/KafkaStreamer.java [4] https://github.com/samaitra/streamersk-extensions/blob/main/src/main/kotlin/com/example/streamerskextensions/kafka/KafkaStreamer.kt Please let me know your feedback. Regards, Saikat On Tue, Oct 27, 2020 at 12:48 PM Denis Magda wrote: > Michael, glad to see you back! > > Could you please explain in a few words what this integration does and what > it enables for Ignite and Micronaout? So that we are as a community are on > the same page. > > - > Denis > > > On Sun, Oct 25, 2020 at 3:05 PM Michael Pollind > wrote: > > > I've started to work on adding some basic pubsub support for > > Micronaut-ignite. I only have a draft PR in progress. There are a couple > > modules that already implement pub-sub so those modules would be a good > > start for reference: > > https://github.com/micronaut-projects/micronaut-gcp > > https://github.com/micronaut-projects/micronaut-kafka > > https://github.com/micronaut-projects/micronaut-mqtt > > > > https://github.com/micronaut-projects/micronaut-ignite/pull/62 > > > > > > >
[MTCGA]: new failures in builds [5693965] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New test failure in master IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-3517804902867109324=%3Cdefault%3E=testDetails Changes may lead to failure were done by - mirza aliev https://ci.ignite.apache.org/viewModification.html?modId=909181 - vladimir steshin https://ci.ignite.apache.org/viewModification.html?modId=909165 - andrey gura https://ci.ignite.apache.org/viewModification.html?modId=909184 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 02:11:17 28-10-2020
Re: [MTCGA]: new failures in builds [5695120] needs to be handled
Fixed (rearranged imports) вт, 27 окт. 2020 г. в 20:41, : > Hi Igniters, > > I've detected some new issue on TeamCity to be handled. You are more than > welcomed to help. > > If your changes can lead to this failure(s): We're grateful that you were > a volunteer to make the contribution to this project, but things change and > you may no longer be able to finalize your contribution. > Could you respond to this email and indicate if you wish to continue and > fix test failures or step down and some committer may revert you commit. > > *New Critical Failure in master ~Build Apache Ignite~ > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_BuildApacheIgnite?branch=%3Cdefault%3E > Changes may lead to failure were done by > - denis mekhanikov > https://ci.ignite.apache.org/viewModification.html?modId=909187 > > - Here's a reminder of what contributors were agreed to do > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > - Should you have any questions please contact > dev@ignite.apache.org > > Best Regards, > Apache Ignite TeamCity Bot > https://github.com/apache/ignite-teamcity-bot > Notification generated at 20:41:18 27-10-2020 >
Re: 2.9.1 release proposal
Hello, Agree with Pavel. On Tue, 27 Oct 2020 at 19:22, Pavel Tupitsyn wrote: > Igniters, > > I think we should plan 2.10 instead of 2.9.1. > ignite-2.9 branch was cut 4 months ago, a bunch of new features are waiting > to be released. > > On Tue, Oct 27, 2020 at 4:23 AM 18624049226 <18624049...@163.com> wrote: > > > Hello, > > > > I suggest that the remaining document issue in version 2.9.0 can be > > solved in version 2.9.1, and it is not a good practice to postpone to > > version 2.10. > > > > 在 2020/10/27 上午2:00, Maxim Muzafarov 写道: > > > Hello, > > > > > > +1 > > > Should we start the discussion about the release leader and release > > dates? > > > > > > On Tue, 20 Oct 2020 at 10:12, Anton Vinogradov wrote: > > >> +1 to start the 2.9.1 release process once as soon as 2.9 released. > > >> > > >> On Mon, Oct 19, 2020 at 8:49 PM Nikolay Izhikov > > wrote: > > >> > > >>> Hello, Yaroslav. > > >>> > > >>> I support the idea. > > >>> But, we should carefully work with the release scope. > > >>> > > >>> IGNITE-13477 - fix for a SQL tracing that will be available only in > > 2.10 > > >>> IGNITE-13427 - fix for a new system view that exists in master only, > we > > >>> need to include IGNITE-13409 > > >>> > > >>> Other tickets should be checked, also. > > >>> Is this a real fix of a released bug or we fix some issue we bring > with > > >>> the brand new contribution. > > >>> > > >>> > > >>> I propose to include the following tickets, also: > > >>> > > >>> CMD tools improvements: > > >>> > > >>> IGNITE-13488 - Command to print metric value > > >>> IGNITE-13426 - Command to print system view content > > >>> IGNITE-13422 - Parameter to explicitly enable experimental commands > > >>> > > >>> IGNITE-13380 - Output IgniteSystemProperties via ignite.sh > > >>> > > >>> New system views: > > >>> > > >>> IGNITE-13409 Metastorage and DistributedMetastorage viewы. > > >>> IGNITE-13408 BinaryMetadata view. > > >>> > > >>> > > 19 окт. 2020 г., в 18:20, Yaroslav Molochkov > > > >>> написал(а): > > Hello, Igniters! > > > > I've compiled a list of tickets that, i think, deserve to be > released > > in > > >>> a > > minor Ignite release (meaning in 2.9.1) after 2.9. Here they are: > > > > IGNITE-13569 > > disable archiving + walCompactionEnabled probably broke reading from > > wal > > >>> on > > server restart > > > > IGNITE-13418 > > Deadlock on multiple cache delete > > > > IGNITE-13563 > > Deserializing IBinaryObject containing an IBinaryObject field fails > > > > IGNITE-13575 > > Invalid blocking section in GridNioWorker and GridNioClientWorker > > leads > > >>> to > > false positive blocking thread detection > > > > IGNITE-13458 > > RebalancingPartitionsTotal metrics > > > > IGNITE-13536 > > .NET: Child processes become zombies when persistence is used with > > direct-io on Linux > > > > IGNITE-13500 > > Checkpoint read lock fail if it is taking under write lock during > the > > stopping node > > > > IGNITE-13431 > > NPE during Cassandra Store initialization with PRIMITIVE strategy > > > > IGNITE-13417 > > Cache Interceptors deserialization on client nodes > > > > IGNITE-13495 > > ZookeeperDiscoverySpiMBeanImpl#getCoordinator can return invalid > node > > as > > coordinator > > > > IGNITE-13479 > > Both ignite.sh and control.sh use the same JVM_OPTS. Control.sh > > doesn't > > start if JMX port was set > > > > IGNITE-11312 > > JDBC: Thin driver reports incorrect property names > > > > IGNITE-13462 > > .NET: Thin client Dispose hangs when continuous query is active on > > .NET > > Core 3.x > > > > IGNITE-13484 > > C++ odbc-example losing some values if run with 1 additional node > > > > IGNITE-13477 > > Fix NPE in SQL tracing implementation. > > > > IGNITE-13435 > > Fixing some unrecorded issues command warm-up control.sh > > > > IGNITE-13403 > > Update JDBC metadata to match actual capabilities > > > > IGNITE-13427 > > The local metastorage system view fails if unmarshallable values > > present > > > > IGNITE-13401 > > Unsupported protocol version exception when getting cache > > configuration > > from Java thin client > > > > IGNITE-13388 > > apache-ignite deb package depends on a non-existent package and > can't > > be > > installed on Debian 10 > > > > IGNITE-13397 > > NPE in logSupplierDone(UUID nodeId) > > > > IGNITE-13296 > > .NET: TransactionImpl finalizer can crash the process > > > > IGNITE-13382 > > DurableBackgroundTask can abandon incomplete task > > > > IGNITE-12509 > > CACHE_REBALANCE_STOPPED event raises for wrong caches in case of > > >>> specified > > RebalanceDelay > >
Re: [Micronaut] pubsub support
Michael, glad to see you back! Could you please explain in a few words what this integration does and what it enables for Ignite and Micronaout? So that we are as a community are on the same page. - Denis On Sun, Oct 25, 2020 at 3:05 PM Michael Pollind wrote: > I've started to work on adding some basic pubsub support for > Micronaut-ignite. I only have a draft PR in progress. There are a couple > modules that already implement pub-sub so those modules would be a good > start for reference: > https://github.com/micronaut-projects/micronaut-gcp > https://github.com/micronaut-projects/micronaut-kafka > https://github.com/micronaut-projects/micronaut-mqtt > > https://github.com/micronaut-projects/micronaut-ignite/pull/62 > > >
[MTCGA]: new failures in builds [5695120] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New Critical Failure in master ~Build Apache Ignite~ https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_BuildApacheIgnite?branch=%3Cdefault%3E Changes may lead to failure were done by - denis mekhanikov https://ci.ignite.apache.org/viewModification.html?modId=909187 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 20:41:18 27-10-2020
Re: [ANNOUNCE] Apache Ignite 2.9.0 Released
Congratulations, everyone, and big thanks to Alex! As always, I've prepared an overview for .NET features and improvements: https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.9/ Pavel On Fri, Oct 23, 2020 at 10:35 PM Denis Magda wrote: > We made it! Congrats, community! Thanks, Alex for pushing the release till > the end, that was a long road ;) > > I decided to record a quick video featuring top-3 changes in the release. > Those are my top-3 additions while you can have yours. Anyway, check it > out: > https://youtu.be/ewwjq8SIk-s > > - > Denis > > > On Fri, Oct 23, 2020 at 7:38 AM Aleksey Plekhanov > wrote: > > > The Apache Ignite Community is pleased to announce the release of > > Apache Ignite 2.9.0. > > > > Apache Ignite® is an in-memory computing platform for transactional, > > analytical, and streaming workloads delivering in-memory speeds at > > petabyte scale. > > https://ignite.apache.org > > > > For the full list of changes, you can refer to the RELEASE_NOTES list > > which is trying to catalogue the most significant improvements for > > this version of the platform. > > https://ignite.apache.org/releases/2.9.0/release_notes.html > > > > Download the latest Ignite version from here: > > https://ignite.apache.org/download.cgi > > > > Please let us know if you encounter any problems: > > https://ignite.apache.org/community/resources.html#ask > > > > > > Regards, > > Aleksey Plekhanov on behalf of Apache Ignite community. > > >
Re: 2.9.1 release proposal
Igniters, I think we should plan 2.10 instead of 2.9.1. ignite-2.9 branch was cut 4 months ago, a bunch of new features are waiting to be released. On Tue, Oct 27, 2020 at 4:23 AM 18624049226 <18624049...@163.com> wrote: > Hello, > > I suggest that the remaining document issue in version 2.9.0 can be > solved in version 2.9.1, and it is not a good practice to postpone to > version 2.10. > > 在 2020/10/27 上午2:00, Maxim Muzafarov 写道: > > Hello, > > > > +1 > > Should we start the discussion about the release leader and release > dates? > > > > On Tue, 20 Oct 2020 at 10:12, Anton Vinogradov wrote: > >> +1 to start the 2.9.1 release process once as soon as 2.9 released. > >> > >> On Mon, Oct 19, 2020 at 8:49 PM Nikolay Izhikov > wrote: > >> > >>> Hello, Yaroslav. > >>> > >>> I support the idea. > >>> But, we should carefully work with the release scope. > >>> > >>> IGNITE-13477 - fix for a SQL tracing that will be available only in > 2.10 > >>> IGNITE-13427 - fix for a new system view that exists in master only, we > >>> need to include IGNITE-13409 > >>> > >>> Other tickets should be checked, also. > >>> Is this a real fix of a released bug or we fix some issue we bring with > >>> the brand new contribution. > >>> > >>> > >>> I propose to include the following tickets, also: > >>> > >>> CMD tools improvements: > >>> > >>> IGNITE-13488 - Command to print metric value > >>> IGNITE-13426 - Command to print system view content > >>> IGNITE-13422 - Parameter to explicitly enable experimental commands > >>> > >>> IGNITE-13380 - Output IgniteSystemProperties via ignite.sh > >>> > >>> New system views: > >>> > >>> IGNITE-13409 Metastorage and DistributedMetastorage viewы. > >>> IGNITE-13408 BinaryMetadata view. > >>> > >>> > 19 окт. 2020 г., в 18:20, Yaroslav Molochkov > >>> написал(а): > Hello, Igniters! > > I've compiled a list of tickets that, i think, deserve to be released > in > >>> a > minor Ignite release (meaning in 2.9.1) after 2.9. Here they are: > > IGNITE-13569 > disable archiving + walCompactionEnabled probably broke reading from > wal > >>> on > server restart > > IGNITE-13418 > Deadlock on multiple cache delete > > IGNITE-13563 > Deserializing IBinaryObject containing an IBinaryObject field fails > > IGNITE-13575 > Invalid blocking section in GridNioWorker and GridNioClientWorker > leads > >>> to > false positive blocking thread detection > > IGNITE-13458 > RebalancingPartitionsTotal metrics > > IGNITE-13536 > .NET: Child processes become zombies when persistence is used with > direct-io on Linux > > IGNITE-13500 > Checkpoint read lock fail if it is taking under write lock during the > stopping node > > IGNITE-13431 > NPE during Cassandra Store initialization with PRIMITIVE strategy > > IGNITE-13417 > Cache Interceptors deserialization on client nodes > > IGNITE-13495 > ZookeeperDiscoverySpiMBeanImpl#getCoordinator can return invalid node > as > coordinator > > IGNITE-13479 > Both ignite.sh and control.sh use the same JVM_OPTS. Control.sh > doesn't > start if JMX port was set > > IGNITE-11312 > JDBC: Thin driver reports incorrect property names > > IGNITE-13462 > .NET: Thin client Dispose hangs when continuous query is active on > .NET > Core 3.x > > IGNITE-13484 > C++ odbc-example losing some values if run with 1 additional node > > IGNITE-13477 > Fix NPE in SQL tracing implementation. > > IGNITE-13435 > Fixing some unrecorded issues command warm-up control.sh > > IGNITE-13403 > Update JDBC metadata to match actual capabilities > > IGNITE-13427 > The local metastorage system view fails if unmarshallable values > present > > IGNITE-13401 > Unsupported protocol version exception when getting cache > configuration > from Java thin client > > IGNITE-13388 > apache-ignite deb package depends on a non-existent package and can't > be > installed on Debian 10 > > IGNITE-13397 > NPE in logSupplierDone(UUID nodeId) > > IGNITE-13296 > .NET: TransactionImpl finalizer can crash the process > > IGNITE-13382 > DurableBackgroundTask can abandon incomplete task > > IGNITE-12509 > CACHE_REBALANCE_STOPPED event raises for wrong caches in case of > >>> specified > RebalanceDelay > > IGNITE-13072 > Synchronization problems when different classloaders are used for > deployment of same class > > IGNITE-13379 > Exception occur on SQL caches when client reconnect > > IGNITE-13363 > GridDhtCacheEntry::toString locks > > IGNITE-13373 > WAL segmentns do not released on releaseHistoryForPreloading() > > IGNITE-13540 >
[jira] [Created] (IGNITE-13632) Transaction hangs due to communication failures
Pavel Vinokurov created IGNITE-13632: Summary: Transaction hangs due to communication failures Key: IGNITE-13632 URL: https://issues.apache.org/jira/browse/IGNITE-13632 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.8.1 Reporter: Pavel Vinokurov Attachments: TxReproducer.java Transaction hangs after dropping communication messages. The reproducer is attached -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13631) Improve names and descriptions of data storage metrics
Denis Mekhanikov created IGNITE-13631: - Summary: Improve names and descriptions of data storage metrics Key: IGNITE-13631 URL: https://issues.apache.org/jira/browse/IGNITE-13631 Project: Ignite Issue Type: Improvement Reporter: Denis Mekhanikov Assignee: Denis Mekhanikov Data storage metrics have unclear descriptions. They need to be improved. ||Metric||Description||Comment|| |*WalLoggingRate*|Average number of WAL records per second written during the last time interval.|The "time interval" part is unclear. Which time interval?| |*WalFsyncTimeDuration*|Total duration of fsync|Why not just *WalFsyncDuration*? The description could be more verbose.| |*WalFsyncTimeNum*|Total count of fsync|Why not just *WalFsyncNum*? The description could be more verbose| |*WalBuffPollSpinsRate*|WAL buffer poll spins number over the last time interval. |Over which time interval?| |*LastCheckpointMarkDuration*|Duration of the checkpoint lock wait in milliseconds |The description doesn't match the name.| |*CheckpointTotalTime*|Total duration of checkpoint|Is it the duration of the last checkpoint or all checkpoints from the beginning?| |*StorageSize*|Storage space allocated, in bytes.|It's unclear which storage this is about. Is disk included, or is it just about memory?| |*WalTotalSize*|Total size in bytes for storage wal files.|WAL should be capital. The grammar| -- This message was sent by Atlassian Jira (v8.3.4#803005)
