[jira] [Commented] (IGNITE-2938) IgfsBackupsDualAsyncSelfTest.testAppendParentMissing and IgfsBackupsDualAsyncSelfTest.testAppendParentMissingPartially fail sometimes on master
[
https://issues.apache.org/jira/browse/IGNITE-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325099#comment-15325099
]
Ivan Veselovsky commented on IGNITE-2938:
-
https://github.com/apache/ignite/pull/793
> IgfsBackupsDualAsyncSelfTest.testAppendParentMissing and
> IgfsBackupsDualAsyncSelfTest.testAppendParentMissingPartially fail sometimes
> on master
> ---
>
> Key: IGNITE-2938
> URL: https://issues.apache.org/jira/browse/IGNITE-2938
> Project: Ignite
> Issue Type: Test
> Components: IGFS
>Affects Versions: 1.5.0.final
>Reporter: Ivan Veselovsky
>Assignee: Ivan Veselovsky
> Fix For: 1.7
>
>
> Tests
> IgfsBackupsDualAsyncSelfTest.testAppendParentMissing
> IgfsBackupsDualAsyncSelfTest.testAppendParentMissingPartially
> fail from time to time on master -- need to investigate.
> It looks like that started to happen after fix
> https://issues.apache.org/jira/browse/IGNITE-1631 .
> The failure happens with probability ~1/50 :
> {code}
> [18:14:50,772][INFO ][main][root] >>> Starting test:
> IgfsBackupsDualAsyncSelfTest#testAppendParentMissingPartially <<<
> [18:14:50,792][ERROR][main][root] Test failed.
> java.io.IOException: Inconsistent file's data block (incorrectly written?)
> [path=/dir/subdir/file, blockIdx=0, blockSize=128, expectedBlockSize=256,
> fileBlockSize=524288, fileLen=256]
> at
> org.apache.ignite.internal.processors.igfs.IgfsInputStreamImpl.block(IgfsInputStreamImpl.java:485)
> at
> org.apache.ignite.internal.processors.igfs.IgfsInputStreamImpl.blockFragmentizerSafe(IgfsInputStreamImpl.java:399)
> at
> org.apache.ignite.internal.processors.igfs.IgfsInputStreamImpl.readFromStore(IgfsInputStreamImpl.java:373)
> at
> org.apache.ignite.internal.processors.igfs.IgfsInputStreamImpl.readFully(IgfsInputStreamImpl.java:222)
> at
> org.apache.ignite.internal.processors.igfs.IgfsInputStreamImpl.readFully(IgfsInputStreamImpl.java:216)
> at
> org.apache.ignite.internal.processors.igfs.IgfsAbstractSelfTest.checkFileContent(IgfsAbstractSelfTest.java:2999)
> at
> org.apache.ignite.internal.processors.igfs.IgfsAbstractSelfTest.checkFile(IgfsAbstractSelfTest.java:2969)
> at
> org.apache.ignite.internal.processors.igfs.IgfsDualAbstractSelfTest.testAppendParentMissingPartially(IgfsDualAbstractSelfTest.java:1364)
> at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1759)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1697)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3293) AWS bootstrap scripts patch for Ignite-Cassandra
[ https://issues.apache.org/jira/browse/IGNITE-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325090#comment-15325090 ] ASF GitHub Bot commented on IGNITE-3293: GitHub user irudyak opened a pull request: https://github.com/apache/ignite/pull/794 IGNITE-3293 AWS bootstrap scripts patch for Ignite-Cassandra You can merge this pull request into a Git repository by running: $ git pull https://github.com/irudyak/ignite ignite-3293 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/794.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #794 commit a725b5f16d9b6fb4363432710cb87d420b2c8a88 Author: Igor Date: 2016-06-10T00:03:09Z fix for ignite-3293 commit 7ba18f937fcd4d54ba156397d893731588a04f4e Author: Igor Date: 2016-06-10T04:04:21Z shell scripts to recreate Cassandra artifacts on each load tests execution > AWS bootstrap scripts patch for Ignite-Cassandra > - > > Key: IGNITE-3293 > URL: https://issues.apache.org/jira/browse/IGNITE-3293 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.6, 1.7 >Reporter: Igor Rudyak >Assignee: Igor Rudyak > > New version of AWS bootstrap script having: > 1) Gaglia monitoring > 2) Allows to manually trigger tests execution multiple times on the same > ifstastructure -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1789) Data Snapshots for Ignite caches
[
https://issues.apache.org/jira/browse/IGNITE-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324894#comment-15324894
]
Dmitriy Setrakyan commented on IGNITE-1789:
---
Michael, why do you need 2 identical data sets in memory? What you are asking
for can be done with a simple iteration through one cache and putting data into
another. However, you would have to make sure that when changing keys, the
key-affinity remains the same, so it stays on the same node. Please see
{{AffinityKeyMapped}} and {{AffinityKeyMapper}} interfaces to control affinity
mapping.
> Data Snapshots for Ignite caches
>
>
> Key: IGNITE-1789
> URL: https://issues.apache.org/jira/browse/IGNITE-1789
> Project: Ignite
> Issue Type: New Feature
> Components: cache
>Reporter: Raúl Kripalani
>Assignee: Saikat Maitra
>
> There was a discussion in the dev forum about Data Snapshots in Ignite as a
> way to obtain a consistent and "frozen" view of one or multiple caches in
> order to execute a set of SQL queries, distributed closures, map reduce, etc.
> without having to worry about data slippage (or moving data).
> The discussion is here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Data-Snapshots-in-Ignite-td4183.html
> and we still need to mature the idea, but several users chimed in and
> considered it interesting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3272) Memory consumption in ContinuousQueryHandler
[ https://issues.apache.org/jira/browse/IGNITE-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324757#comment-15324757 ] Nikolay Tikhonov commented on IGNITE-3272: -- Implemented that in backup queue don't saved key and value for filtered events. > Memory consumption in ContinuousQueryHandler > > > Key: IGNITE-3272 > URL: https://issues.apache.org/jira/browse/IGNITE-3272 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.6 >Reporter: Nikolay Tikhonov >Assignee: Nikolay Tikhonov > Attachments: IgniteCacheContinuousQueryBackupQueueTest.java > > > On backup nodes events put in queue with value and key. For filtered events > need to store only update counter and partition. In attached test which > should pass with -Xmx2g -Xms2g -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2680) Terminating running SQL queries
[
https://issues.apache.org/jira/browse/IGNITE-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324739#comment-15324739
]
Alexei Scherbakov commented on IGNITE-2680:
---
Manual and initiator failure cancellation is working, tests are passing locally.
Need to add tests for SqlFieldQuery.timeout() query property and schedule TC
run.
> Terminating running SQL queries
> ---
>
> Key: IGNITE-2680
> URL: https://issues.apache.org/jira/browse/IGNITE-2680
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Alexei Scherbakov
> Labels: important
>
> If to start a long running SQL query over a huge cache will millions of
> entries there should be a way terminate it. Even if {{QueryCursor}} is closed
> the query won't be cancelled consuming available resources.
> There should be a way to close a query having using an object that is related
> to it. Seems that ideally we can use {{QueryCursor.close()}} method for that;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3014) Optimize GridDhtPartitionTopologyImpl#localPartition()
[ https://issues.apache.org/jira/browse/IGNITE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324599#comment-15324599 ] Ilya Lantukh commented on IGNITE-3014: -- [~sboikov], I've implemented changes you suggested and re-tested this branch. Please review again. > Optimize GridDhtPartitionTopologyImpl#localPartition() > -- > > Key: IGNITE-3014 > URL: https://issues.apache.org/jira/browse/IGNITE-3014 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Lantukh >Assignee: Ilya Lantukh > Labels: performance > > This method is called at least once for every cache operation on each node. > It was partially optimized in > https://issues.apache.org/jira/browse/IGNITE-2948. > It seems that we can reduce time spent in that method even further by > removing excessive RW locks and using volatile read/write instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3014) Optimize GridDhtPartitionTopologyImpl#localPartition()
[ https://issues.apache.org/jira/browse/IGNITE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-3014: Assignee: Semen Boikov (was: Ilya Lantukh) > Optimize GridDhtPartitionTopologyImpl#localPartition() > -- > > Key: IGNITE-3014 > URL: https://issues.apache.org/jira/browse/IGNITE-3014 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Lantukh >Assignee: Semen Boikov > Labels: performance > > This method is called at least once for every cache operation on each node. > It was partially optimized in > https://issues.apache.org/jira/browse/IGNITE-2948. > It seems that we can reduce time spent in that method even further by > removing excessive RW locks and using volatile read/write instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1952) Visorcmd: add a command for reset (clear) of metrics
[ https://issues.apache.org/jira/browse/IGNITE-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-1952: - Assignee: Saikat Maitra > Visorcmd: add a command for reset (clear) of metrics > > > Key: IGNITE-1952 > URL: https://issues.apache.org/jira/browse/IGNITE-1952 > Project: Ignite > Issue Type: Task > Components: UI >Affects Versions: ignite-1.4, 1.5.0.final >Reporter: Sergey Kozlov >Assignee: Saikat Maitra >Priority: Minor > > There is no command to reset metrics data for a cache. But it is useful to > interactively reset metrics values for during a troubleshooting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1110) REST API: create/delete cache
[ https://issues.apache.org/jira/browse/IGNITE-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-1110: - Assignee: Saikat Maitra > REST API: create/delete cache > - > > Key: IGNITE-1110 > URL: https://issues.apache.org/jira/browse/IGNITE-1110 > Project: Ignite > Issue Type: Task >Affects Versions: sprint-8 >Reporter: Sergey Kozlov >Assignee: Saikat Maitra >Priority: Minor > > Apache Ignite supports dynamic caches so REST API could be extended by > following commands: > - get or create cache (start cache) > - destroy cache (stop cache) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-2741) Ignite as Spring Session data store
[ https://issues.apache.org/jira/browse/IGNITE-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-2741: - Assignee: Saikat Maitra > Ignite as Spring Session data store > --- > > Key: IGNITE-2741 > URL: https://issues.apache.org/jira/browse/IGNITE-2741 > Project: Ignite > Issue Type: New Feature >Reporter: Roman Shtykh >Assignee: Saikat Maitra > Labels: web > > On Spring Session: > http://docs.spring.io/spring-session/docs/current/reference/html5/# > How to contribute the integration: > http://docs.spring.io/spring-session/docs/current/reference/html5/#community-contributing > _From 1.1.0 Gemfire and Hazelcast are supported and can be used for > reference, if needed._ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-2345) Implement JPA-based store session listener
[ https://issues.apache.org/jira/browse/IGNITE-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-2345: - Assignee: Saikat Maitra > Implement JPA-based store session listener > -- > > Key: IGNITE-2345 > URL: https://issues.apache.org/jira/browse/IGNITE-2345 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Valentin Kulichenko >Assignee: Saikat Maitra > Fix For: 1.7 > > > We already have JDBC, Spring and Hibernate-based listeners, but it would be > useful to have JPA-based implementation as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1789) Data Snapshots for Ignite caches
[ https://issues.apache.org/jira/browse/IGNITE-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-1789: - Assignee: Saikat Maitra > Data Snapshots for Ignite caches > > > Key: IGNITE-1789 > URL: https://issues.apache.org/jira/browse/IGNITE-1789 > Project: Ignite > Issue Type: New Feature > Components: cache >Reporter: Raúl Kripalani >Assignee: Saikat Maitra > > There was a discussion in the dev forum about Data Snapshots in Ignite as a > way to obtain a consistent and "frozen" view of one or multiple caches in > order to execute a set of SQL queries, distributed closures, map reduce, etc. > without having to worry about data slippage (or moving data). > The discussion is here: > http://apache-ignite-developers.2346864.n4.nabble.com/Data-Snapshots-in-Ignite-td4183.html > and we still need to mature the idea, but several users chimed in and > considered it interesting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3227) IgniteCache: add method to calculate size per partition
[
https://issues.apache.org/jira/browse/IGNITE-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra reassigned IGNITE-3227:
-
Assignee: Saikat Maitra
> IgniteCache: add method to calculate size per partition
> ---
>
> Key: IGNITE-3227
> URL: https://issues.apache.org/jira/browse/IGNITE-3227
> Project: Ignite
> Issue Type: Improvement
>Reporter: Denis Magda
>Assignee: Saikat Maitra
> Labels: community, important
>
> It makes sense to add size calculation per partition. Actually the following
> methods should be added to the {{IgniteCache}} API.
> {code}
> public int size(int partition, CachePeekMode... peekModes) throws
> CacheException;
> public int localSize(int partition, CachePeekMode... peekModes);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3302) .NET: Inject resources into user ILogger
Pavel Tupitsyn created IGNITE-3302: -- Summary: .NET: Inject resources into user ILogger Key: IGNITE-3302 URL: https://issues.apache.org/jira/browse/IGNITE-3302 Project: Ignite Issue Type: Sub-task Components: platforms Affects Versions: 1.7 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 1.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2616) NonHeap memory usage metrics don't work as expected.
[
https://issues.apache.org/jira/browse/IGNITE-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324532#comment-15324532
]
Vladislav Pyatkov commented on IGNITE-2616:
---
[~dmagda] I corrected all the comments.
And the node metrics is working correctly now.
> NonHeap memory usage metrics don't work as expected.
>
>
> Key: IGNITE-2616
> URL: https://issues.apache.org/jira/browse/IGNITE-2616
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ershov
>Assignee: Vladislav Pyatkov
>Priority: Minor
> Attachments: ClusterMetricsOnCacheSelfTest.java
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> This simple code:
> {noformat}
> public static void main(String ... args) {
> MemoryMXBean mxBean = ManagementFactory.getMemoryMXBean();
> System.out.println(mxBean.getNonHeapMemoryUsage());
> GridUnsafeMemory uMem = new GridUnsafeMemory(1024L * 1024 * 1024 *
> 3); //3GB
> System.out.println(mxBean.getNonHeapMemoryUsage());
> uMem.allocate(1024 * 1024 * 1024, true, false);
> System.out.println(mxBean.getNonHeapMemoryUsage());
> uMem.allocate(1024 * 1024 * 1024, true, true);
> System.out.println(mxBean.getNonHeapMemoryUsage());
> }
> {noformat}
> shows:
> {noformat}
> init = 2555904(2496K) used = 4783352(4671K) committed = 8060928(7872K) max =
> -1(-1K)
> init = 2555904(2496K) used = 5018704(4901K) committed = 8060928(7872K) max =
> -1(-1K)
> init = 2555904(2496K) used = 5018960(4901K) committed = 8060928(7872K) max =
> -1(-1K)
> init = 2555904(2496K) used = 5018960(4901K) committed = 8060928(7872K) max =
> -1(-1K)
> {noformat}
> which means: offHeap metrics are incorrect. The problem is: Apache Ignite
> uses that MemoryMXBean for collecting metrics, thus Apache Ignite offHeap
> metrics are incorrect too. We should find the way to fix this, if there are
> any.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (IGNITE-3151) Using IgniteCountDownLatch sometimes drives to dead lock.
[ https://issues.apache.org/jira/browse/IGNITE-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-3151: -- Comment: was deleted (was: [~dmagda] I corrected all the comments.) > Using IgniteCountDownLatch sometimes drives to dead lock. > - > > Key: IGNITE-3151 > URL: https://issues.apache.org/jira/browse/IGNITE-3151 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov > Attachments: igniteBugShot.zip > > > Run several serve node (recoment use count of CPU - 1). > Wait update topology. > Run client > After some iteration exception will thrown (In my case it take place after > around 10K iteration). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3151) Using IgniteCountDownLatch sometimes drives to dead lock.
[ https://issues.apache.org/jira/browse/IGNITE-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324528#comment-15324528 ] Vladislav Pyatkov commented on IGNITE-3151: --- [~dmagda] I corrected all the comments. > Using IgniteCountDownLatch sometimes drives to dead lock. > - > > Key: IGNITE-3151 > URL: https://issues.apache.org/jira/browse/IGNITE-3151 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov > Attachments: igniteBugShot.zip > > > Run several serve node (recoment use count of CPU - 1). > Wait update topology. > Run client > After some iteration exception will thrown (In my case it take place after > around 10K iteration). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3301) .NET: Logging extension methods
Pavel Tupitsyn created IGNITE-3301: -- Summary: .NET: Logging extension methods Key: IGNITE-3301 URL: https://issues.apache.org/jira/browse/IGNITE-3301 Project: Ignite Issue Type: Sub-task Components: platforms Affects Versions: 1.7 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 1.7 * Trace, Debug, Info, Warn, Error overloads * GetLogger(category) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-3301) .NET: Logging extension methods
[ https://issues.apache.org/jira/browse/IGNITE-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn closed IGNITE-3301. -- > .NET: Logging extension methods > --- > > Key: IGNITE-3301 > URL: https://issues.apache.org/jira/browse/IGNITE-3301 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Affects Versions: 1.7 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: 1.7 > > > * Trace, Debug, Info, Warn, Error overloads > * GetLogger(category) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-3301) .NET: Logging extension methods
[ https://issues.apache.org/jira/browse/IGNITE-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-3301. Resolution: Done > .NET: Logging extension methods > --- > > Key: IGNITE-3301 > URL: https://issues.apache.org/jira/browse/IGNITE-3301 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Affects Versions: 1.7 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: 1.7 > > > * Trace, Debug, Info, Warn, Error overloads > * GetLogger(category) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-3283) .NET Windows Event Log logger
[ https://issues.apache.org/jira/browse/IGNITE-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn closed IGNITE-3283. -- > .NET Windows Event Log logger > - > > Key: IGNITE-3283 > URL: https://issues.apache.org/jira/browse/IGNITE-3283 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Affects Versions: 1.7 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: 1.7 > > > Provide an optional Event Log logger -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-3283) .NET Windows Event Log logger
[ https://issues.apache.org/jira/browse/IGNITE-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-3283. Resolution: Won't Fix NLog and Log4net can write to EventLog. No need to reinvent this. > .NET Windows Event Log logger > - > > Key: IGNITE-3283 > URL: https://issues.apache.org/jira/browse/IGNITE-3283 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Affects Versions: 1.7 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: 1.7 > > > Provide an optional Event Log logger -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3300) ArrayIndexOutOfBoundsException: -1 during capitalization benchmark running
Ksenia Rybakova created IGNITE-3300:
---
Summary: ArrayIndexOutOfBoundsException: -1 during capitalization
benchmark running
Key: IGNITE-3300
URL: https://issues.apache.org/jira/browse/IGNITE-3300
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.7
Reporter: Ksenia Rybakova
Test config:
1 client, 16 servers
warmup 60
duration 1h
preload 5M
operations: capitalization benchmark
backups count 1
After ~30 min after start the following errors occur at the driver:
{noformat}
[08:42:51,367][ERROR][sys-#5%null%][GridTaskWorker] Failed to obtain remote job
result policy for result from ComputeTask.result(..) method (will fail the
whole task): GridJobResultImpl [job=C4V2
[r=o.a.i.yardstick.cache.load.IgniteCapitalizationBenchmark$ScanQueryBroadcastClosure@41013d64],
sib=GridJobSiblingImpl
[sesId=bfb21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63,
jobId=51c21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63,
nodeId=79226bcc-651f-4af7-8d39-fd4019b7708c, isJobDone=false],
jobCtx=GridJobContextImpl
[jobId=51c21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63, timeoutObj=null,
attrs={}], node=TcpDiscoveryNode [id=79226bcc-651f-4af7-8d39-fd4019b7708c,
addrs=[10.20.0.216, 127.0.0.1], sockAddrs=[fosters-216/10.20.0.216:47501,
/10.20.0.216:47501, /127.0.0.1:47501], discPort=47501, order=5, intOrder=5,
lastExchangeTime=1465485122287, loc=false, ver=1.7.0#20160603-sha1:82573436,
isClient=false], ex=class o.a.i.compute.ComputeUserUndeclaredException: Failed
to execute job due to unexpected runtime exception
[jobId=51c21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63, ses=GridJobSessionImpl
[ses=GridTaskSessionImpl
[taskName=o.a.i.yardstick.cache.load.IgniteCapitalizationBenchmark$ScanQueryBroadcastClosure,
dep=LocalDeployment [super=GridDeployment [ts=1465485111989, depMode=SHARED,
clsLdr=sun.misc.Launcher$AppClassLoader@6da264f1,
clsLdrId=cee28b53551-79226bcc-651f-4af7-8d39-fd4019b7708c, userVer=0, loc=true,
sampleClsName=java.lang.String, pendingUndeploy=false, undeployed=false,
usage=0]],
taskClsName=o.a.i.yardstick.cache.load.IgniteCapitalizationBenchmark$ScanQueryBroadcastClosure,
sesId=bfb21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63,
startTime=1465486810898, endTime=9223372036854775807,
taskNodeId=a8d91d06-89bd-41a5-8b4f-6a02416dfc63,
clsLdr=sun.misc.Launcher$AppClassLoader@6da264f1, closed=false, cpSpi=null,
failSpi=null, loadSpi=null, usage=1, fullSup=false,
subjId=a8d91d06-89bd-41a5-8b4f-6a02416dfc63, mapFut=IgniteFuture
[orig=GridFutureAdapter [resFlag=0, res=null, startTime=1465486811180,
endTime=0, ignoreInterrupts=false, state=INIT]]],
jobId=51c21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63]], hasRes=true,
isCancelled=false, isOccupied=true]
class org.apache.ignite.IgniteException: Remote job threw user exception
(override or implement ComputeTask.result(..) method if you would like to have
automatic failover for this exception).
at
org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
at
org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:912)
at
org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:905)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6491)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:905)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:801)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:995)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1220)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:105)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.compute.ComputeUserUndeclaredException:
Failed to execute job due to unexpected runtime exception
[jobId=51c21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63, ses=GridJobSessionImpl
[ses=GridTaskSessionImpl
[taskName=org.apache.ignite.yardstick.cache.load.IgniteCapitalizationBenchmark$ScanQueryBroadcastClosure,
dep=LocalDeployment [super=GridDeployment [ts=14
[jira] [Created] (IGNITE-3299) Cache remove can be lost in ATOMIC cache with OFFHEAP_TIERED memory mode
Semen Boikov created IGNITE-3299:
Summary: Cache remove can be lost in ATOMIC cache with
OFFHEAP_TIERED memory mode
Key: IGNITE-3299
URL: https://issues.apache.org/jira/browse/IGNITE-3299
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Semen Boikov
Assignee: Semen Boikov
Priority: Critical
Fix For: 1.7
Added test reproducing issue (IgniteCacheConcurrentPutGetRemove).
1. There is an issue with 'deferredDelete' implementation - entry marked as
'deleted' can be evicted from cache, after this information about remove is
lost (note: this can be reproduced not only in OFFHEAP_TIERED, but also in
ONHEAP_TIERED mode with eviction policy, also this can also cause lost update
in transactional cache on changing topology).
2. Looks like condition for removing from offheap in
GridCacheMapEntry.innerUpdate is not correct:
{noformat}
if (op != GridCacheOperation.UPDATE && cctx.offheapTiered() &&
hasValPtr) {
boolean rmv = cctx.swap().removeOffheap(key);
{noformat}
It is possible that value was put in offheap, but 'hasValPtr' is false.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3298) Action "Export all" does not work on SQL page
[ https://issues.apache.org/jira/browse/IGNITE-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-3298: - Summary: Action "Export all" does not work on SQL page (was: Do not work "Export all" on SQL page) > Action "Export all" does not work on SQL page > - > > Key: IGNITE-3298 > URL: https://issues.apache.org/jira/browse/IGNITE-3298 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.7 >Reporter: Vasiliy Sisko > Fix For: 1.7 > > > Log is empty. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3298) Do not work "Export all" on SQL page
Vasiliy Sisko created IGNITE-3298: - Summary: Do not work "Export all" on SQL page Key: IGNITE-3298 URL: https://issues.apache.org/jira/browse/IGNITE-3298 Project: Ignite Issue Type: Sub-task Components: wizards Affects Versions: 1.7 Reporter: Vasiliy Sisko -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3298) Do not work "Export all" on SQL page
[ https://issues.apache.org/jira/browse/IGNITE-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-3298: -- Description: Log is empty. > Do not work "Export all" on SQL page > > > Key: IGNITE-3298 > URL: https://issues.apache.org/jira/browse/IGNITE-3298 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.7 >Reporter: Vasiliy Sisko > Fix For: 1.7 > > > Log is empty. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3297) Pipe chart is empty in special case.
Vasiliy Sisko created IGNITE-3297: - Summary: Pipe chart is empty in special case. Key: IGNITE-3297 URL: https://issues.apache.org/jira/browse/IGNITE-3297 Project: Ignite Issue Type: Sub-task Components: wizards Affects Versions: 1.7 Reporter: Vasiliy Sisko # Execute query where column A and B have the same values in all rows. # Build Pipe chart where A and B columns set as X and Y columns. Showed legend for chart but chart area is empty. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3152) Client node's addresses are registered in IP finder
[ https://issues.apache.org/jira/browse/IGNITE-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324164#comment-15324164 ] Anton Vinogradov commented on IGNITE-3152: -- I've updated test to ensure it works. > Client node's addresses are registered in IP finder > --- > > Key: IGNITE-3152 > URL: https://issues.apache.org/jira/browse/IGNITE-3152 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.5.0.final >Reporter: Valentin Kulichenko >Assignee: Anton Vinogradov > Labels: important > Fix For: 1.7 > > Attachments: Test.java > > > Currently client node register its addresses in IP finder and never > deregisters them. Also looks like coordinator address is also not removed. > The simple test that shows this behavior is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-3238) Javadoc Warning due to cassandra libs usage
[
https://issues.apache.org/jira/browse/IGNITE-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov closed IGNITE-3238.
Master fixed.
> Javadoc Warning due to cassandra libs usage
> ---
>
> Key: IGNITE-3238
> URL: https://issues.apache.org/jira/browse/IGNITE-3238
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Anton Vinogradov
>Assignee: Igor Rudyak
>Priority: Critical
> Fix For: 1.7
>
>
> I found following at Ignite 1.6 build log:
> {code} [WARNING] Javadoc Warnings
> [WARNING] warning:
> /home/teamcity/.m2/repository/org/apache/cassandra/cassandra-all/3.3/cassandra-all-3.3.jar(org/apache/cassandra/service/CassandraDaemon.class):
> major version 52 is newer than 51, the highest major version supported by
> this compiler.
> [WARNING] It is recommended that the compiler be upgraded.{code}
> seems this warning related to
> https://issues.apache.org/jira/browse/IGNITE-1371.
> Command to gain this is:
> {code} mvn clean package -DskipTests{code}
> also you can use this TeamCity task:
> http://149.202.210.143:8111/viewType.html?buildTypeId=IgniteTests_RatJavadoc
> Need to fix it without using JDK 8.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2969) Optimistic transactions support in deadlock detection
[ https://issues.apache.org/jira/browse/IGNITE-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324141#comment-15324141 ] Andrey Gura commented on IGNITE-2969: - Tests fixed. Please review. > Optimistic transactions support in deadlock detection > - > > Key: IGNITE-2969 > URL: https://issues.apache.org/jira/browse/IGNITE-2969 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Andrey Gura >Assignee: Andrey Gura > Fix For: 1.7 > > > Deadlock detection doesn't support optimistic transactions now. It should be > implemented. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3296) Validation fail in special case
Vasiliy Sisko created IGNITE-3296: - Summary: Validation fail in special case Key: IGNITE-3296 URL: https://issues.apache.org/jira/browse/IGNITE-3296 Project: Ignite Issue Type: Sub-task Components: wizards Affects Versions: 1.7 Reporter: Vasiliy Sisko Assignee: Dmitriyff # Enable some section that have disabled fields. # Input in field invalid value. # Disable section and try to save. - Validation show invalid message for disabled field. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-3238) Javadoc Warning due to cassandra libs usage
[
https://issues.apache.org/jira/browse/IGNITE-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov resolved IGNITE-3238.
--
Resolution: Fixed
Merged to master.
> Javadoc Warning due to cassandra libs usage
> ---
>
> Key: IGNITE-3238
> URL: https://issues.apache.org/jira/browse/IGNITE-3238
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Anton Vinogradov
>Assignee: Igor Rudyak
>Priority: Critical
> Fix For: 1.7
>
>
> I found following at Ignite 1.6 build log:
> {code} [WARNING] Javadoc Warnings
> [WARNING] warning:
> /home/teamcity/.m2/repository/org/apache/cassandra/cassandra-all/3.3/cassandra-all-3.3.jar(org/apache/cassandra/service/CassandraDaemon.class):
> major version 52 is newer than 51, the highest major version supported by
> this compiler.
> [WARNING] It is recommended that the compiler be upgraded.{code}
> seems this warning related to
> https://issues.apache.org/jira/browse/IGNITE-1371.
> Command to gain this is:
> {code} mvn clean package -DskipTests{code}
> also you can use this TeamCity task:
> http://149.202.210.143:8111/viewType.html?buildTypeId=IgniteTests_RatJavadoc
> Need to fix it without using JDK 8.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3216) Need to deduplicate addresses registered in the IP finder
[
https://issues.apache.org/jira/browse/IGNITE-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324109#comment-15324109
]
Anton Vinogradov commented on IGNITE-3216:
--
TeamCity passed.
> Need to deduplicate addresses registered in the IP finder
> -
>
> Key: IGNITE-3216
> URL: https://issues.apache.org/jira/browse/IGNITE-3216
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Assignee: Anton Vinogradov
> Fix For: 1.7
>
>
> {{IgniteUtils.toSocketAddresses(...)}} method can produce the collection with
> duplicated addresses in some cases (e.g., if one of hostnames is provided as
> an IP). We should deduplicate the list before returning it (most likely we
> should simply use {{Set}} instead).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3151) Using IgniteCountDownLatch sometimes drives to dead lock.
[ https://issues.apache.org/jira/browse/IGNITE-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324103#comment-15324103 ] Denis Magda commented on IGNITE-3151: - [~v.pyatkov] Please see my review notes in the pull-request. Aslo I would add the same test but when a half of the nodes are client nodes. Client nodes receive update notifications a bit later and we must be sure that your fix didn't break anything. > Using IgniteCountDownLatch sometimes drives to dead lock. > - > > Key: IGNITE-3151 > URL: https://issues.apache.org/jira/browse/IGNITE-3151 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov > Attachments: igniteBugShot.zip > > > Run several serve node (recoment use count of CPU - 1). > Wait update topology. > Run client > After some iteration exception will thrown (In my case it take place after > around 10K iteration). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3238) Javadoc Warning due to cassandra libs usage
[
https://issues.apache.org/jira/browse/IGNITE-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324099#comment-15324099
]
Anton Vinogradov commented on IGNITE-3238:
--
Igor, Thanks for branch recreation.
I closed pull request I've made before and created new.
Now I see only changes related to this task.
TeamCity Task should be checked is specified at Issue description.
I checked it at your branch:
http://149.202.210.143:8111/viewLog.html?buildId=261612&tab=buildResultsDiv&buildTypeId=IgniteTests_RatJavadoc
And it works instead of original master branch:
http://149.202.210.143:8111/viewLog.html?buildId=260834&tab=buildResultsDiv&buildTypeId=IgniteTests_RatJavadoc
Thanks for your contribution, that's really important fix, I'll merge your
changes.
> Javadoc Warning due to cassandra libs usage
> ---
>
> Key: IGNITE-3238
> URL: https://issues.apache.org/jira/browse/IGNITE-3238
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Anton Vinogradov
>Assignee: Igor Rudyak
>Priority: Critical
> Fix For: 1.7
>
>
> I found following at Ignite 1.6 build log:
> {code} [WARNING] Javadoc Warnings
> [WARNING] warning:
> /home/teamcity/.m2/repository/org/apache/cassandra/cassandra-all/3.3/cassandra-all-3.3.jar(org/apache/cassandra/service/CassandraDaemon.class):
> major version 52 is newer than 51, the highest major version supported by
> this compiler.
> [WARNING] It is recommended that the compiler be upgraded.{code}
> seems this warning related to
> https://issues.apache.org/jira/browse/IGNITE-1371.
> Command to gain this is:
> {code} mvn clean package -DskipTests{code}
> also you can use this TeamCity task:
> http://149.202.210.143:8111/viewType.html?buildTypeId=IgniteTests_RatJavadoc
> Need to fix it without using JDK 8.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1631) IGFS: append fails to create a new file in DUAL modes
[ https://issues.apache.org/jira/browse/IGNITE-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-1631: Fix Version/s: (was: 1.6) 1.7 > IGFS: append fails to create a new file in DUAL modes > - > > Key: IGNITE-1631 > URL: https://issues.apache.org/jira/browse/IGNITE-1631 > Project: Ignite > Issue Type: Bug > Components: hadoop >Affects Versions: ignite-1.4 >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky > Labels: community > Fix For: 1.7 > > > An attempt to create a new file using IGFS#append() method with "create" flag > being 'true' constantly fails with the below exception. > Fix that and cover with tests. > Caused by: class org.apache.ignite.IgniteCheckedException: Failed to append > to the file due to secondary file system exception: /dir/subdir/file2 > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager$6.onFailure(IgfsMetaManager.java:2332) > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager$6.onFailure(IgfsMetaManager.java:2284) > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:3065) > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:2860) > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager.appendDual(IgfsMetaManager.java:2337) > at > org.apache.ignite.internal.processors.igfs.IgfsImpl$16.call(IgfsImpl.java:1119) > at > org.apache.ignite.internal.processors.igfs.IgfsImpl$16.call(IgfsImpl.java:1104) > at > org.apache.ignite.internal.processors.igfs.IgfsImpl.safeOp(IgfsImpl.java:2014) > ... 11 more > Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create > path locally due to secondary file system exception: /dir > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronize(IgfsMetaManager.java:2814) > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:3018) > ... 16 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1631) IGFS: append fails to create a new file in DUAL modes
[ https://issues.apache.org/jira/browse/IGNITE-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324059#comment-15324059 ] Vladimir Ozerov commented on IGNITE-1631: - Test still fails. > IGFS: append fails to create a new file in DUAL modes > - > > Key: IGNITE-1631 > URL: https://issues.apache.org/jira/browse/IGNITE-1631 > Project: Ignite > Issue Type: Bug > Components: hadoop >Affects Versions: ignite-1.4 >Reporter: Ivan Veselovsky >Assignee: Vladimir Ozerov > Labels: community > Fix For: 1.7 > > > An attempt to create a new file using IGFS#append() method with "create" flag > being 'true' constantly fails with the below exception. > Fix that and cover with tests. > Caused by: class org.apache.ignite.IgniteCheckedException: Failed to append > to the file due to secondary file system exception: /dir/subdir/file2 > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager$6.onFailure(IgfsMetaManager.java:2332) > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager$6.onFailure(IgfsMetaManager.java:2284) > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:3065) > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:2860) > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager.appendDual(IgfsMetaManager.java:2337) > at > org.apache.ignite.internal.processors.igfs.IgfsImpl$16.call(IgfsImpl.java:1119) > at > org.apache.ignite.internal.processors.igfs.IgfsImpl$16.call(IgfsImpl.java:1104) > at > org.apache.ignite.internal.processors.igfs.IgfsImpl.safeOp(IgfsImpl.java:2014) > ... 11 more > Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create > path locally due to secondary file system exception: /dir > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronize(IgfsMetaManager.java:2814) > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:3018) > ... 16 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1631) IGFS: append fails to create a new file in DUAL modes
[ https://issues.apache.org/jira/browse/IGNITE-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-1631: Assignee: Ivan Veselovsky (was: Vladimir Ozerov) > IGFS: append fails to create a new file in DUAL modes > - > > Key: IGNITE-1631 > URL: https://issues.apache.org/jira/browse/IGNITE-1631 > Project: Ignite > Issue Type: Bug > Components: hadoop >Affects Versions: ignite-1.4 >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky > Labels: community > Fix For: 1.7 > > > An attempt to create a new file using IGFS#append() method with "create" flag > being 'true' constantly fails with the below exception. > Fix that and cover with tests. > Caused by: class org.apache.ignite.IgniteCheckedException: Failed to append > to the file due to secondary file system exception: /dir/subdir/file2 > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager$6.onFailure(IgfsMetaManager.java:2332) > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager$6.onFailure(IgfsMetaManager.java:2284) > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:3065) > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:2860) > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager.appendDual(IgfsMetaManager.java:2337) > at > org.apache.ignite.internal.processors.igfs.IgfsImpl$16.call(IgfsImpl.java:1119) > at > org.apache.ignite.internal.processors.igfs.IgfsImpl$16.call(IgfsImpl.java:1104) > at > org.apache.ignite.internal.processors.igfs.IgfsImpl.safeOp(IgfsImpl.java:2014) > ... 11 more > Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create > path locally due to secondary file system exception: /dir > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronize(IgfsMetaManager.java:2814) > at > org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:3018) > ... 16 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3294) IGFS: Merge create routine for PRIMARY and DUAL modes.
[ https://issues.apache.org/jira/browse/IGNITE-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3294: Summary: IGFS: Merge create routine for PRIMARY and DUAL modes. (was: IGFS: Request multiple path IDs in a single request during sync step.) > IGFS: Merge create routine for PRIMARY and DUAL modes. > -- > > Key: IGNITE-3294 > URL: https://issues.apache.org/jira/browse/IGNITE-3294 > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 1.7 > > > Currently during secondary file system synchronization we request multiple > paths in a separate "idsForPaths()" requests. > Instead, it is better to get all required IDs in a single request. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-3287) IGFS: Do not synchronize file system during deletes.
[ https://issues.apache.org/jira/browse/IGNITE-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-3287. --- > IGFS: Do not synchronize file system during deletes. > > > Key: IGNITE-3287 > URL: https://issues.apache.org/jira/browse/IGNITE-3287 > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.7 > > > There is no need to synchronize IGFS with secondary file system when > performing removes. Instead, we should simply call the secondary file system > and exit form within a transaction, and exit. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-3287) IGFS: Do not synchronize file system during deletes.
[ https://issues.apache.org/jira/browse/IGNITE-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-3287. - Resolution: Fixed > IGFS: Do not synchronize file system during deletes. > > > Key: IGNITE-3287 > URL: https://issues.apache.org/jira/browse/IGNITE-3287 > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.7 > > > There is no need to synchronize IGFS with secondary file system when > performing removes. Instead, we should simply call the secondary file system > and exit form within a transaction, and exit. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2616) NonHeap memory usage metrics don't work as expected.
[
https://issues.apache.org/jira/browse/IGNITE-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324055#comment-15324055
]
Denis Magda commented on IGNITE-2616:
-
[~v.pyatkov], reviewed. Please see my comments in the pull request.
In short the issue hasn't been fixed for node metrics. The fix is only for the
cluster metrics. Please fix it for the node metrics instead and cluster metrics
will work in a correct way automatically after that.
> NonHeap memory usage metrics don't work as expected.
>
>
> Key: IGNITE-2616
> URL: https://issues.apache.org/jira/browse/IGNITE-2616
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ershov
>Assignee: Vladislav Pyatkov
>Priority: Minor
> Attachments: ClusterMetricsOnCacheSelfTest.java
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> This simple code:
> {noformat}
> public static void main(String ... args) {
> MemoryMXBean mxBean = ManagementFactory.getMemoryMXBean();
> System.out.println(mxBean.getNonHeapMemoryUsage());
> GridUnsafeMemory uMem = new GridUnsafeMemory(1024L * 1024 * 1024 *
> 3); //3GB
> System.out.println(mxBean.getNonHeapMemoryUsage());
> uMem.allocate(1024 * 1024 * 1024, true, false);
> System.out.println(mxBean.getNonHeapMemoryUsage());
> uMem.allocate(1024 * 1024 * 1024, true, true);
> System.out.println(mxBean.getNonHeapMemoryUsage());
> }
> {noformat}
> shows:
> {noformat}
> init = 2555904(2496K) used = 4783352(4671K) committed = 8060928(7872K) max =
> -1(-1K)
> init = 2555904(2496K) used = 5018704(4901K) committed = 8060928(7872K) max =
> -1(-1K)
> init = 2555904(2496K) used = 5018960(4901K) committed = 8060928(7872K) max =
> -1(-1K)
> init = 2555904(2496K) used = 5018960(4901K) committed = 8060928(7872K) max =
> -1(-1K)
> {noformat}
> which means: offHeap metrics are incorrect. The problem is: Apache Ignite
> uses that MemoryMXBean for collecting metrics, thus Apache Ignite offHeap
> metrics are incorrect too. We should find the way to fix this, if there are
> any.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3294) IGFS: Request multiple path IDs in a single request during sync step.
[ https://issues.apache.org/jira/browse/IGNITE-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3294: Description: Currently during secondary file system synchronization we request multiple paths in a separate "idsForPaths()" requests. Instead, it is better to get all required IDs in a single request. was: Currently during secondary file system synchronization we request multiple paths in a separate "idsForPaths()" requests. Instead, it is better to get all required IDs in a single request. Moreover, we can re-use already requested IDs. > IGFS: Request multiple path IDs in a single request during sync step. > - > > Key: IGNITE-3294 > URL: https://issues.apache.org/jira/browse/IGNITE-3294 > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 1.7 > > > Currently during secondary file system synchronization we request multiple > paths in a separate "idsForPaths()" requests. > Instead, it is better to get all required IDs in a single request. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3295) IGFS: Introduce file ID cache (HashMap) to minimize cache calls.
Vladimir Ozerov created IGNITE-3295: --- Summary: IGFS: Introduce file ID cache (HashMap) to minimize cache calls. Key: IGNITE-3295 URL: https://issues.apache.org/jira/browse/IGNITE-3295 Project: Ignite Issue Type: Sub-task Components: IGFS Affects Versions: 1.6 Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 1.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3294) IGFS: Request multiple path IDs in a single request during sync step.
[ https://issues.apache.org/jira/browse/IGNITE-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3294: Issue Type: Sub-task (was: Task) Parent: IGNITE-3245 > IGFS: Request multiple path IDs in a single request during sync step. > - > > Key: IGNITE-3294 > URL: https://issues.apache.org/jira/browse/IGNITE-3294 > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 1.7 > > > Currently during secondary file system synchronization we request multiple > paths in a separate "idsForPaths()" requests. > Instead, it is better to get all required IDs in a single request. Moreover, > we can re-use already requested IDs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3294) IGFS: Request multiple path IDs in a single request during sync step.
Vladimir Ozerov created IGNITE-3294: --- Summary: IGFS: Request multiple path IDs in a single request during sync step. Key: IGNITE-3294 URL: https://issues.apache.org/jira/browse/IGNITE-3294 Project: Ignite Issue Type: Task Components: IGFS Affects Versions: 1.6 Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 1.7 Currently during secondary file system synchronization we request multiple paths in a separate "idsForPaths()" requests. Instead, it is better to get all required IDs in a single request. Moreover, we can re-use already requested IDs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
