[jira] [Created] (IGNITE-11539) Document services hot redeployment via DeploymentSpi
Vyacheslav Daradur created IGNITE-11539: --- Summary: Document services hot redeployment via DeploymentSpi Key: IGNITE-11539 URL: https://issues.apache.org/jira/browse/IGNITE-11539 Project: Ignite Issue Type: Task Components: documentation, managed services Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.8 It's necessary to document "how to use" service hot redeployment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11384) Introduce an opportunity of services hot redeployment via DeploymentSpi
Vyacheslav Daradur created IGNITE-11384: --- Summary: Introduce an opportunity of services hot redeployment via DeploymentSpi Key: IGNITE-11384 URL: https://issues.apache.org/jira/browse/IGNITE-11384 Project: Ignite Issue Type: Sub-task Components: managed services Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.8 We can integrate service processor with DeploymentSpi to introduce an opportunity of services hot redeployment. For this change, the service processor should try to get and use registered classloader registered for the service's class in DeploymentSpi. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10910) GridTaskProcessor#onKernalStop may lead to a deadlock and execution timeout in "SPI" TC build-plan
Vyacheslav Daradur created IGNITE-10910:
---
Summary: GridTaskProcessor#onKernalStop may lead to a deadlock and
execution timeout in "SPI" TC build-plan
Key: IGNITE-10910
URL: https://issues.apache.org/jira/browse/IGNITE-10910
Project: Ignite
Issue Type: Task
Affects Versions: 2.7
Reporter: Vyacheslav Daradur
Fix For: 2.8
In rare cases calling of {{GridTaskProcessor#onKernalStop}} may lead to a
deadlock with the following stack trace:
{code:java}
"node-stopper" #225287 prio=5 os_prio=0 tid=0x7f224057a800 nid=0x233aae
waiting on condition [0x7f24607ef000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at
org.apache.ignite.internal.util.GridSpinReadWriteLock.tryWriteLock(GridSpinReadWriteLock.java:347)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.onKernalStop(GridTaskProcessor.java:198)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2305)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2253)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2614)
- locked <0x9f42a970> (a
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2577)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:379)
at
org.apache.ignite.failure.StopNodeFailureHandler$1.run(StopNodeFailureHandler.java:36)
at java.lang.Thread.run(Thread.java:748)
{code}
It's the cause of execution timeout of "SPI" build-plan on TC:
[https://ci.ignite.apache.org/viewLog.html?buildId=2698887]
[https://ci.ignite.apache.org/viewLog.html?buildId=2689621]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10899) Service Grid: disconnecting during node stop may lead to deadlock
Vyacheslav Daradur created IGNITE-10899:
---
Summary: Service Grid: disconnecting during node stop may lead to
deadlock
Key: IGNITE-10899
URL: https://issues.apache.org/jira/browse/IGNITE-10899
Project: Ignite
Issue Type: Task
Components: managed services
Affects Versions: 2.7
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
Fix For: 2.8
In a rare case, when {{onDisconneced}} may be called during node stopping
deadlock may occur because of {{ServiceDeploymentManage#stopProcessong}}
blocks busyLock and not release it intended.
The issue found on TeamCity Zookeeper suite with the following stack trace:
{CODE}
disco-notifier-worker-#569118%client4%"
#609288
prio=5 os_prio=0 tid=0x7f905b440800 nid=0x3f6fbd
sleeping[0x7f9383efd000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at
org.apache.ignite.internal.util.GridSpinReadWriteLock.writeLock(GridSpinReadWriteLock.java:204)
at
org.apache.ignite.internal.util.GridSpinBusyLock.block(GridSpinBusyLock.java:76)
at
org.apache.ignite.internal.processors.service.ServiceDeploymentManager.stopProcessing(ServiceDeploymentManager.java:137)
at
org.apache.ignite.internal.processors.service.IgniteServiceProcessor.stopProcessor(IgniteServiceProcessor.java:261)
at
org.apache.ignite.internal.processors.service.IgniteServiceProcessor.onDisconnected(IgniteServiceProcessor.java:429)
at
org.apache.ignite.internal.IgniteKernal.onDisconnected(IgniteKernal.java:4010)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:819)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:602)
- locked <0xf7ecdfa0> (a java.lang.Object)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4$$Lambda$25/2087171109.run(Unknown
Source)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2696)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2734)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{CODE}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10888) .NET: ServicesTest.TestGetServiceProxy(False) became flaky with high fail rate
Vyacheslav Daradur created IGNITE-10888:
---
Summary: .NET: ServicesTest.TestGetServiceProxy(False) became
flaky with high fail rate
Key: IGNITE-10888
URL: https://issues.apache.org/jira/browse/IGNITE-10888
Project: Ignite
Issue Type: Task
Components: managed services, platforms
Affects Versions: 2.7
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
Fix For: 2.8
Looks like {{ServicesTest.TestGetServiceProxy(False)}} became flaky after
IGNITE-9607.
The problem is in a flag "executed" of platforms proxy. Need to investigate a
reason.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10862) Introduce tool to free up space on a disc of unused memory pages
Vyacheslav Daradur created IGNITE-10862: --- Summary: Introduce tool to free up space on a disc of unused memory pages Key: IGNITE-10862 URL: https://issues.apache.org/jira/browse/IGNITE-10862 Project: Ignite Issue Type: Improvement Components: persistence Affects Versions: 2.7 Reporter: Vyacheslav Daradur Fix For: 2.8 At the current time, Ignite is not able to release occupied disc space even if a significant amount of data was removed from IgniteCache. It disturbs our users because they can't use hardware effectively, also it increases TCO. *Use-cases:* Let's imagine that we have used IgniteCache with enabled PDS during the time: - hardware disc space has been occupied during growing up of an amount of data, e.g. 100Gb; - then, we removed non-actual data, e.g 50Gb, which became useless for us; - disc space stopped growing up with new data, but it was not released, and still took 100Gb, instead of expected 50Gb; Another use case: - a user extracts data from IgniteCache to store it in separate IgniteCache or another store; - disc still is occupied and the user is not able to store data in the different cache at the same cluster because of disc limitation; *Possible solutions:* Introduce some kind of mechanics which will be able to shrink data in IgniteCache and to free up space on a disc of mapped free memory pages. A solution should take into account possible concurrent reads and updates of data and indexes to maintain consistency. Maybe, it makes sense to implement a tool to be offline at the first step that means concurrent operations will be prohibited. Strongly recommended discussing design on dev-list with Ignite experts before the start of implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10830) Return back semantic of GridServiceProcessor#ServiceTopologyCallable to avoid possible serialization issues
Vyacheslav Daradur created IGNITE-10830:
---
Summary: Return back semantic of
GridServiceProcessor#ServiceTopologyCallable to avoid possible serialization
issues
Key: IGNITE-10830
URL: https://issues.apache.org/jira/browse/IGNITE-10830
Project: Ignite
Issue Type: Task
Components: managed services
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
Fix For: 2.8
It's necessary to revert changes of
{{GridServiceProcessor#ServiceTopologyCallable}} introduced within IGNITE-9607.
This may lead to serialization issues in some cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10817) Service Grid: Introduce diagnostic tool to dump pending deployment tasks
Vyacheslav Daradur created IGNITE-10817: --- Summary: Service Grid: Introduce diagnostic tool to dump pending deployment tasks Key: IGNITE-10817 URL: https://issues.apache.org/jira/browse/IGNITE-10817 Project: Ignite Issue Type: Task Components: managed services Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.8 It's necessary to introduce some kind of diagnostic tools to dump service deployments task which are pending in the queue in a log. If possible, existing PME diagnostic mechanics should be reused. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10811) Add new TC build-config to test Service Grid new and old implementations
Vyacheslav Daradur created IGNITE-10811: --- Summary: Add new TC build-config to test Service Grid new and old implementations Key: IGNITE-10811 URL: https://issues.apache.org/jira/browse/IGNITE-10811 Project: Ignite Issue Type: Task Components: managed services Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.8 It's necessary to add new build configuration on TeamCity (after merge IGNITE-9607) to have ability testing new and old implementations of the service processor. In general, new build plan we should contain 2 test suites: 1) To place Service Grid related tests which *do not depend on* service processor's implementation (like classic unit tests) and *should be executed once*; 2) To place Service Grid related tests which *depend* on service processor's implementation and *should be executed twice* in the new mode and old mode (-DIGNITE_EVENT_DRIVEN_SERVICE_PROCESSOR_ENABLED=false) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10715) Remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in tests
Vyacheslav Daradur created IGNITE-10715: --- Summary: Remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in tests Key: IGNITE-10715 URL: https://issues.apache.org/jira/browse/IGNITE-10715 Project: Ignite Issue Type: Task Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.8 It's necessary to remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in tests since this is default IP finder in tests after IGNITE-10555. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10705) Wrong check of test's compatible 'dataMode' in IgniteConfigVariationsAbstractTest
Vyacheslav Daradur created IGNITE-10705:
---
Summary: Wrong check of test's compatible 'dataMode' in
IgniteConfigVariationsAbstractTest
Key: IGNITE-10705
URL: https://issues.apache.org/jira/browse/IGNITE-10705
Project: Ignite
Issue Type: Bug
Reporter: Vyacheslav Daradur
Found that method {{IgniteConfigVariationsAbstractTest#isCompatible}} works
incorrectly.
Here is the actual code:
{code:java}
protected boolean isCompatible() throws Exception {
switch (dataMode) {
case BINARILIZABLE:
case PLANE_OBJECT:
return !(getConfiguration().getMarshaller() instanceof
JdkMarshaller);
}
return false;
}
{code}
It returns {{false}} if a test mode is [SERIALIZABLE, CUSTOM_SERIALIZABLE], but
this is main modes which are supported by any marshaller.
*That means a set of tests which should be executed will be skipped instead.*
Also, modes {{BINARILIZABLE}} and {{PLANE_OBJECT}} are supported only by
{{BinaryMarshaller}} and {{OptimizedMarshaller.setRequireSerializable(false)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10615) Ignite Compatibility: fix arguments' checking in the node runner
Vyacheslav Daradur created IGNITE-10615:
---
Summary: Ignite Compatibility: fix arguments' checking in the node
runner
Key: IGNITE-10615
URL: https://issues.apache.org/jira/browse/IGNITE-10615
Project: Ignite
Issue Type: Improvement
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
Fix For: 2.8
There is the checking of arguments number In
{{IgniteCompatibilityNodeRunner#main}}, which expected at least 3 arguments,
but in actual code at least 5 arguments are required.
The checking should be fixed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10555) Set 'TcpDiscoveryVmIpFinder' as default IP finder for tests instead of 'TcpDiscoveryMulticastIpFinder'
Vyacheslav Daradur created IGNITE-10555: --- Summary: Set 'TcpDiscoveryVmIpFinder' as default IP finder for tests instead of 'TcpDiscoveryMulticastIpFinder' Key: IGNITE-10555 URL: https://issues.apache.org/jira/browse/IGNITE-10555 Project: Ignite Issue Type: Improvement Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.8 Most of our tests starting Ignite nodes in the same JVM, that allows us using shared 'TcpDiscoveryVmIpFinder'. There are following main advantages of using 'TcpDiscoveryVmIpFinder': * reducing possible conflicts in the development environment, when nodes from different clusters may find each other; * speedup of nodes initial discovery, especially on Windows; * avoiding of overwriting 'getConfiguration' and copypasta only to set up static IP finder in tests; We should change the default IP finder in tests to 'TcpDiscoveryVmIpFinder' as the first step and remove related boilerplate as the second step. Once the first step of the change will be finished then we should fill a separate task for removing related boilerplate. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10523) Ignite Compatibility: add check that started node is of expected version
Vyacheslav Daradur created IGNITE-10523: --- Summary: Ignite Compatibility: add check that started node is of expected version Key: IGNITE-10523 URL: https://issues.apache.org/jira/browse/IGNITE-10523 Project: Ignite Issue Type: Improvement Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur It's necessary to check that node started in separate JVM is of a specified version to avoid unexpected behavior. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10116) Document implemented design of Service Grid (redesign phase 1)
Vyacheslav Daradur created IGNITE-10116: --- Summary: Document implemented design of Service Grid (redesign phase 1) Key: IGNITE-10116 URL: https://issues.apache.org/jira/browse/IGNITE-10116 Project: Ignite Issue Type: Task Components: managed services Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.8 It's necessary to document implemented design of Service Grid and publish in wiki. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9832) MTCGA: Licenses Headers failed
Vyacheslav Daradur created IGNITE-9832: -- Summary: MTCGA: Licenses Headers failed Key: IGNITE-9832 URL: https://issues.apache.org/jira/browse/IGNITE-9832 Project: Ignite Issue Type: Bug Affects Versions: 2.6 Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.8 Attachments: rat.zip TeamCity's build plan "Licenses Headers" failed with errors. (report|^rat.zip) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9742) Illegal change of DiscoveryCustomEvent in GridDhtPartitionsExchangeFuture#onDone
Vyacheslav Daradur created IGNITE-9742:
--
Summary: Illegal change of DiscoveryCustomEvent in
GridDhtPartitionsExchangeFuture#onDone
Key: IGNITE-9742
URL: https://issues.apache.org/jira/browse/IGNITE-9742
Project: Ignite
Issue Type: Bug
Affects Versions: 2.6
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
Fix For: 2.8
The following code is called in {{GridDhtPartitionsExchangeFuture#onDone}}:
{code}
((DiscoveryCustomEvent)firstDiscoEvt).customMessage(null);
{code}
That means a global instance of 'DiscoveryCustomEvent' is being
mutated outside discovery-spi infrastructure. It also means that
discovery listeners receive 'DiscoveryCustomEvent' with 'null' field
instead of 'CustomMessage' which they may rely on.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9710) Ignite watchdog service handles cache creation
Vyacheslav Daradur created IGNITE-9710:
--
Summary: Ignite watchdog service handles cache creation
Key: IGNITE-9710
URL: https://issues.apache.org/jira/browse/IGNITE-9710
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.6
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
Fix For: 2.7
Ignite watchdog service introduced by IGNITE-6587 handles long running cache
creation.
Action in {{GridDhtPartitionsExchangeFuture#init}} may take significant time
and possibly should be covered by blocking section of warchdog service.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9709) IgniteCache : Put/Get operations hang on deactivated cluster
Vyacheslav Daradur created IGNITE-9709:
--
Summary: IgniteCache : Put/Get operations hang on deactivated
cluster
Key: IGNITE-9709
URL: https://issues.apache.org/jira/browse/IGNITE-9709
Project: Ignite
Issue Type: Bug
Affects Versions: 2.6
Reporter: Vyacheslav Daradur
{{IgniteCache#put/get}} operations hang on inactive cluster.
Scenario:
# Get instance of {{IgniteCache}} on active cluster;
# Deactivate cluster;
# Perform put/get operation using instance from step 1;
{code}
IgniteEx ignite = startGrid(0);
assertTrue(ignite.cluster().active());
IgniteCache cache = ignite.getOrCreateCache("testCache");
cache.put("key", "val");
ignite.cluster().active(false);
assertFalse(ignite.cluster().active());
IgniteInternalFuture fut = GridTestUtils.runAsync(() ->
cache.get("key"));
ignite.cluster().active(true);
assertTrue(ignite.cluster().active());
assertNotNull(fut.get(10_000)); // Timeout was reached here
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9692) Cache creation request may be missed on coordinator change
Vyacheslav Daradur created IGNITE-9692: -- Summary: Cache creation request may be missed on coordinator change Key: IGNITE-9692 URL: https://issues.apache.org/jira/browse/IGNITE-9692 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.6 Reporter: Vyacheslav Daradur Attachments: CacheCreationOnCoordinatorChange.java Request of cache creation may be missed in case of coordinator change. Reproducer: [^CacheCreationOnCoordinatorChange.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9607) Service Grid redesign - phase 1
Vyacheslav Daradur created IGNITE-9607: -- Summary: Service Grid redesign - phase 1 Key: IGNITE-9607 URL: https://issues.apache.org/jira/browse/IGNITE-9607 Project: Ignite Issue Type: Improvement Components: managed services Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.7 This is an umbrella ticket for tasks which should be implemented atomically in phase #1 of Service Grid redesign. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9232) Remove commented method GridCacheUtils#isMongoCache
Vyacheslav Daradur created IGNITE-9232:
--
Summary: Remove commented method GridCacheUtils#isMongoCache
Key: IGNITE-9232
URL: https://issues.apache.org/jira/browse/IGNITE-9232
Project: Ignite
Issue Type: Task
Reporter: Vyacheslav Daradur
There is a method: {{GridCacheUtils#isMongoCache}} which has been commented in
2014y.
Shoud be removed as unused.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9076) Service Grid: Introduce timeout to interrupt long Service#init on deployment
Vyacheslav Daradur created IGNITE-9076: -- Summary: Service Grid: Introduce timeout to interrupt long Service#init on deployment Key: IGNITE-9076 URL: https://issues.apache.org/jira/browse/IGNITE-9076 Project: Ignite Issue Type: Task Components: managed services Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.7 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9075) Service Grid: Lifecycle of affinity deployed service should be reworked
Vyacheslav Daradur created IGNITE-9075: -- Summary: Service Grid: Lifecycle of affinity deployed service should be reworked Key: IGNITE-9075 URL: https://issues.apache.org/jira/browse/IGNITE-9075 Project: Ignite Issue Type: Task Components: managed services Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.7 The main question shoud be clarified: Should we automatically undeploy services, which had been deployed using #deployKeyAffinitySingleton, on destroying of related IgniteCache? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8915) NPE during executing local SqlQuery from client node
Vyacheslav Daradur created IGNITE-8915:
--
Summary: NPE during executing local SqlQuery from client node
Key: IGNITE-8915
URL: https://issues.apache.org/jira/browse/IGNITE-8915
Project: Ignite
Issue Type: Task
Affects Versions: 2.5
Reporter: Vyacheslav Daradur
Attachments: IgniteCacheReplicatedClientLocalQuerySelfTest.java
NPE when trying to execute {{SqlQuery}} with {{setLocal(true)}} from client
node.
[Reproducer|^IgniteCacheReplicatedClientLocalQuerySelfTest.java].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8512) Abbr-plugin: Add check of method arguments code style
Vyacheslav Daradur created IGNITE-8512: -- Summary: Abbr-plugin: Add check of method arguments code style Key: IGNITE-8512 URL: https://issues.apache.org/jira/browse/IGNITE-8512 Project: Ignite Issue Type: Task Reporter: Vyacheslav Daradur It is necessary to add check of method arguments code style to Abbreviation Plugin: https://github.com/dspavlov/ignite-abbrev-plugin Methods arguments have to be checked according to coding guidelines: https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-MethodArguments Dev-list discussion: http://apache-ignite-developers.2346864.n4.nabble.com/method-arguments-code-style-td30088.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8315) Prevent printing the partition distribution on clients nodes
Vyacheslav Daradur created IGNITE-8315: -- Summary: Prevent printing the partition distribution on clients nodes Key: IGNITE-8315 URL: https://issues.apache.org/jira/browse/IGNITE-8315 Project: Ignite Issue Type: Bug Components: general Affects Versions: 2.6 Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.6 subj -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8283) CPP: Implement 'varint' solution to be configurable via BinaryConfiguration
Vyacheslav Daradur created IGNITE-8283: -- Summary: CPP: Implement 'varint' solution to be configurable via BinaryConfiguration Key: IGNITE-8283 URL: https://issues.apache.org/jira/browse/IGNITE-8283 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Daradur Assignee: Nikolay Izhikov Fix For: 2.6 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8156) Ignite Compatibility: common improvements
Vyacheslav Daradur created IGNITE-8156:
--
Summary: Ignite Compatibility: common improvements
Key: IGNITE-8156
URL: https://issues.apache.org/jira/browse/IGNITE-8156
Project: Ignite
Issue Type: Task
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
Fix For: 2.6
Found issues in the 'compatibility' module:
* classpath building process should be simplified
* {{DummyPersistenceCompatibilityTest}} should be renamed or split
* needs resolve code style issues
* {{IgniteUuidCompatibilityTest}} should be removed. {{UUID type}} should be
checked in common test
* PDS's directory cleaning logic should be moved to
{{IgniteCompatibilityAbstractTest}}
* etc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7588) Deprecate CacheLocalStore annotation
Vyacheslav Daradur created IGNITE-7588: -- Summary: Deprecate CacheLocalStore annotation Key: IGNITE-7588 URL: https://issues.apache.org/jira/browse/IGNITE-7588 Project: Ignite Issue Type: Task Components: general Affects Versions: 2.3, 2.4 Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.5 We should annotate @CacheLocalStore as @Depricated, because of using CacheLocalStore annotation has the hidden issues like rebalancing and possible data consistency issues. See [dev-list discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Should-we-annotate-CacheLocalStore-as-Depricated-tt26490.html] for details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-6658) Add a version of Ignite instance to logger category
Vyacheslav Daradur created IGNITE-6658: -- Summary: Add a version of Ignite instance to logger category Key: IGNITE-6658 URL: https://issues.apache.org/jira/browse/IGNITE-6658 Project: Ignite Issue Type: Improvement Security Level: Public (Viewable by anyone) Affects Versions: 2.2 Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Priority: Minor Fix For: 2.4 Needs to add a version of Ignite instance to logger category in Compatibility Testing Framework. This would make it easier to analyze the tests logged output. The improvement suggested by [~avinogradov]. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6473) Introduce a constant of default persistence store directory name
Vyacheslav Daradur created IGNITE-6473:
--
Summary: Introduce a constant of default persistence store
directory name
Key: IGNITE-6473
URL: https://issues.apache.org/jira/browse/IGNITE-6473
Project: Ignite
Issue Type: Improvement
Components: persistence
Affects Versions: 2.2
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
Fix For: 2.3
Found that the name of default persistence store ("db") is hardcoded in
{{FilePageStoreManager}} and in some related unit tests.
This may lead to issues in case of changing the directory name.
Need to introduce a constant of default persistence store directory name, for
example:
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5910) Method stopGrid(name) doesn't work in multiJvm mode
Vyacheslav Daradur created IGNITE-5910:
--
Summary: Method stopGrid(name) doesn't work in multiJvm mode
Key: IGNITE-5910
URL: https://issues.apache.org/jira/browse/IGNITE-5910
Project: Ignite
Issue Type: Bug
Affects Versions: 2.1
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
Fix For: 2.2
{code:title=Exception at call}
java.lang.ClassCastException:
org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy cannot be
cast to org.apache.ignite.internal.IgniteKernal
{code}
{code:title=Reproducer snippet}
/** {@inheritDoc} */
@Override protected boolean isMultiJvm() {
return true;
}
/**
* @throws Exception If failed.
*/
public void testGrid() throws Exception {
try {
startGrid(0);
startGrid(1);
}
finally {
stopGrid(1);
stopGrid(0);
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5882) Duplicated dependency in pom.xml of core module
Vyacheslav Daradur created IGNITE-5882:
--
Summary: Duplicated dependency in pom.xml of core module
Key: IGNITE-5882
URL: https://issues.apache.org/jira/browse/IGNITE-5882
Project: Ignite
Issue Type: Bug
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
{code}
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-core:jar:2.2.0-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must
be unique: com.google.guava:guava:jar -> version 14.0.1 vs ${guava.version} @
line 215, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5736) Add test of backward-compatibility
Vyacheslav Daradur created IGNITE-5736: -- Summary: Add test of backward-compatibility Key: IGNITE-5736 URL: https://issues.apache.org/jira/browse/IGNITE-5736 Project: Ignite Issue Type: Sub-task Components: general Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.2 Need to add unit-test to test compatibility with AI 2.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5477) Java: BinaryMarshaller should write ints in "varint" encoding where it makes sense
Vyacheslav Daradur created IGNITE-5477: -- Summary: Java: BinaryMarshaller should write ints in "varint" encoding where it makes sense Key: IGNITE-5477 URL: https://issues.apache.org/jira/browse/IGNITE-5477 Project: Ignite Issue Type: Sub-task Components: platforms Affects Versions: 2.0 Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.1 Need to implement IGNITE-5097 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5226) Annotated fields compression
Vyacheslav Daradur created IGNITE-5226:
--
Summary: Annotated fields compression
Key: IGNITE-5226
URL: https://issues.apache.org/jira/browse/IGNITE-5226
Project: Ignite
Issue Type: New Feature
Components: binary, cache
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
Fix For: 2.1
Develop solution for compression of annotated fields of an object.
For example:
{code}
class Foo {
@BinaryCompession
String data;
}
{code}
It must be compatible with querying and indexing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5153) CPP: BinaryMarshaller should write ints in "varint" encoding where it makes sense
Vyacheslav Daradur created IGNITE-5153: -- Summary: CPP: BinaryMarshaller should write ints in "varint" encoding where it makes sense Key: IGNITE-5153 URL: https://issues.apache.org/jira/browse/IGNITE-5153 Project: Ignite Issue Type: Sub-task Components: general Affects Versions: 2.0 Reporter: Vyacheslav Daradur Fix For: 2.1 Need to implement IGNITE-5097 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5152) .NET: BinaryMarshaller should write ints in "varint" encoding where it makes sense
Vyacheslav Daradur created IGNITE-5152: -- Summary: .NET: BinaryMarshaller should write ints in "varint" encoding where it makes sense Key: IGNITE-5152 URL: https://issues.apache.org/jira/browse/IGNITE-5152 Project: Ignite Issue Type: Sub-task Components: general Affects Versions: 2.0 Reporter: Vyacheslav Daradur Fix For: 2.1 Need to implement IGNITE-5097 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4884) Visorcmd - minor text mistake
Vyacheslav Daradur created IGNITE-4884:
--
Summary: Visorcmd - minor text mistake
Key: IGNITE-4884
URL: https://issues.apache.org/jira/browse/IGNITE-4884
Project: Ignite
Issue Type: Task
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
Priority: Trivial
Fix For: 2.0
{noformat}
'Hi' - Number of cache hits.
'Mi' - Number of cache misses.
'Rd' - number of cache reads.
'Wr' - Number of cache writes.
{noformat}
Looks like "number of cache reads" should begin with the capital "N"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-4877) Add test covers get(key, type) in direct way (via SpringCache)
Vyacheslav Daradur created IGNITE-4877: -- Summary: Add test covers get(key, type) in direct way (via SpringCache) Key: IGNITE-4877 URL: https://issues.apache.org/jira/browse/IGNITE-4877 Project: Ignite Issue Type: Test Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4823) SpringCache#putIfAbsent - wrong implementation
Vyacheslav Daradur created IGNITE-4823:
--
Summary: SpringCache#putIfAbsent - wrong implementation
Key: IGNITE-4823
URL: https://issues.apache.org/jira/browse/IGNITE-4823
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
Current implementation:
{code}
Object old;
if (val == null)
old = cache.withSkipStore().putIfAbsent(key, NULL);
else
old = cache.putIfAbsent(key, val);
return old != null ? fromValue(old) : null;
{code}
cache.putIfAbsent(key, val) - return boolean, not cached value
*Excepted behavior (according to the Spring-docs)*
{code}
Object existingValue = cache.get(key);
if (existingValue == null) {
cache.put(key, value);
return null;
} else {
return existingValue;
}
{code}
1. Need to fix implementation
2. Cover SpringCache class with unit-tests
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-4804) Remove duplicated properties in parent-pom
Vyacheslav Daradur created IGNITE-4804: -- Summary: Remove duplicated properties in parent-pom Key: IGNITE-4804 URL: https://issues.apache.org/jira/browse/IGNITE-4804 Project: Ignite Issue Type: Bug Components: build Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Priority: Minor ignite\parent\pom.xml сontains duplicated properties. In case of their separate change it can result in not expected behavior. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4771) Building error - Apache Ignite 1.9.0 RC1
Vyacheslav Daradur created IGNITE-4771:
--
Summary: Building error - Apache Ignite 1.9.0 RC1
Key: IGNITE-4771
URL: https://issues.apache.org/jira/browse/IGNITE-4771
Project: Ignite
Issue Type: Bug
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
Priority: Blocker
Valentin Kulichenko:
Building with 'mvn clean package -DskipTests' under JDK8 fails with the
error below. JDK7 is fine, though.
{CODE}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 12.626 s
[INFO] Finished at: 2017-03-01T14:05:08-08:00
[INFO] Final Memory: 80M/654M
[INFO]
[ERROR] Failed to execute goal org.apache.maven.plugins:
maven-javadoc-plugin:2.10.1:jar (module-javadoc) on project ignite-tools:
MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - javadoc: error - invalid flag:
--allow-script-in-comments
[ERROR]
[ERROR] Command line was: /Library/Java/JavaVirtualMachines/jdk1.8.0_
92.jdk/Contents/Home/jre/../bin/javadoc @options @packages
[ERROR]
[ERROR] Refer to the generated Javadoc files in
'/Users/vkulichenko/Downloads/apache-ignite-1.9.0-src/modules/tools/target/apidocs'
dir.
[ERROR] -> [Help 1]
{CODE}
dev-list:
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-9-0-RC1-td14985.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-4719) Create documentation of current checks at Ignite-startup
Vyacheslav Daradur created IGNITE-4719: -- Summary: Create documentation of current checks at Ignite-startup Key: IGNITE-4719 URL: https://issues.apache.org/jira/browse/IGNITE-4719 Project: Ignite Issue Type: Task Components: documentation Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4501) Improvement of connection in a cluster of new node
Vyacheslav Daradur created IGNITE-4501:
--
Summary: Improvement of connection in a cluster of new node
Key: IGNITE-4501
URL: https://issues.apache.org/jira/browse/IGNITE-4501
Project: Ignite
Issue Type: Improvement
Reporter: Vyacheslav Daradur
h3. Main description:
Cluster nodes connect a ring.
For example: we have 6 nodes: A, B, C, D, E, F.
They can connect a ring in any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A,
etc.
If some node leaves topology, adjacent nodes must reconnect.
If nodes A, B, C are in same physical place, nodes D, E, F are in other place,
and places lost connect each other, we will have many ways of reconnections.
At best case, if we had a ring: A-B-CxD-E-FxA ('x' means disconnect) -- then we
have only one reconnect (C
will be connected to A or F will be connected to D -- depends on what part of
the cluster was alive.
Also, if we had a not ring: AxFxBxExCxDxA -- then we have a lot of
reconnections (A to B, B to C, C to A -- in general n/2 reconnections, where n
-- number of nodes).
h3. Approach:
It is necessary to develop approach of node insertion to the correct place for
creation of the correct ring-topology.
h3. Solutions:
Main idea is a sorting according to latency.
* group nodes in arcs on an ARC_ID. (manualy?)
* implement NodeComparator (nodes on the same host : nodes on the same subnet :
other nodes). We will use it when we connect a new node.
* [dev list
thread|http://mail-archives.apache.org/mod_mbox/ignite-dev/201612.mbox/%3CCAN+WSNyWYXSXEBpGErVt72zTgi2pTQzUWLv8JY=ke83-5-r...@mail.gmail.com%3E]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
