Request for edit permissions on cwiki.apache.org
Hi, igniters! Recently i've contributed offline utility for analyzing indexes and detecting errors to Ignite: https://issues.apache.org/jira/browse/IGNITE-14529 I feel that it would be nice to add some information about how to use it and interprete it's output. I wanted to write an article on apache wiki, but I need edit permissions to do this. Could someone grant me them? My username: denis.chudov
Re: [DISCUSSION] index-reader and orphaned pages
> Do we know the way how orphaned pages sneaks into index.bin? No, index reader just checks if there are pages in index.bin that have no links to them from index trees nor from reuse lists. Such pages are considered "orphan". This just indicates possible problem but unfortunately there is no information about how they appeared. On Tue, Jun 21, 2022 at 12:21 PM Anton Vinogradov : > > - Do we know the way how orphaned pages sneaks into index.bin? > Could this be because of nodes crashes and restarts? > Looks like we have no failovers to restore indices after the crash. > > On Mon, Jun 20, 2022 at 10:47 PM Николай Ижиков wrote: > > > Hello Igniters. > > > > We have very useful `index-reader` utility that can check index file > > consistency. > > I try to run it on several test and production Ignite deployments and > > found that frequently util report orphaned pages inside index.bin file. > > > > Example of output of production deployment: > > > > ``` > > Exception occurred on step 981750: Possibly orphan InlineInnerIO page, > > pageId=844420636146422 > > Exception occurred on step 981759: Possibly orphan InlineInnerIO page, > > pageId=844420636146431 > > Exception occurred on step 981775: Possibly orphan InlineInnerIO page, > > pageId=844420636146447 > > Exception occurred on step 981790: Possibly orphan InlineInnerIO page, > > pageId=844420636146462 > > Total pages encountered during sequential scan: 981844 > > Total errors occurred during sequential scan: 44853 > > > > ``` > > > > Test deployment: > > > > ``` > > Error [step=10876, msg=Possibly orphan InlineInnerIO page, > > pageId=844420635175548] > > Error [step=11048, msg=Possibly orphan InlineInnerIO page, > > pageId=844420635175720] > > Error [step=11081, msg=Possibly orphan InlineInnerIO page, > > pageId=844420635175753] > > Error [step=9, msg=Possibly orphan InlineInnerIO page, > > pageId=844420635175791] > > Error [step=11169, msg=Possibly orphan InlineInnerIO page, > > pageId=844420635175841] > > > > Total pages encountered during sequential scan:11543 > > Total errors occurred during sequential scan: 88 > > ``` > > > > So my questions are > > > > - Do we know the way how orphaned pages sneaks into index.bin? > > - Do we have tickets/fixes to prevent this situation? > > - How Ignite admin should fix this in real-world deployments?
Re: [ANNOUNCE] Welcome Kirill Tkalenko as a new committer
Congratulations! вт, 11 окт. 2022 г. в 09:46, Aleksandr Pakhomov : > Congratulations! > > > On 10 Oct 2022, at 22:15, Pavel Tupitsyn wrote: > > > > The Project Management Committee (PMC) for Apache Ignite > > has invited Kirill Tkalenko to become a committer and we are pleased > > to announce that they have accepted. > > > > Kirill is an active contributor and community member, he made significant > > additions to Ignite 2.x and 3.x code bases, WAL and PageMemory > improvements > > among others. > > > > 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 me in welcoming Kirill, and congratulating him on the new > role > > in > > the Apache Ignite Community! > > > > Regards, > > Pavel Tupitsyn > >
Re: [VOTE] Release Apache Ignite 3.0.0-beta1 RC2
+1 вт, 15 нояб. 2022 г. в 13:33, Alexander Lapin : > +1 > > вт, 15 нояб. 2022 г. в 08:48, Pavel Tupitsyn : > > > +1 (binding) > > > > On Mon, Nov 14, 2022 at 9:05 PM Вячеслав Коптилин < > > slava.kopti...@gmail.com> > > wrote: > > > > > Dear Community, > > > > > > Ignite 3 is moving forward and I think we're in a good spot to release > > the > > > first beta version. In the last few months the following major features > > > have been added: > > > - RPM and DEB packages: simplified installation and node management > with > > > system services. > > > - Client's Partition Awareness: Clients are now aware of data > > distribution > > > over the cluster nodes which helps avoid additional network > transmissions > > > and lowers operations latency. > > > - C++ client: Basic C++ client, able to perform operations on data. > > > - Autogenerated values: now a function can be specified as a default > > value > > > generator during a table creation. Currently only gen_random_uuid is > > > supported. > > > - SQL Transactions. > > > - Transactional Protocol: improved locking model, multi-version based > > > lock-free read-only transactions. > > > - Storage: A number of improvements to memory-only and on-disk engines > > > based on Page Memory. > > > - Indexes: Basic functionality, hash and sorted indexes. > > > - Client logging: A LoggerFactory may be provided during client > creation > > to > > > specify a custom logger for logs generated by the client. > > > - Metrics framework: Collection and export of cluster metrics. > > > > > > I propose to release 3.0.0-beta1 with the features listed above. > > > > > > Release Candidate: > > > https://dist.apache.org/repos/dist/dev/ignite/3.0.0-beta1-rc2/ > > > Maven Staging: > > > > https://repository.apache.org/content/repositories/orgapacheignite-1556/ > > > Tag: https://github.com/apache/ignite-3/tree/3.0.0-beta1-rc2 > > > > > > +1 - accept Apache Ignite 3.0.0-beta1 RC2 > > > 0 - don't care either way > > > -1 - DO NOT accept Apache Ignite 3.0.0-beta1 RC2 (explain why) > > > > > > Voting guidelines: https://www.apache.org/foundation/voting.html > > > How to verify the release: > https://www.apache.org/info/verification.html > > > > > > The vote will be closed on Wednesday, 16 November 2022, 18:00:00 (UTC > > time) > > > > > > > > > https://www.timeanddate.com/countdown/generic?iso=20221116T18&p0=1440&msg=Apache+Ignite+3.0.0-beta1+RC2&font=cursive&csz=1 > > > > > > Thanks, > > > S. > > > > > >
Re: [VOTE] Move Ignite 2.x sources to JDK11
+1 вт, 16 июл. 2024 г., 12:20 18624049226 <18624049...@163.com>: > +1 > > 在 2024/7/16 16:38, Pavel Tupitsyn 写道: > > +1 > > > > On Tue, Jul 16, 2024 at 10:14 AM Zhenya Stanilovsky > > wrote: > > > >> Great ! > >> +1 > >> > >>> Hi Igniters, > >>> > >>> I'd like to start a voting process about moving Ignite 2.x sources to > >>> JDK11. Discussion of the proposal is here [1]. > >>> > >>> The plan is as follows: > >>> 1. Upgrade all TeamCity jobs from jdk1.8 to jdk11. > >>> 2. Review and merge the patch [2] that changes `maven.source.version` > in > >>> Ignite's pom.xml to 11. This means that Apache Ignite 2.17 will be > built > >>> using jdk11. > >>> 3. Clean up all code that relies on jdk1.8 (docs, ignite-tools for 1.8, > >>> pom.xml configs, etc). > >>> > >>> I consider this vote as a *code modification* vote, see voting > guidelines > >>> [3]. > >>> > >>> +1 - to accept the plan above > >>> 0 - don’t care either way > >>> -1 - DO NOT accept the plan (*veto *[3], please explain why) > >>> > >>> This vote will be open for at least 4 days till Saturday July 20, 2024, > >>> 10:00 Moscow TZ. > >>> > >>> [1]https://lists.apache.org/thread/v81wt7xzvrk6o04sb2k4fmydctqgtjlg > >>> [2]https://issues.apache.org/jira/browse/IGNITE-22669 > >>> [3]https://www.apache.org/foundation/voting.html > >> > >> > >>
[DISCUSSION] IEP-133: Replicated zones
Hello Igniters, Please take a look at this proposal [1]. [1] IEP-133 Replicated zones https://cwiki.apache.org/confluence/display/IGNITE/IEP-133+Replicated+zones -- Denis Chudov
