[jira] [Created] (IGNITE-12304) All DataRegionMetrics should be documented
Andrey Kuznetsov created IGNITE-12304:
-
Summary: All DataRegionMetrics should be documented
Key: IGNITE-12304
URL: https://issues.apache.org/jira/browse/IGNITE-12304
Project: Ignite
Issue Type: Task
Components: documentation
Reporter: Andrey Kuznetsov
Fix For: 2.8
All metrics added to {{DataRegionMetrics}} interface by [1] should be
documented.
[1] https://issues.apache.org/jira/browse/IGNITE-8078
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11992) Improvements for new security approach
[
https://issues.apache.org/jira/browse/IGNITE-11992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16955891#comment-16955891
]
Ignite TC Bot commented on IGNITE-11992:
{panel:title=Branch: [pull/6990/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=4708108buildTypeId=IgniteTests24Java8_RunAll]
> Improvements for new security approach
> --
>
> Key: IGNITE-11992
> URL: https://issues.apache.org/jira/browse/IGNITE-11992
> Project: Ignite
> Issue Type: Improvement
> Components: security
>Affects Versions: 2.8
>Reporter: Stepachev Maksim
>Assignee: Stepachev Maksim
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> 1. The visor tasks lost permission.
> The method VisorQueryUtils#scheduleQueryStart makes a new thread and loses
> context.
> 2. The GridRestProcessor does tasks outside "withContext" section. As result
> context loses.
> In additional:
> Change a java docs for TaskEvent, CacheEvent, CacheQueryExecutedEvent and
> CacheQueryReadEvent.
> "Gets security subject ID initiated this task event, if available.
> This property is not available for GridEventType#EVT_TASK_SESSION_ATTR_SET
> task event.
> Subject ID will be set either to node ID or client ID initiated task
> execution."
> by:
> "Gets security subject ID initiated this task event if IgniteSecurity is
> enabled, otherwise returns null."
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12142) Ignite ignores that on-heap store is disabled when putting values through near cache
[
https://issues.apache.org/jira/browse/IGNITE-12142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16955896#comment-16955896
]
Alexey Goncharuk commented on IGNITE-12142:
---
[~bstefanski], [~dmagda], this is an expected behavior based on the current
near cache design. The reason for keeping a reader is to properly update near
caches when an update for the corresponding cache entry happens.
Moving this to offheap is quite complicated. We cannot keep this information in
the data store tree because it is persisted when Ignite native persistence is
enabled, but the readers information is transient. Moving this information to a
separate off-heap data structure will most likely impose a visible slowdown for
reads (however, this may be a reasonable tradeoff given that subsequent reads
will be server from near nodes).
I am not sure if anybody in the community is willing to work on this
improvement as of now.
> Ignite ignores that on-heap store is disabled when putting values through
> near cache
>
>
> Key: IGNITE-12142
> URL: https://issues.apache.org/jira/browse/IGNITE-12142
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7, 2.7.5
>Reporter: Bartłomiej Stefański
>Priority: Major
>
> I have an Ignite cluster that consists of two nodes:
> * @n0 - server node
> * @n1 - client node
> Installed PARTITIONED cache {{myCache}} on both of them. Cache has near cache
> on client node and disabled on-heap caching on server.
> Server configuration:
> {code:xml}
>
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd;>
>
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
>
>
>
>
>
>
>
> {code}
> Client configuration:
> {code:xml}
>
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd;>
>
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
>
>
>
> class="org.apache.ignite.configuration.NearCacheConfiguration">
>
> class="org.apache.ignite.cache.eviction.lru.LruEvictionPolicy">
>
>
>
>
>
>
>
>
>
>
> {code}
> I have noticed (using visor) strange cache state after putting 20k entries to
> that cache through client node (@n1):
> {code}
> +==+
> | Node ID8(@), IP | CPUs | Heap Used | CPU Load | Up Time|
> Size (Primary / Backup)| Hi/Mi/Rd/Wr |
> +==+
> | 99E64885(@n0), 172.17.0.1 | 4| 2.56 %| 0.50 % | 00:02:47.615 |
> Total: 4 (4 / 0) | Hi: 0 |
> | | | | | |
> Heap: 2 (2 / ) | Mi: 0 |
> | | | | | |
> Off-Heap: 2 (2 / 0) | Rd: 0 |
> | | | | | |
> Off-Heap Memory: | Wr: 0 |
> +---+--+---+--+--+---+-+
> | FE7BEE4F(@n1), 172.17.0.1 | 4| 3.89 %| 3.10 % | 00:02:37.269 |
> Total: 1000 (1000 / 0)| Hi: 0 |
> | | | | | |
> Heap: 1000 (1000 / ) | Mi: 0 |
> | | | | | |
> Off-Heap: 0 (0 / 0) | Rd: 0 |
> | | | | | |
> Off-Heap Memory: 0 | Wr: 0 |
> +--+
> {code}
> Why Ignite stores entries
[jira] [Updated] (IGNITE-12304) All DataRegionMetrics should be documented
[
https://issues.apache.org/jira/browse/IGNITE-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-12304:
-
Ignite Flags: Docs Required (was: Docs Required,Release Notes Required)
> All DataRegionMetrics should be documented
> --
>
> Key: IGNITE-12304
> URL: https://issues.apache.org/jira/browse/IGNITE-12304
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Andrey Kuznetsov
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8
>
>
> All metrics added to {{DataRegionMetrics}} interface by [1] should be
> documented.
> [1] https://issues.apache.org/jira/browse/IGNITE-8078
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-11724) IgniteSpark integration forget to close the IgniteContext and stops the client node in case if error during PairFunction logic
[
https://issues.apache.org/jira/browse/IGNITE-11724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16955967#comment-16955967
]
Andrey Aleksandrov edited comment on IGNITE-11724 at 10/21/19 11:21 AM:
[~nizhikov] sorry, my example wasn't full. {{IgniteContext#close doesn't help
in this case. Please take a look at the updated example and logs.}}
{{After getting IllegalStateException("some error") current job will not be
stopped at all and Ignite node started in spark will continue working
regardless of }}{{IgniteContext#close method call.}}{{}}
{{Possible it can be fixed more accurate but the current fix can help with this
case.}}
{{BR,}}
{{Andrei}}
was (Author: aealeksandrov):
[~nizhikov] sorry, my example wasn't full. {{IgniteContext#close doesn't help
in this case. Please take a look at the updated example and logs.}}
{{After getting IllegalStateException("some error") current job will not be
stopped at all.}}
{{Possible it can be fixed more accurate but the current fix can help with this
case.}}
{{BR,}}
{{Andrei}}
> IgniteSpark integration forget to close the IgniteContext and stops the
> client node in case if error during PairFunction logic
> ---
>
> Key: IGNITE-11724
> URL: https://issues.apache.org/jira/browse/IGNITE-11724
> Project: Ignite
> Issue Type: Bug
> Components: spark
>Affects Versions: 2.8
>Reporter: Andrey Aleksandrov
>Assignee: Alexey Zinoviev
>Priority: Major
> Labels: await
> Fix For: 2.8
>
> Attachments: logs.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Next code could hang in case if PairFunction logic will throw the exception:
> {code:java}
> public class Example {
> public static void main(String[] args) {
> String configPath =
> "/home/andrei/BDP/big-data-accelerator/modules/gridgain-spark-loader-examples/config/client.xml";
> IgniteSparkSession igniteSession = IgniteSparkSession.builder()
> .appName("Spark Ignite catalog example")
> .master("local")
> .config("ignite.disableSparkSQLOptimization", true)
> .igniteConfig(configPath)
> .getOrCreate();
> JavaSparkContext sparkCtx = new
> JavaSparkContext(igniteSession.sparkContext());
> final JavaRDD records = sparkCtx.parallelize(Arrays.asList(
> new GenericRow()
> ));
> JavaPairRDD rdd_records = records.mapToPair(new
> PairFunction() {
> @Override
> public Tuple2 call(Row row) throws Exception {
> throw new IllegalStateException("some error");
> }
> });
> JavaIgniteContext igniteContext = new
> JavaIgniteContext<>(sparkCtx, configPath);
> JavaIgniteRDD igniteRdd = igniteContext. Integer>fromCache("Person");
> igniteRdd.savePairs(rdd_records);
> igniteContext.close(true);
> }
> }
> Looks like next internal code (saveValues method)should also close the
> IgniteContext in case of an unexpected exception, not only data streamer:
> try {
> it.foreach(value ⇒
> { val key = affinityKeyFunc(value, node.orNull)
> streamer.addData(key, value) }
> )
> }
> finally
> { streamer.close() }
> })
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-8003) Dead documentation interface element
[ https://issues.apache.org/jira/browse/IGNITE-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-8003: Fix Version/s: (was: 2.8) 2.9 > Dead documentation interface element > > > Key: IGNITE-8003 > URL: https://issues.apache.org/jira/browse/IGNITE-8003 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.4 >Reporter: Peter Ivanov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.9 > > Attachments: Screen_Shot_2018_03_15_at_11_43_07.png > > > Most of the tables in lists of artifacts (for example on Downloads page) have > strange interface element settling down to the right, which does nothing (see > [^Screen_Shot_2018_03_15_at_11_43_07.png]). > I guess it should be either removed or fixed, whatever designation it has. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel=16956075#comment-16956075 ] Maxim Muzafarov commented on IGNITE-7704: - [~slukyanov] Hello, what should be the next steps to resolve this issue? > 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.8 > > 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.8) 2.9 > 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.9 > > -- 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.8) 2.9 > 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.9 > > 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-10740) Add documentation for IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT
[
https://issues.apache.org/jira/browse/IGNITE-10740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-10740:
-
Fix Version/s: (was: 2.8)
> Add documentation for IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT
> -
>
> Key: IGNITE-10740
> URL: https://issues.apache.org/jira/browse/IGNITE-10740
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Sergey Antonov
>Assignee: Alexey Goncharuk
>Priority: Major
>
> We should add to documentation
> IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT option.
> As a reference you could get javadoc from skipInterceptor() :
> {{Checks, that cache interceptor should be skipped. It is expects by default
> behavior that Interceptor methods (\{@link
> CacheInterceptor#onBeforePut(Cache.Entry, Object)}, \{@link
> CacheInterceptor#onAfterPut(Cache.Entry)}, \{@link
> CacheInterceptor#onBeforeRemove(Cache.Entry)} and \{@link
> CacheInterceptor#onAfterRemove(Cache.Entry)}) will be called, but \{@link
> CacheInterceptor#onGet(Object, Object)}. This can even make DR-update flow
> broken in case of non-idempotent Interceptor and force users to call onGet
> manually as the only workaround. Also, user may want to skip Interceptor to
> avoid redundant entry transformation for DR updates and exchange with
> internal data b/w data centres which is a normal case.}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-9308) Add baseline topology command to REST API
[ https://issues.apache.org/jira/browse/IGNITE-9308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-9308: Ignite Flags: Docs Required,Release Notes Required (was: Docs Required) > Add baseline topology command to REST API > -- > > Key: IGNITE-9308 > URL: https://issues.apache.org/jira/browse/IGNITE-9308 > Project: Ignite > Issue Type: Bug > Components: rest >Affects Versions: 2.6 >Reporter: ARomantsov >Assignee: Andrey Novikov >Priority: Major > Fix For: 2.8 > > > Not found in https://apacheignite.readme.io/docs/rest-api info about baseline > command https://apacheignite.readme.io/docs/baseline-topology -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9524) Ignite Spring Session Integration
[ https://issues.apache.org/jira/browse/IGNITE-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-9524: Fix Version/s: (was: 2.8) > Ignite Spring Session Integration > - > > Key: IGNITE-9524 > URL: https://issues.apache.org/jira/browse/IGNITE-9524 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Prachi Garg >Assignee: Prachi Garg >Priority: Major > > Mentioned in https://cwiki.apache.org/confluence/display/IGNITE/Required+Docs > > [https://github.com/antkr/spring-session-ignite] and > [https://github.com/antkr/spring-session-ignite-rest] - to be merged to Ignite > > [https://apacheignite-mix.readme.io/docs] under "Spring" section with a > reference from "web session clustering" section. Ignite web site needs to be > updated as well - > [https://ignite.apache.org/use-cases/caching/web-session-clustering.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10051) Kubernetes documentation improvements
[
https://issues.apache.org/jira/browse/IGNITE-10051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-10051:
-
Fix Version/s: (was: 2.8)
> Kubernetes documentation improvements
> -
>
> Key: IGNITE-10051
> URL: https://issues.apache.org/jira/browse/IGNITE-10051
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.6
>Reporter: Maxim Pudov
>Assignee: Artem Budnikov
>Priority: Major
> Attachments: kube-dashboard-access.yaml, mongodb-deployment.yaml
>
>
> I verified the deployment instructions of a kubernetes cluster with apache
> ignite and found some issues.
> 1. AWS deployment:
> [https://apacheignite.readme.io/docs/amazon-web-services-eks-deployment]
> miss print:
> {quote}{{kubbectl get pods}}
> {quote}
> has to be:
> {quote}{{kubectl get pods}}
> {quote}
> 2. Google Cloud deployment
> [https://apacheignite.readme.io/docs/google-cloud-deployment]
> Screenshots seem to be outdated
> 3. Microsoft Azure deployment
> [https://apacheignite.readme.io/docs/microsoft-azure-deployment#section-access-to-your-kubernetes-cluster]
> 3.1 At first I had no access to Kubernetes dashboard having this error:
> azure kubernetes dashboard namespaces is forbidden: User
> "system:serviceaccount:kube-system:kubernetes-dashboard" cannot list
> namespaces at the cluster scope
> This problem was solved by adding this config:
> {quote}kubectl create -f [^kube-dashboard-access.yaml]
> {quote}
> 3.2 Screenshots seem to be outdated for azure too.
> 4. Stateless deployment:
> [https://apacheignite.readme.io/docs/stateless-deployment]
> 4.1 At first we create example-cube-rbac.xml locally, but then we don't use
> it.
> 4.2 Instead the configuration file ignite-deployment.yaml
> ([https://apacheignite.readme.io/docs/stateless-deployment#section-ignite-pods-deployment])
> points to the wrong external configuration file:
> {quote}{{https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube-persistence.xml}}
> {quote}
> I believe, it has to point to
> {quote}[{{https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube-rback.xml}}|https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube-rbac.xml]
> {quote}
> 4.3 In the same configuration file ignite-deployment.yaml there is a row
> {quote}{{serviceAccountName: ignite}}
> {quote}
> with Tab symbol, which has to be replaced with double Space.
> 5. Web console kubernetes installation.
> [https://apacheignite-tools.readme.io/docs/kubernetes-installation]
> 5.1 mongodb-deployment.yaml doesn't work as is. I had to modified it (check
> the attachment [^mongodb-deployment.yaml])
> 5.2 web-console-deployment.yaml - default image values aren't specified for
> frontend and backend (apacheignite/web-console-frontend,
> apacheignite/web-console-backend)
> 5.3 web-agent-deployment.yaml - serviceAccountName: "ignite-cluster" is
> incorrect. I guess "ignite" is the right one.
> 5.4 No such docker image as apacheignite/web-agent:mytag3.
> 6. General suggestions for kubernetes cluster deployment on GCC, AWS, Azure.
> 6.1 Create cluster via AWS Console, not command line. It's easier to pick
> values from drop down lists, and we don't provide complete installation via
> command line anyway.
> 6.2 When we suggest to use our configuration files for setting up services
> and pods, it is worth mentioning that our configs contain region parameter
> (zones: eu-west-1a) and user has to modify it himself.
> 6.3 The link to download configuration files points to the master branch,
> which could cause problems in future. For AWS it's
> [https://github.com/apache/ignite/tree/master/modules/kubernetes/config/eks]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-9780) SQL system view for cache groups
[
https://issues.apache.org/jira/browse/IGNITE-9780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-9780:
Ignite Flags: Docs Required,Release Notes Required (was: Docs Required)
> SQL system view for cache groups
>
>
> Key: IGNITE-9780
> URL: https://issues.apache.org/jira/browse/IGNITE-9780
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: iep-13
> Fix For: 2.8
>
>
> Implement SQL system view to show list of cache groups.
> View must contain information: cache group id, cache group name, caches
> count, and attributes related to cache group from CacheConfiguration (at
> least attributes checked in
> {{ClusterCachesInfo#validateCacheGroupConfiguration()}} method)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11029) Public API for edge-chasing deadlock detection configuration
[
https://issues.apache.org/jira/browse/IGNITE-11029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11029:
-
Ignite Flags: Docs Required,Release Notes Required (was: Docs Required)
> Public API for edge-chasing deadlock detection configuration
>
>
> Key: IGNITE-11029
> URL: https://issues.apache.org/jira/browse/IGNITE-11029
> Project: Ignite
> Issue Type: Task
> Components: mvcc
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> As deadlock detection introduce overhead during transaction processing some
> configuration means should be introduced. Following aspects should be
> addressed:
> 1. Turning detection on/off.
> 2. Adjusting a timeout before starting actual detection.
> It is proposed to introduce single property in {{TransactionConfiguration}}
> to address both concerns.
> Also it is desired that configuration is consistent across all cluster nodes
> (detection turned off on even one node can lead to undetected deadlocks).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11341) SQL: Enable lazy mode by default
[ https://issues.apache.org/jira/browse/IGNITE-11341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11341: - Ignite Flags: Docs Required,Release Notes Required (was: Docs Required) > SQL: Enable lazy mode by default > > > Key: IGNITE-11341 > URL: https://issues.apache.org/jira/browse/IGNITE-11341 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Priority: Critical > Labels: h2-limitation > > We redesigned lazy mode, so that now it doesn't spawn new thread and has the > same performance as old "eager" mode (IGNITE-9171). However, we didn't enable > it by default because H2 1.4.197 contains several bugs causing query engine > slowdown in some cases when lazy mode is set. These issues are resolved in H2 > master and will become available as a part of the next release (presumably > 1.4.198). > We need to make lazy mode enabled by default once new version is available > (IGNITE-10801). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9322) MVCC: implement deadlock detector
[ https://issues.apache.org/jira/browse/IGNITE-9322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-9322: Ignite Flags: Docs Required,Release Notes Required (was: Docs Required) > MVCC: implement deadlock detector > - > > Key: IGNITE-9322 > URL: https://issues.apache.org/jira/browse/IGNITE-9322 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Vladimir Ozerov >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Deadlocks are not uncommon during SQL execution. > We need to implement distributed deadlock detection protocol for MVCC. > Essentially, nodes should exchange some map of tx wait lists, and try to find > a loop. If loop is found, then one of problematic transactions should be > rolled back. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11363) Document replicated cache performance degradation.
[ https://issues.apache.org/jira/browse/IGNITE-11363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11363: - Fix Version/s: (was: 2.8) > Document replicated cache performance degradation. > -- > > Key: IGNITE-11363 > URL: https://issues.apache.org/jira/browse/IGNITE-11363 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Sergey Kozlov >Priority: Major > > The performance degradation for REPLICATED caches should be properly > documented -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10206) Allow specifying query parallelism in CREATE TABLE's WITH "" clause
[
https://issues.apache.org/jira/browse/IGNITE-10206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-10206:
-
Ignite Flags: Docs Required,Release Notes Required (was: Docs Required)
> Allow specifying query parallelism in CREATE TABLE's WITH "" clause
> ---
>
> Key: IGNITE-10206
> URL: https://issues.apache.org/jira/browse/IGNITE-10206
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Kuznetsov
>Priority: Minor
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As in
> {code}
> CREATE TABLE foo (id long primary key, val varchar) WITH "backups=1,
> query_parallelism=4";
> {code}
> upd: actually "parallelism=4"
> Currently it is possible to specify e.g. backups but not query_parallelism.
> This leads to necessity to specify cache template for such tables, which is
> cumbersome.
> Moreover, people may ignore this option outright and get worse performance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-9500) SQL system view for list of caches
[ https://issues.apache.org/jira/browse/IGNITE-9500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-9500: Ignite Flags: Docs Required,Release Notes Required > SQL system view for list of caches > -- > > Key: IGNITE-9500 > URL: https://issues.apache.org/jira/browse/IGNITE-9500 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: iep-13 > Fix For: 2.8 > > > Implement SQL system view to show list of caches with basic cache information > (name, cache group, atomicity mode, cache mode, data region) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11724) IgniteSpark integration forget to close the IgniteContext and stops the client node in case if error during PairFunction logic
[
https://issues.apache.org/jira/browse/IGNITE-11724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Aleksandrov updated IGNITE-11724:
Description:
Next code could hang in case if PairFunction logic will throw the exception:
{code:java}
public class Example {
public static void main(String[] args) {
String configPath =
"/home/andrei/BDP/big-data-accelerator/modules/gridgain-spark-loader-examples/config/client.xml";
IgniteSparkSession igniteSession = IgniteSparkSession.builder()
.appName("Spark Ignite catalog example")
.master("local")
.config("ignite.disableSparkSQLOptimization", true)
.igniteConfig(configPath)
.getOrCreate();
JavaSparkContext sparkCtx = new
JavaSparkContext(igniteSession.sparkContext());
final JavaRDD records = sparkCtx.parallelize(Arrays.asList(
new GenericRow()
));
JavaPairRDD rdd_records = records.mapToPair(new
PairFunction() {
@Override
public Tuple2 call(Row row) throws Exception {
throw new IllegalStateException("some error");
}
});
JavaIgniteContext igniteContext = new
JavaIgniteContext<>(sparkCtx, configPath);
JavaIgniteRDD igniteRdd = igniteContext.fromCache("Person");
igniteRdd.savePairs(rdd_records);
igniteContext.close(true);
}
}
Looks like next internal code (saveValues method)should also close the
IgniteContext in case of an unexpected exception, not only data streamer:
try {
it.foreach(value ⇒
{ val key = affinityKeyFunc(value, node.orNull)
streamer.addData(key, value) }
)
}
finally
{ streamer.close() }
})
}
{code}
was:
Next code could hang in case if PairFunction logic will throw the exception:
{code:java}
JavaPairRDD rdd_records = records.mapToPair(new MapFunction());
JavaIgniteContext igniteContext = new JavaIgniteContext<>(sparkCtx,
configUrl);
JavaIgniteRDD igniteRdd = igniteContext.fromCache(cacheName);
igniteRdd.savePairs(rdd_records);
Looks like next internal code (saveValues method)should also close the
IgniteContext in case of an unexpected exception, not only data streamer:
try {
it.foreach(value ⇒
{ val key = affinityKeyFunc(value, node.orNull)
streamer.addData(key, value) }
)
}
finally
{ streamer.close() }
})
}
{code}
> IgniteSpark integration forget to close the IgniteContext and stops the
> client node in case if error during PairFunction logic
> ---
>
> Key: IGNITE-11724
> URL: https://issues.apache.org/jira/browse/IGNITE-11724
> Project: Ignite
> Issue Type: Bug
> Components: spark
>Affects Versions: 2.8
>Reporter: Andrey Aleksandrov
>Assignee: Alexey Zinoviev
>Priority: Major
> Labels: await
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Next code could hang in case if PairFunction logic will throw the exception:
> {code:java}
> public class Example {
> public static void main(String[] args) {
> String configPath =
> "/home/andrei/BDP/big-data-accelerator/modules/gridgain-spark-loader-examples/config/client.xml";
> IgniteSparkSession igniteSession = IgniteSparkSession.builder()
> .appName("Spark Ignite catalog example")
> .master("local")
> .config("ignite.disableSparkSQLOptimization", true)
> .igniteConfig(configPath)
> .getOrCreate();
> JavaSparkContext sparkCtx = new
> JavaSparkContext(igniteSession.sparkContext());
> final JavaRDD records = sparkCtx.parallelize(Arrays.asList(
> new GenericRow()
> ));
> JavaPairRDD rdd_records = records.mapToPair(new
> PairFunction() {
> @Override
> public Tuple2 call(Row row) throws Exception {
> throw new IllegalStateException("some error");
> }
> });
> JavaIgniteContext igniteContext = new
> JavaIgniteContext<>(sparkCtx, configPath);
> JavaIgniteRDD igniteRdd = igniteContext. Integer>fromCache("Person");
> igniteRdd.savePairs(rdd_records);
> igniteContext.close(true);
> }
> }
> Looks like next internal code (saveValues method)should also close the
> IgniteContext in case of an unexpected exception, not only data streamer:
> try {
> it.foreach(value ⇒
> { val key = affinityKeyFunc(value, node.orNull)
> streamer.addData(key, value) }
> )
> }
> finally
> { streamer.close() }
> })
> }
>
[jira] [Comment Edited] (IGNITE-11724) IgniteSpark integration forget to close the IgniteContext and stops the client node in case if error during PairFunction logic
[
https://issues.apache.org/jira/browse/IGNITE-11724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956006#comment-16956006
]
Nikolay Izhikov edited comment on IGNITE-11724 at 10/21/19 12:12 PM:
-
[~aealeksandrov]
I can't run this example locally, because of the absence of config files.
Following log messages said that you have an exception in the main thread and
can catch it.
{noformat}
19/10/21 07:08:21 INFO DAGScheduler: Job 0 failed: foreachPartition at
IgniteRDD.scala:232, took 0.739143 s
Exception in thread "main" org.apache.spark.SparkException: Job aborted due to
stage failure: Task 0 in stage 0.0 failed 1 times, most recent failure: Lost
task 0.0 in stage 0.0 (TID 0, localhost, executor driver):
java.lang.IllegalStateException: some error
{noformat}
Seems, an example should be rewritten to:
{code:java}
IgniteContext ctx = ...;
try {
ctx.savePairs();
} finally {
ctx.close();
}
{code}
Also, note, that {{IgniteContext}} will be closed automatically on
{{SparkContext}} close.
I don't see any issue here, so I close it with Won'tfix.
was (Author: nizhikov):
[~aealeksandrov]
I can't run this example locally, because of the absence of config files.
Following log messages said that you have an exception in the main thread and
can catch it.
{noformat}
19/10/21 07:08:21 INFO DAGScheduler: Job 0 failed: foreachPartition at
IgniteRDD.scala:232, took 0.739143 s
Exception in thread "main" org.apache.spark.SparkException: Job aborted due to
stage failure: Task 0 in stage 0.0 failed 1 times, most recent failure: Lost
task 0.0 in stage 0.0 (TID 0, localhost, executor driver):
java.lang.IllegalStateException: some error
{noformat}
Seems, an example should be rewritten to:
{code:java}
IgniteContext ctx = ...;
try {
ctx.savePairs();
} finally {
ctx.close();
}
{code}
Also, note, that {IgniteContext} will be closed automatically on {SparkContext}
close.
I don't see any issue here, so I close it with Won'tfix.
> IgniteSpark integration forget to close the IgniteContext and stops the
> client node in case if error during PairFunction logic
> ---
>
> Key: IGNITE-11724
> URL: https://issues.apache.org/jira/browse/IGNITE-11724
> Project: Ignite
> Issue Type: Bug
> Components: spark
>Affects Versions: 2.8
>Reporter: Andrey Aleksandrov
>Assignee: Alexey Zinoviev
>Priority: Major
> Labels: await
> Fix For: 2.8
>
> Attachments: logs.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Next code could hang in case if PairFunction logic will throw the exception:
> {code:java}
> public class Example {
> public static void main(String[] args) {
> String configPath =
> "/home/andrei/BDP/big-data-accelerator/modules/gridgain-spark-loader-examples/config/client.xml";
> IgniteSparkSession igniteSession = IgniteSparkSession.builder()
> .appName("Spark Ignite catalog example")
> .master("local")
> .config("ignite.disableSparkSQLOptimization", true)
> .igniteConfig(configPath)
> .getOrCreate();
> JavaSparkContext sparkCtx = new
> JavaSparkContext(igniteSession.sparkContext());
> final JavaRDD records = sparkCtx.parallelize(Arrays.asList(
> new GenericRow()
> ));
> JavaPairRDD rdd_records = records.mapToPair(new
> PairFunction() {
> @Override
> public Tuple2 call(Row row) throws Exception {
> throw new IllegalStateException("some error");
> }
> });
> JavaIgniteContext igniteContext = new
> JavaIgniteContext<>(sparkCtx, configPath);
> JavaIgniteRDD igniteRdd = igniteContext. Integer>fromCache("Person");
> igniteRdd.savePairs(rdd_records);
> igniteContext.close(true);
> }
> }
> Looks like next internal code (saveValues method)should also close the
> IgniteContext in case of an unexpected exception, not only data streamer:
> try {
> it.foreach(value ⇒
> { val key = affinityKeyFunc(value, node.orNull)
> streamer.addData(key, value) }
> )
> }
> finally
> { streamer.close() }
> })
> }
> {code}
--
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.8) 2.9 > 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.9 > > > 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-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: - Priority: Blocker (was: Major) > 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.8 > > > 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-11256) Implement read-only mode for grid
[ https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11256: - Labels: important (was: ) > Implement read-only mode for grid > - > > Key: IGNITE-11256 > URL: https://issues.apache.org/jira/browse/IGNITE-11256 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Sergey Antonov >Priority: Major > Labels: important > Fix For: 2.8 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > Should be triggered from control.sh utility. > Useful for maintenance work, for example checking partition consistency > (idle_verify) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11719) Document cluster read-only mode
[ https://issues.apache.org/jira/browse/IGNITE-11719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11719: - Priority: Critical (was: Major) > Document cluster read-only mode > --- > > Key: IGNITE-11719 > URL: https://issues.apache.org/jira/browse/IGNITE-11719 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Sergey Antonov >Assignee: Artem Budnikov >Priority: Critical > Fix For: 2.8 > > > We should document cluster wide read-only mode. -- 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.8)
2.9
> 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.9
>
>
> 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-11701) SQL: Reflect in documentation change of system views schema from "IGNITE" to "SYS"
[ https://issues.apache.org/jira/browse/IGNITE-11701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11701: - Fix Version/s: (was: 2.8) > SQL: Reflect in documentation change of system views schema from "IGNITE" to > "SYS" > -- > > Key: IGNITE-11701 > URL: https://issues.apache.org/jira/browse/IGNITE-11701 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > > Previously all system views were located in "IGNITE" schema. Now we moved > them to "SYS" because this is more intuitive and consistent with other > database vendors. Need to do two things: > # Updated documentation of system views: change "IGNITE" schema to "SYS" > # Add a balloon informing users that before AI 2.8 system views were located > in "IGNITE" schema and that previous behavior could be forced with > "-DIGNITE_SQL_SYSTEM_SCHEMA_NAME_IGNITE=true" system property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11142) Control.sh should print detailed information about transaction.
[
https://issues.apache.org/jira/browse/IGNITE-11142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11142:
-
Ignite Flags: Docs Required,Release Notes Required (was: Docs Required)
> Control.sh should print detailed information about transaction.
> ---
>
> Key: IGNITE-11142
> URL: https://issues.apache.org/jira/browse/IGNITE-11142
> Project: Ignite
> Issue Type: Improvement
>Reporter: Sergey Antonov
>Assignee: Ivan Rakov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 7.5h
> Remaining Estimate: 0h
>
> We should be able to get detailed information about transactions. Approximate
> info per node:
> * Initiator node
> * Transaction state
> * Used caches
> * Used entry keys
> * Locked keys
>
> Possible command: {{control.sh --tx-info --ids txid1[txid2,...txidN]}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11770) Document PARTITON_SUPPLIED and PARTITION_MISSED events
[ https://issues.apache.org/jira/browse/IGNITE-11770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11770: - Fix Version/s: (was: 2.8) > Document PARTITON_SUPPLIED and PARTITION_MISSED events > -- > > Key: IGNITE-11770 > URL: https://issues.apache.org/jira/browse/IGNITE-11770 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Ilya Kasnacheev >Assignee: Artem Budnikov >Priority: Major > > Previously rebalance events will only fire on the node which does > rebalancing. Now we are introducing two events which are fired on node which > supplies data for rebalancing - SUPPLIED when partition is fully transferred > to demanding node, and MISSED when partition was not present on node > (normally should only happen on unstable topology). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-6716) Document "Affinity key backups mismatch" resolution steps
[
https://issues.apache.org/jira/browse/IGNITE-6716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-6716:
Fix Version/s: (was: 2.8)
> Document "Affinity key backups mismatch" resolution steps
> -
>
> Key: IGNITE-6716
> URL: https://issues.apache.org/jira/browse/IGNITE-6716
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Reporter: Nicholas DiPiazza
>Assignee: Artem Budnikov
>Priority: Major
>
> Please see the issue below:
> https://stackoverflow.com/questions/46894435/how-do-i-fix-affinity-key-backups-in-cache-configuration
> results in this error:
> {code}
> org.apache.ignite.IgniteCheckedException: Affinity key backups mismatch (fix
> affinity key backups in cache configuration or set
> -DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK=true system property)
> {code}
> Can someone help me get the steps in order to fix this issue? we should add
> it to the documentation somewhere.
> # What causes this error?
> # How to fix this error?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11747) Document --tx control script commands
[
https://issues.apache.org/jira/browse/IGNITE-11747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11747:
-
Priority: Critical (was: Major)
> Document --tx control script commands
> -
>
> Key: IGNITE-11747
> URL: https://issues.apache.org/jira/browse/IGNITE-11747
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Ivan Rakov
>Priority: Critical
> Fix For: 2.8
>
>
> Along with consistency check utilities, ./control.sh script has --tx command
> which allows to display info about active transactions and even kill hanging
> transactions directly.
> ./control.sh provides just brief description of options:
> {code:java}
> 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] [--info] [--yes]
> {code}
> We should document possible use cases and options of the command, possibly
> somewhere close to [https://apacheignite-tools.readme.io/docs/control-script]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12170) DOC: Advanced security should be better documented
[ https://issues.apache.org/jira/browse/IGNITE-12170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12170: - Fix Version/s: (was: 2.8) > DOC: Advanced security should be better documented > -- > > Key: IGNITE-12170 > URL: https://issues.apache.org/jira/browse/IGNITE-12170 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.7.5 >Reporter: Andrey Aleksandrov >Priority: Major > > [https://apacheignite.readme.io/docs/advanced-security#section-enable-authentication] > After applying the example, in the server log you can see: > [12:44:11] Security status [authentication=off, tls/ssl=off] > After that, I was able to connect the client without any username/password. > So looks like we should add into documentation the information about how it > works. > I checked that it worked with thin clients and web console. But for user it > can be not clear that authentication between nodes doesn' work out of the > boxes. > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11915) Document all ways to download Ignite in YARN
[ https://issues.apache.org/jira/browse/IGNITE-11915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11915: - Fix Version/s: (was: 2.8) > Document all ways to download Ignite in YARN > > > Key: IGNITE-11915 > URL: https://issues.apache.org/jira/browse/IGNITE-11915 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Ilya Kasnacheev >Priority: Major > > That is, automatic mirror download, download by URL, local file, HDFS path, > HDFS releases dir. > For other properties it would be nice to mention whether they accept local or > HDFS paths because it's not obvious. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10850) Clarify the use of the enforceJoinOrder flag
[ https://issues.apache.org/jira/browse/IGNITE-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10850: - Fix Version/s: (was: 2.8) > Clarify the use of the enforceJoinOrder flag > - > > Key: IGNITE-10850 > URL: https://issues.apache.org/jira/browse/IGNITE-10850 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Artem Budnikov >Assignee: Artem Budnikov >Priority: Major > > Need to clarify the use of the enforceJoinOrder flag and how it can be used > to optimize queries. Add this information to > [https://apacheignite-sql.readme.io/docs/performance-and-debugging] > -- This message was sent by Atlassian Jira (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.8)
2.9
> 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.9
>
>
> 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-11577) Yarn Ignite Deployment Documentation change to include Queue override option
[ https://issues.apache.org/jira/browse/IGNITE-11577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11577: - Fix Version/s: (was: 2.8) > Yarn Ignite Deployment Documentation change to include Queue override option > > > Key: IGNITE-11577 > URL: https://issues.apache.org/jira/browse/IGNITE-11577 > Project: Ignite > Issue Type: Task > Components: documentation, yarn >Affects Versions: 2.7 >Reporter: ARAVINDA REDDY N >Assignee: Prachi Garg >Priority: Minor > > I have worked on https://issues.apache.org/jira/browse/IGNITE-11508 (Yarn > Ignite deployment: Add support to override queue name through cluster > properties) > The above fix needs [https://apacheignite.readme.io/docs/yarn-deployment] > configuration section change about the Queue override property changes. > Please find the details to be added to the configuration for the release in > which the above fix will be included. > Name: IGNITE_YARN_QUEUE > Description: The Yarn queue name which will be used for starting the Ignite > application > Default: default > Example: ignite -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-5922) Improve FifoCollisionSpi doc - ParallelJobsNumber should be less than PublicThreadPoolSize
[ https://issues.apache.org/jira/browse/IGNITE-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-5922: Fix Version/s: (was: 2.8) > Improve FifoCollisionSpi doc - ParallelJobsNumber should be less than > PublicThreadPoolSize > -- > > Key: IGNITE-5922 > URL: https://issues.apache.org/jira/browse/IGNITE-5922 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Evgenii Zhuravlev >Assignee: Prachi Garg >Priority: Minor > -- 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: Priority: Major (was: Minor) > 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.8 > > > Current capacity planning guide [1] is too high level and should be > elaborated considering durable memory's internals: > - memory pages overhead. > - per-entry overhead > (http://apache-ignite-users.70518.x6.nabble.com/Re-Memory-Overhead-per-entry-in-Apache-Ignite-td9498.html). > - space occupied for indexing needs. > - free lists > - etc. > The page has to include estimates for the Ignite Native Persistence: > - entry size and its overheads. > - index size and overheads. > - data files overheads. > - estimated WAL size and how to shrink it basing on checkpointing settings. > [1] https://apacheignite.readme.io/docs/capacity-planning -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11508) Yarn Ignite deployment: Add support to over ride queue name through cluster properties
[
https://issues.apache.org/jira/browse/IGNITE-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11508:
-
Ignite Flags: Docs Required,Release Notes Required (was: Docs Required)
> Yarn Ignite deployment: Add support to over ride queue name through cluster
> properties
> --
>
> Key: IGNITE-11508
> URL: https://issues.apache.org/jira/browse/IGNITE-11508
> Project: Ignite
> Issue Type: Improvement
> Components: yarn
>Affects Versions: 2.7
>Reporter: ARAVINDA REDDY N
>Assignee: ARAVINDA REDDY N
>Priority: Minor
> Fix For: 2.8
>
> Attachments:
> IGNITE_11508_Implemented_yarn_queue_override_feature_for_Yarn_Deployment.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Yarn ignite 2.7.0 doesn't have the facility to provide queue name through the
> cluster.properties. When i checked the IgniteYarnClient source code by
> default it is set to "default".
> // Finally, set-up ApplicationSubmissionContext for the application
> ApplicationSubmissionContext appContext =
> app.getApplicationSubmissionContext();
> appContext.setApplicationName("ignition"); // application name
> appContext.setAMContainerSpec(amContainer);
> appContext.setResource(capability);
> appContext.setQueue("default"); // queue
>
> It would be a great support if we can allow overriding it through cluster
> properties.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11724) IgniteSpark integration forget to close the IgniteContext and stops the client node in case if error during PairFunction logic
[
https://issues.apache.org/jira/browse/IGNITE-11724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Aleksandrov updated IGNITE-11724:
Attachment: logs.txt
> IgniteSpark integration forget to close the IgniteContext and stops the
> client node in case if error during PairFunction logic
> ---
>
> Key: IGNITE-11724
> URL: https://issues.apache.org/jira/browse/IGNITE-11724
> Project: Ignite
> Issue Type: Bug
> Components: spark
>Affects Versions: 2.8
>Reporter: Andrey Aleksandrov
>Assignee: Alexey Zinoviev
>Priority: Major
> Labels: await
> Fix For: 2.8
>
> Attachments: logs.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Next code could hang in case if PairFunction logic will throw the exception:
> {code:java}
> public class Example {
> public static void main(String[] args) {
> String configPath =
> "/home/andrei/BDP/big-data-accelerator/modules/gridgain-spark-loader-examples/config/client.xml";
> IgniteSparkSession igniteSession = IgniteSparkSession.builder()
> .appName("Spark Ignite catalog example")
> .master("local")
> .config("ignite.disableSparkSQLOptimization", true)
> .igniteConfig(configPath)
> .getOrCreate();
> JavaSparkContext sparkCtx = new
> JavaSparkContext(igniteSession.sparkContext());
> final JavaRDD records = sparkCtx.parallelize(Arrays.asList(
> new GenericRow()
> ));
> JavaPairRDD rdd_records = records.mapToPair(new
> PairFunction() {
> @Override
> public Tuple2 call(Row row) throws Exception {
> throw new IllegalStateException("some error");
> }
> });
> JavaIgniteContext igniteContext = new
> JavaIgniteContext<>(sparkCtx, configPath);
> JavaIgniteRDD igniteRdd = igniteContext. Integer>fromCache("Person");
> igniteRdd.savePairs(rdd_records);
> igniteContext.close(true);
> }
> }
> Looks like next internal code (saveValues method)should also close the
> IgniteContext in case of an unexpected exception, not only data streamer:
> try {
> it.foreach(value ⇒
> { val key = affinityKeyFunc(value, node.orNull)
> streamer.addData(key, value) }
> )
> }
> finally
> { streamer.close() }
> })
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12305) Extend test coverage [IGNITE-11959] NullPointerException If transaction failed and failure handler doesn't configured explicitly
Kirill Tkalenko created IGNITE-12305: Summary: Extend test coverage [IGNITE-11959] NullPointerException If transaction failed and failure handler doesn't configured explicitly Key: IGNITE-12305 URL: https://issues.apache.org/jira/browse/IGNITE-12305 Project: Ignite Issue Type: Improvement Reporter: Kirill Tkalenko Assignee: Kirill Tkalenko Fix For: 2.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12220) Allow to use cache-related permissions both at system and per-cache levels
[
https://issues.apache.org/jira/browse/IGNITE-12220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956030#comment-16956030
]
Ignite TC Bot commented on IGNITE-12220:
{panel:title=Branch: [pull/6904/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=4707966buildTypeId=IgniteTests24Java8_RunAll]
> Allow to use cache-related permissions both at system and per-cache levels
> --
>
> Key: IGNITE-12220
> URL: https://issues.apache.org/jira/browse/IGNITE-12220
> Project: Ignite
> Issue Type: Task
> Components: security
>Affects Versions: 2.7.6
>Reporter: Andrey Kuznetsov
>Assignee: Sergei Ryzhov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> Currently, {{CACHE_CREATE}} and {{CACHE_DESTROY}} permissions are enforced to
> be system-level permissions, see for instance
> {{SecurityPermissionSetBuilder#appendCachePermissions}}. This looks
> inflexible: Ignite Security implementations are not able to manage cache
> creation and deletion permissions on per-cache basis (unlike get/put/remove
> permissions). All such limitations should be found and removed in order to
> allow all {{CACHE_*}} permissions to be set both at system and per-cache
> levels.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12134) Document default Ignite work dir location
[ https://issues.apache.org/jira/browse/IGNITE-12134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12134: - Priority: Critical (was: Major) > Document default Ignite work dir location > - > > Key: IGNITE-12134 > URL: https://issues.apache.org/jira/browse/IGNITE-12134 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Ilya Kasnacheev >Priority: Critical > Fix For: 2.8 > > > What should be documented: > Contents and significance of work dir - db, marshaller, wal. > Default for cases when there is IGNITE_HOME (such as running from binary > distribution) > Default for cases when there's no IGNITE_HOME (running Ignite as library) > Changing default > logs/ that sometimes comes alongside work/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12134) Document default Ignite work dir location
[ https://issues.apache.org/jira/browse/IGNITE-12134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12134: - Affects Version/s: 2.7 > Document default Ignite work dir location > - > > Key: IGNITE-12134 > URL: https://issues.apache.org/jira/browse/IGNITE-12134 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Priority: Critical > Fix For: 2.8 > > > What should be documented: > Contents and significance of work dir - db, marshaller, wal. > Default for cases when there is IGNITE_HOME (such as running from binary > distribution) > Default for cases when there's no IGNITE_HOME (running Ignite as library) > Changing default > logs/ that sometimes comes alongside work/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-2771) Document machine safety
[ https://issues.apache.org/jira/browse/IGNITE-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-2771: Fix Version/s: (was: 2.8) > Document machine safety > --- > > Key: IGNITE-2771 > URL: https://issues.apache.org/jira/browse/IGNITE-2771 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Valentin Kulichenko >Assignee: Prachi Garg >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-7611: Fix Version/s: 2.8 > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956072#comment-16956072 ] Maxim Muzafarov commented on IGNITE-7611: - [~Artem Budnikov] It seems to me that this issue is in `PA` status, right? Can we set it? > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-6806) Document logs forwarding to ELK stack
[ https://issues.apache.org/jira/browse/IGNITE-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-6806: Fix Version/s: (was: 2.8) > Document logs forwarding to ELK stack > - > > Key: IGNITE-6806 > URL: https://issues.apache.org/jira/browse/IGNITE-6806 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Assignee: Prachi Garg >Priority: Major > > Ignite logs can be forwarded to remote servers and software stacks for > advanced processing. > For instance, this project shows how to do this for ELK stack: > https://github.com/akuramshingg/elk-monitor > Mention it on Ignite logging page: > https://apacheignite.readme.io/docs/logging -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9791) Document: SQL query lazy mode is used by default
[
https://issues.apache.org/jira/browse/IGNITE-9791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-9791:
Fix Version/s: (was: 2.8)
> Document: SQL query lazy mode is used by default
>
>
> Key: IGNITE-9791
> URL: https://issues.apache.org/jira/browse/IGNITE-9791
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Affects Versions: 2.6
>Reporter: Taras Ledkov
>Assignee: Artem Budnikov
>Priority: Major
>
> We need to document changes in 'lazy' mode SQL query execution:
> - since Ignite 2.7 the lazy mode is ON by default and user should use
> explicit {{lazy=false}} to disable it.
> - but for JDBC, ODBC drivers and thin clients with version less than 2.7 lazy
> mode is false by default because the the default value is kept on the client
> side too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-10959) Memory leaks in continuous query handlers
[ https://issues.apache.org/jira/browse/IGNITE-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956101#comment-16956101 ] Trung commented on IGNITE-10959: I don't think the problem is related to backups. I have tested with * single member grid, and * multi-member grid in PARTITIONED mode with no backup In both cases, the leak was still there. > Memory leaks in continuous query handlers > - > > Key: IGNITE-10959 > URL: https://issues.apache.org/jira/browse/IGNITE-10959 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Denis Mekhanikov >Priority: Major > Fix For: 2.9 > > Attachments: CacheContinuousQueryMemoryUsageTest.java, > continuousquery_leak_profile.png > > > Continuous query handlers don't clear internal data structures after cache > events are processed. > A test, that reproduces the problem, is attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12307) Data types coverage for basic cache operations.
[ https://issues.apache.org/jira/browse/IGNITE-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin reassigned IGNITE-12307: Assignee: Alexander Lapin > Data types coverage for basic cache operations. > --- > > Key: IGNITE-12307 > URL: https://issues.apache.org/jira/browse/IGNITE-12307 > Project: Ignite > Issue Type: Task > Components: cache >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Fix For: 2.8 > > > The data types used for testing are not collected at single test/suite and > it's not clear which types are covered and which not. We should redesign the > coverage and cover following > Operations: > * put > * putAll > * remove > * removeAll > * get > * getAll > Data Types both for value and key (if applicable): > * byte/Byte > * short/Short > * int/Integer > * long/Long > * float/Float > * double/Double > * boolean/Boolean > * char/String > * Arrays of primitives (single type) > * Arrays of Objects (different types) > * Collections > ** List > ** Queue > ** Set > * Objects based on: > ** primitives only > ** primitives + collections > ** primitives + collections + nested objects > Persistance mode: > * in-memory > * PDS > Cache configurations: > * atomic/tx/mvcc > * replication/partitioned > * TTL/no TTL > * QueryEntnty > * Backups=1,2 > * EvictionPolicy > * writeSynchronizationMode(FULL_SYNC, PRIMARY_SYNC, FULL_ASYNC) > * onheapCacheEnabled -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-10660) Can't drop index created for dynamic cache
[
https://issues.apache.org/jira/browse/IGNITE-10660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956022#comment-16956022
]
Ilya Kasnacheev commented on IGNITE-10660:
--
However, you can do
{{DROP INDEX "cache1".test_idx_1;}}
> Can't drop index created for dynamic cache
> --
>
> Key: IGNITE-10660
> URL: https://issues.apache.org/jira/browse/IGNITE-10660
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Alex Volkov
>Priority: Major
>
> Here are steps to reproduce:
> # Start cluster with persistence.
> # Start cache with configuration (transactional, replicated full_sync with
> query entity).
> # Connect to cluster using sqlline.
> # Create index on this cache.
> # Try to drop index created on step 4.
> Expecting result:
> Index dropped.
> Actual result:
> Got error:
> {code:java}
> [avolkov@lab37 bin]$ ./sqlline.sh --color=true --verbose=true
> --showWarnings=true --showNestedErrs=true --outputFormat=csv -u
> jdbc:ignite:thin://lab37:10800
> Setting property: [showWarnings, true]
> Setting property: [showNestedErrs, true]
> Setting property: [outputFormat, csv]
> issuing: !connect jdbc:ignite:thin://lab37:10800 '' ''
> org.apache.ignite.IgniteJdbcThinDriver
> Connecting to jdbc:ignite:thin://lab37:10800
> Connected to: Apache Ignite (version 2.7.1#20181210-sha1:a39dbf0f)
> Driver: Apache Ignite Thin JDBC Driver (version 2.7.1#20181210-sha1:a39dbf0f)
> Autocommit status: true
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> sqlline version 1.3.0
> 0: jdbc:ignite:thin://lab37:10800> !tables
> 'TABLE_CAT','TABLE_SCHEM','TABLE_NAME','TABLE_TYPE','REMARKS','TYPE_CAT','TYPE_SCHEM','TYPE_NAME','SELF_REFERENCING_COL_NAME','REF_GENERATION'
> '','cache_group_1_015','ALLTYPESINDEXED','TABLE','','','','','',''
> '','cache_group_1_001','ALLTYPESINDEXED','TABLE','','','','','',''
> '','cache1','ALLTYPESINDEXED','TABLE','','','','','',''
> 0: jdbc:ignite:thin://lab37:10800> select * from "cache1".ALLTYPESINDEXED;
> 'STRCOL','LONGCOL'
> No rows selected (0.576 seconds)
> 0: jdbc:ignite:thin://lab37:10800> create index test_idx_1 on
> "cache1".ALLTYPESINDEXED(STRCOL);
> No rows affected (0.05 seconds)
> 0: jdbc:ignite:thin://lab37:10800> drop index test_idx_1;
> Error: Index doesn't exist: TEST_IDX_1 (state=42000,code=3006)
> java.sql.SQLException: Index doesn't exist: TEST_IDX_1
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 0: jdbc:ignite:thin://lab37:10800> !index
> 'TABLE_CAT','TABLE_SCHEM','TABLE_NAME','NON_UNIQUE','INDEX_QUALIFIER','INDEX_NAME','TYPE','ORDINAL_POSITION','COLUMN_NAME','ASC_OR_DESC','CARDINALITY','PAGES','FILTER_CONDITION'
> '','cache_group_1_001','ALLTYPESINDEXED','true','','ALLTYPESINDEXED_LONGCOL_IDX','3','0','LONGCOL','A','0','0',''
> '','cache1','ALLTYPESINDEXED','true','','ALLTYPESINDEXED_STRCOL_ASC_IDX','3','0','STRCOL','A','0','0',''
> '','cache1','ALLTYPESINDEXED','true','','TEST_IDX_1','3','0','STRCOL','A','0','0',''
> '','cache_group_1_015','ALLTYPESINDEXED','true','','ALLTYPESINDEXED_LONGCOL_IDX','3','0','LONGCOL','A','0','0',''
> {code}
>
> In node log I see the exception:
>
> {code:java}
> [16:01:15,412][SEVERE][client-connector-#179][JdbcRequestHandler] Failed to
> execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=PUBLIC,
> pageSize=1024, maxRows=0, sqlQry=drop index test_idx_1, args=[],
> stmtType=ANY_STATEMENT_TYPE, autoCommit=true]]
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Index
> doesn't exist: TEST_IDX_1
> at
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.convert(DdlStatementsProcessor.java:644)
> at
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:244)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFieldsNative(IgniteH2Indexing.java:1977)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2141)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2135)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2130)
> at
>
[jira] [Commented] (IGNITE-11724) IgniteSpark integration forget to close the IgniteContext and stops the client node in case if error during PairFunction logic
[
https://issues.apache.org/jira/browse/IGNITE-11724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956054#comment-16956054
]
Andrey Aleksandrov commented on IGNITE-11724:
-
[~nizhikov] okay, you are right about the current case.
But if it should be surrounded by try/catch then it will be great to describe
it in java/scala docs. Also, there are no checked exceptions here for
[https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteDataStreamer.html#addData-K-V-].
I mean that at least two cases exist that can throw the exception:
1)Data streamer exceptions - should be added to checked and described
2)Custom exceptions from PairFunction, etc - should be described
At the moment people will use this method without try/catch and get the
situation like I described because there are no checked exceptions added to
savePairs.
If you think that it's fine then leave the current ticket as is but it looks
strange for me.
> IgniteSpark integration forget to close the IgniteContext and stops the
> client node in case if error during PairFunction logic
> ---
>
> Key: IGNITE-11724
> URL: https://issues.apache.org/jira/browse/IGNITE-11724
> Project: Ignite
> Issue Type: Bug
> Components: spark
>Affects Versions: 2.8
>Reporter: Andrey Aleksandrov
>Assignee: Alexey Zinoviev
>Priority: Major
> Labels: await
> Fix For: 2.8
>
> Attachments: logs.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Next code could hang in case if PairFunction logic will throw the exception:
> {code:java}
> public class Example {
> public static void main(String[] args) {
> String configPath =
> "/home/andrei/BDP/big-data-accelerator/modules/gridgain-spark-loader-examples/config/client.xml";
> IgniteSparkSession igniteSession = IgniteSparkSession.builder()
> .appName("Spark Ignite catalog example")
> .master("local")
> .config("ignite.disableSparkSQLOptimization", true)
> .igniteConfig(configPath)
> .getOrCreate();
> JavaSparkContext sparkCtx = new
> JavaSparkContext(igniteSession.sparkContext());
> final JavaRDD records = sparkCtx.parallelize(Arrays.asList(
> new GenericRow()
> ));
> JavaPairRDD rdd_records = records.mapToPair(new
> PairFunction() {
> @Override
> public Tuple2 call(Row row) throws Exception {
> throw new IllegalStateException("some error");
> }
> });
> JavaIgniteContext igniteContext = new
> JavaIgniteContext<>(sparkCtx, configPath);
> JavaIgniteRDD igniteRdd = igniteContext. Integer>fromCache("Person");
> igniteRdd.savePairs(rdd_records);
> igniteContext.close(true);
> }
> }
> Looks like next internal code (saveValues method)should also close the
> IgniteContext in case of an unexpected exception, not only data streamer:
> try {
> it.foreach(value ⇒
> { val key = affinityKeyFunc(value, node.orNull)
> streamer.addData(key, value) }
> )
> }
> finally
> { streamer.close() }
> })
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-4222) Document the usage of ComputeJobContinuation API
[ https://issues.apache.org/jira/browse/IGNITE-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-4222: Fix Version/s: (was: 2.8) > Document the usage of ComputeJobContinuation API > > > Key: IGNITE-4222 > URL: https://issues.apache.org/jira/browse/IGNITE-4222 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Assignee: Prachi Garg >Priority: Major > > The usage and applicability of `ComputeJobContinuation` have to be documented > on Apache Ignite Readme.io which will help out to avoid discussion like those > [1] and [4]. The new page has to be created for the topic and placed here [2]. > The content should consist not only of technical details but also provide use > cases for this API: > - don't block a thread from the public pool if a job is waiting for some > result. Put the thread back into the pool and wait for the result > asynchronously. > - splitting a job into several pieces that can be executed in parallel. Refer > to this example [3]. > > [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 > [3] > https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/computegrid/ComputeFibonacciContinuationExample.java > [4] > http://apache-ignite-users.70518.x6.nabble.com/ignite-compute-job-continuation-documentation-td16725.html -- 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.8) > Document custom node fail functional. > - > > Key: IGNITE-11427 > URL: https://issues.apache.org/jira/browse/IGNITE-11427 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7 >Reporter: Stanilovsky Evgeny >Priority: Major > 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-11435) SQL: Create a view with query history
[ https://issues.apache.org/jira/browse/IGNITE-11435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11435: - Ignite Flags: Docs Required,Release Notes Required (was: Docs Required) > SQL: Create a view with query history > - > > Key: IGNITE-11435 > URL: https://issues.apache.org/jira/browse/IGNITE-11435 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Need to expose Query History view - LOCAL_SQL_QUERY_HISTORY > List of columns: > SCHEMA_NAME - name of schema > QUERY - query text > LOCAL - flag of local query > CALLS - number of execution of the query > FAILURES - number of failures for the query > DURATION_MIN - minimum duration of execution > DURATION_MAX - maximum duration of execution > LAST_QUERY_START - time of the last start of execution > > see QueryHistoryMetrics class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11332) Add jmx ability to exclude node from topology.
[
https://issues.apache.org/jira/browse/IGNITE-11332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11332:
-
Ignite Flags: Docs Required,Release Notes Required
> Add jmx ability to exclude node from topology.
> --
>
> Key: IGNITE-11332
> URL: https://issues.apache.org/jira/browse/IGNITE-11332
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 2.7
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> In very rare corner cases may occur situation that physically unreachable
> host still present in topology that may leads to hanging overall cluster
> operations.
> Add ability to exclude with specific warning.
> {code:java}
> /**
> * Exclude node from cluster.
> *
> * @param nodeId Node id.
> */
> @MXBeanDescription("Exclude node from cluster.")
> public void excludeNode(String nodeId);{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: - Priority: Critical (was: Major) > 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.8 > > Attachments: Screenshot_20190227_100539.png > > > Append additional node fail documentation related to [1] > [1] https://issues.apache.org/jira/browse/IGNITE-11332 > > how it looks into jconsole: > !Screenshot_20190227_100539.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-8376) Add cluster (de)activation events
[
https://issues.apache.org/jira/browse/IGNITE-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-8376:
Ignite Flags: Docs Required,Release Notes Required
> Add cluster (de)activation events
> -
>
> Key: IGNITE-8376
> URL: https://issues.apache.org/jira/browse/IGNITE-8376
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Igor Belyakov
>Priority: Major
> Labels: newbie
> Fix For: 2.8
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Currently, we do not have any way to detect that a cluster got activated,
> which results in busy-loops polling {{cluster().active()}}.
> I suggest to add new events, {{EVT_CLUSTER_ACTIVATED}},
> {{EVT_CLUSTER_DEACTIVATED}}, {{EVT_CLUSTER_ACTIVATION_FAILED}} which will be
> fired when corresponding steps are completed. The event should contain, if
> possible, information about the activation source (public API or
> auto-activation), topology version on which activation was performed. The
> fail event should contain information about the cause of the failure. If
> needed, a new class for this event should be introduced.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11724) IgniteSpark integration forget to close the IgniteContext and stops the client node in case if error during PairFunction logic
[
https://issues.apache.org/jira/browse/IGNITE-11724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956006#comment-16956006
]
Nikolay Izhikov commented on IGNITE-11724:
--
[~aealeksandrov]
I can't run this example locally, because of the absence of config files.
Following log messages said that you have an exception in the main thread and
can catch it.
{noformat}
19/10/21 07:08:21 INFO DAGScheduler: Job 0 failed: foreachPartition at
IgniteRDD.scala:232, took 0.739143 s
Exception in thread "main" org.apache.spark.SparkException: Job aborted due to
stage failure: Task 0 in stage 0.0 failed 1 times, most recent failure: Lost
task 0.0 in stage 0.0 (TID 0, localhost, executor driver):
java.lang.IllegalStateException: some error
{noformat}
Seems, an example should be rewritten to:
{code:java}
IgniteContext ctx = ...;
try {
ctx.savePairs();
} finally {
ctx.close();
}
{code}
Also, note, that {IgniteContext} will be closed automatically on {SparkContext}
close.
I don't see any issue here, so I close it with Won'tfix.
> IgniteSpark integration forget to close the IgniteContext and stops the
> client node in case if error during PairFunction logic
> ---
>
> Key: IGNITE-11724
> URL: https://issues.apache.org/jira/browse/IGNITE-11724
> Project: Ignite
> Issue Type: Bug
> Components: spark
>Affects Versions: 2.8
>Reporter: Andrey Aleksandrov
>Assignee: Alexey Zinoviev
>Priority: Major
> Labels: await
> Fix For: 2.8
>
> Attachments: logs.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Next code could hang in case if PairFunction logic will throw the exception:
> {code:java}
> public class Example {
> public static void main(String[] args) {
> String configPath =
> "/home/andrei/BDP/big-data-accelerator/modules/gridgain-spark-loader-examples/config/client.xml";
> IgniteSparkSession igniteSession = IgniteSparkSession.builder()
> .appName("Spark Ignite catalog example")
> .master("local")
> .config("ignite.disableSparkSQLOptimization", true)
> .igniteConfig(configPath)
> .getOrCreate();
> JavaSparkContext sparkCtx = new
> JavaSparkContext(igniteSession.sparkContext());
> final JavaRDD records = sparkCtx.parallelize(Arrays.asList(
> new GenericRow()
> ));
> JavaPairRDD rdd_records = records.mapToPair(new
> PairFunction() {
> @Override
> public Tuple2 call(Row row) throws Exception {
> throw new IllegalStateException("some error");
> }
> });
> JavaIgniteContext igniteContext = new
> JavaIgniteContext<>(sparkCtx, configPath);
> JavaIgniteRDD igniteRdd = igniteContext. Integer>fromCache("Person");
> igniteRdd.savePairs(rdd_records);
> igniteContext.close(true);
> }
> }
> Looks like next internal code (saveValues method)should also close the
> IgniteContext in case of an unexpected exception, not only data streamer:
> try {
> it.foreach(value ⇒
> { val key = affinityKeyFunc(value, node.orNull)
> streamer.addData(key, value) }
> )
> }
> finally
> { streamer.close() }
> })
> }
> {code}
--
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: - Priority: Critical (was: Major) > 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.8 > > > 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] [Commented] (IGNITE-8003) Dead documentation interface element
[ https://issues.apache.org/jira/browse/IGNITE-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956077#comment-16956077 ] Peter Ivanov commented on IGNITE-8003: -- I am not sure that this ticket is applicable for FixVersion, cause the problem in documentation, not in AI code. What do you think, [~dmagda]? > Dead documentation interface element > > > Key: IGNITE-8003 > URL: https://issues.apache.org/jira/browse/IGNITE-8003 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.4 >Reporter: Peter Ivanov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.9 > > Attachments: Screen_Shot_2018_03_15_at_11_43_07.png > > > Most of the tables in lists of artifacts (for example on Downloads page) have > strange interface element settling down to the right, which does nothing (see > [^Screen_Shot_2018_03_15_at_11_43_07.png]). > I guess it should be either removed or fixed, whatever designation it has. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9853) control.sh show more information about cache configuration
[ https://issues.apache.org/jira/browse/IGNITE-9853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-9853: Ignite Flags: Docs Required,Release Notes Required (was: Docs Required) > control.sh show more information about cache configuration > -- > > Key: IGNITE-9853 > URL: https://issues.apache.org/jira/browse/IGNITE-9853 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Antonov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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.8) 2.9 > 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.9 > > > 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-10205) add to utility command - ./control.sh --cache idle_verify --dump abbility to exclude cache from output file
[ https://issues.apache.org/jira/browse/IGNITE-10205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10205: - Ignite Flags: Docs Required,Release Notes Required (was: Docs Required) > add to utility command - ./control.sh --cache idle_verify --dump abbility to > exclude cache from output file > > > Key: IGNITE-10205 > URL: https://issues.apache.org/jira/browse/IGNITE-10205 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.6 >Reporter: ARomantsov >Assignee: Vladislav Pyatkov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-5439) JDBC thin: support query cancel
[
https://issues.apache.org/jira/browse/IGNITE-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-5439:
Ignite Flags: Docs Required,Release Notes Required
> JDBC thin: support query cancel
> ---
>
> Key: IGNITE-5439
> URL: https://issues.apache.org/jira/browse/IGNITE-5439
> Project: Ignite
> Issue Type: Task
> Components: jdbc
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Alexander Lapin
>Priority: Major
> Fix For: 2.8
>
>
> The JDBC {{Statement.cancel}} method must be supported.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-10836) Add documentation for jdbc thin query cancel
[ https://issues.apache.org/jira/browse/IGNITE-10836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10836: - Fix Version/s: (was: 2.8) > Add documentation for jdbc thin query cancel > > > Key: IGNITE-10836 > URL: https://issues.apache.org/jira/browse/IGNITE-10836 > Project: Ignite > Issue Type: Task > Components: documentation, jdbc >Reporter: Alexander Lapin >Priority: Major > > Query cancel for jdbc thin was implemented. > At least error codes page > ([https://apacheignite-sql.readme.io/docs/error-codes-27)] should be updated, > cause new error code (57014 Query cancelled) was added. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-7739) Write about Spring Injection and IgniteSpringBean in documentation
[ https://issues.apache.org/jira/browse/IGNITE-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-7739: Fix Version/s: (was: 2.8) > Write about Spring Injection and IgniteSpringBean in documentation > -- > > Key: IGNITE-7739 > URL: https://issues.apache.org/jira/browse/IGNITE-7739 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Ilya Kasnacheev >Assignee: Prachi Garg >Priority: Minor > > Currently there is no mention of IgniteSpringBean on readme.io > We have section https://apacheignite.readme.io/docs/resource-injection but > it's totally not obvious how to make e.g. SpringResource work, what are > pre-requisites. > Thing is, if Ignite creates Spring context (via Ignition), then Spring > injection would work out of box. > If Spring context creates Ignite as a bean, that bean should be > IgniteSpringBean and not Ignite. Otherwise, Spring context and lifecycle > would not be visible to Ignite and injection won't work. > On unrelated note, maybe we need support for Spring Boot already? See > https://habrahabr.ru/post/310672/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11724) IgniteSpark integration forget to close the IgniteContext and stops the client node in case if error during PairFunction logic
[
https://issues.apache.org/jira/browse/IGNITE-11724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956066#comment-16956066
]
Nikolay Izhikov commented on IGNITE-11724:
--
[~aealeksandrov] Agree. Feel free to suggest an edit to the Ignite
documentation.
> 1)Data streamer exceptions - should be added to checked and described
> 2)Custom exceptions from PairFunction, etc - should be described
Actually, I don't understand your proposal.
We should describe to the user the clear lifecycle of IgniteContext.
It should be closed to release any resources that were allocated to executed
user payload.
Right now I can't see that requirement in the documentation.
It should be added.
> IgniteSpark integration forget to close the IgniteContext and stops the
> client node in case if error during PairFunction logic
> ---
>
> Key: IGNITE-11724
> URL: https://issues.apache.org/jira/browse/IGNITE-11724
> Project: Ignite
> Issue Type: Bug
> Components: spark
>Affects Versions: 2.8
>Reporter: Andrey Aleksandrov
>Assignee: Alexey Zinoviev
>Priority: Major
> Labels: await
> Fix For: 2.8
>
> Attachments: logs.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Next code could hang in case if PairFunction logic will throw the exception:
> {code:java}
> public class Example {
> public static void main(String[] args) {
> String configPath =
> "/home/andrei/BDP/big-data-accelerator/modules/gridgain-spark-loader-examples/config/client.xml";
> IgniteSparkSession igniteSession = IgniteSparkSession.builder()
> .appName("Spark Ignite catalog example")
> .master("local")
> .config("ignite.disableSparkSQLOptimization", true)
> .igniteConfig(configPath)
> .getOrCreate();
> JavaSparkContext sparkCtx = new
> JavaSparkContext(igniteSession.sparkContext());
> final JavaRDD records = sparkCtx.parallelize(Arrays.asList(
> new GenericRow()
> ));
> JavaPairRDD rdd_records = records.mapToPair(new
> PairFunction() {
> @Override
> public Tuple2 call(Row row) throws Exception {
> throw new IllegalStateException("some error");
> }
> });
> JavaIgniteContext igniteContext = new
> JavaIgniteContext<>(sparkCtx, configPath);
> JavaIgniteRDD igniteRdd = igniteContext. Integer>fromCache("Person");
> igniteRdd.savePairs(rdd_records);
> igniteContext.close(true);
> }
> }
> Looks like next internal code (saveValues method)should also close the
> IgniteContext in case of an unexpected exception, not only data streamer:
> try {
> it.foreach(value ⇒
> { val key = affinityKeyFunc(value, node.orNull)
> streamer.addData(key, value) }
> )
> }
> finally
> { streamer.close() }
> })
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11392) Improve LRT diagnostic messages
[ https://issues.apache.org/jira/browse/IGNITE-11392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11392: - Ignite Flags: Docs Required,Release Notes Required (was: Docs Required) > Improve LRT diagnostic messages > --- > > Key: IGNITE-11392 > URL: https://issues.apache.org/jira/browse/IGNITE-11392 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Denis Chudov >Priority: Major > Fix For: 2.8 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Currently we print out only local information about long-running > transactions. This makes it hard to understand the cause of the LRT when an > ACTIVE transaction is initiated by a client in a large system and is not > being committed. > Given that a primary node knows the near node ID, we can send a diagnostic > message to the near node for an ACTIVE transaction, find the thread that > started the transaction and dump it's stack, so the server node logs can at > least give an idea why the transaction is not being committed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11703) CPP: Add default BinaryType methods implementations where possible
[
https://issues.apache.org/jira/browse/IGNITE-11703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11703:
-
Ignite Flags: Docs Required,Release Notes Required (was: Docs Required)
> CPP: Add default BinaryType methods implementations where possible
> --
>
> Key: IGNITE-11703
> URL: https://issues.apache.org/jira/browse/IGNITE-11703
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: cpp
> Fix For: 2.8
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently, most of specifications of {{BinaryType}} template have the same
> default implementations of certain methods, which may be implemented by
> default. Here is the list:
> * {{GetTypeId()}}
> * {{GetFieldId()}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12306) .NET: Java version is not taken into account when detecting JAVA_HOME
Pavel Tupitsyn created IGNITE-12306: --- Summary: .NET: Java version is not taken into account when detecting JAVA_HOME Key: IGNITE-12306 URL: https://issues.apache.org/jira/browse/IGNITE-12306 Project: Ignite Issue Type: Bug Components: platforms Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 2.8 When multiple Java versions are installed on the machine, random one is picked up. For example, when 7 and 8 are installed, only 8 is suitable for Ignite. We should check versions and pick the right one: * Collect all known versions * Filter out all below 8 * Pick the lowest Lower versions are prioritized - we don't want to use latest. Brand new Java version with breaking changes might be released where Ignite does not work. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-8617) Node Discovery Using AWS Application ELB
[ https://issues.apache.org/jira/browse/IGNITE-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-8617: Component/s: (was: documentation) Ignite Flags: Docs Required,Release Notes Required > Node Discovery Using AWS Application ELB > > > Key: IGNITE-8617 > URL: https://issues.apache.org/jira/browse/IGNITE-8617 > Project: Ignite > Issue Type: New Feature > Components: aws >Reporter: Uday Kale >Assignee: Uday Kale >Priority: Major > Fix For: 2.8 > > > Support for Node discovery using AWS Application ELB. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10019) Documentation: partition preloading
[ https://issues.apache.org/jira/browse/IGNITE-10019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10019: - Fix Version/s: (was: 2.8) > Documentation: partition preloading > --- > > Key: IGNITE-10019 > URL: https://issues.apache.org/jira/browse/IGNITE-10019 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexei Scherbakov >Assignee: Artem Budnikov >Priority: Major > > We have to add documentation for partition preloading feature: > IgniteCache.preloadPartition -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11724) IgniteSpark integration forget to close the IgniteContext and stops the client node in case if error during PairFunction logic
[
https://issues.apache.org/jira/browse/IGNITE-11724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16955967#comment-16955967
]
Andrey Aleksandrov commented on IGNITE-11724:
-
[~nizhikov] sorry, my example wasn't full. {{IgniteContext#close doesn't help
in this case. Please take a look at the updated example and logs.}}
{{After getting IllegalStateException("some error") current job will not be
stopped at all.}}
{{Possible it can be fixed more accurate but the current fix can help with this
case.}}
{{BR,}}
{{Andrei}}
> IgniteSpark integration forget to close the IgniteContext and stops the
> client node in case if error during PairFunction logic
> ---
>
> Key: IGNITE-11724
> URL: https://issues.apache.org/jira/browse/IGNITE-11724
> Project: Ignite
> Issue Type: Bug
> Components: spark
>Affects Versions: 2.8
>Reporter: Andrey Aleksandrov
>Assignee: Alexey Zinoviev
>Priority: Major
> Labels: await
> Fix For: 2.8
>
> Attachments: logs.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Next code could hang in case if PairFunction logic will throw the exception:
> {code:java}
> public class Example {
> public static void main(String[] args) {
> String configPath =
> "/home/andrei/BDP/big-data-accelerator/modules/gridgain-spark-loader-examples/config/client.xml";
> IgniteSparkSession igniteSession = IgniteSparkSession.builder()
> .appName("Spark Ignite catalog example")
> .master("local")
> .config("ignite.disableSparkSQLOptimization", true)
> .igniteConfig(configPath)
> .getOrCreate();
> JavaSparkContext sparkCtx = new
> JavaSparkContext(igniteSession.sparkContext());
> final JavaRDD records = sparkCtx.parallelize(Arrays.asList(
> new GenericRow()
> ));
> JavaPairRDD rdd_records = records.mapToPair(new
> PairFunction() {
> @Override
> public Tuple2 call(Row row) throws Exception {
> throw new IllegalStateException("some error");
> }
> });
> JavaIgniteContext igniteContext = new
> JavaIgniteContext<>(sparkCtx, configPath);
> JavaIgniteRDD igniteRdd = igniteContext. Integer>fromCache("Person");
> igniteRdd.savePairs(rdd_records);
> igniteContext.close(true);
> }
> }
> Looks like next internal code (saveValues method)should also close the
> IgniteContext in case of an unexpected exception, not only data streamer:
> try {
> it.foreach(value ⇒
> { val key = affinityKeyFunc(value, node.orNull)
> streamer.addData(key, value) }
> )
> }
> finally
> { streamer.close() }
> })
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-8629) There is no documentation about on which nodes Ignite Predicate will be executed during service/cache deploying with NodeFilter
[
https://issues.apache.org/jira/browse/IGNITE-8629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-8629:
Fix Version/s: (was: 2.8)
> There is no documentation about on which nodes Ignite Predicate will be
> executed during service/cache deploying with NodeFilter
> ---
>
> Key: IGNITE-8629
> URL: https://issues.apache.org/jira/browse/IGNITE-8629
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.4
>Reporter: Andrey Aleksandrov
>Assignee: Prachi Garg
>Priority: Major
>
> In documentation we could see that:
> [https://apacheignite.readme.io/docs/service-grid#section-node-filter-based-deployment]
> This approach is based on a filtering predicate that gets called on every
> node at the time Ignite Service engine determines a set of possible
> candidates for the Ignite Service deployment.
> Looks like it's not correct because in Ignite 2.4 next code:
> {code:java}
> Ignite ignite = IgnitionEx.start("examples/config/example-ignite.xml",
> "ignite-1");
> Ignite ignite2 = IgnitionEx.start("examples/config/example-ignite.xml",
> "ignite-2");
> // Deploy services only on server nodes.
> ignite2.services().deploy(new ServiceConfiguration()
> .setMaxPerNodeCount(1)
> .setNodeFilter(new IgnitePredicate() {
> @IgniteInstanceResource Ignite filterIgnite;
> @Override public boolean apply(ClusterNode node) {
> System.out.println("Is local node: " + node.isLocal());
> System.out.println("ignite: " + (isNull(filterIgnite) ? null :
> filterIgnite.name()));
> return true;
> }
> })
> .setName("my-service")
> .setService(new SimpleMapServiceImpl<>())
> );
> {code}
> Will be executed only on "ignite-1"
> {code:java}
> Is local node: true
> ignite: ignite-1
> Is local node: false
> ignite: ignite-1
> Service was initialized: my-service
> Is local node: true
> ignite: ignite-1
> Is local node: false
> ignite: ignite-1
> Service was initialized: my-service
> Executing distributed service: my-service
> Executing distributed service: my-service
> Is local node: true
> ignite: ignite-1
> Is local node: false
> ignite: ignite-1
> {code}
> Looks like ignite-1 is the coordinator node in this case. But this behavior
> is different from described in the documentation.
> Also, this should be described in case of the cache deployment:
> {code:java}
> Ignite ignite = IgnitionEx.start("examples/config/example-ignite.xml",
> "ignite-1");
> Ignite ignite2 = IgnitionEx.start("examples/config/example-ignite.xml",
> "ignite-2");
> // Deploy services only on server nodes.
> ignite2.services().deploy(new ServiceConfiguration()
> .setMaxPerNodeCount(1)
> .setNodeFilter(new IgnitePredicate() {
> Ignite filterIgnite;
> @Override public boolean apply(ClusterNode node) {
> System.out.println("Is local node: " + node.isLocal());
> System.out.println("ignite: " + (isNull(filterIgnite) ? null :
> filterIgnite.name()));
> return true;
> }
> @IgniteInstanceResource
> void setFilterIgnite(Ignite filterIgnite) {
> this.filterIgnite = filterIgnite;
> }
> })
> .setName("my-service")
> .setService(new SimpleMapServiceImpl<>())
> );
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-7611: Fix Version/s: (was: 2.8) > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Artem Budnikov >Priority: Major > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11576) Web console: Documentation for webconsole upgraging from version to version should be created (including mongoDB specific)
[ https://issues.apache.org/jira/browse/IGNITE-11576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11576: - Fix Version/s: (was: 2.8) > Web console: Documentation for webconsole upgraging from version to version > should be created (including mongoDB specific) > -- > > Key: IGNITE-11576 > URL: https://issues.apache.org/jira/browse/IGNITE-11576 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.7 >Reporter: Andrey Aleksandrov >Priority: Major > Labels: web-console > > It's important to get the documentation about all steps and limitation > related to upgrading of the web console. > Also in case if upgrading requires changing of the mongoDB version then the > instructions for backuping and restoring of the data should be added to our > documentation too. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10347) Expose system SQL view for running queries
[ https://issues.apache.org/jira/browse/IGNITE-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10347: - Ignite Flags: Docs Required,Release Notes Required (was: Docs Required) > Expose system SQL view for running queries > -- > > Key: IGNITE-10347 > URL: https://issues.apache.org/jira/browse/IGNITE-10347 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Need to expose system SQL view to provide list of running queries. Proposed > name is *running_queries* with following columns: query_id, node_id, sql, > schema_name, duration. > Where, > query_id - cluster unique id of query > sql - sql command > cancelable - is is possible to cancel the query. > schema_name - SQL schema name > duration - time in ms from start of execution of query > > The view should contains all kind of running queries from RunningQueryManager > on local node -- 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: 2.8 > Document custom node fail functional. > - > > Key: IGNITE-11427 > URL: https://issues.apache.org/jira/browse/IGNITE-11427 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7 >Reporter: Stanilovsky Evgeny >Priority: Major > Fix For: 2.8 > > Attachments: Screenshot_20190227_100539.png > > > Append additional node fail documentation related to [1] > [1] https://issues.apache.org/jira/browse/IGNITE-11332 > > how it looks into jconsole: > !Screenshot_20190227_100539.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10507) Control.sh add ability to check crc sums of stored pages
[ https://issues.apache.org/jira/browse/IGNITE-10507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10507: - Ignite Flags: Docs Required,Release Notes Required (was: Docs Required) > Control.sh add ability to check crc sums of stored pages > > > Key: IGNITE-10507 > URL: https://issues.apache.org/jira/browse/IGNITE-10507 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.6 >Reporter: Sergey Antonov >Assignee: Sergey Antonov >Priority: Critical > Fix For: 2.8 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We should have ability to check stored data on disk. Also we should return > all exceptions from all nodes, if they are occurred. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-7132) Investigate and document Ignite Persistence usage in Docker
[ https://issues.apache.org/jira/browse/IGNITE-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-7132: Fix Version/s: (was: 2.8) > Investigate and document Ignite Persistence usage in Docker > --- > > Key: IGNITE-7132 > URL: https://issues.apache.org/jira/browse/IGNITE-7132 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Assignee: Ilya Murchenko >Priority: Minor > > Inspired by the following talk: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-in-docker-Native-Persistence-td18426.html > The aim is to investigate how is better to deploy Ignite persistence in > Docker. Probably with the usage of Docker volumes: > https://docs.docker.com/engine/admin/volumes/volumes/#use-a-read-only-volume > Once the configuration option is clear the following documentation needs to > be updated: > https://apacheignite.readme.io/docs/docker-deployment -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-7781) JMX beans documentation
[ https://issues.apache.org/jira/browse/IGNITE-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-7781: Fix Version/s: (was: 2.8) > JMX beans documentation > --- > > Key: IGNITE-7781 > URL: https://issues.apache.org/jira/browse/IGNITE-7781 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Assignee: Artem Budnikov >Priority: Minor > Labels: documentation, jmx > Attachments: MXBeansJavaDoc.zip > > > There are about 30 JMX beans implemented in Ignite, but there is no > documentation for most of these beans, except memory metrics and brief > overview of cache metrics. > Folowing MBeans/MXBeans can be documented: > ||MBeans group||Interface||Path||Comment|| > |Eviction > metrics|org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicyMBean, > org.apache.ignite.cache.eviction.igfs.IgfsPerBlockLruEvictionPolicyMXBean, > org.apache.ignite.cache.eviction.lru.LruEvictionPolicyMBean, > org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicyMBean|org.apache|For > each cache, if eviction for cache is configured| > |Cache group > metrics|org.apache.ignite.mxbean.CacheGroupMetricsMXBean|org.apache..."Cache > groups".|For each group| > |Cache > metrics|org.apache.ignite.mxbean.CacheMetricsMXBean|org.apacheCacheClusterMetricsMXBeanImpl, > > org.apacheCacheLocalMetricsMXBeanImpl|For > each cache| > |Cluster > metrics|org.apache.ignite.mxbean.ClusterMetricsMXBean|org.apache...Kernal.ClusterLocalNodeMetricsMXBeanImpl, > org.apache...Kernal.ClusterMetricsMXBeanImpl| > |Data region (memory) > metrics|org.apache.ignite.mxbean.DataRegionMetricsMXBean|org.apache...DataRegionMetrics.|For > each data region| > |Data storage > metrics|org.apache.ignite.mxbean.DataStorageMetricsMXBean|org.apache..."Persistent > Store".DataStorageMetrics| > |Instance > information|org.apache.ignite.mxbean.IgniteMXBean|org.apache...Kernal.IgniteKernal| > |Ignition > state|org.apache.ignite.mxbean.IgnitionMXBean|org.apache..Kernel.Ignition| > |Thread pools metrics|org.apache.ignite.mxbean.ThreadPoolMXBean, > org.apache.ignite.mxbean.StripedExecutorMXBean|org.apache..."Thread > Pools".|For each executor| > |SPI|org.apache.ignite.spi.cache.CacheCheckpointSpiMBean, > org.apache.ignite.spi.collision.fifoqueue.FifoQueueCollisionSpiMBean, > org.apache.ignite.spi.collision.jobstealing.JobStealingCollisionSpiMBean, > org.apache.ignite.spi.collision.priorityqueue.PriorityQueueCollisionSpiMBean, > org.apache.ignite.spi.communication.tcp.TcpCommunicationSpiMBean, > org.apache.ignite.spi.deployment.local.LocalDeploymentSpiMBean, > org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpiMBean, > org.apache.ignite.spi.eventstorage.memory.MemoryEventStorageSpiMBean, > org.apache.ignite.spi.failover.always.AlwaysFailoverSpiMBean, > org.apache.ignite.spi.failover.jobstealing.JobStealingFailoverSpiMBean, > org.apache.ignite.spi.failover.never.NeverFailoverSpiMBean, > org.apache.ignite.spi.jdbc.JdbcCheckpointSpiMBean, > org.apache.ignite.spi.loadbalancing.adaptive.AdaptiveLoadBalancingSpiMBean, > org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinLoadBalancingSpiMBean, > > org.apache.ignite.spi.loadbalancing.weightedrandom.WeightedRandomLoadBalancingSpiMBean, > > org.apache.ignite.spi.sharedfs.SharedFsCheckpointSpiMBean|org.apache...SPIs.| > > JavaDoc for this beans is attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10688) Expose SQL views for cache groups IO statistics
[
https://issues.apache.org/jira/browse/IGNITE-10688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-10688:
-
Ignite Flags: Docs Required,Release Notes Required (was: Docs Required)
> Expose SQL views for cache groups IO statistics
> ---
>
> Key: IGNITE-10688
> URL: https://issues.apache.org/jira/browse/IGNITE-10688
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Yury Gerzhedovich
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: iep-29
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As of now no such way to get IO statistics through SQL.
> Need to expose system SQL views to be able view statistics for cache group
> caches.
>
> CACHE_GROUPS_IO
> {quote}group_id - Cache group id
> group_name - Name of cache group
> physical_read - Number of physical read of pages
> logical_read - Number of logical read of pages
> {quote}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-10784) SQL: Create a view with list of existing tables
[
https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-10784:
-
Ignite Flags: Docs Required,Release Notes Required (was: Docs Required)
> SQL: Create a view with list of existing tables
> ---
>
> Key: IGNITE-10784
> URL: https://issues.apache.org/jira/browse/IGNITE-10784
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Pavel Kuznetsov
>Priority: Major
> Labels: iep-29
> Fix For: 2.8
>
>
> We need to create a system view of currently available SQL tables.
> Minimal required information:
> 1) Schema name
> 2) Table name
> 3) Owning cache name
> 4) Owning cache ID
> Other info to consider:
> 1) Affinity column name
> 2) Key/value aliases
> 3) Key/value type names
> 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful
> information could be exposed (taking in count that a lot of engine properties
> are already exposed through {{CACHES}} view)
> Starting point: {{SqlSystemView}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11724) IgniteSpark integration forget to close the IgniteContext and stops the client node in case if error during PairFunction logic
[
https://issues.apache.org/jira/browse/IGNITE-11724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956103#comment-16956103
]
Andrey Aleksandrov commented on IGNITE-11724:
-
[~nizhikov] the proposal is pretty simple.
We have some method that can throw exceptions but there is no information about
it. These exceptions can be related to Ignite internals or can be related to
user logic.
1)We should catch the Ignite exception inside integration OR add them to
exceptions list like it was done here (throws javax.cache.CacheException,
IgniteInterruptedException, IllegalStateException,
IgniteDataStreamerTimeoutException):
[https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteDataStreamer.html#addData-K-V-]
2)Users exceptions. Yes, here we should provide to the user the details of the
implementation or just the information that we can throw here some exceptions.
It also can be done by catching these exceptions and put them as a clause to
some IgniteCheckedException that can be added to exception list of savePairs
API.
Okay, I will create a separate ticket on it with normal example that can be
started in every environment and description of exceptions that can be handled.
> IgniteSpark integration forget to close the IgniteContext and stops the
> client node in case if error during PairFunction logic
> ---
>
> Key: IGNITE-11724
> URL: https://issues.apache.org/jira/browse/IGNITE-11724
> Project: Ignite
> Issue Type: Bug
> Components: spark
>Affects Versions: 2.8
>Reporter: Andrey Aleksandrov
>Assignee: Alexey Zinoviev
>Priority: Major
> Labels: await
> Fix For: 2.8
>
> Attachments: logs.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Next code could hang in case if PairFunction logic will throw the exception:
> {code:java}
> public class Example {
> public static void main(String[] args) {
> String configPath =
> "/home/andrei/BDP/big-data-accelerator/modules/gridgain-spark-loader-examples/config/client.xml";
> IgniteSparkSession igniteSession = IgniteSparkSession.builder()
> .appName("Spark Ignite catalog example")
> .master("local")
> .config("ignite.disableSparkSQLOptimization", true)
> .igniteConfig(configPath)
> .getOrCreate();
> JavaSparkContext sparkCtx = new
> JavaSparkContext(igniteSession.sparkContext());
> final JavaRDD records = sparkCtx.parallelize(Arrays.asList(
> new GenericRow()
> ));
> JavaPairRDD rdd_records = records.mapToPair(new
> PairFunction() {
> @Override
> public Tuple2 call(Row row) throws Exception {
> throw new IllegalStateException("some error");
> }
> });
> JavaIgniteContext igniteContext = new
> JavaIgniteContext<>(sparkCtx, configPath);
> JavaIgniteRDD igniteRdd = igniteContext. Integer>fromCache("Person");
> igniteRdd.savePairs(rdd_records);
> igniteContext.close(true);
> }
> }
> Looks like next internal code (saveValues method)should also close the
> IgniteContext in case of an unexpected exception, not only data streamer:
> try {
> it.foreach(value ⇒
> { val key = affinityKeyFunc(value, node.orNull)
> streamer.addData(key, value) }
> )
> }
> finally
> { streamer.close() }
> })
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12307) Data types coverage for basic cache operations.
Alexander Lapin created IGNITE-12307: Summary: Data types coverage for basic cache operations. Key: IGNITE-12307 URL: https://issues.apache.org/jira/browse/IGNITE-12307 Project: Ignite Issue Type: Task Components: cache Reporter: Alexander Lapin Fix For: 2.8 The data types used for testing are not collected at single test/suite and it's not clear which types are covered and which not. We should redesign the coverage and cover following Operations: * put * putAll * remove * removeAll * get * getAll Data Types both for value and key (if applicable): * byte/Byte * short/Short * int/Integer * long/Long * float/Float * double/Double * boolean/Boolean * char/String * Arrays of primitives (single type) * Arrays of Objects (different types) * Collections ** List ** Queue ** Set * Objects based on: ** primitives only ** primitives + collections ** primitives + collections + nested objects Persistance mode: * in-memory * PDS Cache configurations: * atomic/tx/mvcc * replication/partitioned * TTL/no TTL * QueryEntnty * Backups=1,2 * EvictionPolicy * writeSynchronizationMode(FULL_SYNC, PRIMARY_SYNC, FULL_ASYNC) * onheapCacheEnabled -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11508) Yarn Ignite deployment: Add support to over ride queue name through cluster properties
[
https://issues.apache.org/jira/browse/IGNITE-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-11508:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
Release Note: Added IGNITE_YARN_QUEUE property to override YARN queue name.
> Yarn Ignite deployment: Add support to over ride queue name through cluster
> properties
> --
>
> Key: IGNITE-11508
> URL: https://issues.apache.org/jira/browse/IGNITE-11508
> Project: Ignite
> Issue Type: Improvement
> Components: yarn
>Affects Versions: 2.7
>Reporter: ARAVINDA REDDY N
>Assignee: ARAVINDA REDDY N
>Priority: Minor
> Fix For: 2.8
>
> Attachments:
> IGNITE_11508_Implemented_yarn_queue_override_feature_for_Yarn_Deployment.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Yarn ignite 2.7.0 doesn't have the facility to provide queue name through the
> cluster.properties. When i checked the IgniteYarnClient source code by
> default it is set to "default".
> // Finally, set-up ApplicationSubmissionContext for the application
> ApplicationSubmissionContext appContext =
> app.getApplicationSubmissionContext();
> appContext.setApplicationName("ignition"); // application name
> appContext.setAMContainerSpec(amContainer);
> appContext.setResource(capability);
> appContext.setQueue("default"); // queue
>
> It would be a great support if we can allow overriding it through cluster
> properties.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12313) Unable to update value via sql update query if a key is a byte array within non-mvcc mode.
Alexander Lapin created IGNITE-12313:
Summary: Unable to update value via sql update query if a key is a
byte array within non-mvcc mode.
Key: IGNITE-12313
URL: https://issues.apache.org/jira/browse/IGNITE-12313
Project: Ignite
Issue Type: Bug
Reporter: Alexander Lapin
{code:java}
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: [B
cannot be cast to java.lang.Comparable
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2350)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2283)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2210)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2183)
at
org.apache.ignite.sqltests.SqlDataTypesCoverageTests.checkCRUD(SqlDataTypesCoverageTests.java:381)
at
org.apache.ignite.sqltests.SqlDataTypesCoverageTests.checkBasicSqlOperations(SqlDataTypesCoverageTests.java:335)
at
org.apache.ignite.sqltests.SqlDataTypesCoverageTests.testBinaryDataType(SqlDataTypesCoverageTests.java:269)
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
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2075)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: [B cannot be cast to
java.lang.Comparable
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2828)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$1(GridQueryProcessor.java:2309)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2347)
... 17 more
Caused by: java.lang.ClassCastException: [B cannot be cast to
java.lang.Comparable
at
org.apache.ignite.internal.binary.BinaryObjectImpl.compareForDml(BinaryObjectImpl.java:863)
at
org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender$BatchEntryComparator.compare(DmlBatchSender.java:423)
at java.util.TreeMap.compare(TreeMap.java:1295)
at java.util.TreeMap.put(TreeMap.java:538)
at
org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender$Batch.put(DmlBatchSender.java:368)
at
org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.add(DmlBatchSender.java:118)
at
org.apache.ignite.internal.processors.query.h2.dml.DmlUtils.doUpdate(DmlUtils.java:252)
at
org.apache.ignite.internal.processors.query.h2.dml.DmlUtils.processSelectResult(DmlUtils.java:168)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdateNonTransactional(IgniteH2Indexing.java:2765)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdate(IgniteH2Indexing.java:2625)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdateDistributed(IgniteH2Indexing.java:2555)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeDml(IgniteH2Indexing.java:1167)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1093)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2293)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2289)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:35)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2805)
... 19 more
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11770) Document PARTITON_SUPPLIED and PARTITION_MISSED events
[ https://issues.apache.org/jira/browse/IGNITE-11770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956191#comment-16956191 ] Ilya Kasnacheev commented on IGNITE-11770: -- [~mmuzaf] why did you remove 2.8 from this ticket? I think this feature should be documented once 2.8 is out. > Document PARTITON_SUPPLIED and PARTITION_MISSED events > -- > > Key: IGNITE-11770 > URL: https://issues.apache.org/jira/browse/IGNITE-11770 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Ilya Kasnacheev >Assignee: Artem Budnikov >Priority: Major > > Previously rebalance events will only fire on the node which does > rebalancing. Now we are introducing two events which are fired on node which > supplies data for rebalancing - SUPPLIED when partition is fully transferred > to demanding node, and MISSED when partition was not present on node > (normally should only happen on unstable topology). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11915) Document all ways to download Ignite in YARN
[ https://issues.apache.org/jira/browse/IGNITE-11915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956192#comment-16956192 ] Ilya Kasnacheev commented on IGNITE-11915: -- [~mmuzaf] why did you remove 2.8 from this ticket? I think this feature should be documented once 2.8 is out. > Document all ways to download Ignite in YARN > > > Key: IGNITE-11915 > URL: https://issues.apache.org/jira/browse/IGNITE-11915 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Ilya Kasnacheev >Priority: Major > > That is, automatic mirror download, download by URL, local file, HDFS path, > HDFS releases dir. > For other properties it would be nice to mention whether they accept local or > HDFS paths because it's not obvious. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11724) IgniteSpark integration forget to close the IgniteContext and stops the client node in case if error during PairFunction logic
[
https://issues.apache.org/jira/browse/IGNITE-11724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956144#comment-16956144
]
Nikolay Izhikov commented on IGNITE-11724:
--
[~aealeksandrov]
I don't think we should add RuntimeExceptions to the method exception list.
Methods that initiates execution of some network operations(distributed
computing) can throw runtime exceptions.
> IgniteSpark integration forget to close the IgniteContext and stops the
> client node in case if error during PairFunction logic
> ---
>
> Key: IGNITE-11724
> URL: https://issues.apache.org/jira/browse/IGNITE-11724
> Project: Ignite
> Issue Type: Bug
> Components: spark
>Affects Versions: 2.8
>Reporter: Andrey Aleksandrov
>Assignee: Alexey Zinoviev
>Priority: Major
> Labels: await
> Fix For: 2.8
>
> Attachments: logs.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Next code could hang in case if PairFunction logic will throw the exception:
> {code:java}
> public class Example {
> public static void main(String[] args) {
> String configPath =
> "/home/andrei/BDP/big-data-accelerator/modules/gridgain-spark-loader-examples/config/client.xml";
> IgniteSparkSession igniteSession = IgniteSparkSession.builder()
> .appName("Spark Ignite catalog example")
> .master("local")
> .config("ignite.disableSparkSQLOptimization", true)
> .igniteConfig(configPath)
> .getOrCreate();
> JavaSparkContext sparkCtx = new
> JavaSparkContext(igniteSession.sparkContext());
> final JavaRDD records = sparkCtx.parallelize(Arrays.asList(
> new GenericRow()
> ));
> JavaPairRDD rdd_records = records.mapToPair(new
> PairFunction() {
> @Override
> public Tuple2 call(Row row) throws Exception {
> throw new IllegalStateException("some error");
> }
> });
> JavaIgniteContext igniteContext = new
> JavaIgniteContext<>(sparkCtx, configPath);
> JavaIgniteRDD igniteRdd = igniteContext. Integer>fromCache("Person");
> igniteRdd.savePairs(rdd_records);
> igniteContext.close(true);
> }
> }
> Looks like next internal code (saveValues method)should also close the
> IgniteContext in case of an unexpected exception, not only data streamer:
> try {
> it.foreach(value ⇒
> { val key = affinityKeyFunc(value, node.orNull)
> streamer.addData(key, value) }
> )
> }
> finally
> { streamer.close() }
> })
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12308) Data types coverage for basic sql operations.
Alexander Lapin created IGNITE-12308: Summary: Data types coverage for basic sql operations. Key: IGNITE-12308 URL: https://issues.apache.org/jira/browse/IGNITE-12308 Project: Ignite Issue Type: Task Components: sql Reporter: Alexander Lapin Fix For: 2.8 For more details see: https://issues.apache.org/jira/browse/IGNITE-12307 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12308) Data types coverage for basic sql operations.
[ https://issues.apache.org/jira/browse/IGNITE-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin reassigned IGNITE-12308: Assignee: Alexander Lapin > Data types coverage for basic sql operations. > - > > Key: IGNITE-12308 > URL: https://issues.apache.org/jira/browse/IGNITE-12308 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Fix For: 2.8 > > > For more details see: https://issues.apache.org/jira/browse/IGNITE-12307 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12311) DELETE by PK doesn't work if PK is TINYINT or SMALLINT.
Alexander Lapin created IGNITE-12311:
Summary: DELETE by PK doesn't work if PK is TINYINT or SMALLINT.
Key: IGNITE-12311
URL: https://issues.apache.org/jira/browse/IGNITE-12311
Project: Ignite
Issue Type: Bug
Reporter: Alexander Lapin
1. Start bin\ignite.bat
2. Start bin\sqlline.bat -d org.apache.ignite.IgniteJdbcThinDriver -u
jdbc:ignite:thin://127.0.0.1/distributedJoins=true
3. Execute operations:
{color:#172b4d}{{{color:#0052cc}0{color}:
jdbc:ignite:thin://{color:#0052cc}127.0{color}{color:#0052cc}.0{color}{color:#0052cc}.1{color}/>
create table t1 (a tinyint {color:#0052cc}null{color} primary key, b
VARCHAR);{color:#6554c0}No{color} rows affected
({color:#0052cc}0{color},{color:#0052cc}198{color}
seconds){color:#0052cc}0{color}:
jdbc:ignite:thin://{color:#0052cc}127.0{color}{color:#0052cc}.0{color}{color:#0052cc}.1{color}/>
insert into t1 values ({color:#0052cc}1{color},
{color:#36b37e}'a'{color});{color:#0052cc}1{color} row affected
({color:#0052cc}0{color},{color:#0052cc}036{color}
seconds){color:#0052cc}0{color}:
jdbc:ignite:thin://{color:#0052cc}127.0{color}{color:#0052cc}.0{color}{color:#0052cc}.1{color}/>
select * from
t1;+++|
{color:#6554c0}A{color}|
{color:#6554c0}B{color}
|+++|
{color:#0052cc}1{color} | a
|+++{color:#0052cc}1{color}
row selected ({color:#0052cc}0{color},{color:#0052cc}048{color}
seconds){color:#0052cc}0{color}:
jdbc:ignite:thin://{color:#0052cc}127.0{color}{color:#0052cc}.0{color}{color:#0052cc}.1{color}/>
update t1 set b = {color:#36b37e}'b'{color} where
a={color:#0052cc}1{color};{color:#0052cc}1{color} row affected
({color:#0052cc}0{color},{color:#0052cc}018{color}
seconds){color:#0052cc}0{color}:
jdbc:ignite:thin://{color:#0052cc}127.0{color}{color:#0052cc}.0{color}{color:#0052cc}.1{color}/>
select * from
t1;+++|
{color:#6554c0}A{color}|
{color:#6554c0}B{color}
|+++|
{color:#0052cc}1{color} | b
|+++{color:#0052cc}1{color}
row selected ({color:#0052cc}0{color},{color:#0052cc}006{color}
seconds){color:#0052cc}0{color}:
jdbc:ignite:thin://{color:#0052cc}127.0{color}{color:#0052cc}.0{color}{color:#0052cc}.1{color}/>
delete from t1 where a={color:#0052cc}1{color};{color:#6554c0}No{color} rows
affected ({color:#0052cc}0{color},{color:#0052cc}003{color}
seconds){color:#0052cc}0{color}:
jdbc:ignite:thin://{color:#0052cc}127.0{color}{color:#0052cc}.0{color}{color:#0052cc}.1{color}/>
select * from
t1;+++|
{color:#6554c0}A{color}|
{color:#6554c0}B{color}
|+++|
{color:#0052cc}1{color} | b
|+++{color:#0052cc}1{color}
row selected ({color:#0052cc}0{color},{color:#0052cc}006{color}
seconds){color:#0052cc}0{color}:
jdbc:ignite:thin://{color:#0052cc}127.0{color}{color:#0052cc}.0{color}{color:#0052cc}.1{color}/>}}{color}
Same behavoir is for SMALLINT type
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12314) Unexpected return type in case of retrieving Byte[]{1,2,3} from cache value.
Alexander Lapin created IGNITE-12314:
Summary: Unexpected return type in case of retrieving
Byte[]{1,2,3} from cache value.
Key: IGNITE-12314
URL: https://issues.apache.org/jira/browse/IGNITE-12314
Project: Ignite
Issue Type: Bug
Reporter: Alexander Lapin
Unexpected return type in case of retrieving Byte[]\{1,2,3} from cache value:
{color:#172b4d}{{cache.{color:#172b4d}put{color}({color:#36b37e}"aaa"{color},
{color:#0052cc}new{color} {color:#6554c0}Byte{color}[]
{{color:#0052cc}1{color}, {color:#0052cc}2{color}, {color:#0052cc}3{color}});
cache.{color:#172b4d}get{color}({color:#36b37e}"aaa"{color});}}{color}
Byte[3]@... expected with corresponding content, however Object[3]@... got.
Seems that it's related to primitive wrapers, cause String[] as value works as
expected:
{color:#172b4d}{{cache.{color:#172b4d}put{color}({color:#36b37e}"aaa"{color},
{color:#0052cc}new{color} {color:#6554c0}String{color}[]
{{color:#36b37e}"1"{color}, {color:#36b37e}"2"{color},
{color:#36b37e}"3"{color}});
cache.{color:#172b4d}get{color}({color:#36b37e}"aaa"{color});}}{color}
Arrays of primitives also works as expected:
{color:#172b4d}{{cache.{color:#172b4d}put{color}({color:#36b37e}"aaa"{color},
{color:#0052cc}new{color} {color:#0052cc}byte{color}[]
{{color:#0052cc}1{color}, {color:#0052cc}2{color}, {color:#0052cc}3{color}});
cache.{color:#172b4d}get{color}({color:#36b37e}"aaa"{color});}}{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-10959) Memory leaks in continuous query handlers
[ https://issues.apache.org/jira/browse/IGNITE-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956149#comment-16956149 ] Grey Guo commented on IGNITE-10959: --- |CacheConfig|NoBackup|OneBackup|TwoBackup|Replicated| |AtomicPartitionedPrimarySync|Passed|Failed|Failed|NA| |AtomicPartitionedFullSync|Passed|Failed|Failed|NA| |AtomicReplicatedPrimarySync|NA|NA|NA|Failed| |AtomicReplicateFullSync|NA|NA|NA|Failed| |LocalAtomicPartitionedPrimarySync|Passed|Failed|Failed|NA| |LocalAtomicPartitionedFullSync|Passed|Failed|Failed|NA| |LocalAtomicReplicatedPrimarySync|NA|NA|NA|Passed| |LocalAtomicReplicateFullSync|NA|NA|NA|Passed| |TransactionPartitionedPrimarySync|Passed|Passed|Failed|NA| |TransactionPartitionedFullSync|Passed|Passed|Failed|NA| |TransactionReplicatedPrimarySync|NA|NA|NA|Failed| |TransactionReplicatedFullSync|NA|NA|NA|Failed| |LocalTransactionPartitionedPrimarySync|Passed|Passed|Failed|NA| |LocalTransactionPartitionedFullSync|Passed|Passed|Failed|NA| |LocalTransactionReplicatedPrimarySync|NA|NA|NA|Passed| |LocalTransactionReplicatedFullSync|NA|NA|NA|Passed| This is our testing > Memory leaks in continuous query handlers > - > > Key: IGNITE-10959 > URL: https://issues.apache.org/jira/browse/IGNITE-10959 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Denis Mekhanikov >Priority: Major > Fix For: 2.9 > > Attachments: CacheContinuousQueryMemoryUsageTest.java, > continuousquery_leak_profile.png > > > Continuous query handlers don't clear internal data structures after cache > events are processed. > A test, that reproduces the problem, is attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12310) SortedEvictionPolicy fails with java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang. in case of Byte, Short, Long, etc.
Alexander Lapin created IGNITE-12310:
Summary: SortedEvictionPolicy fails with
java.lang.ClassCastException: java.lang.Integer cannot be cast to
java.lang. in case of Byte, Short, Long, etc.
Key: IGNITE-12310
URL: https://issues.apache.org/jira/browse/IGNITE-12310
Project: Ignite
Issue Type: Bug
Reporter: Alexander Lapin
{code:java}
java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.Integer
at java.lang.Integer.compareTo(Integer.java:52)
at
org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicy$DefaultHolderComparator.compare(SortedEvictionPolicy.java:359)
at
org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicy$DefaultHolderComparator.compare(SortedEvictionPolicy.java:347)
at
java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655)
at
java.util.concurrent.ConcurrentSkipListMap.doPut(ConcurrentSkipListMap.java:835)
at
java.util.concurrent.ConcurrentSkipListMap.putIfAbsent(ConcurrentSkipListMap.java:1979)
at
org.apache.ignite.internal.util.GridConcurrentSkipListSet.add(GridConcurrentSkipListSet.java:142)
at
org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicy$GridConcurrentSkipListSetEx.add(SortedEvictionPolicy.java:397)
at
org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicy.touch(SortedEvictionPolicy.java:175)
at
org.apache.ignite.cache.eviction.AbstractEvictionPolicy.onEntryAccessed(AbstractEvictionPolicy.java:87)
at
org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.notifyPolicy(GridCacheEvictionManager.java:319)
at
org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(GridCacheEvictionManager.java:228)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.touch(GridCacheMapEntry.java:5052)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(GridDhtAtomicCache.java:3104)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1905)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1668)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:814)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:666)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAll0(GridDhtAtomicCache.java:1104)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAll0(GridDhtAtomicCache.java:654)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAll(GridCacheAdapter.java:2513)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.putAll(IgniteCacheProxyImpl.java:1264)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.putAll(GatewayProtectedCacheProxy.java:863)
at
org.apache.ignite.internal.processors.cache.GridCacheDataTypesCoverageTest.checkBasicCacheOperations(GridCacheDataTypesCoverageTest.java:624)
at
org.apache.ignite.internal.processors.cache.GridCacheDataTypesCoverageTest.testLongDataType(GridCacheDataTypesCoverageTest.java:347)
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
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2075)
at java.lang.Thread.run(Thread.java:748)
[2019-08-23 12:26:39,784][INFO ][main][root] >>>
[jira] [Updated] (IGNITE-12314) Unexpected return type in case of retrieving Byte[]{1,2,3} from cache value.
[
https://issues.apache.org/jira/browse/IGNITE-12314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-12314:
-
Description:
Unexpected return type in case of retrieving Byte[]\{1,2,3} from cache value:
{code:java}
cache.put("aaa", new Byte[] {1, 2, 3});
cache.get("aaa");{code}
Byte[3]@... expected with corresponding content, however Object[3]@... got.
Seems that it's related to primitive wrapers, cause String[] as value works as
expected:
{{cache.put({color:#36b37e}"aaa"{color}, {color:#0052cc}new{color}
{color:#6554c0}String{color}[] {{color:#36b37e}"1", "2",
{color:#36b37e}"3"\{color}}); cache.get{color}({color:#36b37e}"aaa"{color});}}
Arrays of primitives also works as expected:
{{cache.put({color:#36b37e}"aaa"{color}, {color:#0052cc}new{color}
{color:#0052cc}byte{color}[] {{color:#0052cc}1, 2, {color:#0052cc}3\{color}});
cache.get{color}({color:#36b37e}"aaa"{color});}}
was:
Unexpected return type in case of retrieving Byte[]\{1,2,3} from cache value:
{color:#172b4d}{{cache.{color:#172b4d}put{color}({color:#36b37e}"aaa"{color},
{color:#0052cc}new{color} {color:#6554c0}Byte{color}[]
{{color:#0052cc}1{color}, {color:#0052cc}2{color}, {color:#0052cc}3{color}});
cache.{color:#172b4d}get{color}({color:#36b37e}"aaa"{color});}}{color}
Byte[3]@... expected with corresponding content, however Object[3]@... got.
Seems that it's related to primitive wrapers, cause String[] as value works as
expected:
{color:#172b4d}{{cache.{color:#172b4d}put{color}({color:#36b37e}"aaa"{color},
{color:#0052cc}new{color} {color:#6554c0}String{color}[]
{{color:#36b37e}"1"{color}, {color:#36b37e}"2"{color},
{color:#36b37e}"3"{color}});
cache.{color:#172b4d}get{color}({color:#36b37e}"aaa"{color});}}{color}
Arrays of primitives also works as expected:
{color:#172b4d}{{cache.{color:#172b4d}put{color}({color:#36b37e}"aaa"{color},
{color:#0052cc}new{color} {color:#0052cc}byte{color}[]
{{color:#0052cc}1{color}, {color:#0052cc}2{color}, {color:#0052cc}3{color}});
cache.{color:#172b4d}get{color}({color:#36b37e}"aaa"{color});}}{color}
> Unexpected return type in case of retrieving Byte[]{1,2,3} from cache value.
>
>
> Key: IGNITE-12314
> URL: https://issues.apache.org/jira/browse/IGNITE-12314
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexander Lapin
>Priority: Major
>
> Unexpected return type in case of retrieving Byte[]\{1,2,3} from cache value:
>
> {code:java}
> cache.put("aaa", new Byte[] {1, 2, 3});
> cache.get("aaa");{code}
> Byte[3]@... expected with corresponding content, however Object[3]@... got.
>
> Seems that it's related to primitive wrapers, cause String[] as value works
> as expected:
>
> {{cache.put({color:#36b37e}"aaa"{color}, {color:#0052cc}new{color}
> {color:#6554c0}String{color}[] {{color:#36b37e}"1", "2",
> {color:#36b37e}"3"\{color}}); cache.get{color}({color:#36b37e}"aaa"{color});}}
> Arrays of primitives also works as expected:
>
> {{cache.put({color:#36b37e}"aaa"{color}, {color:#0052cc}new{color}
> {color:#0052cc}byte{color}[] {{color:#0052cc}1, 2,
> {color:#0052cc}3\{color}}); cache.get{color}({color:#36b37e}"aaa"{color});}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
