[jira] [Commented] (IGNITE-12733) File transmission must notify listeners when transmission ends and resources released
[
https://issues.apache.org/jira/browse/IGNITE-12733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053535#comment-17053535
]
Maxim Muzafarov commented on IGNITE-12733:
--
Merged to the master branch.
> File transmission must notify listeners when transmission ends and resources
> released
> -
>
> Key: IGNITE-12733
> URL: https://issues.apache.org/jira/browse/IGNITE-12733
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Currently, there is no such ability to notify a users receiver listener
> ({{TransmissionHandler}}) when a file transmission is fully ended.
> So, in case of the next transmission request will be fired right after the
> current on we may get an error -- "Error has been sent back to a remote node.
> The receiver holds the local topic" due to channel resources are not released
> yet.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12732) SQL: KILL QUERY command hangs on query when query cursor is held by user or leak
[
https://issues.apache.org/jira/browse/IGNITE-12732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053522#comment-17053522
]
Ignite TC Bot commented on IGNITE-12732:
{panel:title=Branch: [pull/7498/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5104597&buildTypeId=IgniteTests24Java8_RunAll]
> SQL: KILL QUERY command hangs on query when query cursor is held by user or
> leak
>
>
> Key: IGNITE-12732
> URL: https://issues.apache.org/jira/browse/IGNITE-12732
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Scenario to reproduce:
> 1. Execute a query
> 2. Don't close the query cursor, don't iterate to the end of results.
> 3. Run "KILL QUERY" command. The command hangs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12756) TcpCommunicationSpi metrics implementation improvements
[
https://issues.apache.org/jira/browse/IGNITE-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053481#comment-17053481
]
Ivan Bessonov commented on IGNITE-12756:
[~agura] looks good, I see no issues in your code, thank you!
> TcpCommunicationSpi metrics implementation improvements
>
>
> Key: IGNITE-12756
> URL: https://issues.apache.org/jira/browse/IGNITE-12756
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
> Labels: IEP-35
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Implementation of IGNITE-12682 allows now to create sent/received counters by
> message direct type statically during SPI initialization. Data structure for
> this counters does have any contention so we can remove thread local
> HashMap's for this counters. As result we will also reduce memory footprint
> (we can use IntHashMap which is more memory effective and we will have only
> one map instance instead of map per thread).
> Also there is a couple of problems which could be solved during
> implementation this issue:
> - SPI uses internal API while we should extend IgniteSpiContext that will
> provide access to the {{GridMEtricManager}} functionality.
> - {{MetricManagerResource}} annotation is redundant and has only one usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12757) ignitevisorcmd does not connect to the cluster
[ https://issues.apache.org/jira/browse/IGNITE-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12757: - Ignite Flags: (was: Docs Required,Release Notes Required) > ignitevisorcmd does not connect to the cluster > -- > > Key: IGNITE-12757 > URL: https://issues.apache.org/jira/browse/IGNITE-12757 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Nikolai Kulagin >Priority: Blocker > Fix For: 2.8.1 > > > ignitevisorcmd does not connect to the cluster (on default configs). The log > does not contain any errors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12757) ignitevisorcmd does not connect to the cluster
[ https://issues.apache.org/jira/browse/IGNITE-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12757: - Priority: Blocker (was: Major) > ignitevisorcmd does not connect to the cluster > -- > > Key: IGNITE-12757 > URL: https://issues.apache.org/jira/browse/IGNITE-12757 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Nikolai Kulagin >Priority: Blocker > > ignitevisorcmd does not connect to the cluster (on default configs). The log > does not contain any errors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12757) ignitevisorcmd does not connect to the cluster
[ https://issues.apache.org/jira/browse/IGNITE-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12757: - Fix Version/s: 2.8.1 > ignitevisorcmd does not connect to the cluster > -- > > Key: IGNITE-12757 > URL: https://issues.apache.org/jira/browse/IGNITE-12757 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Nikolai Kulagin >Priority: Blocker > Fix For: 2.8.1 > > > ignitevisorcmd does not connect to the cluster (on default configs). The log > does not contain any errors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12756) TcpCommunicationSpi metrics implementation improvements
[
https://issues.apache.org/jira/browse/IGNITE-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-12756:
Ignite Flags: (was: Docs Required,Release Notes Required)
> TcpCommunicationSpi metrics implementation improvements
>
>
> Key: IGNITE-12756
> URL: https://issues.apache.org/jira/browse/IGNITE-12756
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Implementation of IGNITE-12682 allows now to create sent/received counters by
> message direct type statically during SPI initialization. Data structure for
> this counters does have any contention so we can remove thread local
> HashMap's for this counters. As result we will also reduce memory footprint
> (we can use IntHashMap which is more memory effective and we will have only
> one map instance instead of map per thread).
> Also there is a couple of problems which could be solved during
> implementation this issue:
> - SPI uses internal API while we should extend IgniteSpiContext that will
> provide access to the {{GridMEtricManager}} functionality.
> - {{MetricManagerResource}} annotation is redundant and has only one usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12756) TcpCommunicationSpi metrics implementation improvements
[
https://issues.apache.org/jira/browse/IGNITE-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-12756:
Labels: IEP-35 (was: )
> TcpCommunicationSpi metrics implementation improvements
>
>
> Key: IGNITE-12756
> URL: https://issues.apache.org/jira/browse/IGNITE-12756
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
> Labels: IEP-35
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Implementation of IGNITE-12682 allows now to create sent/received counters by
> message direct type statically during SPI initialization. Data structure for
> this counters does have any contention so we can remove thread local
> HashMap's for this counters. As result we will also reduce memory footprint
> (we can use IntHashMap which is more memory effective and we will have only
> one map instance instead of map per thread).
> Also there is a couple of problems which could be solved during
> implementation this issue:
> - SPI uses internal API while we should extend IgniteSpiContext that will
> provide access to the {{GridMEtricManager}} functionality.
> - {{MetricManagerResource}} annotation is redundant and has only one usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12756) TcpCommunicationSpi metrics implementation improvements
[
https://issues.apache.org/jira/browse/IGNITE-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053459#comment-17053459
]
Andrey N. Gura commented on IGNITE-12756:
-
I already run test using other branch and PR so change could be reviewed while
I am trying to get new visa.
> TcpCommunicationSpi metrics implementation improvements
>
>
> Key: IGNITE-12756
> URL: https://issues.apache.org/jira/browse/IGNITE-12756
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Implementation of IGNITE-12682 allows now to create sent/received counters by
> message direct type statically during SPI initialization. Data structure for
> this counters does have any contention so we can remove thread local
> HashMap's for this counters. As result we will also reduce memory footprint
> (we can use IntHashMap which is more memory effective and we will have only
> one map instance instead of map per thread).
> Also there is a couple of problems which could be solved during
> implementation this issue:
> - SPI uses internal API while we should extend IgniteSpiContext that will
> provide access to the {{GridMEtricManager}} functionality.
> - {{MetricManagerResource}} annotation is redundant and has only one usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12757) ignitevisorcmd does not connect to the cluster
[ https://issues.apache.org/jira/browse/IGNITE-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolai Kulagin updated IGNITE-12757: - Description: ignitevisorcmd does not connect to the cluster (on default configs). The log does not contain any errors. (was: ignitevisorcmd does not connect to the cluster. The log does not contain any errors.) > ignitevisorcmd does not connect to the cluster > -- > > Key: IGNITE-12757 > URL: https://issues.apache.org/jira/browse/IGNITE-12757 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Nikolai Kulagin >Priority: Major > > ignitevisorcmd does not connect to the cluster (on default configs). The log > does not contain any errors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12757) ignitevisorcmd does not connect to the cluster
Nikolai Kulagin created IGNITE-12757: Summary: ignitevisorcmd does not connect to the cluster Key: IGNITE-12757 URL: https://issues.apache.org/jira/browse/IGNITE-12757 Project: Ignite Issue Type: Bug Affects Versions: 2.8 Reporter: Nikolai Kulagin ignitevisorcmd does not connect to the cluster. The log does not contain any errors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12756) TcpCommunicationSpi metrics implementation improvements
[
https://issues.apache.org/jira/browse/IGNITE-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-12756:
Description:
Implementation of IGNITE-12682 allows now to create sent/received counters by
message direct type statically during SPI initialization. Data structure for
this counters does have any contention so we can remove thread local HashMap's
for this counters. As result we will also reduce memory footprint (we can use
IntHashMap which is more memory effective and we will have only one map
instance instead of map per thread).
Also there is a couple of problems which could be solved during implementation
this issue:
- SPI uses internal API while we should extend IgniteSpiContext that will
provide access to the {{GridMEtricManager}} functionality.
- {{MetricManagerResource}} annotation is redundant and has only one usage.
was:
Implementation of IGNITE-12682 allows now to create cent/received counters by
message direct type statically during SPI initialization. Data structure for
this counters does have any contention so we can remove thread local HashMap's
for this counters. As result we will also reduce memory footprint (we can use
IntHashMap which is more memory effective and we will have only one map
instance instead of map per thread).
Also there is a couple of problems which could be solved during implementation
this issue:
- SPI uses internal API while we should extend IgniteSpiContext that will
provide access to the {{GridMEtricManager}} functionality.
- {{MetricManagerResource}} annotation is redundant and has only one usage.
> TcpCommunicationSpi metrics implementation improvements
>
>
> Key: IGNITE-12756
> URL: https://issues.apache.org/jira/browse/IGNITE-12756
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
>
> Implementation of IGNITE-12682 allows now to create sent/received counters by
> message direct type statically during SPI initialization. Data structure for
> this counters does have any contention so we can remove thread local
> HashMap's for this counters. As result we will also reduce memory footprint
> (we can use IntHashMap which is more memory effective and we will have only
> one map instance instead of map per thread).
> Also there is a couple of problems which could be solved during
> implementation this issue:
> - SPI uses internal API while we should extend IgniteSpiContext that will
> provide access to the {{GridMEtricManager}} functionality.
> - {{MetricManagerResource}} annotation is redundant and has only one usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12756) TcpCommunicationSpi metrics implementation improvements
Andrey N. Gura created IGNITE-12756:
---
Summary: TcpCommunicationSpi metrics implementation improvements
Key: IGNITE-12756
URL: https://issues.apache.org/jira/browse/IGNITE-12756
Project: Ignite
Issue Type: Improvement
Reporter: Andrey N. Gura
Assignee: Andrey N. Gura
Implementation of IGNITE-12682 allows now to create cent/received counters by
message direct type statically during SPI initialization. Data structure for
this counters does have any contention so we can remove thread local HashMap's
for this counters. As result we will also reduce memory footprint (we can use
IntHashMap which is more memory effective and we will have only one map
instance instead of map per thread).
Also there is a couple of problems which could be solved during implementation
this issue:
- SPI uses internal API while we should extend IgniteSpiContext that will
provide access to the {{GridMEtricManager}} functionality.
- {{MetricManagerResource}} annotation is redundant and has only one usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12733) File transmission must notify listeners when transmission ends and resources released
[
https://issues.apache.org/jira/browse/IGNITE-12733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053413#comment-17053413
]
Pavel Pereslegin commented on IGNITE-12733:
---
[~mmuzaf], looks good to me, thanks for this fix.
> File transmission must notify listeners when transmission ends and resources
> released
> -
>
> Key: IGNITE-12733
> URL: https://issues.apache.org/jira/browse/IGNITE-12733
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Currently, there is no such ability to notify a users receiver listener
> ({{TransmissionHandler}}) when a file transmission is fully ended.
> So, in case of the next transmission request will be fired right after the
> current on we may get an error -- "Error has been sent back to a remote node.
> The receiver holds the local topic" due to channel resources are not released
> yet.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12728) The cache#putAllAsync method does not collect statistics
[
https://issues.apache.org/jira/browse/IGNITE-12728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053295#comment-17053295
]
Aleksey Plekhanov commented on IGNITE-12728:
[~agura], I agree with Nikita. Using putAllAsync is ever worse now, because we
don't increment put time at all and it leads to more significant statistics
skew.
Computing statistics in a right way is not only extract dedicated metrics for
putAll/getAll/removeAll time. It's a complicated task, because:
# Puts count is incremented in {{innerSet/innerUpdate}} methods, and not
coupled directly with {{put}} or {{putAll}} methods, we can't distinct two
different calls from two different methods.
# Puts count is incremented on each affinity (primary or backup) node, but put
time is incremented only on initiator node.
So, to compute average operations time we should add new metrics counting
put/putAll/get/getAll/remove/removeAll invocations on initiator node and these
metrics should be counted independently of current operations count metrics on
affinity node.
> The cache#putAllAsync method does not collect statistics
>
>
> Key: IGNITE-12728
> URL: https://issues.apache.org/jira/browse/IGNITE-12728
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: IEP-35
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The cache#putAllAsync method does not collect statistics.
> The reproducer for {{GridCacheAbstractMetricsSelfTest}}:
> {noformat}
> @Test
> public void testPutAllAsyncAvgTime() throws Exception {
> IgniteCache cache =
> grid(0).cache(DEFAULT_CACHE_NAME);
> assertEquals(0.0, cache.localMetrics().getAveragePutTime(), 0.0);
> assertEquals(0, cache.localMetrics().getCachePuts());
> Map values = new HashMap<>();
> values.put(1, 1);
> values.put(2, 2);
> values.put(3, 3);
> IgniteFuture fut = cache.putAllAsync(values);
> fut.get();
> assertTrue(waitForCondition(() ->
> cache.localMetrics().getAveragePutTime() > 0, 30_000));
> assertEquals(values.size(), cache.localMetrics().getCachePuts());
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Deleted] (IGNITE-12755) Not enough information about error
[
https://issues.apache.org/jira/browse/IGNITE-12755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev deleted IGNITE-12755:
-
> Not enough information about error
> --
>
> Key: IGNITE-12755
> URL: https://issues.apache.org/jira/browse/IGNITE-12755
> Project: Ignite
> Issue Type: Improvement
>Reporter: Surkov Aleksandr
>Priority: Major
>
> Unfortunately, when one node leaves the topology failure handler does not
> print enough information.
>
> {code:java}
> JVM will be halted immediately due to the failure: [failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.NullPointerException]]
> vmop [threads: total initially_running wait_to_block]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12701) Disallow silent deactivation in CLI and REST.
[
https://issues.apache.org/jira/browse/IGNITE-12701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053209#comment-17053209
]
Ignite TC Bot commented on IGNITE-12701:
{panel:title=Branch: [pull/7471/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5100677&buildTypeId=IgniteTests24Java8_RunAll]
> Disallow silent deactivation in CLI and REST.
> -
>
> Key: IGNITE-12701
> URL: https://issues.apache.org/jira/browse/IGNITE-12701
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.7.6
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 6h
> Remaining Estimate: 0h
>
> Disallow silent deactivation through the CLI and REST.
> Skip JMX call
> {code:java}
> void IgniteMXBean#active(boolean active)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-12549) Scan query/iterator on a replicated cache may get wrong results
[ https://issues.apache.org/jira/browse/IGNITE-12549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin resolved IGNITE-12549. - Fix Version/s: (was: 2.8.1) Resolution: Fixed [~macrergate], I merged PR to master. Thank you for contribution! By the way I left only 2.9 as fix version as it is resolved only in master for now. > Scan query/iterator on a replicated cache may get wrong results > --- > > Key: IGNITE-12549 > URL: https://issues.apache.org/jira/browse/IGNITE-12549 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7.6 >Reporter: Sergey Kosarev >Assignee: Sergey Kosarev >Priority: Critical > Fix For: 2.9 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > Case 1 > 1. start server node 1 > 2. create and fill replicated cache with RebalanceMode.Async (as by default) > 3. start servr node 2 > 4. immediately execute scan query on the replicated cache((or just iterate > the cache)) on the node 2 > It can get empty or partial results. (if rebalance on node 2 is finished) > Case 2 > 1. start server node 1 > 2. create and fill replicated cache with RebalanceMode.Async (as by default) > 3. start client node 2 > 4. start server node 3 > 5. immediately execute scan query on the replicated cache((or just iterate > the cache)) on the client node 2 > It can get empty or partial results. (if rebalance on node 2 is not finished > and query is mapped on the node 2) > It looks like problem in the > org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter#nodes() > case REPLICATED: > if (prj != null || part != null) > return nodes(cctx, prj, part); > if (cctx.affinityNode()) > return *Collections.singletonList(cctx.localNode())*; > Collection affNodes = nodes(cctx, null, null); > return affNodes.isEmpty() ? affNodes : > *Collections.singletonList(F.rand(affNodes))*; > case PARTITIONED: > return nodes(cctx, prj, part); > which is executed in > org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter#executeScanQuery. > If executed on a just started node it obviously returns the local node > disregarding was it rebalanced or not. > If executed on a client it returns a random affinity node, so it also can be > not yet rebalanced node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12740) Supports feature flags on index meta page
[ https://issues.apache.org/jira/browse/IGNITE-12740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053150#comment-17053150 ] Taras Ledkov edited comment on IGNITE-12740 at 3/6/20, 8:33 AM: [~amashenkov], [~ivan.glukos] please review the patch. was (Author: tledkov-gridgain): [~amashenkov], please review the patch. > Supports feature flags on index meta page > - > > Key: IGNITE-12740 > URL: https://issues.apache.org/jira/browse/IGNITE-12740 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Some changes on indexing e.g. inl;ine java objects, unwrap PK columns and > several planned features (change inline pojo format, inline DECIMAL fields > etc) break backward compatibility. > We have to add metadata about index layout and format to index tree meta-page. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-12755) Not enough information about error
[
https://issues.apache.org/jira/browse/IGNITE-12755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Surkov Aleksandr resolved IGNITE-12755.
---
Resolution: Fixed
The problem was in the logging settings.
> Not enough information about error
> --
>
> Key: IGNITE-12755
> URL: https://issues.apache.org/jira/browse/IGNITE-12755
> Project: Ignite
> Issue Type: Improvement
>Reporter: Surkov Aleksandr
>Priority: Major
>
> Unfortunately, when one node leaves the topology failure handler does not
> print enough information.
>
> {code:java}
> JVM will be halted immediately due to the failure: [failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.NullPointerException]]
> vmop [threads: total initially_running wait_to_block]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12740) Supports feature flags on index meta page
[
https://issues.apache.org/jira/browse/IGNITE-12740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053141#comment-17053141
]
Ignite TC Bot commented on IGNITE-12740:
{panel:title=Branch: [pull/7493/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5098391&buildTypeId=IgniteTests24Java8_RunAll]
> Supports feature flags on index meta page
> -
>
> Key: IGNITE-12740
> URL: https://issues.apache.org/jira/browse/IGNITE-12740
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some changes on indexing e.g. inl;ine java objects, unwrap PK columns and
> several planned features (change inline pojo format, inline DECIMAL fields
> etc) break backward compatibility.
> We have to add metadata about index layout and format to index tree meta-page.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
