[jira] [Assigned] (IGNITE-12991) Calcite integration. Pass cancel flag to VolcanoPlanner
[
https://issues.apache.org/jira/browse/IGNITE-12991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich reassigned IGNITE-12991:
--
Assignee: Yury Gerzhedovich
> Calcite integration. Pass cancel flag to VolcanoPlanner
> ---
>
> Key: IGNITE-12991
> URL: https://issues.apache.org/jira/browse/IGNITE-12991
> Project: Ignite
> Issue Type: Improvement
>Reporter: Igor Seliverstov
>Assignee: Yury Gerzhedovich
>Priority: Minor
>
> see {{AbstractRelOptPlanner.java:91}}, here {{CancelFlag}} is used to cancel
> planning loop. We need to pass it into a newly created context and bind its
> state with {{PlanningContext#queryCancel}} to break possible infinite
> planning loop. See also {{PlanningContext#unwrap}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14224) Extend logging of client failure handling.
[ https://issues.apache.org/jira/browse/IGNITE-14224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17302263#comment-17302263 ] Stanilovsky Evgeny commented on IGNITE-14224: - [~sergey-chugunov] [~ptupitsyn] thanks for review, all done. > Extend logging of client failure handling. > -- > > Key: IGNITE-14224 > URL: https://issues.apache.org/jira/browse/IGNITE-14224 > Project: Ignite > Issue Type: Improvement > Components: clients >Affects Versions: 2.9.1 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > # "Finished serving remote node connection " but this message doesn't contain > node id, it should be added (check > org.apache.ignite.spi.discovery.tcp.ServerImpl.SocketReader#body). > # When client worker is removed from clientMsgWorkers, > org.apache.ignite.internal.util.IgniteUtils#closeQuiet(java.lang.AutoCloseable) > is used to close the socket, we don't see any exception if it has happened, > closeQuiet should be replaced with > org.apache.ignite.internal.util.IgniteUtils#close(java.lang.AutoCloseable, > org.apache.ignite.IgniteLogger) which works in the same way but prints > exception. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14321) Forced index rebuilding does not work correctly
Kirill Tkalenko created IGNITE-14321: Summary: Forced index rebuilding does not work correctly Key: IGNITE-14321 URL: https://issues.apache.org/jira/browse/IGNITE-14321 Project: Ignite Issue Type: Bug Components: sql Reporter: Kirill Tkalenko Assignee: Kirill Tkalenko Fix For: 2.11 At the moment, it is not possible to force an index rebuild twice (or more) even if the first run fails, and this also applies to command *control.sh --cache indexes_force_rebuild*. Thus, you need to fix: * *GridCacheDatabaseSharedManager#forceRebuildIndexes* * *CacheIndexesForceRebuild#execute* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14321) Forced index rebuilding does not work correctly
[ https://issues.apache.org/jira/browse/IGNITE-14321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-14321: - Description: At the moment, it is not possible to force an index rebuild twice (or more) even if the first run fails, and this also applies to command *control.sh --cache indexes_force_rebuild*. Thus, we need to fix: * *GridCacheDatabaseSharedManager#forceRebuildIndexes* * *CacheIndexesForceRebuild#execute* was: At the moment, it is not possible to force an index rebuild twice (or more) even if the first run fails, and this also applies to command *control.sh --cache indexes_force_rebuild*. Thus, you need to fix: * *GridCacheDatabaseSharedManager#forceRebuildIndexes* * *CacheIndexesForceRebuild#execute* > Forced index rebuilding does not work correctly > --- > > Key: IGNITE-14321 > URL: https://issues.apache.org/jira/browse/IGNITE-14321 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.11 > > > At the moment, it is not possible to force an index rebuild twice (or more) > even if the first run fails, and this also applies to command *control.sh > --cache indexes_force_rebuild*. > Thus, we need to fix: > * *GridCacheDatabaseSharedManager#forceRebuildIndexes* > * *CacheIndexesForceRebuild#execute* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13524) Ignite Docs: fix Jekyll warnings reported during docs transformation to HTML
[
https://issues.apache.org/jira/browse/IGNITE-13524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-13524:
-
Fix Version/s: (was: 2.10)
2.11
> Ignite Docs: fix Jekyll warnings reported during docs transformation to HTML
>
>
> Key: IGNITE-13524
> URL: https://issues.apache.org/jira/browse/IGNITE-13524
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Reporter: Denis A. Magda
>Priority: Major
> Labels: new-docs
> Fix For: 2.11
>
>
> Try to build the docs with the `run.sh` command located in the docs' root
> folder:
> https://github.com/apache/ignite/tree/master/docs
> Jekyll will report many warnings that need to be reviewed and handled. Some
> of the warnings are printed below:
> {noformat}
> There is an empty tab (C#/.NET) on the JDBC Driver page:
> /Users/dmagda/ignite-website/_docs/_docs/SQL/JDBC/jdbc-driver.adoc
> There is an empty tab (C++) on the JDBC Driver page:
> /Users/dmagda/ignite-website/_docs/_docs/SQL/JDBC/jdbc-driver.adoc
> There is an empty tab (C++) on the SQL Performance Tuning page:
> /Users/dmagda/ignite-website/_docs/_docs/SQL/sql-tuning.adoc
> There is an empty tab (C++) on the Baseline Topology page:
> /Users/dmagda/ignite-website/_docs/_docs/clustering/baseline-topology.adoc
> There is an empty tab (C++) on the Baseline Topology page:
> /Users/dmagda/ignite-website/_docs/_docs/clustering/baseline-topology.adoc
> There is an empty tab (C++) on the Baseline Topology page:
> /Users/dmagda/ignite-website/_docs/_docs/clustering/baseline-topology.adoc
> There is an empty tab (C#/.NET) on the Connecting Client Nodes page:
> /Users/dmagda/ignite-website/_docs/_docs/clustering/connect-client-nodes.adoc
> There is an empty tab (C#/.NET) on the Connecting Client Nodes page:
> /Users/dmagda/ignite-website/_docs/_docs/clustering/connect-client-nodes.adoc
> There is an empty tab (C++) on the Connecting Client Nodes page:
> /Users/dmagda/ignite-website/_docs/_docs/clustering/connect-client-nodes.adoc
> There is an empty tab (C#/.NET) on the Connecting Client Nodes page:
> /Users/dmagda/ignite-website/_docs/_docs/clustering/connect-client-nodes.adoc
> There is an empty tab (C++) on the Deploying User Code page:
> /Users/dmagda/ignite-website/_docs/_docs/code-deployment/deploying-user-code.adoc
> There is an empty tab (C#/.NET) on the Deploying User Code page:
> /Users/dmagda/ignite-website/_docs/_docs/code-deployment/deploying-user-code.adoc
> There is an empty tab (C++) on the Deploying User Code page:
> /Users/dmagda/ignite-website/_docs/_docs/code-deployment/deploying-user-code.adoc
> asciidoctor: WARNING: : line 56: id assigned to anchor already in use:
> readfrombackup
> There is an empty tab (C++) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C#/.NET) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C++) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C#/.NET) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C++) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C#/.NET) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C++) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C#/.NET) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C++) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> asciidoctor: ERROR: configuration.adoc: line 3: level 0 sections can only be
> used when doctype is book
> Improper use of Lexer#lex - this method does not receive options. This will
> become an error in a future version.
> Improper use of Lexer#lex - this method does not receive options. This will
> become an error in a future version.
> Improper use of Lexer#lex - this method does not receive options. This will
> become an error in a future version.
> Improper use of Lexer#lex - this method does not receive options. This will
> become an error in a future version.
> There is an empty tab (C#/.NET)
[jira] [Updated] (IGNITE-11020) Document edge-chasing deadlock detection
[ https://issues.apache.org/jira/browse/IGNITE-11020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11020: - Fix Version/s: (was: 2.10) 2.11 > Document edge-chasing deadlock detection > > > Key: IGNITE-11020 > URL: https://issues.apache.org/jira/browse/IGNITE-11020 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Ivan Pavlukhin >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.11 > > > Documentation for deadlock detection implemented in related ticket is needed. > Initially detection was implemented for MVCC caches. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9091) IEP-25: creating documentation
[ https://issues.apache.org/jira/browse/IGNITE-9091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-9091: Fix Version/s: (was: 2.10) 2.11 > 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.11 > > > 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-11057) Document new SQL system view "CACHE_GROUPS_IO"
[
https://issues.apache.org/jira/browse/IGNITE-11057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11057:
-
Fix Version/s: (was: 2.10)
2.11
> Document new SQL system view "CACHE_GROUPS_IO"
> --
>
> Key: IGNITE-11057
> URL: https://issues.apache.org/jira/browse/IGNITE-11057
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Reporter: Vladimir Ozerov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.11
>
>
> See
> {{modules\indexing\src\main\java\org\apache\ignite\internal\processors\query\h2\sys\view\SqlSystemViewCacheGroupsIOStatistics.java}}
> # {{GROUP_ID}} - cache group ID
> # {{GROUP_ID}} - cache group name
> # {{PHYSICAL_READS}} - number of physical reads (i.e. block read from disk)
> for the given group
> # {{LOGICAL_READS}} - number of logical reads (i.e. from buffer cache) for
> the given group.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-9856) Update documentation for control.sh --cache list
[
https://issues.apache.org/jira/browse/IGNITE-9856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-9856:
Fix Version/s: (was: 2.10)
2.11
> Update documentation for control.sh --cache list
>
>
> Key: IGNITE-9856
> URL: https://issues.apache.org/jira/browse/IGNITE-9856
> Project: Ignite
> Issue Type: Improvement
> Components: control.sh, documentation
>Reporter: Sergey Antonov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.11
>
>
> {{Documentation for option --cache list in control.sh}} must be updated.
> As reference could be used help message:
> {noformat}
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User: santonov
>
> The '--cache subcommand' is used to get information about and perform
> actions with caches. The command has the following syntax:
> control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
> PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
> --cache[subcommand]
> The subcommands that take [nodeId] as an argument ('list', 'contention' and
> 'validate_indexes') will be executed on the given node or on all server nodes
> if the option is not specified. Other commands will run on a random server
> node.
> Subcommands:
>
>
> --cache list regexPattern [groups|seq] [nodeId] [--config] [--output-format
> multi-line]
> Show information about caches, groups or sequences that match a regular
> expression. When executed without parameters, this subcommand prints the list
> of caches.
> Parameters:
> --config- print a all configuration parameters for
> each cache.
> --output-format multi-line - print configuration parameters per line.
> This option has effect only when used with --config and without [groups|seq].
>
>
> --cache contention minQueueSize [nodeId] [maxPrint]
> Show the keys that are point of contention for multiple transactions.
>
>
> --cache idle_verify [--dump] [--skipZeros] [cache1,...,cacheN]
> Verify counters and hash sums of primary and backup partitions for the
> specified caches on an idle cluster and print out the differences, if any.
>
>
> --cache validate_indexes [cache1,...,cacheN] [nodeId] [checkFirst
> N|checkThrough K]
> Validate indexes on an idle cluster and print out the keys that are
> missing in the indexes.
> Parameters:
> checkFirst N- validate only the first N keys
> checkThrough K - validate every Kth key
>
>
> --cache distribution nodeId|null [cacheName1,...,cacheNameN]
> [--user-attributes attName1,...,attrNameN]
> Prints the information about partition distribution.
>
>
> --cache reset_lost_partitions cacheName1,...,cacheNameN
> Reset the state of lost partitions for the specified caches.
> {noformat}
> And output example:
> {noformat}
> control.sh --cache list .* --config --yes
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User: santonov
>
> ignite-sys-cache: [name=ignite-sys-cache, grpName=null, mode=REPLICATED,
> atomicityMode=TRANSACTIONAL, eagerTtl=true,
> writeSynchronizationMode=FULL_SYNC, invalidate=false,
> maxConcurrentAsyncOps=500, interceptor=null, dfltLockTimeout=0,
> affinityCfg=VisorCacheAffinityConfiguration
> [function=o.a.i.cache.affinity.rendezvous.RendezvousAffinityFunction,
> mapper=o.a.i.i.processors.cache.GridCacheDefaultAffinityKeyMapper,
> partitionedBackups=2147483647, partitions=100, exclNeighbors=false],
> rebalanceCfg=VisorCacheRebalanceConfiguration [mode=SYNC, batchSize=524288,
> partitionedDelay=0, throttle=0, timeout=1, batchesPrefetchCnt=2,
> rebalanceOrder=-2], evictCfg=VisorCacheEvictionConfiguration [plc=null,
> plcMaxSize=null, filter=null], nearCfg=VisorCacheNearConfiguration
> [nearEnabled=false, nearStartSize=0, nearEvictPlc=null,
> nearEvictMaxSize=null], storeCfg=VisorCacheStoreConfiguration
> [jdbcStore=false, store=null, storeFactory=null, readThrough=false,
> writeThrough=false, writeB
[jira] [Updated] (IGNITE-10845) Ignite Production Readiness Section Enhancement
[ https://issues.apache.org/jira/browse/IGNITE-10845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10845: - Fix Version/s: (was: 2.10) 2.11 > Ignite Production Readiness Section Enhancement > --- > > Key: IGNITE-10845 > URL: https://issues.apache.org/jira/browse/IGNITE-10845 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.11 > > > Enhance Ignite production readiness section with points from here: > https://www.gridgain.com/resources/blog/checklist-assembling-your-first-apacher-ignitetm-cluster -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10710) Document new REST API for baseline topology command.
[ https://issues.apache.org/jira/browse/IGNITE-10710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10710: - Fix Version/s: (was: 2.10) 2.11 > Document new REST API for baseline topology command. > > > Key: IGNITE-10710 > URL: https://issues.apache.org/jira/browse/IGNITE-10710 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.8 >Reporter: Andrey Novikov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.11 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-7704) Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations
[ https://issues.apache.org/jira/browse/IGNITE-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-7704: Fix Version/s: (was: 2.10) 2.11 > Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts > and their relations > --- > > Key: IGNITE-7704 > URL: https://issues.apache.org/jira/browse/IGNITE-7704 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.3 >Reporter: Alexey Popov >Assignee: Stanislav Lukyanov >Priority: Major > Fix For: 2.11 > > Attachments: timeouts.md, timeouts_v2.md > > > We often see similar questions related to IgniteConfiguration, > TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations. And we see > several side-effects after incorrect timeout configuration. > It looks like this question is not well documented. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9485) Update documentation for ScanQuery with setLocal flag
[ https://issues.apache.org/jira/browse/IGNITE-9485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-9485: Fix Version/s: (was: 2.10) 2.11 > Update documentation for ScanQuery with setLocal flag > - > > Key: IGNITE-9485 > URL: https://issues.apache.org/jira/browse/IGNITE-9485 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.11 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9547) Document DML operations prohibited inside transaction
[ https://issues.apache.org/jira/browse/IGNITE-9547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-9547: Fix Version/s: (was: 2.10) 2.11 > Document DML operations prohibited inside transaction > - > > Key: IGNITE-9547 > URL: https://issues.apache.org/jira/browse/IGNITE-9547 > Project: Ignite > Issue Type: Task > Components: documentation, sql >Reporter: Yury Gerzhedovich >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.11 > > > Docs says: > ""Presently, DML supports the atomic mode only meaning that if there is a DML > query that is executed as a part of an Ignite transaction then it will not be > enlisted in the transaction's writing queue and will be executed right away"" > However it's wrong. > We need to document that now any DML operations is prohibited and throw > Exception in case it will be executed inside a transaction. > > Also appeared new boolean property IGNITE_ALLOW_DML_INSIDE_TRANSACTION. it is > necessary to emulate the old behavior. In case value is true then DML > operation is allowed, but it be applied only after transaction will be > commited. > By default value is false. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10741) MVCC: Document disabled page evictions for in-memory MVCC caches.
[
https://issues.apache.org/jira/browse/IGNITE-10741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-10741:
-
Fix Version/s: (was: 2.10)
2.11
> MVCC: Document disabled page evictions for in-memory MVCC caches.
> -
>
> Key: IGNITE-10741
> URL: https://issues.apache.org/jira/browse/IGNITE-10741
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Roman Kondakov
>Priority: Major
> Fix For: 2.11
>
>
> Currently data pages evictions are disabled for {{TRANSACTIONAL_SNAPSHOT}}
> caches because it can cause violations for repeatable read guarantees.
> User should either disable evictions or enable persistence in such cases.
> We should reflect it in our documentation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-10268) Remove documentation about "replicatedOnly" flag
[ https://issues.apache.org/jira/browse/IGNITE-10268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10268: - Fix Version/s: (was: 2.10) 2.11 > Remove documentation about "replicatedOnly" flag > > > Key: IGNITE-10268 > URL: https://issues.apache.org/jira/browse/IGNITE-10268 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.11 > > > SqlQuery.replicatedOnly and SqlFieldsQuery.replicatedOnly flags were > deprecated. Need to remove all places where it is mentioned from docs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10947) CPP: Fix documentation on how to build Ignite C++ on Linux
[
https://issues.apache.org/jira/browse/IGNITE-10947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-10947:
-
Fix Version/s: (was: 2.10)
2.11
> CPP: Fix documentation on how to build Ignite C++ on Linux
> --
>
> Key: IGNITE-10947
> URL: https://issues.apache.org/jira/browse/IGNITE-10947
> Project: Ignite
> Issue Type: Improvement
> Components: documentation, platforms
>Reporter: Igor Sapego
>Priority: Major
> Fix For: 2.11
>
>
> We now have build step (IGNITE-10940) that performs following steps during
> release of the binary package of the Ignite:
> {code}
> # libtoolize
> # aclocal
> # autoheader
> # automake --add-missing
> # autoreconf
> {code}
> So we now should change documentation, that users only need to run following
> commands to build Ignite C++ from binary distribution of Ignite.
> {code}
> # ./configure
> # make
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-8411) Binary Client Protocol spec: other parts clarifications
[ https://issues.apache.org/jira/browse/IGNITE-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-8411: Fix Version/s: (was: 2.10) 2.11 > Binary Client Protocol spec: other parts clarifications > --- > > Key: IGNITE-8411 > URL: https://issues.apache.org/jira/browse/IGNITE-8411 > Project: Ignite > Issue Type: Improvement > Components: documentation, thin client >Affects Versions: 2.4 >Reporter: Alexey Kosenchuk >Assignee: Igor Sapego >Priority: Major > Fix For: 2.11 > > > issues against previous parts: IGNITE-8039 IGNITE-8212 > Cache Configuration > --- > > [https://apacheignite.readme.io/docs/binary-client-protocol-cache-configuration-operations] > - OP_CACHE_GET_CONFIGURATION and OP_CACHE_CREATE_WITH_CONFIGURATION - > QueryEntity - Structure of QueryField: > absent "default value - type Object" - it is the last field of the > QueryField in reality. > - OP_CACHE_GET_CONFIGURATION - Structure of Cache Configuration: > Absent CacheAtomicityMode - is the first field in reality. > Absent MaxConcurrentAsyncOperations - is between DefaultLockTimeout and > MaxQueryIterators in reality. > "Invalidate" field - does not exist in reality. > - meaning and possible values of every configuration parameter must be > clarified. If clarified in other docs, this spec must have link(s) to that > docs. > - suggest to combine somehow Cache Configuration descriptions in > OP_CACHE_GET_CONFIGURATION and OP_CACHE_CREATE_WITH_CONFIGURATION - to avoid > duplicated descriptions. > SQL and Scan Queries > > [https://apacheignite.readme.io/docs/binary-client-protocol-sql-operations] > - "Flag. Pass 0 for default, or 1 to keep the value in binary form.": > "the value in binary form" flag should be left end clarified in the > operations to which it is applicable for. > - OP_QUERY_SQL: > most of the fields in the request must be clarified. If clarified in other > docs, this spec must have link(s) to that docs. > For example: > ** "Name of a type or SQL table": name of what type? > - OP_QUERY_SQL_FIELDS: > most of the fields in the request must be clarified. If clarified in other > docs, this spec must have link(s) to that docs. > For example: > ** is there any correlation between "Query cursor page size" and "Max rows"? > ** "Statement type": why there are only three types? what about INSERT, etc.? > - OP_QUERY_SQL_FIELDS_CURSOR_GET_PAGE Response does not contain Cursor id. > But responses for all other query operations contain it. Is it intentional? > - OP_QUERY_SCAN_CURSOR_GET_PAGE Response - Cursor id is absent in reality. > - OP_QUERY_SCAN_CURSOR_GET_PAGE Response - Row count field: says type > "long". Should be "int". > - OP_QUERY_SCAN: > format and rules of the Filter object must be clarified. If clarified in > other docs, this spec must have link(s) to that docs. > - OP_QUERY_SCAN: > in general, it's not clear how this operation should be supported on > platforms other than the mentioned in "Filter platform" field. > - OP_QUERY_SCAN: "Number of partitions to query" > Should be updated to "A partition number to query" > > Binary Types > > > [https://apacheignite.readme.io/docs/binary-client-protocol-binary-type-operations] > - somewhere should be explained when and why these operations need to be > supported by a client. > - Type id and Field id: > should be clarified that before an Id calculation Type and Field names must > be updated to low case. > - OP_GET_BINARY_TYPE and OP_PUT_BINARY_TYPE - BinaryField - Type id: > in reality it is not a type id (hash code) but a type code (1, 2,... 10,... > 103,...). > - OP_GET_BINARY_TYPE and OP_PUT_BINARY_TYPE - "Affinity key field name": > should be explained what is it. If explained in other docs, this spec must > have link(s) to that docs. > - OP_PUT_BINARY_TYPE - schema id: > mandatory algorithm of schema Id calculation must be described somewhere. If > described in other docs, this spec must have link(s) to that docs. > - OP_REGISTER_BINARY_TYPE_NAME and OP_GET_BINARY_TYPE_NAME: > should be explained when and why these operations need to be supported by a > client. > How this operation should be supported on platforms other than the mentioned > in "Platform id" field. > - OP_REGISTER_BINARY_TYPE_NAME: > Type name - is it "full" or "short" name here? > Type id - is it a hash from "full" or "short" name here? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-4221) Document ComputeJobMasterLeaveAware interface usage
[ https://issues.apache.org/jira/browse/IGNITE-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-4221: Fix Version/s: (was: 2.10) 2.11 > Document ComputeJobMasterLeaveAware interface usage > --- > > Key: IGNITE-4221 > URL: https://issues.apache.org/jira/browse/IGNITE-4221 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.11 > > > The usage and applicability of `ComputeJobMasterLeaveAware` have to be > documented on Apache Ignite Readme.io which will help out to avoid discussion > like that [1]. The new page has to be created for the topic and placed here > [2]. > In advance, the following example has to be contributed to Apache Ignite > https://github.com/gridgain/gridgain-advanced-examples/blob/master/src/main/java/org/gridgain/examples/compute/masterleave/ComputeMasterLeaveAwareExample.java > > [1] > http://apache-ignite-users.70518.x6.nabble.com/Remote-Server-Thread-Not-exit-when-Job-finished-Cause-out-of-memory-tp8934p8947.html > [2] https://apacheignite.readme.io/docs/compute-grid#section-features -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (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 ] Maxim Muzafarov updated IGNITE-6526: Fix Version/s: (was: 2.10) 2.11 > 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 A. Magda >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.11 > > > 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 (v8.3.4#803005)
[jira] [Updated] (IGNITE-11184) add example of ssl rest protocol on ignite
[ https://issues.apache.org/jira/browse/IGNITE-11184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11184: - Fix Version/s: (was: 2.10) 2.11 > add example of ssl rest protocol on ignite > -- > > Key: IGNITE-11184 > URL: https://issues.apache.org/jira/browse/IGNITE-11184 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.7 >Reporter: ARomantsov >Priority: Critical > Fix For: 2.11 > > > Add information about ssl Jetty configuration to ignite documentation about > restApi > https://apacheignite.readme.io/docs/rest-api#sample-jetty-xml-configuration -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9716) Document partition distribution and reset lost partitions commands of control script
[ https://issues.apache.org/jira/browse/IGNITE-9716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-9716: Fix Version/s: (was: 2.10) 2.11 > Document partition distribution and reset lost partitions commands of control > script > > > Key: IGNITE-9716 > URL: https://issues.apache.org/jira/browse/IGNITE-9716 > Project: Ignite > Issue Type: Task > Components: control.sh, documentation >Affects Versions: 2.7 >Reporter: Alexey Goncharuk >Priority: Major > Fix For: 2.11 > > > See [IGNITE-9549] - > control.sh add command to collect information on the distribution of > partitions and reset lost partitions > for details. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11064) Add documentation for enabling cache statistics only on appropriate nodes.
[ https://issues.apache.org/jira/browse/IGNITE-11064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11064: - Fix Version/s: (was: 2.10) 2.11 > Add documentation for enabling cache statistics only on appropriate nodes. > -- > > Key: IGNITE-11064 > URL: https://issues.apache.org/jira/browse/IGNITE-11064 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7 >Reporter: Stanilovsky Evgeny >Priority: Major > Fix For: 2.11 > > > System property: IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE (false > default) will disable statistic collecting even if statisticsEnabled flag is > true. > [IGNITE-10172|https://issues.apache.org/jira/browse/IGNITE-10172] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11187) Additional documentation for re-balancing is canceled if client node joins.
[ https://issues.apache.org/jira/browse/IGNITE-11187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11187: - Fix Version/s: (was: 2.10) 2.11 > Additional documentation for re-balancing is canceled if client node joins. > --- > > Key: IGNITE-11187 > URL: https://issues.apache.org/jira/browse/IGNITE-11187 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7 >Reporter: Stanilovsky Evgeny >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.11 > > > Need additional documentation for [IGNITE-7165] Re-balancing is canceled if > client node joins. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11252) Docs: Index corruption recovery procedure
[ https://issues.apache.org/jira/browse/IGNITE-11252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11252: - Fix Version/s: (was: 2.10) 2.11 > Docs: Index corruption recovery procedure > - > > Key: IGNITE-11252 > URL: https://issues.apache.org/jira/browse/IGNITE-11252 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.7 >Reporter: Denis A. Magda >Assignee: Prachi Garg >Priority: Critical > Fix For: 2.11 > > > We need to document a recovery procedure if an index corruption happens. > Refer to this thread for details and examples of the exception dumped to the > logs if the issue occurs: > http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-index-corruption-issue-gt-unrecoverable-cluster-td39869.html > # Recovering from an index corruption > ## Applicable if > It is known that an index of a cache is corrupted, but the main data > (partition files and WAL) is fine. Show code snippets of possible examples. > Find via the references shared in the dev list discussion. > ## Steps to recover > 1. Stop the node > 2. Delete index.bin of the affected caches (path is > db//cache-/index.bin) > 3. Start the node > - Note: At this point the node is active in the cluster but don’t have > indexes. > It means that it serves SQL queries but their performance can be low. > Avoid running SQL queries on large tables at this point > 4. Wait for message “Finished indexes rebuilding for cache ” in > the Ignite log > # Recovering from a persistent storage corruption > ## Applicable if > A part of the persistent storage (partition files, checkpoint markers or WAL) > was corrupted > and there is no other way to recover it, but there are healthy copies of all > data on other nodes. > ## Steps to recover > 1. Stop the node > 2. Delete all persistence files of the node (best to clear Ignite working > directory, storage directory, WAL and WAL archive directories) > 3. Make sure consistentId is explicitly set in the configuration of the node > - If it isn’t, lookup the generated consistentId using control.sh and set it > explicitly in the config or via IGNITE_CONSISTENT_ID (2.8+ only) > 4. Start the node > 5. Wait for messages for all caches -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10880) Document how we should evolve our persistence functionality while keeping it compatible with files created by old versions
[ https://issues.apache.org/jira/browse/IGNITE-10880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10880: - Fix Version/s: (was: 2.10) 2.11 > Document how we should evolve our persistence functionality while keeping it > compatible with files created by old versions > -- > > Key: IGNITE-10880 > URL: https://issues.apache.org/jira/browse/IGNITE-10880 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Eduard Shangareev >Assignee: Alexey Goncharuk >Priority: Critical > Fix For: 2.11 > > > It's not documented at all (???). > We need complete documentation to not break compatibility with previously > created database files while updating/evolving code. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11427) Document custom node fail functional.
[ https://issues.apache.org/jira/browse/IGNITE-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11427: - Fix Version/s: (was: 2.10) 2.11 > 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: Critical > Fix For: 2.11 > > 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 (v8.3.4#803005)
[jira] [Updated] (IGNITE-11630) Document changes to SQL views
[
https://issues.apache.org/jira/browse/IGNITE-11630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11630:
-
Fix Version/s: (was: 2.10)
2.11
> Document changes to SQL views
> -
>
> Key: IGNITE-11630
> URL: https://issues.apache.org/jira/browse/IGNITE-11630
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Reporter: Vladimir Ozerov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.11
>
>
> The following changes were made to our views.
> {{CACHE_GROUPS}}
> # {{ID}} -> {{CACHE_GROUP_ID}}
> # {{GROUP_NAME}} -> {{CACHE_GROUP_NAME}}
> {{LOCAL_CACHE_GROUPS_IO}}
> # {{GROUP_ID}} -> {{CACHE_GROUP_ID}}
> # {{GROUP_NAME}} -> {{CACHE_GROUP_NAME}}
> {{CACHES}}
> # {{NAME}} -> {{CACHE_NAME}}
> # {{GROUP_ID}} -> {{CACHE_GROUP_ID}}
> # {{GROUP_NAME}} -> {{CACHE_GROUP_NAME}}
> {{INDEXES}}
> # {{GROUP_ID}} -> {{CACHE_GROUP_ID}}
> # {{GROUP_NAME}} -> {{CACHE_GROUP_NAME}}
> {{NODES}}
> # {{ID}} -> {{NODE_ID}}
> {{TABLES}}
> # Added {{CACHE_GROUP_ID}}
> # Added {{CACHE_GROUP_NAME}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-10846) Improve docs for "Disabling WAL Archiving"
[ https://issues.apache.org/jira/browse/IGNITE-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10846: - Fix Version/s: (was: 2.10) 2.11 > 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.11 > > > Provide pros and cons of disabling WAL Archiving. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11628) Document the possibility to use JAR files in UriDeploymentSpi
[
https://issues.apache.org/jira/browse/IGNITE-11628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11628:
-
Fix Version/s: (was: 2.10)
2.11
> Document the possibility to use JAR files in UriDeploymentSpi
> -
>
> Key: IGNITE-11628
> URL: https://issues.apache.org/jira/browse/IGNITE-11628
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Denis Mekhanikov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.11
>
>
> {{UriDeploymentSpi}} got a possibility to support regular JAR files along
> with GARs in IGNITE-11380
> This possibility should be reflected in the documentation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11404) Document CREATE TABLE "parallelism" option
[
https://issues.apache.org/jira/browse/IGNITE-11404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11404:
-
Fix Version/s: (was: 2.10)
2.11
> Document CREATE TABLE "parallelism" option
> --
>
> Key: IGNITE-11404
> URL: https://issues.apache.org/jira/browse/IGNITE-11404
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Reporter: Vladimir Ozerov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.11
>
>
> We added new {{PARALLELISM}} option:
> {code}
> CREATE TABLE ... WITH "parallelism = 4"
> {code}
> This option affect query parallelism which is otherwise set from
> {{CacheConfiguration.queryParallelism}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-9406) Improve SQL "Performance and Debugging" page
[ https://issues.apache.org/jira/browse/IGNITE-9406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-9406: Fix Version/s: (was: 2.10) 2.11 > 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: Artem Budnikov >Priority: Major > Fix For: 2.11 > > 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 (v8.3.4#803005)
[jira] [Updated] (IGNITE-10649) Add documentation for control.sh about SSL
[
https://issues.apache.org/jira/browse/IGNITE-10649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-10649:
-
Fix Version/s: (was: 2.10)
2.11
> Add documentation for control.sh about SSL
> --
>
> Key: IGNITE-10649
> URL: https://issues.apache.org/jira/browse/IGNITE-10649
> Project: Ignite
> Issue Type: Task
> Components: control.sh, documentation
>Reporter: Sergey Antonov
>Priority: Major
> Fix For: 2.11
>
>
> Control.sh help output:
> {noformat}
> Control.sh is used to execute admin commands on cluster or get common cluster
> info. The command has the following syntax:
> control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
> PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
> [--ssl-protocol SSL_PROTOCOL[, SSL_PROTOCOL_2, ..., SSL_PROTOCOL_N]]
> [--ssl-cipher-suites SSL_CIPHER_1[, SSL_CIPHER_2, ..., SSL_CIPHER_N]]
> [--ssl-key-algorithm SSL_KEY_ALGORITHM] [--keystore-type KEYSTORE_TYPE]
> [--keystore KEYSTORE_PATH] [--keystore-password KEYSTORE_PASSWORD]
> [--truststore-type TRUSTSTORE_TYPE] [--truststore TRUSTSTORE_PATH]
> [--truststore-password TRUSTSTORE_PASSWORD] [command]
> This utility can do the following commands:
> Activate cluster:
> control.sh --activate
> Deactivate cluster:
> control.sh --deactivate [--yes]
> Print current cluster state:
> control.sh --state
> Print cluster baseline topology:
> control.sh --baseline
> Add nodes into baseline topology:
> control.sh --baseline add consistentId1[,consistentId2,,consistentIdN]
> [--yes]
> Remove nodes from baseline topology:
> control.sh --baseline remove consistentId1[,consistentId2,,consistentIdN]
> [--yes]
> Set baseline topology:
> control.sh --baseline set consistentId1[,consistentId2,,consistentIdN]
> [--yes]
> Set baseline topology based on version:
> control.sh --baseline version topologyVersion [--yes]
> List or kill transactions:
> control.sh --tx [--xid XID] [--min-duration SECONDS] [--min-size SIZE]
> [--label PATTERN_REGEX] [--servers|--clients] [--nodes
> consistentId1[,consistentId2,,consistentIdN]] [--limit NUMBER] [--order
> DURATION|SIZE|START_TIME] [--kill] [--yes]
> Print absolute paths of unused archived wal segments on each node:
> control.sh --wal print [consistentId1,consistentId2,,consistentIdN]
> Delete unused archived wal segments on each node:
> control.sh --wal delete [consistentId1,consistentId2,,consistentIdN]
> [--yes]
> View caches information in a cluster. For more details type:
> control.sh --cache help
> By default commands affecting the cluster require interactive confirmation.
> Use --yes option to disable it.
> Default values:
> HOST_OR_IP=127.0.0.1
> PORT=11211
> PING_INTERVAL=5000
> PING_TIMEOUT=3
> SSL_PROTOCOL=TLS
> SSL_KEY_ALGORITHM=SunX509
> KEYSTORE_TYPE=JKS
> TRUSTSTORE_TYPE=JKS
> Exit codes:
> 0 - successful execution.
> 1 - invalid arguments.
> 2 - connection failed.
> 3 - authentication failed.
> 4 - unexpected error.{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-9984) Documentation for EVT_MANAGEMENT_TASK_STARTED will be required.
[
https://issues.apache.org/jira/browse/IGNITE-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-9984:
Fix Version/s: (was: 2.10)
2.11
> Documentation for EVT_MANAGEMENT_TASK_STARTED will be required.
> ---
>
> Key: IGNITE-9984
> URL: https://issues.apache.org/jira/browse/IGNITE-9984
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.8
>Reporter: Andrey Aleksandrov
>Priority: Major
> Fix For: 2.11
>
>
> New EVT_MANAGEMENT_TASK_STARTED will be added in future release.
> Documentation for it should be added too.
> Next information should be added to web console and visor documentation:
> EVT_MANAGEMENT_TASK_STARTED provide the possibility to track next tasks that
> could be started by the user from web console and visor during some
> operations:
> +Baseline:+
> VisorBaselineTask - Task that will collect information about baseline
> topology and can change its state
> +Binaries:+
> VisorBinaryMetadataCollectorTask - Task that collects binary metadata.
> +Services:+
> VisorCancelServiceTask - Task for cancel services with the specified name.
> +Metrics:+
> VisorComputeResetMetricsTask - Task for cancel services with specified name.
> +Caches:+
> VisorCacheLostPartitionsTask - Collect list of lost partitions.
> VisorCacheResetLostPartitionsTask - Reset lost partitions for caches.
> VisorCacheStartTask - Task that start cache or near cache with specified
> configuration.
> VisorCacheStopTask - Task that stop specified caches on specified node.
> VisorCacheAffinityNodeTask - Task that will find affinity node for key.
> VisorCacheModifyTask - Task that modify value in specified cache.
> VisorCacheRebalanceTask - Pre-loads caches. Made callable just to conform
> common pattern.
> VisorCacheLoadTask - Task to loads caches.
> VisorCacheClearTask - Task that clears specified caches on specified node.
> +Queries+:
> VisorQueryResetMetricsTask - Reset compute grid query metrics.
> VisorQueryTask - Task for executing SQL fields query and get the first page
> of results.
> VisorQueryCancelTask - Task to cancel queries.
> +Computes:+
> VisorComputeResetMetricsTask - Reset compute grid metrics.
> VisorComputeCancelSessionsTask - Cancels given tasks sessions.
> +DEBUG:+
> VisorThreadDumpTask - Creates a thread dump.
> +IGFS:+
> VisorIgfsFormatTask - Format IGFS instance.
> VisorIgfsProfilerClearTask - Remove all IGFS profiler logs.
> VisorIgfsResetMetricsTask - Resets IGFS metrics.
> +LOGS:+
> VisorLogSearchTask - Search text matching in logs
> +CLUSTER:+
> VisorChangeGridActiveStateTask - Task for changing grid active state.
> VisorNodeGcTask - Task to run gc on nodes.
> VisorNodeRestartTask - Restarts nodes.
> VisorNodeStopTask - Stops nodes.
>
> {color:#33}
> {color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11965) Pyton client: Expiration policies are missed
[ https://issues.apache.org/jira/browse/IGNITE-11965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11965: - Fix Version/s: (was: 2.10) 2.11 > Pyton client: Expiration policies are missed > > > Key: IGNITE-11965 > URL: https://issues.apache.org/jira/browse/IGNITE-11965 > Project: Ignite > Issue Type: Bug > Components: documentation, thin client >Affects Versions: 2.7, 2.7.5 >Reporter: Andrey Aleksandrov >Priority: Major > Fix For: 2.11 > > > [https://apacheignite.readme.io/docs/expiry-policies] are missed but > [https://apacheignite.readme.io/docs/expiry-policies#section-eager-ttl] can > be set. > Should be added. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9758) Document data injection via the REST API
[
https://issues.apache.org/jira/browse/IGNITE-9758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-9758:
Fix Version/s: (was: 2.10)
2.11
> Document data injection via the REST API
>
>
> Key: IGNITE-9758
> URL: https://issues.apache.org/jira/browse/IGNITE-9758
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.6
>Reporter: Pavel Petroshenko
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.11
>
>
> There should a documentation on how to post data via the REST API.
>
> Just to capture what was proposed by [~ilyak] over email:
>
> {quote}REST API will convert complex BinaryObjects into JSON by default. But
> to put such objects via REST you will need to define your own
> ConnectorMessageInterceptor and plug it in. You will need to define string to
> entity mapping in onReceive. You can leave onSend returning arg.
>
> This interface should be used:
> [https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ConnectorMessageInterceptor.html].
> You need to put it into ConnectorConfiguration, which you should put into
> IgniteConfiguration.{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-10979) Add documentation for control.sh idle_verify --check-crc
[ https://issues.apache.org/jira/browse/IGNITE-10979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10979: - Fix Version/s: (was: 2.10) 2.11 > Add documentation for control.sh idle_verify --check-crc > > > Key: IGNITE-10979 > URL: https://issues.apache.org/jira/browse/IGNITE-10979 > Project: Ignite > Issue Type: New Feature > Components: control.sh, documentation >Reporter: Sergey Antonov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.11 > > > We should document new option --check-crc in control.sh idle_verify command. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10581) Document new flag to filter cache types in control.sh
[ https://issues.apache.org/jira/browse/IGNITE-10581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10581: - Fix Version/s: (was: 2.10) 2.11 > Document new flag to filter cache types in control.sh > - > > Key: IGNITE-10581 > URL: https://issues.apache.org/jira/browse/IGNITE-10581 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.11 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10699) Update documentation for control.sh
[
https://issues.apache.org/jira/browse/IGNITE-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-10699:
-
Fix Version/s: (was: 2.10)
2.11
> Update documentation for control.sh
> ---
>
> Key: IGNITE-10699
> URL: https://issues.apache.org/jira/browse/IGNITE-10699
> Project: Ignite
> Issue Type: Task
> Components: control.sh, documentation
>Reporter: Sergey Antonov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.11
>
>
> I renamed view parameters in control.sh utility. The changes are following:
> ||Was||Has been||
> |--skipZeros|--skip-zeros|
> |--cacheFilter|--cache-filter|
> |checkFirst|--check-first|
> |checkThrough|--check-through|
> |limit| --limit|
> |order|--order|
> |servers|--servers|
> |clients|--clients|
> |minDuration|--min-duration|
> |minSize|--min-size|
> |label|--label|
> |nodes|--nodes|
> |xid|--xid|
> |kill|--kill|
> |groups|--groups|
> |seq|--seq|
>
> You could find current output command {{control.sh --cache help}}
> {noformat}
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User: santonov
>
> The '--cache subcommand' is used to get information about and perform actions
> with caches. The command has the following syntax:
> control.sh [[--host HOST_OR_IP], [--port PORT], [--user USER], [--password
> PASSWORD], [--ping-interval PING_INTERVAL], [--ping-timeout PING_TIMEOUT],
> [--ssl-protocol SSL_PROTOCOL[, SSL_PROTOCOL_2, ..., SSL_PROTOCOL_N]],
> [--ssl-cipher-suites SSL_CIPHER_1[, SSL_CIPHER_2, ..., SSL_CIPHER_N]],
> [--ssl-key-algorithm SSL_KEY_ALGORITHM], [--keystore-type KEYSTORE_TYPE],
> [--keystore KEYSTORE_PATH], [--keystore-password KEYSTORE_PASSWORD],
> [--truststore-type TRUSTSTORE_TYPE], [--truststore TRUSTSTORE_PATH],
> [--truststore-password TRUSTSTORE_PASSWORD]] --cache[subcommand]
>
> The subcommands that take [nodeId] as an argument ('list', 'contention' and
> 'validate_indexes') will be executed on the given node or on all server nodes
> if the option is not specified. Other commands will run on a random server
> node.
> Subcommands:
>
> --cache list regexPattern [groups|seq] [nodeId] [--config] [--output-format
> multi-line]
> Show information about caches, groups or sequences that match a regular
> expression. When executed without parameters, this subcommand prints the list
> of caches.
> Parameters:
> --config - print a all configuration parameters for each cache.
> --output-format multi-line - print configuration parameters per line. This
> option has effect only when used with --config and without [groups|seq].
>
> --cache contention minQueueSize [nodeId] [maxPrint]
> Show the keys that are point of contention for multiple transactions.
>
> --cache idle_verify [--dump] [--skip-zeros] [cache1,...,cacheN]
> [--cache-filter ALL|SYSTEM|PERSISTENT|NOT_PERSISTENT]
> Verify counters and hash sums of primary and backup partitions for the
> specified caches on an idle cluster and print out the differences, if any.
>
> --cache validate_indexes [cache1,...,cacheN] [nodeId] [--check-first
> N|--check-through K]
> Validate indexes on an idle cluster and print out the keys that are missing
> in the indexes.
> Parameters:
> --check-first N - validate only the first N keys
> --check-through K - validate every Kth key
>
> --cache distribution nodeId|null [cacheName1,...,cacheNameN]
> [--user-attributes attrName1,...,attrNameN]
> Prints the information about partition distribution.
>
> --cache reset_lost_partitions cacheName1,...,cacheNameN
> Reset the state of lost partitions for the specified caches.{noformat}
> And {{control.sh --help}}
> {noformat}
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User: santonov
>
> Contol.sh is used to execute admin commands on cluster or get common cluster
> info. The command has the following syntax:
> control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
> PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
> [--ssl-protocol SSL_PROTOCOL[, SSL_PROTOCOL_2,
[jira] [Updated] (IGNITE-10887) .NET: Align .Net docs with Java
[ https://issues.apache.org/jira/browse/IGNITE-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10887: - Fix Version/s: (was: 2.10) 2.11 > .NET: Align .Net docs with Java > --- > > Key: IGNITE-10887 > URL: https://issues.apache.org/jira/browse/IGNITE-10887 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Priority: Critical > Fix For: 2.11 > > > It seems that the .Net docs are a bit outdated compared to Java ones. > Need to align .Net and Java docs. .Net pages which are not specific to the > platform should be replaced with a simple link to the Java docs. The docs > that have .Net-specific things (e.g. code examples) should be reworked. > The pages with issues > - Performnace Tips page > (https://apacheignite-net.readme.io/docs/performance-tips) > - Off-heap memory (https://apacheignite-net.readme.io/docs/off-heap-memory) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10895) MVCC: Document several modes of pessimistic transactions are allowed for MVCC caches.
[ https://issues.apache.org/jira/browse/IGNITE-10895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10895: - Fix Version/s: (was: 2.10) 2.11 > MVCC: Document several modes of pessimistic transactions are allowed for MVCC > caches. > - > > Key: IGNITE-10895 > URL: https://issues.apache.org/jira/browse/IGNITE-10895 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Roman Kondakov >Priority: Major > Fix For: 2.11 > > > It is need to document that for MVCC caches optimistic transactions are > prohibited as before, but there are several isolation levels are allowed now: > * READ COMMITTED > * REPEATABLE READ > * SERIALIZABLE > Actually all these levels have the same implementation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13529) Ignite Docs: create docs for OpenShift installation
[ https://issues.apache.org/jira/browse/IGNITE-13529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13529: - Fix Version/s: (was: 2.10) 2.11 > Ignite Docs: create docs for OpenShift installation > --- > > Key: IGNITE-13529 > URL: https://issues.apache.org/jira/browse/IGNITE-13529 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Critical > Labels: new-docs > Fix For: 2.11 > > > We need to create docs specific for OpenShift deployments. Check with > GridGain contributors if GridGain is ready to donate the content of the page > below to Ignite: > https://www.gridgain.com/docs/latest/installation-guide/kubernetes/openshift-deployment -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13612) Ignite Docs: Duplicate document
[ https://issues.apache.org/jira/browse/IGNITE-13612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13612: - Fix Version/s: (was: 2.10) 2.11 > Ignite Docs: Duplicate document > --- > > Key: IGNITE-13612 > URL: https://issues.apache.org/jira/browse/IGNITE-13612 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Priority: Minor > Fix For: 2.11 > > > The following two documents are duplicate. Keep one. > [https://ignite.apache.org/docs/latest/data-structures/atomic-sequence] > [https://ignite.apache.org/docs/latest/data-structures/id-generator] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11076) Add documentation for control.sh idle_verify --exclude-caches and --cache-filter
[
https://issues.apache.org/jira/browse/IGNITE-11076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11076:
-
Fix Version/s: (was: 2.10)
2.11
> Add documentation for control.sh idle_verify --exclude-caches and
> --cache-filter
>
>
> Key: IGNITE-11076
> URL: https://issues.apache.org/jira/browse/IGNITE-11076
> Project: Ignite
> Issue Type: Task
> Components: control.sh, documentation
>Reporter: Sergey Antonov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.11
>
>
> control.sh cache --help output
> {noformat}
> The '--cache subcommand' is used to get information about and perform actions
> with caches. The command has the following syntax:
> control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
> PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
> [--ssl-protocol SSL_PROTOCOL[, SSL_PROTOCOL_2, ..., SSL_PROTOCOL_N]]
> [--ssl-cipher-suites SSL_CIPHER_1[, SSL_CIPHER_2, ..., SSL_CIPHER_N]]
> [--ssl-key-algorithm SSL_KEY_ALGORITHM] [--keystore-type KEYSTORE_TYPE]
> [--keystore KEYSTORE_PATH] [--keystore-password KEYSTORE_PASSWORD]
> [--truststore-type TRUSTSTORE_TYPE] [--truststore TRUSTSTORE_PATH]
> [--truststore-password TRUSTSTORE_PASSWORD] --cache [subcommand]
>
> The subcommands that take [nodeId] as an argument ('list', 'contention' and
> 'validate_indexes') will be executed on the given node or on all server nodes
> if the option is not specified. Other commands will run on a random server
> node.
> Subcommands:
>
> --cache list regexPattern [--groups|--seq] [nodeId] [--config]
> [--output-format multi-line]
> Show information about caches, groups or sequences that match a regular
> expression. When executed without parameters, this subcommand prints the list
> of caches.
> Parameters:
> --config - print all configuration parameters for each cache.
> --output-format multi-line - print configuration parameters per line. This
> option has effect only when used with --config and without [--groups|--seq].
> --groups - print information about groups.
> --seq - print information about sequences.
>
> --cache contention minQueueSize [nodeId] [maxPrint]
> Show the keys that are point of contention for multiple transactions.
>
> --cache idle_verify [--dump] [--skip-zeros] [--check-crc] [(--exclude-caches
> cacheName1,...,cacheNameN)|(--cache-filter
> ALL|SYSTEM|PERSISTENT|NOT_PERSISTENT)|cacheName1,...,cacheNameN]
> Verify counters and hash sums of primary and backup partitions for the
> specified caches on an idle cluster and print out the differences, if any.
> Parameters:
> --check-crc - check the CRC-sum of pages stored on disk before verifying data
> consistency in partitions between primary and backup nodes.
>
> --cache validate_indexes [cacheName1,...,cacheNameN] [nodeId] [--check-first
> N|--check-through K]
> Validate indexes on an idle cluster and print out the keys that are missing
> in the indexes.
> Parameters:
> --check-first N - validate only the first N keys
> --check-through K - validate every Kth key
>
> --cache distribution nodeId|null [cacheName1,...,cacheNameN]
> [--user-attributes attrName1,...,attrNameN]
> Prints the information about partition distribution.
>
> --cache reset_lost_partitions cacheName1,...,cacheNameN
> Reset the state of lost partitions for the specified caches.{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11060) Add documentation about CacheInterceptor.
[ https://issues.apache.org/jira/browse/IGNITE-11060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11060: - Fix Version/s: (was: 2.10) 2.11 > Add documentation about CacheInterceptor. > - > > Key: IGNITE-11060 > URL: https://issues.apache.org/jira/browse/IGNITE-11060 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Sergey Antonov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.11 > > > I didn't find documentation about CacheInterceptor in > [https://apacheignite.readme.io/] > (search request [https://apacheignite.readme.io/v2.7/search?q=interceptor] ) > I think we should document this feature. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12575) Document @IgniteExperimental annotation
[ https://issues.apache.org/jira/browse/IGNITE-12575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12575: - Fix Version/s: (was: 2.10) 2.11 > Document @IgniteExperimental annotation > --- > > Key: IGNITE-12575 > URL: https://issues.apache.org/jira/browse/IGNITE-12575 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.8 >Reporter: Alexey Goncharuk >Priority: Major > Fix For: 2.11 > > > We introduced the annotation to mark APIs which are exposed to users to try > out new features, but the APIs are likely to evolve in the future. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10977) Document unsupported clear() call for MVCC caches
[
https://issues.apache.org/jira/browse/IGNITE-10977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-10977:
-
Fix Version/s: (was: 2.10)
2.11
> Document unsupported clear() call for MVCC caches
> -
>
> Key: IGNITE-10977
> URL: https://issues.apache.org/jira/browse/IGNITE-10977
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Fix For: 2.11
>
>
> Now MVCC caches don't support {{cache.clear()}} by design. So let's document
> it as a known limitations (I suppose we should have such page on readme.io)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13523) Ignite Docs: the "layout: toc" tag no longer produces a table of content
[ https://issues.apache.org/jira/browse/IGNITE-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13523: - Fix Version/s: (was: 2.10) 2.11 > Ignite Docs: the "layout: toc" tag no longer produces a table of content > > > Key: IGNITE-13523 > URL: https://issues.apache.org/jira/browse/IGNITE-13523 > Project: Ignite > Issue Type: Bug > Components: documentation, website >Reporter: Denis A. Magda >Priority: Major > Labels: new-docs > Fix For: 2.11 > > > The "layout: toc" tag that is used on some index pages of a given section is > not taken into account during the HTML generation process. > For instance, the tag is set in sources for this page: > https://github.com/apache/ignite/blob/master/docs/_docs/security/index.adoc > But the TOC is not produced for the HTML output: > https://ignite.apache.org/docs/latest/security/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[
https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-12943:
-
Fix Version/s: (was: 2.10)
2.11
> Document how to filter out metrics from registries
> --
>
> Key: IGNITE-12943
> URL: https://issues.apache.org/jira/browse/IGNITE-12943
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Denis A. Magda
>Priority: Major
> Labels: IEP-35
> Fix For: 2.11
>
>
> As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter
> out metrics for a specific exporter instance. For instance, this is how we
> can ask a JMX exporter instance to ignore the cache metrics:
> {code}
> JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi();
> jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»));
> cfg.setMetricExporterSpi(jmxSpi);
> {code}
> We should add {{Metrics Filtering}} section to this documentation page [1]
> explaining how to use the filtering. Also, I would clarify in the
> {{MetricExporterSpi.setExportFilter}} JavaDocs that the method filters out
> certain metrics from a specific exporter.
> Also, should we possibly rename the method to
> {{MetricExporterSpi.setMetricsFilter}} to make things crystal clear?
> [1] https://apacheignite.readme.io/docs/new-metrics
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13525) Ignite Docs: detect and fix broken cross-links
[ https://issues.apache.org/jira/browse/IGNITE-13525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13525: - Fix Version/s: (was: 2.10) 2.11 > Ignite Docs: detect and fix broken cross-links > -- > > Key: IGNITE-13525 > URL: https://issues.apache.org/jira/browse/IGNITE-13525 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: new-docs > Fix For: 2.11 > > > It's highly likely that some of the references/links used in the docs are > broken or point out to unreachable places. > We need to use some tool that can check all the deployed pages and report > broken references if any: > https://ignite.apache.org/docs/latest/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13585) Ignite Docs: Port AWS and GCE deployment docs from readme.io
[ https://issues.apache.org/jira/browse/IGNITE-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13585: - Fix Version/s: (was: 2.10) 2.11 > Ignite Docs: Port AWS and GCE deployment docs from readme.io > > > Key: IGNITE-13585 > URL: https://issues.apache.org/jira/browse/IGNITE-13585 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: Denis A. Magda >Priority: Critical > Labels: new-docs > Fix For: 2.11 > > > We forgot to port the following pages from readme: > * AWS Deployment: https://apacheignite.readme.io/docs/aws-deployment > * GCE Deployment: > https://apacheignite.readme.io/docs/google-compute-deployment > * RPM installation instructions: > https://apacheignite.readme.io/docs/rpm-and-deb-setup > Move the pages to the new docs and update the references on the Ignite > downloads page sot that they point to the new docs: > https://ignite.apache.org/download.cgi -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12846) Docs: ml package org.apache.ignite.ml.knn.utils.indices have no description in binary release
[
https://issues.apache.org/jira/browse/IGNITE-12846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-12846:
-
Fix Version/s: (was: 2.10)
2.11
> Docs: ml package org.apache.ignite.ml.knn.utils.indices have no description
> in binary release
> -
>
> Key: IGNITE-12846
> URL: https://issues.apache.org/jira/browse/IGNITE-12846
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Zinoviev
>Priority: Major
> Fix For: 2.11
>
>
> apache-ignite-2.8.0-bin/docs/javadoc/overview-summary.html does not contain
> description block for org.apache.ignite.ml.knn.utils.indices
> Actual:
> {code}
>
>
> href="org/apache/ignite/ml/knn/utils/indices/package-summary.html">org.apache.ignite.ml.knn.utils.indices
>
>
> {code}
> Expected:
> {code}
>
>
> href="org/apache/ignite/ml/knn/utils/indices/package-summary.html">org.apache.ignite.ml.knn.utils.indices
>
> [Some description]
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11768) CPP documentation:mention default BinaryType methods implementation
[ https://issues.apache.org/jira/browse/IGNITE-11768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11768: - Fix Version/s: (was: 2.10) 2.11 > CPP documentation:mention default BinaryType methods implementation > --- > > Key: IGNITE-11768 > URL: https://issues.apache.org/jira/browse/IGNITE-11768 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.7 >Reporter: Igor Sapego >Priority: Major > Labels: cpp > Fix For: 2.11 > > > Mention BinaryTypeDefaultHashing, BinaryTypeNonNullableType and > BinaryTypeDefaultAll classes introduced in IGNITE-11703 in documentation. > Also, use them where it is possible and appropriate in code snippets. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13528) Ignite Docs: port generic instructions for Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-13528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13528: - Fix Version/s: (was: 2.10) 2.11 > Ignite Docs: port generic instructions for Kubernetes > - > > Key: IGNITE-13528 > URL: https://issues.apache.org/jira/browse/IGNITE-13528 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: new-docs > Fix For: 2.11 > > > The legacy readme.io-based docs had these generic instructions that didn't > make it to the new docs engine: > https://apacheignite.readme.io/docs/generic-configuration > We need to merge all those pages into a single documentation page "Generic > Kubernetes Deployment" that needs to be placed under the "Installation" -> > "Kubernetes" section of the new docs: > https://ignite.apache.org/docs/latest/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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
]
Maxim Muzafarov updated IGNITE-11729:
-
Fix Version/s: (was: 2.10)
2.11
> 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.11
>
>
> 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
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13688) Ignite Docs: Port Checkpointing&Continuous Mapping from readme.io
[ https://issues.apache.org/jira/browse/IGNITE-13688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13688: - Fix Version/s: (was: 2.10) 2.11 > Ignite Docs: Port Checkpointing&Continuous Mapping from readme.io > - > > Key: IGNITE-13688 > URL: https://issues.apache.org/jira/browse/IGNITE-13688 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Priority: Major > Labels: new-docs > Fix For: 2.11 > > > The content in the link below is missing from the new version of the document: > [https://apacheignite.readme.io/docs/continuous-mapping] > [https://apacheignite.readme.io/docs/checkpointing] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13773) Ignite Docs: Port SQL Tooling from readme.io
[ https://issues.apache.org/jira/browse/IGNITE-13773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13773: - Fix Version/s: (was: 2.10) 2.11 > Ignite Docs: Port SQL Tooling from readme.io > > > Key: IGNITE-13773 > URL: https://issues.apache.org/jira/browse/IGNITE-13773 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Priority: Major > Labels: new-docs > Fix For: 2.11 > > > The content in the link below is missing from the new version of the document: > [https://apacheignite-sql.readme.io/docs/sql-tooling] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11789) Document changes of LRT diagnostic messages made in IGNITE-11392
[
https://issues.apache.org/jira/browse/IGNITE-11789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11789:
-
Fix Version/s: (was: 2.10)
2.11
> Document changes of LRT diagnostic messages made in IGNITE-11392
>
>
> Key: IGNITE-11789
> URL: https://issues.apache.org/jira/browse/IGNITE-11789
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Denis Chudov
>Priority: Major
> Fix For: 2.11
>
>
> When LRT is detected, in the case if it is active, local node creates a
> request to near (client) node to get the dump of a thread that created the
> transaction. Dump of the client node appears in server node log.
> There is new property in org.apache.ignite.mxbean.TransactionsMXBean class
> that shows is thread dumps requesting allowed or disallowed:
> *TxOwnerDumpRequestsAllowed*
> By default, dump requests are turned on.
> Log messages look like following:
> {code:java}
> Dumping the near node thread that started transaction [xidVer=]
> Stack trace of the transaction owner thread:
>
> {code}
> In case of client error or error while trying to read result:
> {code:java}
> Could not get thread dump from transaction owner near node:
> {code}
> In case of error while trying to send request:
> {code:java}
> Could not send dump request to transaction owner near node:
>
> {code}
> In case if client is already out of topology:
> {code:java}
> Could not get thread dump from transaction owner because near node is now out
> of topology. Node ID: {code}
> In case if client does not support this feature:
> {code:java}
> Could not send dump request to transaction owner near node: node does not
> support this feature.
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11487) Document IGNITE_SQL_MERGE_TABLE_MAX_SIZE property
[ https://issues.apache.org/jira/browse/IGNITE-11487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11487: - Fix Version/s: (was: 2.10) 2.11 > Document IGNITE_SQL_MERGE_TABLE_MAX_SIZE property > - > > Key: IGNITE-11487 > URL: https://issues.apache.org/jira/browse/IGNITE-11487 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Evgenii Zhuravlev >Assignee: Artem Budnikov >Priority: Critical > Fix For: 2.11 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11758) Python thin: a lot of documentation files without license header
[ https://issues.apache.org/jira/browse/IGNITE-11758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11758: - Fix Version/s: (was: 2.10) 2.11 > Python thin: a lot of documentation files without license header > > > Key: IGNITE-11758 > URL: https://issues.apache.org/jira/browse/IGNITE-11758 > Project: Ignite > Issue Type: Bug > Components: documentation, thin client >Affects Versions: 2.7 >Reporter: Igor Sapego >Assignee: Dmitry Melnichuk >Priority: Blocker > Fix For: 2.11 > > > There are a lot of .rst documentation files in modules/platforms/python/docs/ > that does not contain license header. We need either delete them if they are > auto generated or add headers to them if they are not. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13538) Ignite Docs: table missing horizontal scroll bar
[ https://issues.apache.org/jira/browse/IGNITE-13538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13538: - Fix Version/s: (was: 2.10) 2.11 > Ignite Docs: table missing horizontal scroll bar > > > Key: IGNITE-13538 > URL: https://issues.apache.org/jira/browse/IGNITE-13538 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Priority: Minor > Labels: new-docs > Fix For: 2.11 > > Attachments: image-2020-10-07-09-01-09-803.png > > > [https://ignite.apache.org/docs/latest/clustering/network-configuration] > !image-2020-10-07-09-01-09-803.png! > If the table is wide, the content on the right will not be visible > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11694) Add documentation for SqlFieldsQuery.updateBatchSize into thin clients docs
[
https://issues.apache.org/jira/browse/IGNITE-11694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11694:
-
Fix Version/s: (was: 2.10)
2.11
> Add documentation for SqlFieldsQuery.updateBatchSize into thin clients docs
> ---
>
> Key: IGNITE-11694
> URL: https://issues.apache.org/jira/browse/IGNITE-11694
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.7
>Reporter: Taras Ledkov
>Priority: Major
> Fix For: 2.11
>
>
> The property {{SqlFieldsQuery.updateBatchSize}} is introduced by the patch
> IGNITE-11499.
> ODBC, thin JDBC, thin client documentation should be changed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13918) Ignite Docs: Port Capacity Planning docs from readme.io
[ https://issues.apache.org/jira/browse/IGNITE-13918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13918: - Fix Version/s: (was: 2.10) 2.11 > Ignite Docs: Port Capacity Planning docs from readme.io > --- > > Key: IGNITE-13918 > URL: https://issues.apache.org/jira/browse/IGNITE-13918 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Priority: Major > Labels: documentation > Fix For: 2.11 > > > The content in the link below is missing from the new version of the document: > [https://apacheignite.readme.io/docs/capacity-planning] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12368) .NET: Make sure units are specified in documentation where applicable
[ https://issues.apache.org/jira/browse/IGNITE-12368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12368: - Fix Version/s: (was: 2.10) 2.11 > .NET: Make sure units are specified in documentation where applicable > - > > Key: IGNITE-12368 > URL: https://issues.apache.org/jira/browse/IGNITE-12368 > Project: Ignite > Issue Type: Improvement > Components: documentation, platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Fix For: 2.11 > > > Units are missing in some docs. For example, XMLDoc for > DataRegionConfiguration does not specify that MaxSize is in bytes: > https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Configuration.DataRegionConfiguration.html > Check entire documentation and add units where needed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13821) Explain how to include a scope into another tracing scope
[ https://issues.apache.org/jira/browse/IGNITE-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13821: - Fix Version/s: (was: 2.10) 2.11 > Explain how to include a scope into another tracing scope > - > > Key: IGNITE-13821 > URL: https://issues.apache.org/jira/browse/IGNITE-13821 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.9 >Reporter: Denis A. Magda >Priority: Major > Fix For: 2.9, 2.11 > > > The documentation explains how to activate a tracing scope: > https://ignite.apache.org/docs/latest/monitoring-metrics/tracing#using-control-script > Also, it's feasible to include another scope inside of a primary one. For > instance, you can ask to include the communication scope into the tx scope. > [Refer to this article in > Russian|https://habr.com/ru/company/gridgain/blog/528836/] for details, > search for the "Мы также можем увеличить степень детализации трейсинга > транзакций, включив трейсинг коммуникационного протокола." occurrence in the > text after which it's show how to include one scope inside of another. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13851) Document persistence forward compatibility policy
[ https://issues.apache.org/jira/browse/IGNITE-13851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13851: - Fix Version/s: (was: 2.10) 2.11 > Document persistence forward compatibility policy > - > > Key: IGNITE-13851 > URL: https://issues.apache.org/jira/browse/IGNITE-13851 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Ilya Kasnacheev >Assignee: Nikita Safonov >Priority: Major > Fix For: 2.11 > > > We have a policy that you can upgrade from 2.x to 2.y, y > x, while keeping > your persistence files. > Let's document that fact. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13611) Ignite Docs: Port Compute Grid/Checkpointing docs from readme.io
[ https://issues.apache.org/jira/browse/IGNITE-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13611: - Fix Version/s: (was: 2.10) 2.11 > Ignite Docs: Port Compute Grid/Checkpointing docs from readme.io > > > Key: IGNITE-13611 > URL: https://issues.apache.org/jira/browse/IGNITE-13611 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Priority: Minor > Fix For: 2.11 > > > The content in the link below is missing from the new version of the document. > https://apacheignite.readme.io/docs/checkpointing -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14212) New web documentation promotion
[ https://issues.apache.org/jira/browse/IGNITE-14212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-14212: - Fix Version/s: (was: 2.10) 2.11 > New web documentation promotion > --- > > Key: IGNITE-14212 > URL: https://issues.apache.org/jira/browse/IGNITE-14212 > Project: Ignite > Issue Type: Wish >Reporter: Anton Vinogradov >Assignee: Mauricio Stekl >Priority: Critical > Fix For: 2.11 > > > Since AI documentation hosting changed (from > https://apacheignite.readme.io/docs to https://ignite.apache.org/docs) a lot > of people faced with nonrelevant search results problems. > Could we > 1) Promote a new site https://ignite.apache.org/docs to have it on the first > page of google results? > 2) Have pop-up with proposal to go to the new site at > https://apacheignite.readme.io/docs? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13651) Ignite Docs: Port Apache Zeppelin docs from readme.io
[ https://issues.apache.org/jira/browse/IGNITE-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13651: - Fix Version/s: (was: 2.10) 2.11 > Ignite Docs: Port Apache Zeppelin docs from readme.io > - > > Key: IGNITE-13651 > URL: https://issues.apache.org/jira/browse/IGNITE-13651 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Priority: Minor > Labels: new-docs > Fix For: 2.11 > > > The content in the link below is missing from the new version of the document: > [https://apacheignite-sql.readme.io/docs/apache-zeppelin] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14320) .NET: Collections can't be used as service method parameters
[
https://issues.apache.org/jira/browse/IGNITE-14320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov reassigned IGNITE-14320:
Assignee: Nikolay Izhikov
> .NET: Collections can't be used as service method parameters
>
>
> Key: IGNITE-14320
> URL: https://issues.apache.org/jira/browse/IGNITE-14320
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>
> Currently, collections (list, map) can't be used as a service method
> parameter in case of
> .Net (client node) -> .Net (server node) call.
> This can be reproduced my one line modification of
> {{ServicesTypeAutoResolveTest#DoTestPlatformService}}
> {code:java}
> ///
> /// Tests .Net service invocation.
> ///
> public void DoTestPlatformService(IServices svcsForProxy)
> {
> const string platformSvcName = "PlatformTestService";
> _grid1.GetServices().DeployClusterSingleton(platformSvcName, new
> PlatformTestService());
> var svc =
> svcsForProxy.GetServiceProxy(platformSvcName);
> DoTestService(svc);
> DoTestCollections(svc); // This line was added.
> _grid1.GetServices().Cancel(platformSvcName);
> }
> {code}
> Exception:
> {noformat}
> Apache.Ignite.Core.Services.ServiceInvocationException : Proxy method
> invocation failed with an exception. Examine InnerException for details.
> > Apache.Ignite.Core.Common.IgniteException : No matching type found
> for object [typeId=1552553483,
> typeName=org.system.collections.generic.List`1[[org.apache.ignite.platform.model.department,
> apache.ignite.core.testDepartment]]]. This usually indicates that assembly
> with specified type is not loaded on a node. When using Apache.Ignite.exe,
> make sure to load assemblies with -assembly parameter. Alternatively, set
> IgniteConfiguration.PeerAssemblyLoadingMode to CurrentAppDomain.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14287) Ignite Accessibility Check: Broken links
[ https://issues.apache.org/jira/browse/IGNITE-14287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301931#comment-17301931 ] Mauricio Stekl commented on IGNITE-14287: - Submitted fixes for all of the broken links, except for the ones from docs, listed on the previous comment. > Ignite Accessibility Check: Broken links > > > Key: IGNITE-14287 > URL: https://issues.apache.org/jira/browse/IGNITE-14287 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Mauricio Stekl >Assignee: Mauricio Stekl >Priority: Major > Labels: audit > Attachments: Broken links (Outbound).xlsx > > > While doing Ignite's usability audit, We have figured out that there's a > small bunch of broken links on the website, leading to 404 pages. The > attached report indicates the origin of these. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14287) Ignite Accessibility Check: Broken links
[ https://issues.apache.org/jira/browse/IGNITE-14287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301922#comment-17301922 ] Mauricio Stekl commented on IGNITE-14287: - [~nsafonov], there are 3 items from this list which belong to documentations, would you please help fixing? # On the left navigation the link for Machine Learning -> Ensemble Methods -> Bagging is pointing to /docs/latest/machine-learning/ensemble-methods/baggin (with the missing 'g' at the end of the URL) # On /docs/latest/machine-learning/machine-learning there is a link to [/docs/latest/machine-learning/binary-classification/random-forest|https://ignite.apache.org/docs/latest/machine-learning/binary-classification/random-forest] Thanks! > Ignite Accessibility Check: Broken links > > > Key: IGNITE-14287 > URL: https://issues.apache.org/jira/browse/IGNITE-14287 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Mauricio Stekl >Assignee: Mauricio Stekl >Priority: Major > Labels: audit > Attachments: Broken links (Outbound).xlsx > > > While doing Ignite's usability audit, We have figured out that there's a > small bunch of broken links on the website, leading to 404 pages. The > attached report indicates the origin of these. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14320) .NET: Collections can't be used as service method parameters
Nikolay Izhikov created IGNITE-14320:
Summary: .NET: Collections can't be used as service method
parameters
Key: IGNITE-14320
URL: https://issues.apache.org/jira/browse/IGNITE-14320
Project: Ignite
Issue Type: Improvement
Reporter: Nikolay Izhikov
Currently, collections (list, map) can't be used as a service method parameter
in case of
.Net (client node) -> .Net (server node) call.
This can be reproduced my one line modification of
{{ServicesTypeAutoResolveTest#DoTestPlatformService}}
{code:java}
///
/// Tests .Net service invocation.
///
public void DoTestPlatformService(IServices svcsForProxy)
{
const string platformSvcName = "PlatformTestService";
_grid1.GetServices().DeployClusterSingleton(platformSvcName, new
PlatformTestService());
var svc =
svcsForProxy.GetServiceProxy(platformSvcName);
DoTestService(svc);
DoTestCollections(svc); // This line was added.
_grid1.GetServices().Cancel(platformSvcName);
}
{code}
Exception:
{noformat}
Apache.Ignite.Core.Services.ServiceInvocationException : Proxy method
invocation failed with an exception. Examine InnerException for details.
> Apache.Ignite.Core.Common.IgniteException : No matching type found for
object [typeId=1552553483,
typeName=org.system.collections.generic.List`1[[org.apache.ignite.platform.model.department,
apache.ignite.core.testDepartment]]]. This usually indicates that assembly
with specified type is not loaded on a node. When using Apache.Ignite.exe, make
sure to load assemblies with -assembly parameter. Alternatively, set
IgniteConfiguration.PeerAssemblyLoadingMode to CurrentAppDomain.
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14315) Ignite 3: Use maven-flatten plugin for project pom.xml
[ https://issues.apache.org/jira/browse/IGNITE-14315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-14315: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Ignite 3: Use maven-flatten plugin for project pom.xml > -- > > Key: IGNITE-14315 > URL: https://issues.apache.org/jira/browse/IGNITE-14315 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Fix For: 3.0.0-alpha2 > > Time Spent: 10m > Remaining Estimate: 0h > > Without the flatten it would be impossible to use the maven-published > artifacts of Ignite 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14319) Multithreaded data generation for rebalance tests
Dmitriy Sorokin created IGNITE-14319:
Summary: Multithreaded data generation for rebalance tests
Key: IGNITE-14319
URL: https://issues.apache.org/jira/browse/IGNITE-14319
Project: Ignite
Issue Type: Sub-task
Reporter: Dmitriy Sorokin
Assignee: Dmitriy Sorokin
At the moment, {{DataGenerationApplication}} generates data in the single
thread. We should make that routine multithreaded.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14079) Add test for checking partition eviction order
[
https://issues.apache.org/jira/browse/IGNITE-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301710#comment-17301710
]
Mirza Aliev edited comment on IGNITE-14079 at 3/15/21, 3:32 PM:
[~slava.koptilin] thank you! I'll resolve
https://issues.apache.org/jira/browse/IGNITE-14318 as duplicate and will fix
the current ticket
was (Author: maliev):
[~slava.koptilin] thank you! I'll close
https://issues.apache.org/jira/browse/IGNITE-14318 as duplicate and will fix
the current ticket
> Add test for checking partition eviction order
> --
>
> Key: IGNITE-14079
> URL: https://issues.apache.org/jira/browse/IGNITE-14079
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9.1
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Add test to check that {{CacheRebalanceMode#SYNC}} caches are evicted before
> {{CacheRebalanceMode#ASYNC}}. It is important because otherwise can lead to
> significant start-up delays. Ignite can send some fat {{ASYNC}} cache groups
> for eviction first and after this only add system cache, which is {{SYNC}},
> for eviction as result sys cache will wait in queue and node startup will be
> blocked until fat partitions will be evicted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14079) Add test for checking partition eviction order
[
https://issues.apache.org/jira/browse/IGNITE-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301710#comment-17301710
]
Mirza Aliev commented on IGNITE-14079:
--
[~slava.koptilin] thank you! I'll close
https://issues.apache.org/jira/browse/IGNITE-14318 as duplicate and will fix
the current ticket
> Add test for checking partition eviction order
> --
>
> Key: IGNITE-14079
> URL: https://issues.apache.org/jira/browse/IGNITE-14079
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9.1
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Add test to check that {{CacheRebalanceMode#SYNC}} caches are evicted before
> {{CacheRebalanceMode#ASYNC}}. It is important because otherwise can lead to
> significant start-up delays. Ignite can send some fat {{ASYNC}} cache groups
> for eviction first and after this only add system cache, which is {{SYNC}},
> for eviction as result sys cache will wait in queue and node startup will be
> blocked until fat partitions will be evicted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-14318) Add PartitionEvictionOrderTest to IgniteBasicTestSuite
[ https://issues.apache.org/jira/browse/IGNITE-14318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev resolved IGNITE-14318. -- Fix Version/s: (was: 2.11) Resolution: Duplicate > Add PartitionEvictionOrderTest to IgniteBasicTestSuite > -- > > Key: IGNITE-14318 > URL: https://issues.apache.org/jira/browse/IGNITE-14318 > Project: Ignite > Issue Type: Bug >Reporter: Mirza Aliev >Assignee: Mirza Aliev >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14023) Password based authentication support in ducktape tests
[
https://issues.apache.org/jira/browse/IGNITE-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Filatov updated IGNITE-14023:
-
Description:
There are users with authentication enabled on the cluster
Ducktape tests should work on such clusters.
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running Ignite node and application with third-party authentication plugin
remains to be implemented by the developers of that plugin.
In this PR we will only implement the ability to tell control.sh how to
connect to the cluster.
connection parameters should be passed through globals with structure like that.
{"authentication":
{ "enabled": true, "username": "admin", "password": "qwe123"}}
was:
There are users with authentication enabled on the cluster
Ducktape tests should work on such clusters.
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running Ignite node and application with third-party authentication plugin
remains to be implemented by the developers of that plugin.
In this PR we will only implement the ability to tell control.sh how to
connect to the cluster.
connection parameters should be passed through globals with structure like that.
{"authentication": {
"enabled": true,
"default_credentials": [
"admin",
"qwe123"]}}
> Password based authentication support in ducktape tests
> ---
>
> Key: IGNITE-14023
> URL: https://issues.apache.org/jira/browse/IGNITE-14023
> Project: Ignite
> Issue Type: Task
>Reporter: Mikhail Filatov
>Assignee: Mikhail Filatov
>Priority: Minor
> Time Spent: 11h 40m
> Remaining Estimate: 0h
>
> There are users with authentication enabled on the cluster
> Ducktape tests should work on such clusters.
> Tests should work if authentication is enabled on the cluster via a
> third-party plugin
> Running Ignite node and application with third-party authentication plugin
> remains to be implemented by the developers of that plugin.
> In this PR we will only implement the ability to tell control.sh how to
> connect to the cluster.
> connection parameters should be passed through globals with structure like
> that.
> {"authentication":
> { "enabled": true, "username": "admin", "password": "qwe123"}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14079) Add test for checking partition eviction order
[
https://issues.apache.org/jira/browse/IGNITE-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301702#comment-17301702
]
Vyacheslav Koptilin commented on IGNITE-14079:
--
Hello [~mmuzaf], [~maliev],
Folks, I have reverted this commit and reopen the ticket.
> Add test for checking partition eviction order
> --
>
> Key: IGNITE-14079
> URL: https://issues.apache.org/jira/browse/IGNITE-14079
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9.1
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Add test to check that {{CacheRebalanceMode#SYNC}} caches are evicted before
> {{CacheRebalanceMode#ASYNC}}. It is important because otherwise can lead to
> significant start-up delays. Ignite can send some fat {{ASYNC}} cache groups
> for eviction first and after this only add system cache, which is {{SYNC}},
> for eviction as result sys cache will wait in queue and node startup will be
> blocked until fat partitions will be evicted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (IGNITE-14079) Add test for checking partition eviction order
[
https://issues.apache.org/jira/browse/IGNITE-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin reopened IGNITE-14079:
--
> Add test for checking partition eviction order
> --
>
> Key: IGNITE-14079
> URL: https://issues.apache.org/jira/browse/IGNITE-14079
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9.1
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Add test to check that {{CacheRebalanceMode#SYNC}} caches are evicted before
> {{CacheRebalanceMode#ASYNC}}. It is important because otherwise can lead to
> significant start-up delays. Ignite can send some fat {{ASYNC}} cache groups
> for eviction first and after this only add system cache, which is {{SYNC}},
> for eviction as result sys cache will wait in queue and node startup will be
> blocked until fat partitions will be evicted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14318) Add PartitionEvictionOrderTest to IgniteBasicTestSuite
[ https://issues.apache.org/jira/browse/IGNITE-14318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev updated IGNITE-14318: - Fix Version/s: 2.11 > Add PartitionEvictionOrderTest to IgniteBasicTestSuite > -- > > Key: IGNITE-14318 > URL: https://issues.apache.org/jira/browse/IGNITE-14318 > Project: Ignite > Issue Type: Bug >Reporter: Mirza Aliev >Assignee: Mirza Aliev >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14318) Add PartitionEvictionOrderTest to IgniteBasicTestSuite
Mirza Aliev created IGNITE-14318: Summary: Add PartitionEvictionOrderTest to IgniteBasicTestSuite Key: IGNITE-14318 URL: https://issues.apache.org/jira/browse/IGNITE-14318 Project: Ignite Issue Type: Bug Reporter: Mirza Aliev Assignee: Mirza Aliev -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14079) Add test for checking partition eviction order
[
https://issues.apache.org/jira/browse/IGNITE-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301684#comment-17301684
]
Mirza Aliev commented on IGNITE-14079:
--
[~mmuzaf] thanks for your catch!
Seems, that I forget to add the test to any suite, will fix asap, here is a
ticket https://issues.apache.org/jira/browse/IGNITE-14318
> Add test for checking partition eviction order
> --
>
> Key: IGNITE-14079
> URL: https://issues.apache.org/jira/browse/IGNITE-14079
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9.1
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Add test to check that {{CacheRebalanceMode#SYNC}} caches are evicted before
> {{CacheRebalanceMode#ASYNC}}. It is important because otherwise can lead to
> significant start-up delays. Ignite can send some fat {{ASYNC}} cache groups
> for eviction first and after this only add system cache, which is {{SYNC}},
> for eviction as result sys cache will wait in queue and node startup will be
> blocked until fat partitions will be evicted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14079) Add test for checking partition eviction order
[
https://issues.apache.org/jira/browse/IGNITE-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301684#comment-17301684
]
Mirza Aliev edited comment on IGNITE-14079 at 3/15/21, 2:56 PM:
[~mmuzaf] thanks for your catch!
Seems, that I forgot to add the test to any suite, will fix asap, here is a
ticket https://issues.apache.org/jira/browse/IGNITE-14318
was (Author: maliev):
[~mmuzaf] thanks for your catch!
Seems, that I forget to add the test to any suite, will fix asap, here is a
ticket https://issues.apache.org/jira/browse/IGNITE-14318
> Add test for checking partition eviction order
> --
>
> Key: IGNITE-14079
> URL: https://issues.apache.org/jira/browse/IGNITE-14079
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9.1
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Add test to check that {{CacheRebalanceMode#SYNC}} caches are evicted before
> {{CacheRebalanceMode#ASYNC}}. It is important because otherwise can lead to
> significant start-up delays. Ignite can send some fat {{ASYNC}} cache groups
> for eviction first and after this only add system cache, which is {{SYNC}},
> for eviction as result sys cache will wait in queue and node startup will be
> blocked until fat partitions will be evicted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14317) IgniteCache.removeAsync(key,val) fails inside an optimistic transaction
Denis Garus created IGNITE-14317:
Summary: IgniteCache.removeAsync(key,val) fails inside an
optimistic transaction
Key: IGNITE-14317
URL: https://issues.apache.org/jira/browse/IGNITE-14317
Project: Ignite
Issue Type: Bug
Affects Versions: 2.9.1
Reporter: Denis Garus
[reproducer|https://github.com/apache/ignite/pull/8841/files]
IgniteCache.removeAsync(key,val) fails inside an optimistic tx with the
exception:
{code:java}
[17:39:28] (err) Failed to notify listener:
o.a.i.i.processors.cache.distributed.near.GridNearTxLocal$6...@19c520dbjava.lang.AssertionError[17:39:28]
(err) Failed to notify listener:
o.a.i.i.processors.cache.distributed.near.GridNearTxLocal$6...@19c520dbjava.lang.AssertionError
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$17.apply(GridNearTxLocal.java:2955)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$17.apply(GridNearTxLocal.java:2937)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.processLoaded(GridNearTxLocal.java:3475)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$21.apply(GridNearTxLocal.java:3217)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$21.apply(GridNearTxLocal.java:3212)
at
org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:78)
at
org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:70)
at
org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:30)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:511)
at
org.apache.ignite.internal.processors.cache.GridCacheFutureAdapter.onDone(GridCacheFutureAdapter.java:55)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:490)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.onDone(GridPartitionedSingleGetFuture.java:935)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:467)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setSkipValueResult(GridPartitionedSingleGetFuture.java:759)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.onResult(GridPartitionedSingleGetFuture.java:636)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearSingleGetResponse(GridDhtCacheAdapter.java:368)
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.access$100(GridDhtColocatedCache.java:88)
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache$2.apply(GridDhtColocatedCache.java:133)
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache$2.apply(GridDhtColocatedCache.java:131)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1143)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:592)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:393)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:319)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:309)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1908)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1529)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.execute(GridIoManager.java:1422)
at
org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:55)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:569)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.base/java.lang.Thread.run(Thread.java:834){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14079) Add test for checking partition eviction order
[
https://issues.apache.org/jira/browse/IGNITE-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301670#comment-17301670
]
Maxim Muzafarov commented on IGNITE-14079:
--
Folks, the build failing with the following error:
https://travis-ci.com/github/apache/ignite/jobs/491166984
{code}
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:java
(default) on project apache-ignite: An exception occured while executing the
Java class. null: InvocationTargetException: All test classes must be include
in any test suite or mark with the @Ignore annotation.
[ERROR] List of non-suited classes (1 items):
[ERROR]
org.apache.ignite.internal.processors.cache.distributed.dht.topology.PartitionEvictionOrderTest
{code}
Can you please fix?
> Add test for checking partition eviction order
> --
>
> Key: IGNITE-14079
> URL: https://issues.apache.org/jira/browse/IGNITE-14079
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9.1
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Add test to check that {{CacheRebalanceMode#SYNC}} caches are evicted before
> {{CacheRebalanceMode#ASYNC}}. It is important because otherwise can lead to
> significant start-up delays. Ignite can send some fat {{ASYNC}} cache groups
> for eviction first and after this only add system cache, which is {{SYNC}},
> for eviction as result sys cache will wait in queue and node startup will be
> blocked until fat partitions will be evicted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14214) Incorrect merge query when using oracle dialect
[
https://issues.apache.org/jira/browse/IGNITE-14214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301668#comment-17301668
]
Yaroslav Molochkov commented on IGNITE-14214:
-
[~korlov], hello! Could you also take a look, please?
> Incorrect merge query when using oracle dialect
> ---
>
> Key: IGNITE-14214
> URL: https://issues.apache.org/jira/browse/IGNITE-14214
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10, 2.9.1
>Reporter: Yaroslav Molochkov
>Assignee: Yaroslav Molochkov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If table contains only keys (e.g. relationship table) then returned query
> contains empty update fields and resulting syntax is incorrect.
> Consider the following example:
> org.apache.ignite.cache.store.jdbc.dialect.OracleDialect#mergeQuery accepts
> key and val collections. The problem is relevant if val collection is empty.
> {code:java}
> return String.format("MERGE INTO %s t" +
> " USING (SELECT %s FROM dual) v" +
> " ON %s" +
> " WHEN MATCHED THEN" +
> " UPDATE SET %s" +
> " WHEN NOT MATCHED THEN" +
> " INSERT (%s) VALUES (%s)", fullTblName, selCols, match, setCols,
> colsLst, valuesCols);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14177) Query parallelism ignores "NULLS LAST" in "order by" clause
[ https://issues.apache.org/jira/browse/IGNITE-14177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301667#comment-17301667 ] Sergey Dorozhkin commented on IGNITE-14177: --- [~amashenkov], Thank you! > Query parallelism ignores "NULLS LAST" in "order by" clause > --- > > Key: IGNITE-14177 > URL: https://issues.apache.org/jira/browse/IGNITE-14177 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.9.1 >Reporter: Ilya Kazakov >Assignee: Sergey Dorozhkin >Priority: Major > Fix For: 2.11 > > Attachments: NullsLastWithParallels.java > > Time Spent: 20m > Remaining Estimate: 0h > > If set QueryParallelism to some value >=2, then "NULLS LAST" is ignored in > "order by clause". > e.g. SELECT * FROM ORDER BY ASC NULLS LAST > A small reproducer is attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14254) Graceful stop rebuilding indexes when deactivating a cluster
[
https://issues.apache.org/jira/browse/IGNITE-14254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301660#comment-17301660
]
Ignite TC Bot commented on IGNITE-14254:
{panel:title=Branch: [pull/8837/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8837/head] Base: [master] : New Tests
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5915021]]
* {color:#013220}IgniteBinaryCacheTestSuite:
GridCacheStopSelfTest.testStoppingCacheContext - PASSED{color}
{color:#8b}PDS (Indexing){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5915034]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
StopRebuildIndexTest.testSchemaIndexCacheCompoundFeature - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
StopRebuildIndexTest.testStopRebuildIndexesOnDeactivation - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
StopRebuildIndexTest.testStopRebuildIndexesOnStopNode - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
StopRebuildIndexTest.testIndexingRebuildFuture - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5915067&buildTypeId=IgniteTests24Java8_RunAll]
> Graceful stop rebuilding indexes when deactivating a cluster
>
>
> Key: IGNITE-14254
> URL: https://issues.apache.org/jira/browse/IGNITE-14254
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If in the process of rebuilding the indexes to deactivate the cluster, then a
> number of errors may appear, including a node fail. It is necessary to stop
> index rebuilding before stopping the cache.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14308) IgnitePeerToPeerClassLoadingException: Could not use deployment to prepare deployable, because local node id does not correspond with class loader id
[
https://issues.apache.org/jira/browse/IGNITE-14308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-14308:
-
Release Note: Change peer class loading error to warning when local class
loader not from current node
> IgnitePeerToPeerClassLoadingException: Could not use deployment to prepare
> deployable, because local node id does not correspond with class loader id
> -
>
> Key: IGNITE-14308
> URL: https://issues.apache.org/jira/browse/IGNITE-14308
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.9
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After IGNITE-12760, the following exception is seen:
> {code}
> IgnitePeerToPeerClassLoadingException
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.checkDeploymentIsCorrect(GridCacheDeploymentManager.java:717)
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.prepare(GridCacheDeploymentManager.java:693)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onSend(GridCacheIoManager.java:1213)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1245)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.proceedPrepare(GridNearOptimisticTxPrepareFuture.java:570)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepareSingle(GridNearOptimisticTxPrepareFuture.java:381)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepare0(GridNearOptimisticTxPrepareFuture.java:324)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFutureAdapter.prepareOnTopology(GridNearOptimisticTxPrepareFutureAdapter.java:204)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFutureAdapter.prepare(GridNearOptimisticTxPrepareFutureAdapter.java:128)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareNearTxLocal(GridNearTxLocal.java:3965)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitNearTxLocalAsync(GridNearTxLocal.java:4013)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.optimisticPutFuture(GridNearTxLocal.java:2958)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAllAsync0(GridNearTxLocal.java:1033)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.invokeAsync(GridNearTxLocal.java:540)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$27.op(GridCacheAdapter.java:2389)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$27.op(GridCacheAdapter.java:2385)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:3830)
> ... 29 more
> {code}
> Turns out, sometimes local deployment belongs to other node id (previous
> client?). Changing behavior for local deployments was not anticipated. Let's
> change this error to warning for local deployments.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14308) IgnitePeerToPeerClassLoadingException: Could not use deployment to prepare deployable, because local node id does not correspond with class loader id
[
https://issues.apache.org/jira/browse/IGNITE-14308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301645#comment-17301645
]
Ilya Kasnacheev commented on IGNITE-14308:
--
[~sergey-chugunov] please review this fix.
> IgnitePeerToPeerClassLoadingException: Could not use deployment to prepare
> deployable, because local node id does not correspond with class loader id
> -
>
> Key: IGNITE-14308
> URL: https://issues.apache.org/jira/browse/IGNITE-14308
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.9
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After IGNITE-12760, the following exception is seen:
> {code}
> IgnitePeerToPeerClassLoadingException
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.checkDeploymentIsCorrect(GridCacheDeploymentManager.java:717)
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.prepare(GridCacheDeploymentManager.java:693)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onSend(GridCacheIoManager.java:1213)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1245)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.proceedPrepare(GridNearOptimisticTxPrepareFuture.java:570)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepareSingle(GridNearOptimisticTxPrepareFuture.java:381)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepare0(GridNearOptimisticTxPrepareFuture.java:324)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFutureAdapter.prepareOnTopology(GridNearOptimisticTxPrepareFutureAdapter.java:204)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFutureAdapter.prepare(GridNearOptimisticTxPrepareFutureAdapter.java:128)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareNearTxLocal(GridNearTxLocal.java:3965)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitNearTxLocalAsync(GridNearTxLocal.java:4013)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.optimisticPutFuture(GridNearTxLocal.java:2958)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAllAsync0(GridNearTxLocal.java:1033)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.invokeAsync(GridNearTxLocal.java:540)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$27.op(GridCacheAdapter.java:2389)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$27.op(GridCacheAdapter.java:2385)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:3830)
> ... 29 more
> {code}
> Turns out, sometimes local deployment belongs to other node id (previous
> client?). Changing behavior for local deployments was not anticipated. Let's
> change this error to warning for local deployments.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster
[
https://issues.apache.org/jira/browse/IGNITE-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-12033:
Labels: iep-70 (was: )
> Callbacks from striped pool due to async/await may hang cluster
> ---
>
> Key: IGNITE-12033
> URL: https://issues.apache.org/jira/browse/IGNITE-12033
> Project: Ignite
> Issue Type: Bug
> Components: cache, platforms
>Affects Versions: 2.7.5
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: iep-70
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Discussed on dev-list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Re-EXTERNAL-Re-Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td42921.html
> *Must use the public pool for callbacks as the most obvious step.*
>
> http://apache-ignite-users.70518.x6.nabble.com/Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td27871.html#a28051
> There's a reproducer project. Long story short, .Net can invoke cache
> operations with future callbacks, which will be invoked from striped pool. If
> such callbacks are to use cache operations, those will be possibly sheduled
> to the same stripe and cause a deadlock.
> The code is very simple:
> {code}
> Console.WriteLine("PutAsync");
> await cache.PutAsync(1, "Test");
> Console.WriteLine("Replace");
> cache.Replace(1, "Testing"); // Hangs here
> Console.WriteLine("Wait");
> await Task.Delay(Timeout.Infinite);
> {code}
> async/await should absolutely not allow any client code to be run from
> stripes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13112) The current security context should be obtained using the IgniteSecurity interface only.
[
https://issues.apache.org/jira/browse/IGNITE-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301632#comment-17301632
]
Ignite TC Bot commented on IGNITE-13112:
{panel:title=Branch: [pull/8038/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8038/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5914556&buildTypeId=IgniteTests24Java8_RunAll]
> The current security context should be obtained using the IgniteSecurity
> interface only.
>
>
> Key: IGNITE-13112
> URL: https://issues.apache.org/jira/browse/IGNITE-13112
> Project: Ignite
> Issue Type: Bug
> Components: cache, security
>Affects Versions: 2.8.1
>Reporter: Denis Garus
>Assignee: Denis Garus
>Priority: Major
> Labels: iep-41
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> For getting the current security context, we have to use the IgniteSecurity
> interface only.
> We need to get rid of all other ways to transfer a security subject id.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14035) Table access public API.
[ https://issues.apache.org/jira/browse/IGNITE-14035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-14035: -- Description: h3. Motivation. Some users may want to use Key-value (KV) pair to store their data, some would like to have a single Record class for the same purpose. Both approaches are reasonable and perfectly maps to the row layout described in IEP. The only difference is separate key and value classes vs a single record class. Also, we must provide lower-level TableView to access data via BinaryObject analogs (like keepBinary() projection does in ignite 2.x) because ones may not have classes on the server-side. h3. Description. Create table access API (incl. Record and KV concepts). Cover the next cases with Examples of how API can be used: * Simple Record case. (Row mapped to a single user class) * Simple KV case. (Row mapped to key-value pair of user classes) * Binary row case. * Binary KV case. * Truncated classes. (Value\Record class that covers a part of value columns.) * Custom class field->columns mapping. * Conditional serialization. * Inheritance mapping single table strategy (wide table schema vs conditional serialization) * Transition from "schemaless" (pure binary KV case) to schema-powered. Serializer\marshaller, schema management, schema versioning, underlying storage are out-of-scope and may be stubbed if needed. was: h3. Motivation. Some users may want to use Key-value (KV) pair to store their data, some would like to have a single Record class for the same purpose. Both approaches are reasonable and perfectly maps to the row layout described in IEP. The only difference is separate key and value classes vs a single record class. Also, we must provide lower-level TableView to access data via BinaryObject analogs (like keepBinary() projection does in ignite 2.x) because ones may not have classes on the server-side. h3. Description. Create table access API (incl. Record and KV concepts). Cover the next cases with Examples of how API can be used: * Simple Record case. (Row mapped to a single user class) * Simple KV case. (Row mapped to key-value pair of user classes) * Binary row case. * Binary KV case. * Truncated classes. (Value\Record class that covers a part of value columns.) * Custom class field->columns mapping. * -Conditional serialization.- * -Inheritance mapping single table strategy (wide table schema vs conditional serialization)- * Transition from "schemaless" (pure binary KV case) to schema-powered. Serializer\marshaller, schema management, schema versioning, underlying storage are out-of-scope and may be stubbed if needed. > Table access public API. > > > Key: IGNITE-14035 > URL: https://issues.apache.org/jira/browse/IGNITE-14035 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > h3. Motivation. > Some users may want to use Key-value (KV) pair to store their data, some > would like to have a single Record class for the same purpose. > Both approaches are reasonable and perfectly maps to the row layout described > in IEP. The only difference is separate key and value classes vs a single > record class. > Also, we must provide lower-level TableView to access data via BinaryObject > analogs (like keepBinary() projection does in ignite 2.x) because ones may > not have classes on the server-side. > h3. Description. > Create table access API (incl. Record and KV concepts). > Cover the next cases with Examples of how API can be used: > * Simple Record case. (Row mapped to a single user class) > * Simple KV case. (Row mapped to key-value pair of user classes) > * Binary row case. > * Binary KV case. > * Truncated classes. (Value\Record class that covers a part of value columns.) > * Custom class field->columns mapping. > * Conditional serialization. > * Inheritance mapping single table strategy (wide table schema vs conditional > serialization) > * Transition from "schemaless" (pure binary KV case) to schema-powered. > Serializer\marshaller, schema management, schema versioning, underlying > storage are out-of-scope and may be stubbed if needed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14035) Table access public API.
[ https://issues.apache.org/jira/browse/IGNITE-14035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-14035: -- Description: h3. Motivation. Some users may want to use Key-value (KV) pair to store their data, some would like to have a single Record class for the same purpose. Both approaches are reasonable and perfectly maps to the row layout described in IEP. The only difference is separate key and value classes vs a single record class. Also, we must provide lower-level TableView to access data via BinaryObject analogs (like keepBinary() projection does in ignite 2.x) because ones may not have classes on the server-side. h3. Description. Create table access API (incl. Record and KV concepts). Cover the next cases with Examples of how API can be used: * Simple Record case. (Row mapped to a single user class) * Simple KV case. (Row mapped to key-value pair of user classes) * Binary row case. * Binary KV case. * Truncated classes. (Value\Record class that covers a part of value columns.) * Custom class field->columns mapping. * -Conditional serialization.- * -Inheritance mapping single table strategy (wide table schema vs conditional serialization)- * Transition from "schemaless" (pure binary KV case) to schema-powered. Serializer\marshaller, schema management, schema versioning, underlying storage are out-of-scope and may be stubbed if needed. was: h3. Motivation. Some users may want to use Key-value (KV) pair to store their data, some would like to have a single Record class for the same purpose. Both approaches are reasonable and perfectly maps to the row layout described in IEP. The only difference is separate key and value classes vs a single record class. Also, we must provide lower-level TableView to access data via BinaryObject analogs (like keepBinary() projection does in ignite 2.x) because ones may not have classes on the server-side. h3. Description. Create table access API (incl. Record and KV concepts). Cover the next cases with Examples of how API can be used: * Simple Record case. * Simple KV case. * Truncated classes. (Value\Record class that covers a part of value columns.) * Binary row projection. * Custom class field->columns mapping. * Conditional serialization. * Inheritance mapping single table strategy (wide table schema vs conditional serialization) * Transition from "schemaless" (pure binary KV case) to schema-powered. Serializer\marshaller, schema management, schema versioning, underlying storage are out-of-scope and may be stubbed if needed. > Table access public API. > > > Key: IGNITE-14035 > URL: https://issues.apache.org/jira/browse/IGNITE-14035 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > h3. Motivation. > Some users may want to use Key-value (KV) pair to store their data, some > would like to have a single Record class for the same purpose. > Both approaches are reasonable and perfectly maps to the row layout described > in IEP. The only difference is separate key and value classes vs a single > record class. > Also, we must provide lower-level TableView to access data via BinaryObject > analogs (like keepBinary() projection does in ignite 2.x) because ones may > not have classes on the server-side. > h3. Description. > Create table access API (incl. Record and KV concepts). > Cover the next cases with Examples of how API can be used: > * Simple Record case. (Row mapped to a single user class) > * Simple KV case. (Row mapped to key-value pair of user classes) > * Binary row case. > * Binary KV case. > * Truncated classes. (Value\Record class that covers a part of value columns.) > * Custom class field->columns mapping. > * -Conditional serialization.- > * -Inheritance mapping single table strategy (wide table schema vs > conditional serialization)- > * Transition from "schemaless" (pure binary KV case) to schema-powered. > Serializer\marshaller, schema management, schema versioning, underlying > storage are out-of-scope and may be stubbed if needed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14316) BinaryObject API
Andrey Mashenkov created IGNITE-14316: - Summary: BinaryObject API Key: IGNITE-14316 URL: https://issues.apache.org/jira/browse/IGNITE-14316 Project: Ignite Issue Type: Improvement Reporter: Andrey Mashenkov Let's create BinaryObject (BO) interface and a builder interface for it assuming - BO is a self-described object. Similar to Ignite-2 one with a compact footer. - BO is unmanaged. SchemaManager doesn't care about its schema at all. - BO can be deserialized to user class with a specified deserializer. - BO has a flat structure, cyclic links are not allowed. However, one can restore links on reserialization. - BO must not have any dependencies on Ignite internals. - Ignite should provide some base implementation for BO and builder. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14019) Calcite bug. Can`t access cache created on the server side from client node.
[
https://issues.apache.org/jira/browse/IGNITE-14019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301610#comment-17301610
]
Aleksey Plekhanov commented on IGNITE-14019:
[~tledkov-gridgain] thanks for the review! Merged to sql-calcite branch.
> Calcite bug. Can`t access cache created on the server side from client node.
>
>
> Key: IGNITE-14019
> URL: https://issues.apache.org/jira/browse/IGNITE-14019
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Stanilovsky Evgeny
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite
> Attachments: SqlFieldsQueryUsageTest.java
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> table created from server node
> {code:java}
> IgniteCache devCache = grid(0).createCache(projCfg);
> assertFalse(grid(0).configuration().isClientMode());
> {code}
> and accessed from client :
> {code:java}
> node.context().query().querySqlFields(new
> SqlFieldsQuery(sql).setSchema("PUBLIC"), true).getAll();
> {code}
> throws:
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.query.calcite.schema.TableDescriptorImpl.distribution(TableDescriptorImpl.java:197)
> at
> org.apache.ignite.internal.processors.query.calcite.schema.IgniteTableImpl.distribution(IgniteTableImpl.java:121)
> at
> org.apache.ignite.internal.processors.query.calcite.schema.IgniteTableImpl.toRel(IgniteTableImpl.java:89)
> at
> org.apache.ignite.internal.processors.query.calcite.schema.IgniteTable.toRel(IgniteTable.java:61)
> at
> org.apache.ignite.internal.processors.query.calcite.schema.IgniteTable.toRel(IgniteTable.java:40)
> at
> org.apache.calcite.prepare.RelOptTableImpl.toRel(RelOptTableImpl.java:285)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.toRel(SqlToRelConverter.java:3585)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertIdentifier(SqlToRelConverter.java:2507)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertFrom(SqlToRelConverter.java:2144)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertFrom(SqlToRelConverter.java:2093)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertFrom(SqlToRelConverter.java:2050)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertSelectImpl(SqlToRelConverter.java:663)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertSelect(SqlToRelConverter.java:644)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertQueryRecursive(SqlToRelConverter.java:3438)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertQuery(SqlToRelConverter.java:570)
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.rel(IgnitePlanner.java:211)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.optimize(ExecutionServiceImpl.java:600)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:568)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareSingle(ExecutionServiceImpl.java:542)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:501)
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.QueryPlanCacheImpl.queryPlan(QueryPlanCacheImpl.java:84)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.executeQuery(ExecutionServiceImpl.java:378)
> at
> org.apache.ignite.internal.processors.query.calcite.CalciteQueryProcessor.query(CalciteQueryProcessor.java:241)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2841)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2766)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2739)
> at
> org.apache.ignite.internal.processors.query.calcite.SqlFieldsQueryUsageTest.execute(SqlFieldsQueryUsageTest.java:99)
> at
> org.apache.ignite.internal.processors.query.calcite.SqlFieldsQueryUsageTest.createCacheOnSrvCallOnCli(SqlFieldsQueryUsageTest.java:89)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
[jira] [Assigned] (IGNITE-14248) Handle exceptions in PartitionReservationManager.onDoneAfterTopologyUnlock properly
[
https://issues.apache.org/jira/browse/IGNITE-14248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Pligin reassigned IGNITE-14248:
Assignee: Vladimir Pligin
> Handle exceptions in PartitionReservationManager.onDoneAfterTopologyUnlock
> properly
> ---
>
> Key: IGNITE-14248
> URL: https://issues.apache.org/jira/browse/IGNITE-14248
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.9.1
>Reporter: Vladimir Pligin
>Assignee: Vladimir Pligin
>Priority: Major
>
> If an exception (or even Error) is thrown inside of the method then the node
> turns into some unrecoverable state. Here's an example.
> # an exchange is about to finish, it's time to invalidate partition
> reservations.
> # exchange thread delegates it to a thread in the management pool
> # management pool tries to allocate a new thread (maybe it's idle and
> therefore empty)
> # for example ulimit is reached, the error is
> java.lang.OutOfMemoryError: unable to create native thread: possibly out of
> memory or process/resource limits reached
> # It's being logged, no further action is taken
> # partitions are reserved forever
> Message:
>
> {code:java}
> 2021-02-25 05:52:03.242 [exchange-worker-#182] ERROR
> o.a.i.i.p.q.h.t.PartitionReservationManager - Unexpected exception on start
> reservations cleanup
> java.lang.OutOfMemoryError: unable to create native thread: possibly out of
> memory or process/resource limits reached
> at java.base/java.lang.Thread.start0(Native Method)
> at java.base/java.lang.Thread.start(Thread.java:803)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:937)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1343)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.runLocal(GridClosureProcessor.java:847)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.PartitionReservationManager.onDoneAfterTopologyUnlock(PartitionReservationManager.java:323)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2617)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:159)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:475)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:1064)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3375)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3194)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
>
>
> Code of PartitionReservationManager.onDoneAfterTopologyUnlock:
> {code:java}
> @Override public void onDoneAfterTopologyUnlock(final
> GridDhtPartitionsExchangeFuture fut) {
> try {
> // Must not do anything at the exchange thread. Dispatch to the
> management thread pool.
> ctx.closure().runLocal(() -> {
> AffinityTopologyVersion topVer =
> ctx.cache().context().exchange()
>
> .lastAffinityChangedTopologyVersion(fut.topologyVersion());
> reservations.forEach((key, r) -> {
> if (r != REPLICATED_RESERVABLE &&
> !F.eq(key.topologyVersion(), topVer)) {
> assert r instanceof GridDhtPartitionsReservation;
>((GridDhtPartitionsReservation)r).invalidate();
> }
> });
> },
> GridIoPolicy.MANAGEMENT_POOL);
> }
> catch (Throwable e) {
> log.error("Unexpected exception on start reservations cleanup",
> e);
> }
> }
> {code}
>
>
> My vision is that there are two basic approaches:
> * to kill the node (it's already non-functional at this point), seems to be
> a FH job.
> * try to recover somehow (to be honest it's not clear how exactly)
> This particular OOM situation seems unrecoverable in fact. It's an
> environment misconfiguration. It would be great to investigate if potentially
> recoverable exceptions are possible to be raised inside this block.
--
This message
[jira] [Commented] (IGNITE-14313) .NET: Add test to call .Net service from .Net
[
https://issues.apache.org/jira/browse/IGNITE-14313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301594#comment-17301594
]
Nikolay Izhikov commented on IGNITE-14313:
--
https://ci.ignite.apache.org/viewLog.html?buildId=5914796&buildTypeId=IgniteTests24Java8_RunAllNet
- tests
> .NET: Add test to call .Net service from .Net
> --
>
> Key: IGNITE-14313
> URL: https://issues.apache.org/jira/browse/IGNITE-14313
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: .NET
> Fix For: 2.11
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, {{IJavaService}} methods in {{ServicesTest}} and
> {{ServicesTypeAutoResolveTest}} only checked for .Net -> Java case. We should
> extends it with .Net -> .Net invocation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
