[jira] [Commented] (IGNITE-12443) Document the Ignite Sandbox
[ https://issues.apache.org/jira/browse/IGNITE-12443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17194044#comment-17194044 ] Artem Budnikov commented on IGNITE-12443: - [~dma...@apache.org] please take a look. > Document the Ignite Sandbox > --- > > Key: IGNITE-12443 > URL: https://issues.apache.org/jira/browse/IGNITE-12443 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Garus >Assignee: Denis Garus >Priority: Major > Labels: iep-38, important > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Document how to configure and use the Ignite Sandbox. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12968) Create cluster snapshot documentation pages
[ https://issues.apache.org/jira/browse/IGNITE-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193435#comment-17193435 ] Artem Budnikov commented on IGNITE-12968: - [~dma...@apache.org] Please take a look. > Create cluster snapshot documentation pages > --- > > Key: IGNITE-12968 > URL: https://issues.apache.org/jira/browse/IGNITE-12968 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Blocker > Labels: iep-43, important > Fix For: 2.9 > > Time Spent: 5.5h > Remaining Estimate: 0h > > Add the following to the Apache Ignite documentation: > 1. How to create a cluster snapshot (describe API, limitations) > 2. How to configure a destination directory > 3. Manual steps for a snapshot restore > 4. Examples -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13239) Document APIs to view and change Cluster ID and Tag
[ https://issues.apache.org/jira/browse/IGNITE-13239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17185815#comment-17185815 ] Artem Budnikov commented on IGNITE-13239: - Added: https://github.com/apache/ignite/blob/IGNITE-7595/docs/_docs/monitoring-metrics/cluster-id.adoc > Document APIs to view and change Cluster ID and Tag > --- > > Key: IGNITE-13239 > URL: https://issues.apache.org/jira/browse/IGNITE-13239 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Sergey Chugunov >Assignee: Artem Budnikov >Priority: Major > Labels: important > Fix For: 2.9 > > > In IGNITE-13185 new APIs and changes were introduced to view Cluster ID and > Tag and change Tag. > These APIs and use cases need to be documented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13332) Document .NET Native Near Cache
[ https://issues.apache.org/jira/browse/IGNITE-13332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17185808#comment-17185808 ] Artem Budnikov commented on IGNITE-13332: - Added: [https://github.com/apache/ignite/blob/IGNITE-7595/docs/_docs/platform-cache.adoc] > Document .NET Native Near Cache > --- > > Key: IGNITE-13332 > URL: https://issues.apache.org/jira/browse/IGNITE-13332 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Assignee: Artem Budnikov >Priority: Major > Labels: important > Fix For: 2.9 > > > Document .NET Native Near Cache -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13332) Document .NET Native Near Cache
[ https://issues.apache.org/jira/browse/IGNITE-13332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-13332: --- Assignee: Artem Budnikov > Document .NET Native Near Cache > --- > > Key: IGNITE-13332 > URL: https://issues.apache.org/jira/browse/IGNITE-13332 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Assignee: Artem Budnikov >Priority: Major > Labels: important > Fix For: 2.9 > > > Document .NET Native Near Cache -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13388) apache-ignite deb package depends on a non-existent package and can't be installed on Debian 10
[
https://issues.apache.org/jira/browse/IGNITE-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Budnikov updated IGNITE-13388:
Summary: apache-ignite deb package depends on a non-existent package and
can't be installed on Debian 10 (was: apache-ignite deb package depends on the
non-existent package and can't be installed on Debian 10)
> apache-ignite deb package depends on a non-existent package and can't be
> installed on Debian 10
> ---
>
> Key: IGNITE-13388
> URL: https://issues.apache.org/jira/browse/IGNITE-13388
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8.1
>Reporter: Artem Budnikov
>Priority: Major
>
> The apache-ignite deb package v. 2.8.1 depends on 'openjdk-8-jdk', which is
> only available in Debian stretch and isn't available in later Debian
> distributions. An attempt to install the package gives this error:
> {code:java}
> $ sudo apt-get install apache-ignite=2.8.1-1
> ...
> The following packages have unmet dependencies:
> apache-ignite : Depends: openjdk-8-jdk but it is not installable or
> oracle-java8-installer but it is not installable
> E: Unable to correct problems, you have held broken packages{code}
> Package information:
> {code:java}
> $ apt-cache show apache-ignite=2.8.1-1
> Package: apache-ignite
> Version: 2.8.1-1
> Architecture: all
> Maintainer: Petr Ivanov
> Installed-Size: 572071
> Depends: openjdk-8-jdk | oracle-java8-installer, systemd, passwd
> Section: misc
> Priority: optional
> Homepage: https://ignite.apache.org
> Description: Apache Ignite In-Memory Computing, Database and Caching Platform
> Ignite™ is a memory-centric distributed database, caching, and processing
> platform for transactional, analytical, and streaming workloads, delivering
> in-memory speeds at petabyte scale
> Description-md5: 6a59db03fa1e142387abef6ef6bb0d83
> Filename: pool/main/a/apache-ignite_2.8.1-1_all.deb
> SHA1: 67d197a5e582f6ea7c66da26a755f937f8e16fc9
> SHA256: fc9a274ecb82716905d4120a715e9c74441dfed67831874eb3c35c4953bfc90d
> Size: 399746094
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13388) apache-ignite deb package depends on the non-existent package and can't be installed on Debian 10
Artem Budnikov created IGNITE-13388:
---
Summary: apache-ignite deb package depends on the non-existent
package and can't be installed on Debian 10
Key: IGNITE-13388
URL: https://issues.apache.org/jira/browse/IGNITE-13388
Project: Ignite
Issue Type: Bug
Affects Versions: 2.8.1
Reporter: Artem Budnikov
The apache-ignite deb package v. 2.8.1 depends on 'openjdk-8-jdk', which is
only available in Debian stretch and isn't available in later Debian
distributions. An attempt to install the package gives this error:
{code:java}
$ sudo apt-get install apache-ignite=2.8.1-1
...
The following packages have unmet dependencies:
apache-ignite : Depends: openjdk-8-jdk but it is not installable or
oracle-java8-installer but it is not installable
E: Unable to correct problems, you have held broken packages{code}
Package information:
{code:java}
$ apt-cache show apache-ignite=2.8.1-1
Package: apache-ignite
Version: 2.8.1-1
Architecture: all
Maintainer: Petr Ivanov
Installed-Size: 572071
Depends: openjdk-8-jdk | oracle-java8-installer, systemd, passwd
Section: misc
Priority: optional
Homepage: https://ignite.apache.org
Description: Apache Ignite In-Memory Computing, Database and Caching Platform
Ignite™ is a memory-centric distributed database, caching, and processing
platform for transactional, analytical, and streaming workloads, delivering
in-memory speeds at petabyte scale
Description-md5: 6a59db03fa1e142387abef6ef6bb0d83
Filename: pool/main/a/apache-ignite_2.8.1-1_all.deb
SHA1: 67d197a5e582f6ea7c66da26a755f937f8e16fc9
SHA256: fc9a274ecb82716905d4120a715e9c74441dfed67831874eb3c35c4953bfc90d
Size: 399746094
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12438) Extend communication protocol to establish client-server connection
[ https://issues.apache.org/jira/browse/IGNITE-12438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-12438: --- Assignee: Artem Budnikov > Extend communication protocol to establish client-server connection > --- > > Key: IGNITE-12438 > URL: https://issues.apache.org/jira/browse/IGNITE-12438 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Alexey Goncharuk >Assignee: Artem Budnikov >Priority: Major > Labels: important > Fix For: 2.9 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Recently there was quite a lot of questions related to thick clients > connectivity issues when the clients are deployed in a k8s pod [1]. The > general issue here is clients reporting network address which are not > reachable from server nodes. At the same time, the clients can connect to > server nodes. > An idea of how to fix this is as follows: > * Make sure that think clients discovery SPI always maintains a connection > to a server node (this should be already implemented) > * (Optionally) detect when a client has only one-way connectivity with the > server nodes. This part should be investigated. We need this to avoid server > nodes attempt to connect to a client and send communication request to the > client node faster > * When a server attempts to establish a connection with a client, check if > client is unreachable or the previous connection attempt failed. If so, send > a discovery message to the client to force a client-server connection. In > this case, server will be able to send the original message via the newly > established connection. > [1] > https://stackoverflow.com/questions/59192075/ignite-communicationspi-questions-in-paas-environment/59232504 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11719) Document cluster read-only mode
[ https://issues.apache.org/jira/browse/IGNITE-11719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183027#comment-17183027 ] Artem Budnikov commented on IGNITE-11719: - First version of the documentation: https://github.com/apache/ignite/blob/IGNITE-7595/docs/_docs/cluster-states.adoc > Document cluster read-only mode > --- > > Key: IGNITE-11719 > URL: https://issues.apache.org/jira/browse/IGNITE-11719 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Sergey Antonov >Assignee: Artem Budnikov >Priority: Critical > Labels: important > Fix For: 2.9 > > > We should document cluster wide read-only mode. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13334) Document initial tracing implementation
[ https://issues.apache.org/jira/browse/IGNITE-13334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183026#comment-17183026 ] Artem Budnikov commented on IGNITE-13334: - First version of the page: https://github.com/apache/ignite/blob/IGNITE-7595/docs/_docs/monitoring-metrics/tracing.adoc > Document initial tracing implementation > --- > > Key: IGNITE-13334 > URL: https://issues.apache.org/jira/browse/IGNITE-13334 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Assignee: Artem Budnikov >Priority: Major > Labels: important > Fix For: 2.9 > > > Document initial tracing implementation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13239) Document APIs to view and change Cluster ID and Tag
[ https://issues.apache.org/jira/browse/IGNITE-13239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-13239: --- Assignee: Artem Budnikov > Document APIs to view and change Cluster ID and Tag > --- > > Key: IGNITE-13239 > URL: https://issues.apache.org/jira/browse/IGNITE-13239 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Sergey Chugunov >Assignee: Artem Budnikov >Priority: Major > Labels: important > Fix For: 2.9 > > > In IGNITE-13185 new APIs and changes were introduced to view Cluster ID and > Tag and change Tag. > These APIs and use cases need to be documented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13330) Document java thin client features implemented in 2.8 and 2.9 release
[ https://issues.apache.org/jira/browse/IGNITE-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181745#comment-17181745 ] Artem Budnikov commented on IGNITE-13330: - Hey [~alex_pl] , The file `docs/_docs/code-snippets/java/src/main/java/org/apache/ignite/snippets/JavaThinClient.java` does not compile with the changes you have added. Could you please make sure it does? The whole purpose of having code snippets in separate java files is to ensure they work (at least compile). > Document java thin client features implemented in 2.8 and 2.9 release > - > > Key: IGNITE-13330 > URL: https://issues.apache.org/jira/browse/IGNITE-13330 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: important > Fix For: 2.9 > > Time Spent: 40m > Remaining Estimate: 0h > > Document implemented in 2.8 and 2.9 release features for java thin client: > * Partition awareness > * Cluster API > * Cluster group API > * Compute > * Services -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-10331) Document Disk page compression
[ https://issues.apache.org/jira/browse/IGNITE-10331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov resolved IGNITE-10331. - Resolution: Fixed > Document Disk page compression > -- > > Key: IGNITE-10331 > URL: https://issues.apache.org/jira/browse/IGNITE-10331 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Sergei Vladykin >Priority: Blocker > Fix For: 2.9 > > > There is an email thread titled "Disk page compression for Ignite persistent > store" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-10331) Document Disk page compression
[ https://issues.apache.org/jira/browse/IGNITE-10331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17180439#comment-17180439 ] Artem Budnikov commented on IGNITE-10331: - This was fixed in 2.8. https://apacheignite.readme.io/docs/disk-page-compression > Document Disk page compression > -- > > Key: IGNITE-10331 > URL: https://issues.apache.org/jira/browse/IGNITE-10331 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Sergei Vladykin >Priority: Blocker > Fix For: 2.9 > > > There is an email thread titled "Disk page compression for Ignite persistent > store" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13334) Document initial tracing implementation
[ https://issues.apache.org/jira/browse/IGNITE-13334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-13334: --- Assignee: Artem Budnikov > Document initial tracing implementation > --- > > Key: IGNITE-13334 > URL: https://issues.apache.org/jira/browse/IGNITE-13334 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Assignee: Artem Budnikov >Priority: Major > Labels: important > Fix For: 2.9 > > > Document initial tracing implementation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13330) Document java thin client features implemented in 2.8 and 2.9 release
[ https://issues.apache.org/jira/browse/IGNITE-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176172#comment-17176172 ] Artem Budnikov commented on IGNITE-13330: - [~alex_pl] Added a couple of comments. Please review. In general looks good. > Document java thin client features implemented in 2.8 and 2.9 release > - > > Key: IGNITE-13330 > URL: https://issues.apache.org/jira/browse/IGNITE-13330 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: important > Fix For: 2.9 > > Time Spent: 20m > Remaining Estimate: 0h > > Document implemented in 2.8 and 2.9 release features for java thin client: > * Partition awareness > * Cluster API > * Cluster group API > * Compute > * Services -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12492) TDE - Phase-2. Documentation.
[ https://issues.apache.org/jira/browse/IGNITE-12492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176048#comment-17176048 ] Artem Budnikov commented on IGNITE-12492: - [~NSAmelchev] Overall looks good. I made 2 minor comments. > TDE - Phase-2. Documentation. > - > > Key: IGNITE-12492 > URL: https://issues.apache.org/jira/browse/IGNITE-12492 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: important > Fix For: 2.9 > > Time Spent: 20m > Remaining Estimate: 0h > > Add documentation for the master key change process. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-7595) Find and switch to alternate documentation engine
[ https://issues.apache.org/jira/browse/IGNITE-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-7595: -- Assignee: Artem Budnikov (was: Denis A. Magda) > Find and switch to alternate documentation engine > - > > Key: IGNITE-7595 > URL: https://issues.apache.org/jira/browse/IGNITE-7595 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Assignee: Artem Budnikov >Priority: Minor > Attachments: Docusaurus-GitBook comparison.docx, > readme-markdown-mapping.xlsx > > > Current readme.io documentation has many drawbacks that make the life of > Ignite technical writers hard. Some of the problems are: > * Each "version" is just a copy of the previous one. When fixing something, > you have to update > all the versions. > * No good way to review changes. > * "Propose edit" functionality is a not suitable for review. You can only > accept or reject an > edit, no way to communicate with a contributor, etc > * There is no way to prevent Google from indexing old documentation > versions. Thus, it's common to come across old doc version in a google > search. > We might consider GitHub based documentation or another approach. The > discussion is here: > http://apache-ignite-developers.2346864.n4.nabble.com/Move-documentation-from-readme-io-to-GitHub-pages-td16409.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11369) Remove H2 console form documentation
[ https://issues.apache.org/jira/browse/IGNITE-11369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057907#comment-17057907 ] Artem Budnikov commented on IGNITE-11369: - Fixed. > Remove H2 console form documentation > > > Key: IGNITE-11369 > URL: https://issues.apache.org/jira/browse/IGNITE-11369 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.7 >Reporter: Taras Ledkov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > > Please remove the [H2 > console|https://apacheignite-sql.readme.io/docs/performance-and-debugging#using-h2-debug-console] > section from documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-11369) Remove H2 console form documentation
[ https://issues.apache.org/jira/browse/IGNITE-11369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov resolved IGNITE-11369. - Resolution: Fixed > Remove H2 console form documentation > > > Key: IGNITE-11369 > URL: https://issues.apache.org/jira/browse/IGNITE-11369 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.7 >Reporter: Taras Ledkov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > > Please remove the [H2 > console|https://apacheignite-sql.readme.io/docs/performance-and-debugging#using-h2-debug-console] > section from documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-11651) Add cluster (de)activation events documentation
[
https://issues.apache.org/jira/browse/IGNITE-11651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Budnikov resolved IGNITE-11651.
-
Resolution: Fixed
> Add cluster (de)activation events documentation
> ---
>
> Key: IGNITE-11651
> URL: https://issues.apache.org/jira/browse/IGNITE-11651
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Igor Belyakov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.8
>
>
> {{Add information regarding cluster activation events to
> [https://apacheignite.readme.io/docs/baseline-topology#section-activating-the-cluster]}}
>
> After cluster activation/deactivation local event will be raised.
> (EVT_CLUSTER_ACTIVATED/EVT_CLUSTER_DEACTIVATED)
> Subscribing for local events described here:
> [https://apacheignite.readme.io/docs/events#section-local-events]
> Example:
> ignite.events().localListen((evt) -> {
> // Do something.
> return true;
> }, EventType.EVT_CLUSTER_ACTIVATED);
> Cluster event types:
> {{EVT_CLUSTER_ACTIVATED - Invoked after Ignite cluster activation.}}
> {{EVT_CLUSTER_DEACTIVATED - Invoked after Ignite cluster deactivation.}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11651) Add cluster (de)activation events documentation
[
https://issues.apache.org/jira/browse/IGNITE-11651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057905#comment-17057905
]
Artem Budnikov commented on IGNITE-11651:
-
Added:
https://apacheignite.readme.io/docs/baseline-topology#section-cluster-activationdeactivation-events
> Add cluster (de)activation events documentation
> ---
>
> Key: IGNITE-11651
> URL: https://issues.apache.org/jira/browse/IGNITE-11651
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Igor Belyakov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.8
>
>
> {{Add information regarding cluster activation events to
> [https://apacheignite.readme.io/docs/baseline-topology#section-activating-the-cluster]}}
>
> After cluster activation/deactivation local event will be raised.
> (EVT_CLUSTER_ACTIVATED/EVT_CLUSTER_DEACTIVATED)
> Subscribing for local events described here:
> [https://apacheignite.readme.io/docs/events#section-local-events]
> Example:
> ignite.events().localListen((evt) -> {
> // Do something.
> return true;
> }, EventType.EVT_CLUSTER_ACTIVATED);
> Cluster event types:
> {{EVT_CLUSTER_ACTIVATED - Invoked after Ignite cluster activation.}}
> {{EVT_CLUSTER_DEACTIVATED - Invoked after Ignite cluster deactivation.}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-12134) Document default Ignite work dir location
[ https://issues.apache.org/jira/browse/IGNITE-12134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov resolved IGNITE-12134. - Resolution: Fixed > Document default Ignite work dir location > - > > Key: IGNITE-12134 > URL: https://issues.apache.org/jira/browse/IGNITE-12134 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Artem Budnikov >Priority: Critical > Fix For: 2.8 > > > What should be documented: > Contents and significance of work dir - db, marshaller, wal. > Default for cases when there is IGNITE_HOME (such as running from binary > distribution) > Default for cases when there's no IGNITE_HOME (running Ignite as library) > Changing default > logs/ that sometimes comes alongside work/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12134) Document default Ignite work dir location
[ https://issues.apache.org/jira/browse/IGNITE-12134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057903#comment-17057903 ] Artem Budnikov commented on IGNITE-12134: - Added: https://apacheignite.readme.io/docs/getting-started#section-setting-up-work-directory > Document default Ignite work dir location > - > > Key: IGNITE-12134 > URL: https://issues.apache.org/jira/browse/IGNITE-12134 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Artem Budnikov >Priority: Critical > Fix For: 2.8 > > > What should be documented: > Contents and significance of work dir - db, marshaller, wal. > Default for cases when there is IGNITE_HOME (such as running from binary > distribution) > Default for cases when there's no IGNITE_HOME (running Ignite as library) > Changing default > logs/ that sometimes comes alongside work/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-10945) Document Baseline auto-adjust feature
[
https://issues.apache.org/jira/browse/IGNITE-10945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Budnikov resolved IGNITE-10945.
-
Resolution: Fixed
> Document Baseline auto-adjust feature
> -
>
> Key: IGNITE-10945
> URL: https://issues.apache.org/jira/browse/IGNITE-10945
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Ivan Bessonov
>Assignee: Artem Budnikov
>Priority: Critical
> Labels: IEP-4, Phase-2
> Fix For: 2.8
>
>
> From IGNITE-8571:
> Now we have only one way to change BLAT - manually update it via console.sh
> or API.
> We need to add the possibility to change it automatically. Adjust to current
> topology.
> So, I propose 3 new parameters which would be responsible to tune this
> feature.
> 1. Flag autoAdjustEnabled - true/false. Easy. Manual baseline control or
> auto adjusting baseline.
> 2. autoAdjustTimeout - time which we would wait after the actual topology
> change. But it would be reset if new discovery event happened. (node
> join/exit).
> 3. autoAdjustMaxTimeout - time which we would wait from the first dicovery
> event in the chain. If we achieved it than we would change BLAT right away
> (no matter were another node join/exit happened or not).
> We need to change API next way:
> 1. org.apache.ignite.IgniteCluster
> *Add*
> isBaselineAutoAdjustEnabled()
> setBaselineAutoAdjustEnabled(boolean enabled);
> setBaselineAutoAdjustTimeout(long timeoutInMs);
> setBaselineAutoAdjustMaxTimeout(long timeoutInMs);
> 2. org.apache.ignite.configuration.IgniteConfiguration
> *Add*
> IgniteConfiguration setBaselineAutoAdjustEnabled(boolean enabled);
> IgniteConfiguration setBaselineAutoAdjustTimeout(long timeoutInMs);
> IgniteConfiguration setBaselineAutoAdjustMaxTimeout(long timeoutInMs);
> Also, we need to ensure that all nodes would have the same parameters.
> And we should be able to survive coordinator left during parameters changes.
> -
> For IGNITE-8575:
> Proposed API format for control.sh:
> {{--baseline autoadjust disable}}
> {{--baseline autoadjust enable }}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-10945) Document Baseline auto-adjust feature
[
https://issues.apache.org/jira/browse/IGNITE-10945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056946#comment-17056946
]
Artem Budnikov commented on IGNITE-10945:
-
Added
https://apacheignite.readme.io/v2.8.0/docs/baseline-topology#section-baseline-topology-autoadjustment
> Document Baseline auto-adjust feature
> -
>
> Key: IGNITE-10945
> URL: https://issues.apache.org/jira/browse/IGNITE-10945
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Ivan Bessonov
>Assignee: Artem Budnikov
>Priority: Critical
> Labels: IEP-4, Phase-2
> Fix For: 2.8
>
>
> From IGNITE-8571:
> Now we have only one way to change BLAT - manually update it via console.sh
> or API.
> We need to add the possibility to change it automatically. Adjust to current
> topology.
> So, I propose 3 new parameters which would be responsible to tune this
> feature.
> 1. Flag autoAdjustEnabled - true/false. Easy. Manual baseline control or
> auto adjusting baseline.
> 2. autoAdjustTimeout - time which we would wait after the actual topology
> change. But it would be reset if new discovery event happened. (node
> join/exit).
> 3. autoAdjustMaxTimeout - time which we would wait from the first dicovery
> event in the chain. If we achieved it than we would change BLAT right away
> (no matter were another node join/exit happened or not).
> We need to change API next way:
> 1. org.apache.ignite.IgniteCluster
> *Add*
> isBaselineAutoAdjustEnabled()
> setBaselineAutoAdjustEnabled(boolean enabled);
> setBaselineAutoAdjustTimeout(long timeoutInMs);
> setBaselineAutoAdjustMaxTimeout(long timeoutInMs);
> 2. org.apache.ignite.configuration.IgniteConfiguration
> *Add*
> IgniteConfiguration setBaselineAutoAdjustEnabled(boolean enabled);
> IgniteConfiguration setBaselineAutoAdjustTimeout(long timeoutInMs);
> IgniteConfiguration setBaselineAutoAdjustMaxTimeout(long timeoutInMs);
> Also, we need to ensure that all nodes would have the same parameters.
> And we should be able to survive coordinator left during parameters changes.
> -
> For IGNITE-8575:
> Proposed API format for control.sh:
> {{--baseline autoadjust disable}}
> {{--baseline autoadjust enable }}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-11370) Doc: remove SqlQuery documentation
[
https://issues.apache.org/jira/browse/IGNITE-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Budnikov resolved IGNITE-11370.
-
Resolution: Fixed
> Doc: remove SqlQuery documentation
> --
>
> Key: IGNITE-11370
> URL: https://issues.apache.org/jira/browse/IGNITE-11370
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.7
>Reporter: Taras Ledkov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.8
>
>
> Need to remove all mentions about {{SqlQuery}} from the whole documentation,
> as it is deprecated for now.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12408) Metrics and SystemView documentation
[ https://issues.apache.org/jira/browse/IGNITE-12408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055970#comment-17055970 ] Artem Budnikov commented on IGNITE-12408: - > Do we have the ability to copy pages for new metrics and system view from > 2.7.6 to 2.8 docs? Yes, I'll do it when we finish working on the docs. > Metrics and SystemView documentation > > > Key: IGNITE-12408 > URL: https://issues.apache.org/jira/browse/IGNITE-12408 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8 > > > We should provide the following documentation > - metric description. > - system view descirption. > - metrics exporter configuration guide. > - system view exporter configuration guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12408) Metrics and SystemView documentation
[ https://issues.apache.org/jira/browse/IGNITE-12408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055876#comment-17055876 ] Artem Budnikov commented on IGNITE-12408: - [~nizhikov] I agree, please move the existing system views page, if you don't mind. > Metrics and SystemView documentation > > > Key: IGNITE-12408 > URL: https://issues.apache.org/jira/browse/IGNITE-12408 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8 > > > We should provide the following documentation > - metric description. > - system view descirption. > - metrics exporter configuration guide. > - system view exporter configuration guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12408) Metrics and SystemView documentation
[ https://issues.apache.org/jira/browse/IGNITE-12408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17046585#comment-17046585 ] Artem Budnikov commented on IGNITE-12408: - [~nizhikov] Since you are working on the system views, I'd like to mention that we already have a page that contains the information about the system views available in Ignite 2.7: [https://apacheignite-sql.readme.io/docs/system-views] Are you going to update this page as well? Or maybe move its content to the page that you created? > Metrics and SystemView documentation > > > Key: IGNITE-12408 > URL: https://issues.apache.org/jira/browse/IGNITE-12408 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8 > > > We should provide the following documentation > - metric description. > - system view descirption. > - metrics exporter configuration guide. > - system view exporter configuration guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12134) Document default Ignite work dir location
[ https://issues.apache.org/jira/browse/IGNITE-12134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17045304#comment-17045304 ] Artem Budnikov commented on IGNITE-12134: - [~ilyak] What is the default work directory if IGNITE_HOME is not set? > Document default Ignite work dir location > - > > Key: IGNITE-12134 > URL: https://issues.apache.org/jira/browse/IGNITE-12134 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Artem Budnikov >Priority: Critical > Fix For: 2.8 > > > What should be documented: > Contents and significance of work dir - db, marshaller, wal. > Default for cases when there is IGNITE_HOME (such as running from binary > distribution) > Default for cases when there's no IGNITE_HOME (running Ignite as library) > Changing default > logs/ that sometimes comes alongside work/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12134) Document default Ignite work dir location
[ https://issues.apache.org/jira/browse/IGNITE-12134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-12134: --- Assignee: Artem Budnikov > Document default Ignite work dir location > - > > Key: IGNITE-12134 > URL: https://issues.apache.org/jira/browse/IGNITE-12134 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Artem Budnikov >Priority: Critical > Fix For: 2.8 > > > What should be documented: > Contents and significance of work dir - db, marshaller, wal. > Default for cases when there is IGNITE_HOME (such as running from binary > distribution) > Default for cases when there's no IGNITE_HOME (running Ignite as library) > Changing default > logs/ that sometimes comes alongside work/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-11422) Remove H2 console from documentation
[ https://issues.apache.org/jira/browse/IGNITE-11422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov resolved IGNITE-11422. - Resolution: Fixed > Remove H2 console from documentation > > > Key: IGNITE-11422 > URL: https://issues.apache.org/jira/browse/IGNITE-11422 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > > H2 console was deprecated as a part of IGNITE-11333. Need to remove all > mentions of "H2 console" from documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11422) Remove H2 console from documentation
[ https://issues.apache.org/jira/browse/IGNITE-11422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038217#comment-17038217 ] Artem Budnikov commented on IGNITE-11422: - removed H2 Console section from https://apacheignite-sql.readme.io/docs/performance-and-debugging > Remove H2 console from documentation > > > Key: IGNITE-11422 > URL: https://issues.apache.org/jira/browse/IGNITE-11422 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > > H2 console was deprecated as a part of IGNITE-11333. Need to remove all > mentions of "H2 console" from documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11847) Change note on the capacity planning page about memory usage
[ https://issues.apache.org/jira/browse/IGNITE-11847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038210#comment-17038210 ] Artem Budnikov commented on IGNITE-11847: - [~ezhuravl] What is the correct value? Or should this statement be removed completely? > Change note on the capacity planning page about memory usage > > > Key: IGNITE-11847 > URL: https://issues.apache.org/jira/browse/IGNITE-11847 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.7 >Reporter: Evgenii Zhuravlev >Assignee: Artem Budnikov >Priority: Major > > https://apacheignite.readme.io/docs/capacity-planning#calculating-memory-usage > It says that "Apache Ignite will typically add around 200 bytes overhead to > each entry.", but it's not true, I think it was applicable only for 1.x > versions, where everything was stored in heap -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-12615) Add warning that cluster deactivation purges data from memory
[ https://issues.apache.org/jira/browse/IGNITE-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov resolved IGNITE-12615. - Resolution: Fixed > Add warning that cluster deactivation purges data from memory > - > > Key: IGNITE-12615 > URL: https://issues.apache.org/jira/browse/IGNITE-12615 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.7.6 >Reporter: Denis A. Magda >Assignee: Artem Budnikov >Priority: Blocker > Fix For: 2.8 > > > Baseline topology [1] and control script's [2] documentation needs to have a > warning callout saying that a cluster deactivation procedure will purge data > from memory requiring users to reload data back after the activation. For > caches that persist data in the native persistence, this will happen > automatically, for all the other cases the user has to reload data manually. > [1] https://apacheignite.readme.io/docs/baseline-topology > [2] > https://apacheignite-tools.readme.io/docs/control-script#section-activation-deactivation-and-topology-management -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12615) Add warning that cluster deactivation purges data from memory
[ https://issues.apache.org/jira/browse/IGNITE-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035106#comment-17035106 ] Artem Budnikov commented on IGNITE-12615: - I added a warning to each section. > Add warning that cluster deactivation purges data from memory > - > > Key: IGNITE-12615 > URL: https://issues.apache.org/jira/browse/IGNITE-12615 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.7.6 >Reporter: Denis A. Magda >Assignee: Artem Budnikov >Priority: Blocker > Fix For: 2.8 > > > Baseline topology [1] and control script's [2] documentation needs to have a > warning callout saying that a cluster deactivation procedure will purge data > from memory requiring users to reload data back after the activation. For > caches that persist data in the native persistence, this will happen > automatically, for all the other cases the user has to reload data manually. > [1] https://apacheignite.readme.io/docs/baseline-topology > [2] > https://apacheignite-tools.readme.io/docs/control-script#section-activation-deactivation-and-topology-management -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12408) Metrics and SystemView documentation
[ https://issues.apache.org/jira/browse/IGNITE-12408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16998159#comment-16998159 ] Artem Budnikov commented on IGNITE-12408: - [~nizhikov] As far as I can see, the most important parts are missing: how to configure exporters; how to get metrics (complete examples); how to use SQL views, how to configure OpenCensus exporter. Users read documentation because they want to find a way to _use_ the functionality. Let's say I want to monitor the number of keys in a specific cache, what should I do to achieve this? It would be nice to have a step by step instruction. > Metrics and SystemView documentation > > > Key: IGNITE-12408 > URL: https://issues.apache.org/jira/browse/IGNITE-12408 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8 > > > We should provide the following documentation > - metric description. > - system view descirption. > - metrics exporter configuration guide. > - system view exporter configuration guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov resolved IGNITE-7611. Resolution: Fixed > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956782#comment-16956782 ] Artem Budnikov commented on IGNITE-7611: That one was fixed. > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov updated IGNITE-7611: --- Fix Version/s: (was: 2.8) > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Artem Budnikov >Priority: Major > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-9091) IEP-25: creating documentation
[ https://issues.apache.org/jira/browse/IGNITE-9091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16946940#comment-16946940 ] Artem Budnikov commented on IGNITE-9091: [~mmuzaf] The page will be published together with Ignite 2.8. Is version 2.8 going to be released any time soon? > IEP-25: creating documentation > -- > > Key: IGNITE-9091 > URL: https://issues.apache.org/jira/browse/IGNITE-9091 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alex Volkov >Assignee: Artem Budnikov >Priority: Major > Labels: iep-25 > Fix For: 2.8 > > > It would be great to have proper documentation for IEP-25: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-25:+Partition+Map+Exchange+hangs+resolving] > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12134) Document default Ignite work dir location
[ https://issues.apache.org/jira/browse/IGNITE-12134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov updated IGNITE-12134: Fix Version/s: (was: 2.7.6) 2.8 > Document default Ignite work dir location > - > > Key: IGNITE-12134 > URL: https://issues.apache.org/jira/browse/IGNITE-12134 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Ilya Kasnacheev >Priority: Major > Fix For: 2.8 > > > What should be documented: > Contents and significance of work dir - db, marshaller, wal. > Default for cases when there is IGNITE_HOME (such as running from binary > distribution) > Default for cases when there's no IGNITE_HOME (running Ignite as library) > Changing default > logs/ that sometimes comes alongside work/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12107) Docs: request setting IGNITE_HOME to permanent location in Docker
[ https://issues.apache.org/jira/browse/IGNITE-12107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919385#comment-16919385 ] Artem Budnikov commented on IGNITE-12107: - I updated the instructions on using Ignite Docker Image [1] and Ignite in Kubernetes [2]. [1]: [https://apacheignite.readme.io/docs/docker-deployment] [2]: [https://apacheignite.readme.io/docs/stateful-deployment#section-statefulset-deployment] [~dmagda] please verify. > Docs: request setting IGNITE_HOME to permanent location in Docker > - > > Key: IGNITE-12107 > URL: https://issues.apache.org/jira/browse/IGNITE-12107 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Blocker > Fix For: 2.7.6 > > > Update Ignite Docker and Kubernetes documentation stating that IGNITE_HOME, > as well as WAL and persistent store directories, must point to the volumes > that are not erased or destroyed on restarts. Please refer to this thread for > more details: > http://apache-ignite-developers.2346864.n4.nabble.com/Metastore-disappears-in-Docker-on-restarts-td43107.html -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12107) Docs: request setting IGNITE_HOME to permanent location in Docker
[ https://issues.apache.org/jira/browse/IGNITE-12107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916758#comment-16916758 ] Artem Budnikov commented on IGNITE-12107: - [~dmagda] Should we document how to set IGNITE_WORK_DIR to point to a persistent volume rather than IGNITE_HOME? Because IGNITE_WORK_DIR is where all the data is stored. > Docs: request setting IGNITE_HOME to permanent location in Docker > - > > Key: IGNITE-12107 > URL: https://issues.apache.org/jira/browse/IGNITE-12107 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Blocker > Fix For: 2.7.6 > > > Update Ignite Docker and Kubernetes documentation stating that IGNITE_HOME, > as well as WAL and persistent store directories, must point to the volumes > that are not erased or destroyed on restarts. Please refer to this thread for > more details: > http://apache-ignite-developers.2346864.n4.nabble.com/Metastore-disappears-in-Docker-on-restarts-td43107.html -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (IGNITE-12107) Docs: request setting IGNITE_HOME to permanent location in Docker
[ https://issues.apache.org/jira/browse/IGNITE-12107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-12107: --- Assignee: Artem Budnikov > Docs: request setting IGNITE_HOME to permanent location in Docker > - > > Key: IGNITE-12107 > URL: https://issues.apache.org/jira/browse/IGNITE-12107 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Blocker > Fix For: 2.7.6 > > > Update Ignite Docker and Kubernetes documentation stating that IGNITE_HOME, > as well as WAL and persistent store directories, must point to the volumes > that are not erased or destroyed on restarts. Please refer to this thread for > more details: > http://apache-ignite-developers.2346864.n4.nabble.com/Metastore-disappears-in-Docker-on-restarts-td43107.html -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-12073) The doc should mention IGNITE_UPDATE_NOTIFIER has no effect if you're not the first node that started up
[ https://issues.apache.org/jira/browse/IGNITE-12073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov updated IGNITE-12073: Labels: javadoc (was: ) > The doc should mention IGNITE_UPDATE_NOTIFIER has no effect if you're not the > first node that started up > > > Key: IGNITE-12073 > URL: https://issues.apache.org/jira/browse/IGNITE-12073 > Project: Ignite > Issue Type: Improvement >Reporter: chin >Priority: Major > Labels: javadoc > > It drove me crazy > I wanted to disable the auto update check. > I found this page > [https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteSystemProperties.html#IGNITE_UPDATE_NOTIFIER] > > spent a few hours trying to set the system property in different ways but > couldn't get the update notification to go away. > > Then I found IGNITE-2350. > > That info should be mentioned clearly in the docs. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-2350) Make IGNITE_UPDATE_NOTIFIER per cluster setting
[ https://issues.apache.org/jira/browse/IGNITE-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov updated IGNITE-2350: --- Labels: important (was: important javadoc) > Make IGNITE_UPDATE_NOTIFIER per cluster setting > --- > > Key: IGNITE-2350 > URL: https://issues.apache.org/jira/browse/IGNITE-2350 > Project: Ignite > Issue Type: Task >Reporter: Yakov Zhdanov >Assignee: Ilya Suntsov >Priority: Critical > Labels: important > Fix For: 1.6 > > Time Spent: 20m > Remaining Estimate: 0h > > We need to refactor update notification behavior to make it more transparent. > # The first node (topVer=1) should behave in accordance to its local settings > # The first node should set cluster-wide default which should survive its > (first node) exit. > # Further nodes should ignore local setting and respect cluster wide value > set on cluster start -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-2350) Make IGNITE_UPDATE_NOTIFIER per cluster setting
[ https://issues.apache.org/jira/browse/IGNITE-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov updated IGNITE-2350: --- Labels: important javadoc (was: important) > Make IGNITE_UPDATE_NOTIFIER per cluster setting > --- > > Key: IGNITE-2350 > URL: https://issues.apache.org/jira/browse/IGNITE-2350 > Project: Ignite > Issue Type: Task >Reporter: Yakov Zhdanov >Assignee: Ilya Suntsov >Priority: Critical > Labels: important, javadoc > Fix For: 1.6 > > Time Spent: 20m > Remaining Estimate: 0h > > We need to refactor update notification behavior to make it more transparent. > # The first node (topVer=1) should behave in accordance to its local settings > # The first node should set cluster-wide default which should survive its > (first node) exit. > # Further nodes should ignore local setting and respect cluster wide value > set on cluster start -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (IGNITE-11539) Document services hot redeployment via DeploymentSpi
[ https://issues.apache.org/jira/browse/IGNITE-11539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830223#comment-16830223 ] Artem Budnikov edited comment on IGNITE-11539 at 4/30/19 12:15 PM: --- Please find the description of the feature here: [https://apacheignite.readme.io/docs/service-grid-28#service-updates-redeployment] was (Author: artem budnikov): Added the description of the feature here: https://apacheignite.readme.io/docs/service-grid-28#service-updates-redeployment > Document services hot redeployment via DeploymentSpi > > > Key: IGNITE-11539 > URL: https://issues.apache.org/jira/browse/IGNITE-11539 > Project: Ignite > Issue Type: Task > Components: documentation, managed services >Reporter: Vyacheslav Daradur >Priority: Major > Labels: iep-17 > Fix For: 2.8 > > > It's necessary to document "how to use" service hot redeployment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11539) Document services hot redeployment via DeploymentSpi
[ https://issues.apache.org/jira/browse/IGNITE-11539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830223#comment-16830223 ] Artem Budnikov commented on IGNITE-11539: - Added the description of the feature here: https://apacheignite.readme.io/docs/service-grid-28#service-updates-redeployment > Document services hot redeployment via DeploymentSpi > > > Key: IGNITE-11539 > URL: https://issues.apache.org/jira/browse/IGNITE-11539 > Project: Ignite > Issue Type: Task > Components: documentation, managed services >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Labels: iep-17 > Fix For: 2.8 > > > It's necessary to document "how to use" service hot redeployment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11539) Document services hot redeployment via DeploymentSpi
[ https://issues.apache.org/jira/browse/IGNITE-11539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-11539: --- Assignee: (was: Vyacheslav Daradur) > Document services hot redeployment via DeploymentSpi > > > Key: IGNITE-11539 > URL: https://issues.apache.org/jira/browse/IGNITE-11539 > Project: Ignite > Issue Type: Task > Components: documentation, managed services >Reporter: Vyacheslav Daradur >Priority: Major > Labels: iep-17 > Fix For: 2.8 > > > It's necessary to document "how to use" service hot redeployment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11729) Low description for lost policy functional
[
https://issues.apache.org/jira/browse/IGNITE-11729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Budnikov updated IGNITE-11729:
Fix Version/s: (was: 3.0)
> Low description for lost policy functional
> --
>
> Key: IGNITE-11729
> URL: https://issues.apache.org/jira/browse/IGNITE-11729
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.7
>Reporter: ARomantsov
>Priority: Major
> Fix For: 2.8
>
>
> Current description in
> https://apacheignite.readme.io/docs/partition-loss-policies seems not covered
> persistence case and text description is not clear
> Probably we need to transform it into two tables (in-memory, persistence)
> Rows - cache_write, cache_read, cache_remove,sql_read, sql_write
> Columns - READ_ONLY_SAFE ,READ_ONLY_ALL, READ_WRITE_SAFE, etc
> {code:java}
> Policies
> Ignite supports the following PartitionLossPolicies:
> READ_ONLY_SAFE - all writes to a cache/table will fail with an exception.
> Reads will only be allowed for entries belonging to survived/alive
> partitions. Reads from lost partitions will fail with an exception.
> READ_ONLY_ALL - reads are allowed from any partition including the lost ones.
> An exception is thrown in an attempt to write to any partition. The result of
> reading from a lost partition is undefined and may be different on different
> nodes in the cluster.
> READ_WRITE_SAFE - all reads and writes are allowed for entries in
> survived/alive partitions. All reads and writes of entries belonging to the
> lost partitions will fail with an exception.
> READ_WRITE_ALL - all reads and writes will proceed as if all partitions were
> in a consistent state (as if no partition loss happened). The result of
> reading from a lost partition is undefined and may be different on different
> nodes in the cluster.
> IGNORE - this mode never marks a lost partition as lost, pretending that no
> partition loss has happened and clearing the partition loss state right away.
> Technically, the partition will not be added to the collection of
> lostPartitions which is the main difference from READ_WRITE_ALL mode. IGNORE
> mode is used by default.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11427) Document custom node fail functional.
[ https://issues.apache.org/jira/browse/IGNITE-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-11427: --- Assignee: (was: Artem Budnikov) > Document custom node fail functional. > - > > Key: IGNITE-11427 > URL: https://issues.apache.org/jira/browse/IGNITE-11427 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7 >Reporter: Stanilovsky Evgeny >Priority: Major > Fix For: 2.8 > > Attachments: Screenshot_20190227_100539.png > > > Append additional node fail documentation related to [1] > [1] https://issues.apache.org/jira/browse/IGNITE-11332 > > how it looks into jconsole: > !Screenshot_20190227_100539.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11165) Add note to the documentation that cache name will be used as folder name in case of using persistence
[ https://issues.apache.org/jira/browse/IGNITE-11165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16765753#comment-16765753 ] Artem Budnikov commented on IGNITE-11165: - Added a callout on page [https://apacheignite.readme.io/v2.7/docs/jcache] > Add note to the documentation that cache name will be used as folder name in > case of using persistence > -- > > Key: IGNITE-11165 > URL: https://issues.apache.org/jira/browse/IGNITE-11165 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Evgenii Zhuravlev >Assignee: Artem Budnikov >Priority: Major > > We should add a note that it's not recommended to use symbols which are not > allowed to use in the file system in case of using persistence. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11113) JVM 9-11 startup parameters have to be mentioned in every section of getting started
[ https://issues.apache.org/jira/browse/IGNITE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758263#comment-16758263 ] Artem Budnikov commented on IGNITE-3: - [~dmagda] I reproduced the problem on my Linux machine. It occurs when JAVA_HOME is not set and you use Java version 10 or 11. In that case the script fails to detect the version of java and does not add the required startup parameters. When JAVA_HOME is set to the JAVA 11 directory, the script works as expected. For those who use `ignite.sh`, the most simple solution would be to set up the JAVA_HOME variable (instead of providing all the JVM options manually). I updated the documentation with that information. > JVM 9-11 startup parameters have to be mentioned in every section of getting > started > > > Key: IGNITE-3 > URL: https://issues.apache.org/jira/browse/IGNITE-3 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Blocker > > Ignite.sh fails on Mac OS with JDK 11. The following startup parameters [1] > have to be mentioned in callout blocks of every section in the getting > started guide [2] where it's explained how to start a node with ignite.sh or > launch an application. > The user has to know how to: > * Fix ignite.sh/ignite.bat to make them workable > * What to do in an IDEA like IntellijIdean and Eclipse to make examples and > apps workable > [1] > https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 > [2] https://apacheignite.readme.io/docs/getting-started -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10896) Add ability to use simultaneous cache filtering options with control.sh --cache idle_verify
[
https://issues.apache.org/jira/browse/IGNITE-10896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755801#comment-16755801
]
Artem Budnikov commented on IGNITE-10896:
-
The behaviour that [~ARomantsov] suggests for the two options should be
extended to all three options. It'll be better if all three options can be used
simultaneously. Mutually exclusive filtering options are really confusing.
This is how I envision it:
The default value for `--exclude-caches` is an empty set.
The default value for `--cache-filter` is no filtering.
The default value for `\-\-caches` is all caches.
All three options can be used simultaneously or all three can be omitted (in
which case the default values are used). If the result of applying the options
is an empty set, the script should print a warning to the console.
> Add ability to use simultaneous cache filtering options with control.sh
> --cache idle_verify
> ---
>
> Key: IGNITE-10896
> URL: https://issues.apache.org/jira/browse/IGNITE-10896
> Project: Ignite
> Issue Type: Improvement
>Reporter: ARomantsov
>Priority: Major
> Fix For: 2.8
>
>
> Now I can use only one of next options
> 1) --exclude-caches cache1,...,cacheN
> 2) --cache-filter ALL|SYSTEM|PERSISTENT|NOT_PERSISTENT
> 3) cache1,...,cacheN
> Trying to use two or more of this options currently results in error:
> {noformat}
> Error: Should use only one of option: --excludeCaches, --cache-filter or pass
> caches explicitly
> {noformat}
> Instead, utility should do the following:
> 1) when two or more options specified, result cache set to make dump of
> should be logical AND of results of each option applied individually.
> ex.
> {noformat}
> cache.* --cache-filter PERSISTENT
> {noformat}
> should select all persistent caches starting from 'cache'
> {noformat}
>--cache-filter ALL
>--exclude-caches wrong-.*-caches
> {noformat}
> should select all caches but matching 'wrong-.*-caches' regexp
> etc.
> 2) filtering options passed to control utility should be logged into result
> dump file, so that user could understand that dump was taken from subset of
> cluster caches
> 3) when result of filter or filters AND'ing is empty set of cache names,
> proper error message should be given and no dump file generated.
> e.g.
> {noformat}Error: can't find any cache matching cache names '--skup-zerus' and
> cache filter 'PERSISTENT', dump won't be generated.{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-7611: -- Assignee: Prachi Garg (was: Artem Budnikov) > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.8 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16751165#comment-16751165 ] Artem Budnikov commented on IGNITE-7611: [~pgarg], please review the changes (the last two sections on the page). > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10740) Add documentation for IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT
[
https://issues.apache.org/jira/browse/IGNITE-10740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748480#comment-16748480
]
Artem Budnikov commented on IGNITE-10740:
-
The behaviour this option enables should be the default behaviour and the
option should be removed (it shouldn't have been added in the first place).
Anyway, if it needs to be documented it should be documented in the javadoc for
interceptors or other interfaces where it is relevant. That's the most
appropriate place for it. Also, if the behaviour of non-idempotent interceptors
is different from idempotent ones, this should also be documented in the
javadoc.
See also: https://issues.apache.org/jira/browse/IGNITE-10984
> Add documentation for IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT
> -
>
> Key: IGNITE-10740
> URL: https://issues.apache.org/jira/browse/IGNITE-10740
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Sergey Antonov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.8
>
>
> We should add to documentation
> IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT option.
> As a reference you could get javadoc from skipInterceptor() :
> {{Checks, that cache interceptor should be skipped. It is expects by default
> behavior that Interceptor methods (\{@link
> CacheInterceptor#onBeforePut(Cache.Entry, Object)}, \{@link
> CacheInterceptor#onAfterPut(Cache.Entry)}, \{@link
> CacheInterceptor#onBeforeRemove(Cache.Entry)} and \{@link
> CacheInterceptor#onAfterRemove(Cache.Entry)}) will be called, but \{@link
> CacheInterceptor#onGet(Object, Object)}. This can even make DR-update flow
> broken in case of non-idempotent Interceptor and force users to call onGet
> manually as the only workaround. Also, user may want to skip Interceptor to
> avoid redundant entry transformation for DR updates and exchange with
> internal data b/w data centres which is a normal case.}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10740) Add documentation for IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT
[
https://issues.apache.org/jira/browse/IGNITE-10740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748480#comment-16748480
]
Artem Budnikov edited comment on IGNITE-10740 at 1/22/19 8:11 AM:
--
The behaviour this option enables should be the default behaviour and the
option should be removed (it shouldn't have been added in the first place).
Anyway, if it needs to be documented it should be documented in the javadoc for
interceptors or other interfaces where it is relevant. That's the most
appropriate place for it. Also, if the behaviour of non-idempotent interceptors
is different from that of idempotent ones, this should also be documented in
the javadoc.
See also: https://issues.apache.org/jira/browse/IGNITE-10984
was (Author: artem budnikov):
The behaviour this option enables should be the default behaviour and the
option should be removed (it shouldn't have been added in the first place).
Anyway, if it needs to be documented it should be documented in the javadoc for
interceptors or other interfaces where it is relevant. That's the most
appropriate place for it. Also, if the behaviour of non-idempotent interceptors
is different from idempotent ones, this should also be documented in the
javadoc.
See also: https://issues.apache.org/jira/browse/IGNITE-10984
> Add documentation for IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT
> -
>
> Key: IGNITE-10740
> URL: https://issues.apache.org/jira/browse/IGNITE-10740
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Sergey Antonov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.8
>
>
> We should add to documentation
> IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT option.
> As a reference you could get javadoc from skipInterceptor() :
> {{Checks, that cache interceptor should be skipped. It is expects by default
> behavior that Interceptor methods (\{@link
> CacheInterceptor#onBeforePut(Cache.Entry, Object)}, \{@link
> CacheInterceptor#onAfterPut(Cache.Entry)}, \{@link
> CacheInterceptor#onBeforeRemove(Cache.Entry)} and \{@link
> CacheInterceptor#onAfterRemove(Cache.Entry)}) will be called, but \{@link
> CacheInterceptor#onGet(Object, Object)}. This can even make DR-update flow
> broken in case of non-idempotent Interceptor and force users to call onGet
> manually as the only workaround. Also, user may want to skip Interceptor to
> avoid redundant entry transformation for DR updates and exchange with
> internal data b/w data centres which is a normal case.}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10740) Add documentation for IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT
[
https://issues.apache.org/jira/browse/IGNITE-10740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Budnikov reassigned IGNITE-10740:
---
Assignee: Alexey Goncharuk (was: Artem Budnikov)
> Add documentation for IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT
> -
>
> Key: IGNITE-10740
> URL: https://issues.apache.org/jira/browse/IGNITE-10740
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Sergey Antonov
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.8
>
>
> We should add to documentation
> IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT option.
> As a reference you could get javadoc from skipInterceptor() :
> {{Checks, that cache interceptor should be skipped. It is expects by default
> behavior that Interceptor methods (\{@link
> CacheInterceptor#onBeforePut(Cache.Entry, Object)}, \{@link
> CacheInterceptor#onAfterPut(Cache.Entry)}, \{@link
> CacheInterceptor#onBeforeRemove(Cache.Entry)} and \{@link
> CacheInterceptor#onAfterRemove(Cache.Entry)}) will be called, but \{@link
> CacheInterceptor#onGet(Object, Object)}. This can even make DR-update flow
> broken in case of non-idempotent Interceptor and force users to call onGet
> manually as the only workaround. Also, user may want to skip Interceptor to
> avoid redundant entry transformation for DR updates and exchange with
> internal data b/w data centres which is a normal case.}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10740) Add documentation for IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT
[
https://issues.apache.org/jira/browse/IGNITE-10740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746236#comment-16746236
]
Artem Budnikov commented on IGNITE-10740:
-
[~antonovsergey93]
I'm not sure I understand what this option does from the end user standpoint.
Why would one want to configure interceptors and then disable them using this
option?
What does DR stand for in this context?
> Add documentation for IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT
> -
>
> Key: IGNITE-10740
> URL: https://issues.apache.org/jira/browse/IGNITE-10740
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Sergey Antonov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.8
>
>
> We should add to documentation
> IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT option.
> As a reference you could get javadoc from skipInterceptor() :
> {{Checks, that cache interceptor should be skipped. It is expects by default
> behavior that Interceptor methods (\{@link
> CacheInterceptor#onBeforePut(Cache.Entry, Object)}, \{@link
> CacheInterceptor#onAfterPut(Cache.Entry)}, \{@link
> CacheInterceptor#onBeforeRemove(Cache.Entry)} and \{@link
> CacheInterceptor#onAfterRemove(Cache.Entry)}) will be called, but \{@link
> CacheInterceptor#onGet(Object, Object)}. This can even make DR-update flow
> broken in case of non-idempotent Interceptor and force users to call onGet
> manually as the only workaround. Also, user may want to skip Interceptor to
> avoid redundant entry transformation for DR updates and exchange with
> internal data b/w data centres which is a normal case.}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10846) Improve docs for "Disabling WAL Archiving"
[ https://issues.apache.org/jira/browse/IGNITE-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738298#comment-16738298 ] Artem Budnikov edited comment on IGNITE-10846 at 1/9/19 2:47 PM: - [~dmagda] I don't think WAL archive can help to accelerate rebalancing when a new node joins the cluster. In this case, a number of partitions has to move to the new node and you can't help it. Correct me if I'm wrong. Also, I think we should mention that if the WAL archive is disabled, the size of the WAL is not 10 segments but is defined by the `DataStorageConfiguration.maxWalArchiveSize` property. Also, I encountered an issue: https://issues.apache.org/jira/browse/IGNITE-10868. If this behavior is expected, it should be documented. was (Author: artem budnikov): [~dmagda] I don't think WAL archive can help to accelerate rebalancing when a new node joins the cluster. In this case, a number of partitions has to move to the new node and you can't help it. Correct me if I'm wrong. Also, I think we should mention that if the WAL archive is disabled, the size of the WAL is not 10 segments but is defined by the `DataStorageConfiguration.maxWalArchiveSize` property. > Improve docs for "Disabling WAL Archiving" > -- > > Key: IGNITE-10846 > URL: https://issues.apache.org/jira/browse/IGNITE-10846 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Prachi Garg >Assignee: Artem Budnikov >Priority: Critical > Fix For: 2.8 > > > Provide pros and cons of disabling WAL Archiving. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10846) Improve docs for "Disabling WAL Archiving"
[ https://issues.apache.org/jira/browse/IGNITE-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738298#comment-16738298 ] Artem Budnikov edited comment on IGNITE-10846 at 1/9/19 2:39 PM: - [~dmagda] I don't think WAL archive can help to accelerate rebalancing when a new node joins the cluster. In this case, a number of partitions has to move to the new node and you can't help it. Correct me if I'm wrong. Also, I think we should mention that if the WAL archive is disabled, the size of the WAL is not 10 segments but is defined by the `DataStorageConfiguration.maxWalArchiveSize` property. was (Author: artem budnikov): [~dmagda] I don't think WAL archive can help to accelerate rebalancing when a new node joins the cluster. In this case, a number of partitions has to move to the new node and you can't help it. Also, I think we should mention that if the WAL archive is disabled, the size of the WAL is not 10 segments but is defined by the `DataStorageConfiguration.maxWalArchiveSize` property. > Improve docs for "Disabling WAL Archiving" > -- > > Key: IGNITE-10846 > URL: https://issues.apache.org/jira/browse/IGNITE-10846 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Prachi Garg >Assignee: Artem Budnikov >Priority: Critical > Fix For: 2.8 > > > Provide pros and cons of disabling WAL Archiving. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10846) Improve docs for "Disabling WAL Archiving"
[ https://issues.apache.org/jira/browse/IGNITE-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738298#comment-16738298 ] Artem Budnikov commented on IGNITE-10846: - [~dmagda] I don't think WAL archive can help to accelerate rebalancing when a new node joins the cluster. In this case, a number of partitions has to move to the new node and you can't help it. Also, I think we should mention that if the WAL archive is disabled, the size of the WAL is not 10 segments but is defined by the `DataStorageConfiguration.maxWalArchiveSize` property. > Improve docs for "Disabling WAL Archiving" > -- > > Key: IGNITE-10846 > URL: https://issues.apache.org/jira/browse/IGNITE-10846 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Prachi Garg >Assignee: Artem Budnikov >Priority: Critical > Fix For: 2.8 > > > Provide pros and cons of disabling WAL Archiving. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10868) WAL segments are removed from WAL archive after each checkpoint
Artem Budnikov created IGNITE-10868: --- Summary: WAL segments are removed from WAL archive after each checkpoint Key: IGNITE-10868 URL: https://issues.apache.org/jira/browse/IGNITE-10868 Project: Ignite Issue Type: Bug Affects Versions: 2.7 Reporter: Artem Budnikov Assignee: Alexey Goncharuk The WAL archive is cleaned up after each checkpoint. This does not cause issues for end users; however, an empty WAL archive won't help in case of historical rebalancing. But our documentation says that it does. Please investigate. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10850) Clarify the use of the enforceJoin flag
Artem Budnikov created IGNITE-10850: --- Summary: Clarify the use of the enforceJoin flag Key: IGNITE-10850 URL: https://issues.apache.org/jira/browse/IGNITE-10850 Project: Ignite Issue Type: Task Components: documentation Reporter: Artem Budnikov Assignee: Artem Budnikov Fix For: 2.8 Need to clarify the use of the enforceJoin flag and how it can be used to optimize queries. Add this information to [https://apacheignite-sql.readme.io/docs/performance-and-debugging] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10850) Clarify the use of the enforceJoinOrder flag
[ https://issues.apache.org/jira/browse/IGNITE-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov updated IGNITE-10850: Description: Need to clarify the use of the enforceJoinOrder flag and how it can be used to optimize queries. Add this information to [https://apacheignite-sql.readme.io/docs/performance-and-debugging] was: Need to clarify the use of the enforceJoin flag and how it can be used to optimize queries. Add this information to [https://apacheignite-sql.readme.io/docs/performance-and-debugging] > Clarify the use of the enforceJoinOrder flag > - > > Key: IGNITE-10850 > URL: https://issues.apache.org/jira/browse/IGNITE-10850 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Artem Budnikov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > > Need to clarify the use of the enforceJoinOrder flag and how it can be used > to optimize queries. Add this information to > [https://apacheignite-sql.readme.io/docs/performance-and-debugging] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10850) Clarify the use of the enforceJoinOrder flag
[ https://issues.apache.org/jira/browse/IGNITE-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov updated IGNITE-10850: Summary: Clarify the use of the enforceJoinOrder flag (was: Clarify the use of the enforceJoin flag ) > Clarify the use of the enforceJoinOrder flag > - > > Key: IGNITE-10850 > URL: https://issues.apache.org/jira/browse/IGNITE-10850 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Artem Budnikov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > > Need to clarify the use of the enforceJoin flag and how it can be used to > optimize queries. Add this information to > [https://apacheignite-sql.readme.io/docs/performance-and-debugging] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6526) Ignite 2.x capacity planning guide
[ https://issues.apache.org/jira/browse/IGNITE-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728635#comment-16728635 ] Artem Budnikov commented on IGNITE-6526: I agree, a html/js page is a better solution. I'll see what can be done. > Ignite 2.x capacity planning guide > -- > > Key: IGNITE-6526 > URL: https://issues.apache.org/jira/browse/IGNITE-6526 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Minor > Fix For: 2.8 > > > Current capacity planning guide [1] is too high level and should be > elaborated considering durable memory's internals: > - memory pages overhead. > - per-entry overhead > (http://apache-ignite-users.70518.x6.nabble.com/Re-Memory-Overhead-per-entry-in-Apache-Ignite-td9498.html). > - space occupied for indexing needs. > - free lists > - etc. > The page has to include estimates for the Ignite Native Persistence: > - entry size and its overheads. > - index size and overheads. > - data files overheads. > - estimated WAL size and how to shrink it basing on checkpointing settings. > [1] https://apacheignite.readme.io/docs/capacity-planning -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-6526) Ignite 2.x capacity planning guide
[ https://issues.apache.org/jira/browse/IGNITE-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-6526: -- Assignee: Alexey Goncharuk (was: Artem Budnikov) > Ignite 2.x capacity planning guide > -- > > Key: IGNITE-6526 > URL: https://issues.apache.org/jira/browse/IGNITE-6526 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Alexey Goncharuk >Priority: Minor > Fix For: 2.8 > > > Current capacity planning guide [1] is too high level and should be > elaborated considering durable memory's internals: > - memory pages overhead. > - per-entry overhead > (http://apache-ignite-users.70518.x6.nabble.com/Re-Memory-Overhead-per-entry-in-Apache-Ignite-td9498.html). > - space occupied for indexing needs. > - free lists > - etc. > The page has to include estimates for the Ignite Native Persistence: > - entry size and its overheads. > - index size and overheads. > - data files overheads. > - estimated WAL size and how to shrink it basing on checkpointing settings. > [1] https://apacheignite.readme.io/docs/capacity-planning -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6526) Ignite 2.x capacity planning guide
[ https://issues.apache.org/jira/browse/IGNITE-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728388#comment-16728388 ] Artem Budnikov commented on IGNITE-6526: I added a section on how to estimate the disk capacity for Ignite [1] and an example of empirical estimation [2]. [~agoncharuk], could you please review the two pages? [1]: [https://apacheignite.readme.io/docs/capacity-planning-updated#section-calculating-disk-space-usage] [2]: [https://apacheignite.readme.io/v2.7/docs/empirical-estimation-of-disk-capacity-usage] > Ignite 2.x capacity planning guide > -- > > Key: IGNITE-6526 > URL: https://issues.apache.org/jira/browse/IGNITE-6526 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Minor > Fix For: 2.8 > > > Current capacity planning guide [1] is too high level and should be > elaborated considering durable memory's internals: > - memory pages overhead. > - per-entry overhead > (http://apache-ignite-users.70518.x6.nabble.com/Re-Memory-Overhead-per-entry-in-Apache-Ignite-td9498.html). > - space occupied for indexing needs. > - free lists > - etc. > The page has to include estimates for the Ignite Native Persistence: > - entry size and its overheads. > - index size and overheads. > - data files overheads. > - estimated WAL size and how to shrink it basing on checkpointing settings. > [1] https://apacheignite.readme.io/docs/capacity-planning -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10802) Documentation for option IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE
[ https://issues.apache.org/jira/browse/IGNITE-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-10802: --- Assignee: Aleksey Plekhanov > Documentation for option IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE > -- > > Key: IGNITE-10802 > URL: https://issues.apache.org/jira/browse/IGNITE-10802 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.8 >Reporter: Alex Volkov >Assignee: Aleksey Plekhanov >Priority: Major > > After implementation -IGNITE-10172- it's not clear how cluster should behave > in some cases. > For example, if I have cluster with option > IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE=True and one additional node > with flag > IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE=False comes to this cluster. > What behaviour should I expect from the cluster? > In general, please provide documentation for this option. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-7611: -- Assignee: Artem Budnikov (was: Prachi Garg) > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708828#comment-16708828 ] Artem Budnikov edited comment on IGNITE-7611 at 12/4/18 3:15 PM: - [~slukyanov] I updated the page adding information you requested except for the following system properties: * IGNITE_UPDATE_NOTIFIER * IGNITE_STARVATION_CHECK_INTERVAL * IGNITE_TROUBLESHOOTING_LOGGER * IGNITE_CONSOLE_APPENDER * IGNITE_GRID_CLIENT_LOG_ENABLED * IGNITE_DEV_ONLY_LOGGING_DISABLED These are difficult to comprehend and bring little value to users. Please review the changes. [https://apacheignite.readme.io/v2.6/docs/logging-27] was (Author: artem budnikov): [~slukyanov] I updated the page adding information you requested except for the following system properties: * IGNITE_UPDATE_NOTIFIER * IGNITE_STARVATION_CHECK_INTERVAL * IGNITE_TROUBLESHOOTING_LOGGER * IGNITE_CONSOLE_APPENDER * IGNITE_GRID_CLIENT_LOG_ENABLED * IGNITE_DEV_ONLY_LOGGING_DISABLED These are difficult to comprehend and bring little value to users. Please review the changes. > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Stanislav Lukyanov >Priority: Major > Fix For: 2.7 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-7611: -- Assignee: Stanislav Lukyanov (was: Artem Budnikov) > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Stanislav Lukyanov >Priority: Major > Fix For: 2.7 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708828#comment-16708828 ] Artem Budnikov commented on IGNITE-7611: [~slukyanov] I updated the page adding information you requested except for the following system properties: * IGNITE_UPDATE_NOTIFIER * IGNITE_STARVATION_CHECK_INTERVAL * IGNITE_TROUBLESHOOTING_LOGGER * IGNITE_CONSOLE_APPENDER * IGNITE_GRID_CLIENT_LOG_ENABLED * IGNITE_DEV_ONLY_LOGGING_DISABLED These ones are difficult to comprehend and bring little value to users. Please review the changes. > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708828#comment-16708828 ] Artem Budnikov edited comment on IGNITE-7611 at 12/4/18 3:06 PM: - [~slukyanov] I updated the page adding information you requested except for the following system properties: * IGNITE_UPDATE_NOTIFIER * IGNITE_STARVATION_CHECK_INTERVAL * IGNITE_TROUBLESHOOTING_LOGGER * IGNITE_CONSOLE_APPENDER * IGNITE_GRID_CLIENT_LOG_ENABLED * IGNITE_DEV_ONLY_LOGGING_DISABLED These are difficult to comprehend and bring little value to users. Please review the changes. was (Author: artem budnikov): [~slukyanov] I updated the page adding information you requested except for the following system properties: * IGNITE_UPDATE_NOTIFIER * IGNITE_STARVATION_CHECK_INTERVAL * IGNITE_TROUBLESHOOTING_LOGGER * IGNITE_CONSOLE_APPENDER * IGNITE_GRID_CLIENT_LOG_ENABLED * IGNITE_DEV_ONLY_LOGGING_DISABLED These ones are difficult to comprehend and bring little value to users. Please review the changes. > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9943) Update documentation for default WAL archive size (added auto-adjust)
[ https://issues.apache.org/jira/browse/IGNITE-9943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708384#comment-16708384 ] Artem Budnikov commented on IGNITE-9943: Added a note about performance impact. [~pgarg] please review the changes. > Update documentation for default WAL archive size (added auto-adjust) > - > > Key: IGNITE-9943 > URL: https://issues.apache.org/jira/browse/IGNITE-9943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9943) Update documentation for default WAL archive size (added auto-adjust)
[ https://issues.apache.org/jira/browse/IGNITE-9943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-9943: -- Assignee: Prachi Garg (was: Artem Budnikov) > Update documentation for default WAL archive size (added auto-adjust) > - > > Key: IGNITE-9943 > URL: https://issues.apache.org/jira/browse/IGNITE-9943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Assignee: Prachi Garg >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8212) Binary Client Protocol spec: Key-Value Queries clarifications
[ https://issues.apache.org/jira/browse/IGNITE-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16703068#comment-16703068 ] Artem Budnikov commented on IGNITE-8212: [~isapego] # I added links only to those operations that I found difficult to explain. Adding links to all operations is unnecessary; however, I've added a link to the javadoc in the introductory section of the page. # The same as above: I added a link to the header description in the first paragraph. # done > Binary Client Protocol spec: Key-Value Queries clarifications > - > > Key: IGNITE-8212 > URL: https://issues.apache.org/jira/browse/IGNITE-8212 > Project: Ignite > Issue Type: Improvement > Components: documentation, thin client >Affects Versions: 2.4 >Reporter: Alexey Kosenchuk >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > https://apacheignite.readme.io/v2.4/docs/binary-client-protocol-key-value-operations > - all operations - "Flag. Pass 0 for default, or 1 to keep the value in > binary form": > -- remove words about binary form and keep "Pass 0 for default" for all > operations where this flag has no meaning. > -- clarify about binary form in operations where it has a meaning. > - OP_CACHE_GET: clarify that null is returned if the provided key does not > exist in the cache. > - OP_CACHE_GET_AND_PUT: clarify that new entry is created, if the provided > key does not exist in the cache, and null is returned in this case. > - OP_CACHE_GET_AND_REPLACE: > -- "if and only if there is a value currently mapped for that key" - is > confusing. Is it possible that an existing key has no associated value? > Suggest to rephrase as "if and only if the key exists in the cache" > -- clarify that null is returned if the key does not exist in the cache. > - OP_CACHE_GET_AND_REMOVE: clarify that null is returned if the key does not > exist in the cache. > - OP_CACHE_PUT_IF_ABSENT: clarify what is "Success Flag" - true if the new > entry is created, false if the specified key already exists in the cache. > - OP_CACHE_GET_AND_PUT_IF_ABSENT: "Previously contained value regardless of > whether put happened or not" - is confusing. Suggest to rewrite "the current > value associated with the key if it already exists in the cache, null if the > new entry is created". > - OP_CACHE_GET_SIZE: clarify Peek modes > - OP_CACHE_CLEAR_XXX and OP_CACHE_REMOVE_XXX: > -- what is the difference between the corresponding operations? Only in > notifying / not notifying listeners and cache writers? Or there are other > differences not clarified by the spec? > -- (the operations could be combined in one set - with a flag required/not > required notifications) > -- there is OP_CACHE_REMOVE_IF_EQUALS. But there is no > OP_CACHE_CLEAR_IF_EQUALS. Is it intentional? > -- OP_CACHE_REMOVE_KEY and OP_CACHE_REMOVE_IF_EQUALS have "Value indicating > whether remove happened" in the response. But OP_CACHE_CLEAR_KEY does not > have such a flag in the response. Is it intentional? > -- OP_CACHE_CLEAR_KEYS, OP_CACHE_REMOVE_KEYS: clarify that even if some of > the specified keys do not exist other entries are removed anyway. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7215) Documentation bug: "Cross-cache Query" page is dead
[ https://issues.apache.org/jira/browse/IGNITE-7215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701971#comment-16701971 ] Artem Budnikov commented on IGNITE-7215: This was fixed in 2.7 documentation. > Documentation bug: "Cross-cache Query" page is dead > --- > > Key: IGNITE-7215 > URL: https://issues.apache.org/jira/browse/IGNITE-7215 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.3 >Reporter: Alexey Kukushkin >Priority: Major > > Could not find "Cross-cache Queries" section in the latest Ignite 2.3 docs. > The only page that references "cross-cache queries" is [JDBC Client > Driver|https://apacheignite-sql.readme.io/docs#section-jdbc-client-driver] > and it points to a [dead > link|https://apacheignite-sql.readme.io/docs/cache-queries#cross-cache-queries] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7215) Documentation bug: "Cross-cache Query" page is dead
[ https://issues.apache.org/jira/browse/IGNITE-7215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov resolved IGNITE-7215. Resolution: Fixed > Documentation bug: "Cross-cache Query" page is dead > --- > > Key: IGNITE-7215 > URL: https://issues.apache.org/jira/browse/IGNITE-7215 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.3 >Reporter: Alexey Kukushkin >Priority: Major > > Could not find "Cross-cache Queries" section in the latest Ignite 2.3 docs. > The only page that references "cross-cache queries" is [JDBC Client > Driver|https://apacheignite-sql.readme.io/docs#section-jdbc-client-driver] > and it points to a [dead > link|https://apacheignite-sql.readme.io/docs/cache-queries#cross-cache-queries] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10350) Document that now it's allowed to stop caches created via SQL/DDL via Java API
[ https://issues.apache.org/jira/browse/IGNITE-10350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701956#comment-16701956 ] Artem Budnikov commented on IGNITE-10350: - [~EdShangGG] I think this was never mentioned in the documentation. Do you know which page (if any) should be fixed? > Document that now it's allowed to stop caches created via SQL/DDL via Java API > -- > > Key: IGNITE-10350 > URL: https://issues.apache.org/jira/browse/IGNITE-10350 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Eduard Shangareev >Priority: Major > > We need to update our documentation that behavior has changed. > https://issues.apache.org/jira/browse/IGNITE-10328 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-4841) Improve TEXT Query Documentation
[
https://issues.apache.org/jira/browse/IGNITE-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Budnikov reassigned IGNITE-4841:
--
Assignee: Andrew Mashenkov (was: Artem Budnikov)
> Improve TEXT Query Documentation
>
>
> Key: IGNITE-4841
> URL: https://issues.apache.org/jira/browse/IGNITE-4841
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 1.9
>Reporter: Daniel Siviter
>Assignee: Andrew Mashenkov
>Priority: Major
> Labels: full-text-search, javadoc
> Fix For: 2.7
>
>
> The documentation for Full TEXT Queries is thin at best:
> * What syntax does it use?
> * ...is it the full [Lucene Classic Query Parser
> Syntax|https://lucene.apache.org/core/6_3_0/queryparser/org/apache/lucene/queryparser/classic/package-summary.html]?
> * ...if so how does the syntax map to the {{@QueryTextField}} annotation?
> * How is Lucene analyser customisation performed?
> * What version is supported? (looks like 3.5.0 which is pretty old, latest is
> 6.4.1)
> * The
> [{{@QueryTextField}}|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/annotations/QueryTextField.html]
> JavaDoc refers to
> [{{CacheQuery}}|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/internal/processors/cache/query/CacheQuery.html]
> but strangely this doesn't even appear in the official JavaDoc. It is
> because it's an 'internal' class?
> It's mentioned multiple times as a feature, but doesn't look like much of
> Lucene can actually be utilised so clarifications would help greatly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-4841) Improve TEXT Query Documentation
[
https://issues.apache.org/jira/browse/IGNITE-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Budnikov updated IGNITE-4841:
---
Labels: full-text-search javadoc (was: full-text-search)
> Improve TEXT Query Documentation
>
>
> Key: IGNITE-4841
> URL: https://issues.apache.org/jira/browse/IGNITE-4841
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 1.9
>Reporter: Daniel Siviter
>Assignee: Artem Budnikov
>Priority: Major
> Labels: full-text-search, javadoc
> Fix For: 2.7
>
>
> The documentation for Full TEXT Queries is thin at best:
> * What syntax does it use?
> * ...is it the full [Lucene Classic Query Parser
> Syntax|https://lucene.apache.org/core/6_3_0/queryparser/org/apache/lucene/queryparser/classic/package-summary.html]?
> * ...if so how does the syntax map to the {{@QueryTextField}} annotation?
> * How is Lucene analyser customisation performed?
> * What version is supported? (looks like 3.5.0 which is pretty old, latest is
> 6.4.1)
> * The
> [{{@QueryTextField}}|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/annotations/QueryTextField.html]
> JavaDoc refers to
> [{{CacheQuery}}|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/internal/processors/cache/query/CacheQuery.html]
> but strangely this doesn't even appear in the official JavaDoc. It is
> because it's an 'internal' class?
> It's mentioned multiple times as a feature, but doesn't look like much of
> Lucene can actually be utilised so clarifications would help greatly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-4841) Improve TEXT Query Documentation
[
https://issues.apache.org/jira/browse/IGNITE-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Budnikov reassigned IGNITE-4841:
--
Assignee: Artem Budnikov
> Improve TEXT Query Documentation
>
>
> Key: IGNITE-4841
> URL: https://issues.apache.org/jira/browse/IGNITE-4841
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 1.9
>Reporter: Daniel Siviter
>Assignee: Artem Budnikov
>Priority: Major
> Labels: full-text-search
> Fix For: 2.7
>
>
> The documentation for Full TEXT Queries is thin at best:
> * What syntax does it use?
> * ...is it the full [Lucene Classic Query Parser
> Syntax|https://lucene.apache.org/core/6_3_0/queryparser/org/apache/lucene/queryparser/classic/package-summary.html]?
> * ...if so how does the syntax map to the {{@QueryTextField}} annotation?
> * How is Lucene analyser customisation performed?
> * What version is supported? (looks like 3.5.0 which is pretty old, latest is
> 6.4.1)
> * The
> [{{@QueryTextField}}|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/annotations/QueryTextField.html]
> JavaDoc refers to
> [{{CacheQuery}}|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/internal/processors/cache/query/CacheQuery.html]
> but strangely this doesn't even appear in the official JavaDoc. It is
> because it's an 'internal' class?
> It's mentioned multiple times as a feature, but doesn't look like much of
> Lucene can actually be utilised so clarifications would help greatly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8090) Explain disk space compaction by WAL and compaction techniques
[ https://issues.apache.org/jira/browse/IGNITE-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-8090: -- Assignee: Prachi Garg (was: Artem Budnikov) > Explain disk space compaction by WAL and compaction techniques > -- > > Key: IGNITE-8090 > URL: https://issues.apache.org/jira/browse/IGNITE-8090 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.7 > > > Explain how WAL occupies the disk space and how to enable the compaction: > https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-underthehood-WALHistorySize > There needs to be a special section in WAL documentation as well as in the > capacity planning. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8212) Binary Client Protocol spec: Key-Value Queries clarifications
[ https://issues.apache.org/jira/browse/IGNITE-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700399#comment-16700399 ] Artem Budnikov commented on IGNITE-8212: [~isapego] I addressed the points mentioned in the description and updated the page. Please review. > Binary Client Protocol spec: Key-Value Queries clarifications > - > > Key: IGNITE-8212 > URL: https://issues.apache.org/jira/browse/IGNITE-8212 > Project: Ignite > Issue Type: Improvement > Components: documentation, thin client >Affects Versions: 2.4 >Reporter: Alexey Kosenchuk >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > https://apacheignite.readme.io/v2.4/docs/binary-client-protocol-key-value-operations > - all operations - "Flag. Pass 0 for default, or 1 to keep the value in > binary form": > -- remove words about binary form and keep "Pass 0 for default" for all > operations where this flag has no meaning. > -- clarify about binary form in operations where it has a meaning. > - OP_CACHE_GET: clarify that null is returned if the provided key does not > exist in the cache. > - OP_CACHE_GET_AND_PUT: clarify that new entry is created, if the provided > key does not exist in the cache, and null is returned in this case. > - OP_CACHE_GET_AND_REPLACE: > -- "if and only if there is a value currently mapped for that key" - is > confusing. Is it possible that an existing key has no associated value? > Suggest to rephrase as "if and only if the key exists in the cache" > -- clarify that null is returned if the key does not exist in the cache. > - OP_CACHE_GET_AND_REMOVE: clarify that null is returned if the key does not > exist in the cache. > - OP_CACHE_PUT_IF_ABSENT: clarify what is "Success Flag" - true if the new > entry is created, false if the specified key already exists in the cache. > - OP_CACHE_GET_AND_PUT_IF_ABSENT: "Previously contained value regardless of > whether put happened or not" - is confusing. Suggest to rewrite "the current > value associated with the key if it already exists in the cache, null if the > new entry is created". > - OP_CACHE_GET_SIZE: clarify Peek modes > - OP_CACHE_CLEAR_XXX and OP_CACHE_REMOVE_XXX: > -- what is the difference between the corresponding operations? Only in > notifying / not notifying listeners and cache writers? Or there are other > differences not clarified by the spec? > -- (the operations could be combined in one set - with a flag required/not > required notifications) > -- there is OP_CACHE_REMOVE_IF_EQUALS. But there is no > OP_CACHE_CLEAR_IF_EQUALS. Is it intentional? > -- OP_CACHE_REMOVE_KEY and OP_CACHE_REMOVE_IF_EQUALS have "Value indicating > whether remove happened" in the response. But OP_CACHE_CLEAR_KEY does not > have such a flag in the response. Is it intentional? > -- OP_CACHE_CLEAR_KEYS, OP_CACHE_REMOVE_KEYS: clarify that even if some of > the specified keys do not exist other entries are removed anyway. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8212) Binary Client Protocol spec: Key-Value Queries clarifications
[ https://issues.apache.org/jira/browse/IGNITE-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-8212: -- Assignee: Igor Sapego (was: Artem Budnikov) > Binary Client Protocol spec: Key-Value Queries clarifications > - > > Key: IGNITE-8212 > URL: https://issues.apache.org/jira/browse/IGNITE-8212 > Project: Ignite > Issue Type: Improvement > Components: documentation, thin client >Affects Versions: 2.4 >Reporter: Alexey Kosenchuk >Assignee: Igor Sapego >Priority: Major > Fix For: 2.7 > > > https://apacheignite.readme.io/v2.4/docs/binary-client-protocol-key-value-operations > - all operations - "Flag. Pass 0 for default, or 1 to keep the value in > binary form": > -- remove words about binary form and keep "Pass 0 for default" for all > operations where this flag has no meaning. > -- clarify about binary form in operations where it has a meaning. > - OP_CACHE_GET: clarify that null is returned if the provided key does not > exist in the cache. > - OP_CACHE_GET_AND_PUT: clarify that new entry is created, if the provided > key does not exist in the cache, and null is returned in this case. > - OP_CACHE_GET_AND_REPLACE: > -- "if and only if there is a value currently mapped for that key" - is > confusing. Is it possible that an existing key has no associated value? > Suggest to rephrase as "if and only if the key exists in the cache" > -- clarify that null is returned if the key does not exist in the cache. > - OP_CACHE_GET_AND_REMOVE: clarify that null is returned if the key does not > exist in the cache. > - OP_CACHE_PUT_IF_ABSENT: clarify what is "Success Flag" - true if the new > entry is created, false if the specified key already exists in the cache. > - OP_CACHE_GET_AND_PUT_IF_ABSENT: "Previously contained value regardless of > whether put happened or not" - is confusing. Suggest to rewrite "the current > value associated with the key if it already exists in the cache, null if the > new entry is created". > - OP_CACHE_GET_SIZE: clarify Peek modes > - OP_CACHE_CLEAR_XXX and OP_CACHE_REMOVE_XXX: > -- what is the difference between the corresponding operations? Only in > notifying / not notifying listeners and cache writers? Or there are other > differences not clarified by the spec? > -- (the operations could be combined in one set - with a flag required/not > required notifications) > -- there is OP_CACHE_REMOVE_IF_EQUALS. But there is no > OP_CACHE_CLEAR_IF_EQUALS. Is it intentional? > -- OP_CACHE_REMOVE_KEY and OP_CACHE_REMOVE_IF_EQUALS have "Value indicating > whether remove happened" in the response. But OP_CACHE_CLEAR_KEY does not > have such a flag in the response. Is it intentional? > -- OP_CACHE_CLEAR_KEYS, OP_CACHE_REMOVE_KEYS: clarify that even if some of > the specified keys do not exist other entries are removed anyway. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9406) Improve SQL "Performance and Debugging" page
[ https://issues.apache.org/jira/browse/IGNITE-9406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697244#comment-16697244 ] Artem Budnikov commented on IGNITE-9406: [~vozerov] If I could clarify, I wouldn't have asked you. > Improve SQL "Performance and Debugging" page > > > Key: IGNITE-9406 > URL: https://issues.apache.org/jira/browse/IGNITE-9406 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > Attachments: ignite_sql_perf.txt > > > I prepared a document for one of Ignite clients with some advanced > information about how various performance optimizations work in Ignite SQL. > Let's compare this document with our "Performance and Debugging" page [1], > and enhance the latter with missing info (if any). > P.S.: Document is attached. Russian language. > [1] > https://apacheignite-sql.readme.io/docs/performance-and-debugging#query-execution-flow-optimizations -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9435) Document MVCC
[ https://issues.apache.org/jira/browse/IGNITE-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696658#comment-16696658 ] Artem Budnikov commented on IGNITE-9435: The feedback addressed in https://issues.apache.org/jira/browse/IGNITE-9880. > Document MVCC > - > > Key: IGNITE-9435 > URL: https://issues.apache.org/jira/browse/IGNITE-9435 > Project: Ignite > Issue Type: Task > Components: documentation, mvcc >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9943) Update documentation for default WAL archive size (added auto-adjust)
[ https://issues.apache.org/jira/browse/IGNITE-9943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696657#comment-16696657 ] Artem Budnikov commented on IGNITE-9943: [~agoncharuk] I updated the WAL archive section: [https://apacheignite.readme.io/v2.6/docs/write-ahead-log-1#section-wal-archive] Please review. > Update documentation for default WAL archive size (added auto-adjust) > - > > Key: IGNITE-9943 > URL: https://issues.apache.org/jira/browse/IGNITE-9943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9943) Update documentation for default WAL archive size (added auto-adjust)
[ https://issues.apache.org/jira/browse/IGNITE-9943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-9943: -- Assignee: Alexey Goncharuk (was: Artem Budnikov) > Update documentation for default WAL archive size (added auto-adjust) > - > > Key: IGNITE-9943 > URL: https://issues.apache.org/jira/browse/IGNITE-9943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9943) Update documentation for default WAL archive size (added auto-adjust)
[ https://issues.apache.org/jira/browse/IGNITE-9943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-9943: -- Assignee: Artem Budnikov > Update documentation for default WAL archive size (added auto-adjust) > - > > Key: IGNITE-9943 > URL: https://issues.apache.org/jira/browse/IGNITE-9943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8212) Binary Client Protocol spec: Key-Value Queries clarifications
[ https://issues.apache.org/jira/browse/IGNITE-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-8212: -- Assignee: Artem Budnikov (was: Igor Sapego) > Binary Client Protocol spec: Key-Value Queries clarifications > - > > Key: IGNITE-8212 > URL: https://issues.apache.org/jira/browse/IGNITE-8212 > Project: Ignite > Issue Type: Improvement > Components: documentation, thin client >Affects Versions: 2.4 >Reporter: Alexey Kosenchuk >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > https://apacheignite.readme.io/v2.4/docs/binary-client-protocol-key-value-operations > - all operations - "Flag. Pass 0 for default, or 1 to keep the value in > binary form": > -- remove words about binary form and keep "Pass 0 for default" for all > operations where this flag has no meaning. > -- clarify about binary form in operations where it has a meaning. > - OP_CACHE_GET: clarify that null is returned if the provided key does not > exist in the cache. > - OP_CACHE_GET_AND_PUT: clarify that new entry is created, if the provided > key does not exist in the cache, and null is returned in this case. > - OP_CACHE_GET_AND_REPLACE: > -- "if and only if there is a value currently mapped for that key" - is > confusing. Is it possible that an existing key has no associated value? > Suggest to rephrase as "if and only if the key exists in the cache" > -- clarify that null is returned if the key does not exist in the cache. > - OP_CACHE_GET_AND_REMOVE: clarify that null is returned if the key does not > exist in the cache. > - OP_CACHE_PUT_IF_ABSENT: clarify what is "Success Flag" - true if the new > entry is created, false if the specified key already exists in the cache. > - OP_CACHE_GET_AND_PUT_IF_ABSENT: "Previously contained value regardless of > whether put happened or not" - is confusing. Suggest to rewrite "the current > value associated with the key if it already exists in the cache, null if the > new entry is created". > - OP_CACHE_GET_SIZE: clarify Peek modes > - OP_CACHE_CLEAR_XXX and OP_CACHE_REMOVE_XXX: > -- what is the difference between the corresponding operations? Only in > notifying / not notifying listeners and cache writers? Or there are other > differences not clarified by the spec? > -- (the operations could be combined in one set - with a flag required/not > required notifications) > -- there is OP_CACHE_REMOVE_IF_EQUALS. But there is no > OP_CACHE_CLEAR_IF_EQUALS. Is it intentional? > -- OP_CACHE_REMOVE_KEY and OP_CACHE_REMOVE_IF_EQUALS have "Value indicating > whether remove happened" in the response. But OP_CACHE_CLEAR_KEY does not > have such a flag in the response. Is it intentional? > -- OP_CACHE_CLEAR_KEYS, OP_CACHE_REMOVE_KEYS: clarify that even if some of > the specified keys do not exist other entries are removed anyway. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7525) ODBC: Add a note about connection non-thread safety to docs
[ https://issues.apache.org/jira/browse/IGNITE-7525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov resolved IGNITE-7525. Resolution: Won't Fix > ODBC: Add a note about connection non-thread safety to docs > --- > > Key: IGNITE-7525 > URL: https://issues.apache.org/jira/browse/IGNITE-7525 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > Our ODBC connection is not thread safe and thus operations on the specific > connection can be only done from a single thread. Let's mention it in docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7525) ODBC: Add a note about connection non-thread safety to docs
[ https://issues.apache.org/jira/browse/IGNITE-7525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691497#comment-16691497 ] Artem Budnikov commented on IGNITE-7525: This is already described here: https://apacheignite-sql.readme.io/docs/odbc-driver#thread-safety > ODBC: Add a note about connection non-thread safety to docs > --- > > Key: IGNITE-7525 > URL: https://issues.apache.org/jira/browse/IGNITE-7525 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > Our ODBC connection is not thread safe and thus operations on the specific > connection can be only done from a single thread. Let's mention it in docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7525) ODBC: Add a note about connection non-thread safety to docs
[ https://issues.apache.org/jira/browse/IGNITE-7525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-7525: -- Assignee: Artem Budnikov (was: Igor Sapego) > ODBC: Add a note about connection non-thread safety to docs > --- > > Key: IGNITE-7525 > URL: https://issues.apache.org/jira/browse/IGNITE-7525 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > Our ODBC connection is not thread safe and thus operations on the specific > connection can be only done from a single thread. Let's mention it in docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
