[jira] [Created] (IGNITE-13285) Document control.sh indexes manipulation commands
Vladimir Malinovskiy created IGNITE-13285:
-
Summary: Document control.sh indexes manipulation commands
Key: IGNITE-13285
URL: https://issues.apache.org/jira/browse/IGNITE-13285
Project: Ignite
Issue Type: Task
Components: control.sh, documentation
Reporter: Vladimir Malinovskiy
Fix For: 2.10
Under IGNITE-13268 3 new cache commands were added: "--indexes_list",
"--indexes_rebuild_status" and "--indexes_force_rebuild". New commands should
be documented.
Here is part of cache help that corresponds to the commands:
{code:java}
--cache indexes_list [--node-id nodeId] [--group-name grpRegExp]
[--cache-name cacheRegExp] [--index-name idxNameRegExp]
List all indexes that match specified filters.Parameters:
--node-id nodeId - Specify node for job execution. If not specified
explicitly, node will be chosen by grid
--group-name regExp - Regular expression allowing filtering by cache
group name
--cache-name regExp - Regular expression allowing filtering by cache name
--index-name regExp - Regular expression allowing filtering by index
name --cache indexes_rebuild_status [--node-id nodeId]
List all indexes that have index rebuild in progress.Parameters:
--node-id nodeId - Specify node for job execution. If not specified
explicitly, info will be gathered from all nodes --cache indexes_force_rebuild
--node-id nodeId --cache-name cacheName1,...cacheNameN|--group-name
groupName1,...groupNameN
Triggers rebuild of all indexes for specified caches or cache groups.
Parameters:
--node-id - Specify node for indexes rebuild.
--cache-names - Comma-separated list of cache names for which indexes
should be rebuilt.
--group-names - Comma-separated list of cache group names for which
indexes should be rebuilt.
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13268) Add indexes manipulation commands to control.sh
Vladimir Malinovskiy created IGNITE-13268: - Summary: Add indexes manipulation commands to control.sh Key: IGNITE-13268 URL: https://issues.apache.org/jira/browse/IGNITE-13268 Project: Ignite Issue Type: Improvement Components: control.sh Reporter: Vladimir Malinovskiy Assignee: Vladimir Malinovskiy These subcommands are to be added to the *--cache* command: h2. --indexes_list Gets list of indexes info. Although filters can be specified via command arguments lines of output should still be grepable. h4. Argument: * *--node-id* is a UUID of node for which to perform the operation. If node isn’t specified explicitly it will be chosen by grid. * *--group-name* is a regular expression corresponding to the group name. * *--cache-name* is a regular expression corresponding to the name of the cache. * *--index-name* is a regular expression that matches the name of the index. h2. --indexes-rebuild-status Gets list of indexes that are currently being rebuilt. h4. Argument: * *--node-id* is a UUID of node for which to perform the operation. If node isn’t specified explicitly indexes rebuild info will be collected from all nodes. h2. --indexes_force_rebuild Triggers force rebuild of indexes. This information should be reported in the output: * List of caches that weren’t found. * List of caches that have index rebuild in progress. Indexes rebuild shouldn’t be restarted for these caches. * List of caches for which index rebuild was triggered. Indexes rebuild should be performed asynchronously. h4. Argument: * *--node-id* is a UUID of node for which to perform the operation. Mandatory parameter. * *--group-names* is a comma-separated list of group names for which to rebuild indexes. Either this option or --cache-names must be specified. * *--cache-names* is a comma-separated list of cache names for which to rebuild indexes. Either this option or --group-names must be specified. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12629) Fit all metrics into single standard
Vladimir Malinovskiy created IGNITE-12629: - Summary: Fit all metrics into single standard Key: IGNITE-12629 URL: https://issues.apache.org/jira/browse/IGNITE-12629 Project: Ignite Issue Type: Bug Reporter: Vladimir Malinovskiy All ignite metrics should be fitted to single standard. This standard should be discussed and documented. Oracle best practices [https://www.oracle.com/technetwork/java/javase/tech/best-practices-jsp-136021.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12628) Add tests for jmx metrics return types
Vladimir Malinovskiy created IGNITE-12628: - Summary: Add tests for jmx metrics return types Key: IGNITE-12628 URL: https://issues.apache.org/jira/browse/IGNITE-12628 Project: Ignite Issue Type: Bug Reporter: Vladimir Malinovskiy Add tests than check if JMX metrics comply with Oracle best practices([https://www.oracle.com/technetwork/java/javase/tech/best-practices-jsp-136021.html]) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12627) Control utility does not show corrupted indexes
Vladimir Malinovskiy created IGNITE-12627:
-
Summary: Control utility does not show corrupted indexes
Key: IGNITE-12627
URL: https://issues.apache.org/jira/browse/IGNITE-12627
Project: Ignite
Issue Type: Bug
Reporter: Vladimir Malinovskiy
In 2.5.11/8.5.11 control utility does not show corrupted indexes:
{noformat}
{{[avolkov@lab43 bin]$ ./control.sh --host 172.25.1.43 --port 11211 --cache
validate_indexes
Control utility [ver. 2.5.11#20191004-sha1:565c778e]
2019 Copyright(C) Apache Software Foundation
User: avolkov
Time: 2019-10-09T11:10:56.519
Command [CACHE] started
Arguments: --host 172.25.1.43 --port 11211 --cache validate_indexes
no issues found.
Command [CACHE] finished with code: 0
Control utility has completed execution at: 2019-10-09T11:10:56.916
Execution time: 397 ms}}
{noformat}{{}}
but in logs I can see:
\{noformat}
{{11:10:56,745][WARNING][pool-6-thread-3][ValidateIndexesClosure] Current
progress of ValidateIndexesClosure: checked integrity of 1 index partitions of
14 cache groups
[11:10:56,850][SEVERE][pool-6-thread-14][ValidateIndexesClosure] Find in index
failed: IndexValidationIssue [key=null, cacheName=cache_group_1_028,
idxName=EXAMPLE_IDX], class org.h2.message.DbException: General error: "class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
B+Tree is corrupted [pages(groupId, pageId)=[], cacheId=1586135659,
cacheName=cache_group_1_028, indexName=EXAMPLE_IDX, msg=Runtime failure on
bounds: [lower=null, upper=null]]" [5-195]
[11:10:56,850][SEVERE][pool-6-thread-12][ValidateIndexesClosure] Find in index
failed: IndexValidationIssue [key=null, cacheName=cache_group_1_028,
idxName=_key_PK], class org.h2.message.DbException: General error: "class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
B+Tree is corrupted [pages(groupId, pageId)=[], cacheId=1586135659,
cacheName=cache_group_1_028, indexName=_key_PK, msg=Runtime failure on bounds:
[lower=null, upper=null]]" [5-195]
[11:10:56,851][SEVERE][pool-6-thread-11][ValidateIndexesClosure] Find in index
failed: IndexValidationIssue [key=null, cacheName=cache_group_1_028,
idxName=ALLTYPESINDEXED_LONGCOL_IDX], class org.h2.message.DbException: General
error: "class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
B+Tree is corrupted [pages(groupId, pageId)=[], cacheId=1586135659,
cacheName=cache_group_1_028, indexName=ALLTYPESINDEXED_LONGCOL_IDX, msg=Runtime
failure on bounds: [lower=null, upper=null]]" [5-195]
[11:10:56,853][SEVERE][pool-6-thread-3][ValidateIndexesClosure] Find in index
failed: IndexValidationIssue [key=null, cacheName=cache_group_1_028,
idxName=EXAMPLE_IDX], class org.h2.message.DbException: General error: "class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
B+Tree is corrupted [pages(groupId, pageId)=[], cacheId=1586135659,
cacheName=cache_group_1_028, indexName=EXAMPLE_IDX, msg=Runtime failure on
bounds: [lower=null, upper=null]]" [5-195]
[11:10:56,853][SEVERE][pool-6-thread-1][ValidateIndexesClosure] Find in index
failed: IndexValidationIssue [key=null, cacheName=cache_group_1_028,
idxName=ALLTYPESINDEXED_LONGCOL_IDX], class org.h2.message.DbException: General
error: "class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
B+Tree is corrupted [pages(groupId, pageId)=[], cacheId=1586135659,
cacheName=cache_group_1_028, indexName=ALLTYPESINDEXED_LONGCOL_IDX, msg=Runtime
failure on bounds: [lower=null, upper=null]]" [5-195]
[11:10:56,856][SEVERE][pool-6-thread-6][ValidateIndexesClosure] Find in index
failed: IndexValidationIssue [key=null, cacheName=cache_group_1_028,
idxName=_key_PK], class org.h2.message.DbException: General error: "class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
B+Tree is corrupted [pages(groupId, pageId)=[], cacheId=1586135659,
cacheName=cache_group_1_028, indexName=_key_PK, msg=Runtime failure on bounds:
[lower=null, upper=null]]" [5-195]
[11:10:56,861][WARNING][mgmt-#131][ValidateIndexesClosure]
ValidateIndexesClosure finished: processed 2648 partitions and 6 indexes.}}
{noformat}{{}}
This information isn't reflected in control utility output.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12351) Append additional cp tracking activity - pages sort.
Vladimir Malinovskiy created IGNITE-12351:
-
Summary: Append additional cp tracking activity - pages sort.
Key: IGNITE-12351
URL: https://issues.apache.org/jira/browse/IGNITE-12351
Project: Ignite
Issue Type: Bug
Reporter: Vladimir Malinovskiy
Assignee: Vladimir Malinovskiy
CheckpointMetricsTracker has no info about _splitAndSortCpPagesIfNeeded_ stage,
thus in case of huge number of dirty pages someone can observe in log:
10:08:00 checkpoint started
10:10:00 checkpoint finished
<--- ??
10:10:20 checkpoint started
if checkpointFrequency = 3 and all tracker durations: beforeLockDuration,
lockWaitDuration gives no clue what kind of work (20 sec) Checkpointer thread
is waiting for.
Additionally (hope this is not big deal) need t obe fixed redundant
effectivePageId computation cause FullPageId already has effectivePageId info.
{{return Long.compare(PageIdUtils.effectivePageId(o1.pageId()),
PageIdUtils.effectivePageId(o2.pageId()));}}
writeCheckpointEntr() duration should also be logged.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-11990) Optimize heap usage for TcpDiscoveryNodeAddedMessage stored in pending messages in ServerImpl
Vladimir Malinovskiy created IGNITE-11990: - Summary: Optimize heap usage for TcpDiscoveryNodeAddedMessage stored in pending messages in ServerImpl Key: IGNITE-11990 URL: https://issues.apache.org/jira/browse/IGNITE-11990 Project: Ignite Issue Type: Improvement Reporter: Vladimir Malinovskiy Assignee: Vladimir Malinovskiy We are storing pending discovery messages in deserialized form. Pending message could be heavy, for example TcpDiscoveryNodeAddedMessage. I think we should store only information requeired for resending messages across ring. In case of TcpDiscoveryNodeAddedMessage we couldn't store unmarhalled data in DiscoveryDataPacket -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-11964) Code style failed
Vladimir Malinovskiy created IGNITE-11964: - Summary: Code style failed Key: IGNITE-11964 URL: https://issues.apache.org/jira/browse/IGNITE-11964 Project: Ignite Issue Type: Bug Reporter: Vladimir Malinovskiy Assignee: Vladimir Malinovskiy [https://ci.ignite.apache.org/viewLog.html?buildId=4258304=IgniteTests24Java8_CheckCodeStyle] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Hello
Hi! I want to start working on IGNITE-11954 Please and me to the contributor list My jira username is vmalinovskiy On Tue, May 21, 2019 at 9:32 PM Denis Magda wrote: > > Hello Vladimir and welcome aboard! > > Please get to know the process and share your JIRA id once you're ready to > take on a task: > https://ignite.apache.org/community/contribute.html#contribute > > - > Denis > > > On Tue, May 21, 2019 at 8:46 AM Vladimir Malinovskiy < > vmalinovs...@gridgain.com> wrote: > > > Hello! > > My name is Vladimir Malinovskiy. > > Please register me as Ignite developer. > > > > -- > > Vladimir Malinovskiy > > Software Engineer, Moscow > > +7-753-767-36-24 > > https://www.gridgain.com > > Powered by Apache® Ignite™ > > -- Vladimir Malinovskiy Software Engineer, Moscow +7-753-767-36-24 https://www.gridgain.com Powered by Apache® Ignite™
[jira] [Created] (IGNITE-11954) control.sh should log actions performed
Vladimir Malinovskiy created IGNITE-11954: - Summary: control.sh should log actions performed Key: IGNITE-11954 URL: https://issues.apache.org/jira/browse/IGNITE-11954 Project: Ignite Issue Type: Bug Reporter: Vladimir Malinovskiy control.sh must log all actions performed to work/log/control-utility.log The fields logged should be as follows: * date and time of action start and finish * version of utility * command name and arguments * user issued command * session id * log level * action error code and/or status message All the same fields but for log level and and session should be also logged to console. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Hello
Hello! My name is Vladimir Malinovskiy. Please register me as Ignite developer. -- Vladimir Malinovskiy Software Engineer, Moscow +7-753-767-36-24 https://www.gridgain.com Powered by Apache® Ignite™
