[jira] [Created] (IGNITE-14317) IgniteCache.removeAsync(key,val) fails inside an optimistic transaction
Denis Garus created IGNITE-14317:
Summary: IgniteCache.removeAsync(key,val) fails inside an
optimistic transaction
Key: IGNITE-14317
URL: https://issues.apache.org/jira/browse/IGNITE-14317
Project: Ignite
Issue Type: Bug
Affects Versions: 2.9.1
Reporter: Denis Garus
[reproducer|https://github.com/apache/ignite/pull/8841/files]
IgniteCache.removeAsync(key,val) fails inside an optimistic tx with the
exception:
{code:java}
[17:39:28] (err) Failed to notify listener:
o.a.i.i.processors.cache.distributed.near.GridNearTxLocal$6...@19c520dbjava.lang.AssertionError[17:39:28]
(err) Failed to notify listener:
o.a.i.i.processors.cache.distributed.near.GridNearTxLocal$6...@19c520dbjava.lang.AssertionError
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$17.apply(GridNearTxLocal.java:2955)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$17.apply(GridNearTxLocal.java:2937)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.processLoaded(GridNearTxLocal.java:3475)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$21.apply(GridNearTxLocal.java:3217)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$21.apply(GridNearTxLocal.java:3212)
at
org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:78)
at
org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:70)
at
org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:30)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:511)
at
org.apache.ignite.internal.processors.cache.GridCacheFutureAdapter.onDone(GridCacheFutureAdapter.java:55)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:490)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.onDone(GridPartitionedSingleGetFuture.java:935)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:467)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setSkipValueResult(GridPartitionedSingleGetFuture.java:759)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.onResult(GridPartitionedSingleGetFuture.java:636)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearSingleGetResponse(GridDhtCacheAdapter.java:368)
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.access$100(GridDhtColocatedCache.java:88)
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache$2.apply(GridDhtColocatedCache.java:133)
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache$2.apply(GridDhtColocatedCache.java:131)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1143)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:592)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:393)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:319)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:309)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1908)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1529)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.execute(GridIoManager.java:1422)
at
org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:55)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:569)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.base/java.lang.Thread.run(Thread.java:834){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14179) The GridDhtTxFinishFuture has the redundant interface declaration 'GridCacheFuture'
Denis Garus created IGNITE-14179: Summary: The GridDhtTxFinishFuture has the redundant interface declaration 'GridCacheFuture' Key: IGNITE-14179 URL: https://issues.apache.org/jira/browse/IGNITE-14179 Project: Ignite Issue Type: Bug Reporter: Denis Garus Remove redundant interface declaration 'GridCacheFuture' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14070) Protecting a snapshot from from unauthorized changes
Denis Garus created IGNITE-14070: Summary: Protecting a snapshot from from unauthorized changes Key: IGNITE-14070 URL: https://issues.apache.org/jira/browse/IGNITE-14070 Project: Ignite Issue Type: New Feature Reporter: Denis Garus Assignee: Denis Garus We have to allow Ignite users to check the integrity of snapshot files before restoring them. This opportunity can be done through the Ignite plugin mechanism. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13652) Wrong GitHub link for Apache Ignite With Spring Data/Example
Denis Garus created IGNITE-13652: Summary: Wrong GitHub link for Apache Ignite With Spring Data/Example Key: IGNITE-13652 URL: https://issues.apache.org/jira/browse/IGNITE-13652 Project: Ignite Issue Type: Bug Components: documentation Affects Versions: 2.9 Reporter: Denis Garus Wrong GihHub link in https://ignite.apache.org/docs/latest/extensions-and-integrations/spring/spring-data#example -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13312) Methods of interface Binarylizable should not get accessing to host resources.
Denis Garus created IGNITE-13312: Summary: Methods of interface Binarylizable should not get accessing to host resources. Key: IGNITE-13312 URL: https://issues.apache.org/jira/browse/IGNITE-13312 Project: Ignite Issue Type: Task Components: security Reporter: Denis Garus Methods of interface Binarylizable should not get accessing to host resources on a remote nodes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13301) IgniteScheduler has to run inside the Ignite Sandbox.
Denis Garus created IGNITE-13301:
Summary: IgniteScheduler has to run inside the Ignite Sandbox.
Key: IGNITE-13301
URL: https://issues.apache.org/jira/browse/IGNITE-13301
Project: Ignite
Issue Type: Task
Components: security
Reporter: Denis Garus
Assignee: Denis Garus
IgniteScheduler has to run inside the Ignite Sandbox on a remote node.
For example:
{code:java}
Ignition.localIgnite().compute().run(() -> {
IgniteScheduler scheduler = Ignition.localIgnite().scheduler();
scheduler.runLocal(AbstractSandboxTest::controlAction).get();
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13261) Using transactions or continuous queries inside the ignite sandbox can throw an AccessControlException
Denis Garus created IGNITE-13261: Summary: Using transactions or continuous queries inside the ignite sandbox can throw an AccessControlException Key: IGNITE-13261 URL: https://issues.apache.org/jira/browse/IGNITE-13261 Project: Ignite Issue Type: Bug Components: security Reporter: Denis Garus Assignee: Denis Garus Any subject should be able to use transactions or continuous queries inside the ignite sandbox without additional permissions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13228) Remote filter of IgniteEvents has to run with appropriate SecurityContext.
Denis Garus created IGNITE-13228: Summary: Remote filter of IgniteEvents has to run with appropriate SecurityContext. Key: IGNITE-13228 URL: https://issues.apache.org/jira/browse/IGNITE-13228 Project: Ignite Issue Type: Improvement Components: security Affects Versions: 2.8.1 Reporter: Denis Garus Assignee: Denis Garus Fix For: 2.9 The remote filter of IgniteEvents has to run on a remote node with the SecurityContext of the initiator node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13113) CacheEvent#subjectId for cache events with types EventType#EVTS_CACHE
Denis Garus created IGNITE-13113: Summary: CacheEvent#subjectId for cache events with types EventType#EVTS_CACHE Key: IGNITE-13113 URL: https://issues.apache.org/jira/browse/IGNITE-13113 Project: Ignite Issue Type: Bug Components: cache, security Affects Versions: 2.8.1 Reporter: Denis Garus Assignee: Denis Garus For cache events with types: EVT_CACHE_ENTRY_CREATED, EVT_CACHE_ENTRY_DESTROYED, EVT_CACHE_OBJECT_PUT, EVT_CACHE_OBJECT_READ, EVT_CACHE_OBJECT_REMOVED, EVT_CACHE_OBJECT_LOCKED, EVT_CACHE_OBJECT_UNLOCKED, EVT_CACHE_OBJECT_EXPIRED field CacheEvent#subjectId should be subject id associated with SecuritySubject that trigged the cache event. Currently, CacheEvent#subjectId for these event types is null or equals subject id associated with the node that sends a change request. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13112) CacheEvent#subjectId is always null for cache events with types EVT_CACHE_STARTED and EVT_CACHE_STOPPED
Denis Garus created IGNITE-13112: Summary: CacheEvent#subjectId is always null for cache events with types EVT_CACHE_STARTED and EVT_CACHE_STOPPED Key: IGNITE-13112 URL: https://issues.apache.org/jira/browse/IGNITE-13112 Project: Ignite Issue Type: Bug Components: cache, security Reporter: Denis Garus CacheEvents with types EVT_CACHE_STARTED and EVT_CACHE_STARTED have fieldCacheEvent#subjectId always null. CacheEvent#subjectId should be subject id associated with SecuritySubject that trigged the cache event. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13010) A local listener for cache events with type EVT_CACHE_STOPPED does not get a cache event from a remote node.
Denis Garus created IGNITE-13010:
Summary: A local listener for cache events with type
EVT_CACHE_STOPPED does not get a cache event from a remote node.
Key: IGNITE-13010
URL: https://issues.apache.org/jira/browse/IGNITE-13010
Project: Ignite
Issue Type: Bug
Affects Versions: 2.8
Reporter: Denis Garus
A local listener for cache events with type EVT_CACHE_STOPPED does not get a
cache event from a remote node.
That occurs due to NPE on a remote node:
{code:java}
[2020-05-14
12:07:25,623][ERROR][sys-#206%security.NpeGridEventConsumeHandlerReproducer2%][GridEventConsumeHandler]
Failed to send event notification to node:
55671ec1-dad9-452b-8ab2-4b7916c0[2020-05-14
12:07:25,623][ERROR][sys-#206%security.NpeGridEventConsumeHandlerReproducer2%][GridEventConsumeHandler]
Failed to send event notification to node:
55671ec1-dad9-452b-8ab2-4b7916c0java.lang.NullPointerException at
org.apache.ignite.internal.GridEventConsumeHandler$2$1.run(GridEventConsumeHandler.java:238)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
{code}
The reproducer:
{code:java}
public class NpeGridEventConsumeHandlerReproducer extends
GridCommonAbstractTest {
private static AtomicInteger rmtCounter = new AtomicInteger();
private static AtomicInteger locCounter = new AtomicInteger();
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
return
super.getConfiguration(igniteInstanceName).setIncludeEventTypes(EVT_CACHE_STOPPED);
}
@Test
public void test() throws Exception {
startGrids(3);
grid(1).createCache(new CacheConfiguration<>("test_cache"));
grid(0).events().remoteListen((uuid, evt) ->{
locCounter.incrementAndGet();
return true;
}, evt->{
rmtCounter.incrementAndGet();
return true;
}, EVT_CACHE_STOPPED);
grid(1).destroyCache("test_cache");
TimeUnit.SECONDS.sleep(10);
assertEquals(rmtCounter.get(), locCounter.get());
}
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12996) Remote listener of IgniteEvents has to run inside the Ignite Sandbox.
Denis Garus created IGNITE-12996: Summary: Remote listener of IgniteEvents has to run inside the Ignite Sandbox. Key: IGNITE-12996 URL: https://issues.apache.org/jira/browse/IGNITE-12996 Project: Ignite Issue Type: Task Components: security Reporter: Denis Garus Remote listener of IgniteEvents has to run on a remote node inside the Ignite Sandbox if it is turned on. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12983) Logging exceptions inside IgniteSecurityProcessor#withContext(java.util.UUID)
Denis Garus created IGNITE-12983: Summary: Logging exceptions inside IgniteSecurityProcessor#withContext(java.util.UUID) Key: IGNITE-12983 URL: https://issues.apache.org/jira/browse/IGNITE-12983 Project: Ignite Issue Type: Improvement Reporter: Denis Garus Assignee: Denis Garus Fix For: 2.9 We should write down to log all exception inside IgniteSecurityProcessor#withContext(java.util.UUID). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12904) ШптшеуЫусгкшен
Denis Garus created IGNITE-12904: Summary: ШптшеуЫусгкшен Key: IGNITE-12904 URL: https://issues.apache.org/jira/browse/IGNITE-12904 Project: Ignite Issue Type: Improvement Reporter: Denis Garus -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12759) Getting a SecurityContext from GridSecurityProcessor
Denis Garus created IGNITE-12759: Summary: Getting a SecurityContext from GridSecurityProcessor Key: IGNITE-12759 URL: https://issues.apache.org/jira/browse/IGNITE-12759 Project: Ignite Issue Type: Improvement Components: security Affects Versions: 2.8 Reporter: Denis Garus Fix For: 2.8.1 1. Extend the _GridSecurityProcessor_ interface by adding _securityContext(UUID subjId)_ method and use this method to get the actual security context. 2. In the case when _GridSecurityProcessor_ cannot get a security context, we should return _the unknown security context_. All operations are forbidden with _the unknown security context_. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12611) EntryProcessorPermissionCheckTest.test: Test looks flaky
Denis Garus created IGNITE-12611: Summary: EntryProcessorPermissionCheckTest.test: Test looks flaky Key: IGNITE-12611 URL: https://issues.apache.org/jira/browse/IGNITE-12611 Project: Ignite Issue Type: Bug Reporter: Denis Garus Assignee: Denis Garus Test looks flaky.Test status change in build without changes: from failed to successful -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12533) Remote security context tests refactoring.
Denis Garus created IGNITE-12533: Summary: Remote security context tests refactoring. Key: IGNITE-12533 URL: https://issues.apache.org/jira/browse/IGNITE-12533 Project: Ignite Issue Type: Improvement Reporter: Denis Garus To make tests more readable and robust, we should use the _AbstractRemoteSecurityContextCheckTest.Verifier#register(String)_ method in all related tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12529) Getting local ignite instance inside ComputeJob#cancel
Denis Garus created IGNITE-12529: Summary: Getting local ignite instance inside ComputeJob#cancel Key: IGNITE-12529 URL: https://issues.apache.org/jira/browse/IGNITE-12529 Project: Ignite Issue Type: Bug Reporter: Denis Garus The Ignition#localIgnite method throws an exception while using inside the ComputeJob#cancel method. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12500) IgniteProxy should be injected into non-system types only.
Denis Garus created IGNITE-12500: Summary: IgniteProxy should be injected into non-system types only. Key: IGNITE-12500 URL: https://issues.apache.org/jira/browse/IGNITE-12500 Project: Ignite Issue Type: Improvement Reporter: Denis Garus When the Ignite Sandbox is enabled, the GridResourceProxiedIgniteInjector should inject an IgniteProxy into non-system types only. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12443) Document the Ignite Sandbox
Denis Garus created IGNITE-12443: Summary: Document the Ignite Sandbox Key: IGNITE-12443 URL: https://issues.apache.org/jira/browse/IGNITE-12443 Project: Ignite Issue Type: Task Components: documentation Reporter: Denis Garus Document how to configure and use the Ignite Sandbox. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12345) Remote listener of IgniteMessaging has to run inside the Ignite Sandbox.
Denis Garus created IGNITE-12345: Summary: Remote listener of IgniteMessaging has to run inside the Ignite Sandbox. Key: IGNITE-12345 URL: https://issues.apache.org/jira/browse/IGNITE-12345 Project: Ignite Issue Type: Task Reporter: Denis Garus Remote listener of IgniteMessaging has to run on a remote node inside the Ignite Sandbox if it is turned on. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12344) Remote listener of IgniteMessaging has to run with appropriate SecurityContext.
Denis Garus created IGNITE-12344: Summary: Remote listener of IgniteMessaging has to run with appropriate SecurityContext. Key: IGNITE-12344 URL: https://issues.apache.org/jira/browse/IGNITE-12344 Project: Ignite Issue Type: Bug Reporter: Denis Garus Remote listener of IgniteMessaging has to run on a remote node with the SecurityContext of the initiator node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12343) Remote filter and transformer of ContinuousQueries have to run inside the Ignite Sandbox
Denis Garus created IGNITE-12343: Summary: Remote filter and transformer of ContinuousQueries have to run inside the Ignite Sandbox Key: IGNITE-12343 URL: https://issues.apache.org/jira/browse/IGNITE-12343 Project: Ignite Issue Type: Task Reporter: Denis Garus Remote filter and transformer of ContinuousQueries have to run on a remote node inside the Ignite Sandbox if it is turned on. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12342) Continuous Queries: Remote filter and transformer have to run with appropriate SecurityContext.
Denis Garus created IGNITE-12342: Summary: Continuous Queries: Remote filter and transformer have to run with appropriate SecurityContext. Key: IGNITE-12342 URL: https://issues.apache.org/jira/browse/IGNITE-12342 Project: Ignite Issue Type: Bug Reporter: Denis Garus Remote filter and transformer of ContinuousQueries have to run on a remote node with the SecurityContext of the initiator node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12341) Sandbox: Adding tests for ComputeJob#cancel
Denis Garus created IGNITE-12341: Summary: Sandbox: Adding tests for ComputeJob#cancel Key: IGNITE-12341 URL: https://issues.apache.org/jira/browse/IGNITE-12341 Project: Ignite Issue Type: Task Reporter: Denis Garus We have to have tests that check the ComputeJob#cancel method is executed inside the Ignite Sandbox on a remote node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12300) ComputeJob#cancel executes with wrong SecurityContext
Denis Garus created IGNITE-12300: Summary: ComputeJob#cancel executes with wrong SecurityContext Key: IGNITE-12300 URL: https://issues.apache.org/jira/browse/IGNITE-12300 Project: Ignite Issue Type: Bug Reporter: Denis Garus ComputeJob#cancel executes with context of current node rather then should be executed with context of node that initiate ComputeJob. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12283) Access restriction to IgniteKernal
Denis Garus created IGNITE-12283: Summary: Access restriction to IgniteKernal Key: IGNITE-12283 URL: https://issues.apache.org/jira/browse/IGNITE-12283 Project: Ignite Issue Type: Task Reporter: Denis Garus IgniteKernal allows a user-defined code to get access to the internal features of Ignite. That behavior leads to security lack. We must encapsulate _IgniteKernal_ to restrict access to it from user-defined code. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12282) Access restriction to the internal package of Ignite
Denis Garus created IGNITE-12282:
Summary: Access restriction to the internal package of Ignite
Key: IGNITE-12282
URL: https://issues.apache.org/jira/browse/IGNITE-12282
Project: Ignite
Issue Type: Task
Reporter: Denis Garus
A user-defined code shouldn't have access to _org.apache.ignite.internal_.*
that is the internal package of Ignite.
To restrict a user-defined code, we need to set the package name to the
_package.access_ security property.
To grand access to a package, we have to use _accessClassInPackage.\{package
name}_ runtime permission.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12055) SecurityTestSuite as a separate test suite at TC
Denis Garus created IGNITE-12055: Summary: SecurityTestSuite as a separate test suite at TC Key: IGNITE-12055 URL: https://issues.apache.org/jira/browse/IGNITE-12055 Project: Ignite Issue Type: Task Components: security Reporter: Denis Garus Need exclude SecurityTestSuite from IgniteBasicTestSuite (Basic 1). Create suite Security with SecurityTestSuite at TC. Config is the same as Basic 1 except additional Maven command line parameters that should be: -P all-java,all-other,scala-2.10,tensorflow,scala,scala-test,surefire-fork-count-1 -pl %MAVEN_MODULES% -am -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dtest=%TEST_SUITE% -Dmaven.javadoc.skip=true %MAVEN_OPTS% Include SecurityTestSuite to Run::All, Run::All (Nightly), Run::Basic Tests at TC. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-11718) Authorizing of SERVICE_INVOKE permission
Denis Garus created IGNITE-11718: Summary: Authorizing of SERVICE_INVOKE permission Key: IGNITE-11718 URL: https://issues.apache.org/jira/browse/IGNITE-11718 Project: Ignite Issue Type: Improvement Affects Versions: 2.7 Reporter: Denis Garus We authorize SERVICE_INVOKE only once on creation of service instance however, we have to authorize SERVICE_INVOKE whenever an operation is invoked on the service instance. If we change some permissions in runtime right after a client got instance, it doesn't see those changes. The scenario: * Client A creates a service instance B. * Administrator forbids invocation of service B to client A. * As long as client A keeps service instance, it can invoke any methods of service B. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9955) Fail of cache creation on cluster activation
Denis Garus created IGNITE-9955: --- Summary: Fail of cache creation on cluster activation Key: IGNITE-9955 URL: https://issues.apache.org/jira/browse/IGNITE-9955 Project: Ignite Issue Type: Bug Reporter: Denis Garus Attachments: CacheStartFailOnClusterActivate.java If an error has occurred during cluster activation (processing of ChangeGlobalStateMessage) then no caches will be created, including system cache. The reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9073) Module ignite-kubernetes should use jackson2 dependency rater then jackson1
Denis Garus created IGNITE-9073: --- Summary: Module ignite-kubernetes should use jackson2 dependency rater then jackson1 Key: IGNITE-9073 URL: https://issues.apache.org/jira/browse/IGNITE-9073 Project: Ignite Issue Type: Improvement Reporter: Denis Garus Fix For: 2.7 Module ignite-kubernetes should use jackson2 dependency rater then jackson1. It is required to run RunAll to check all tests passed, check full build locally using build.sh. Probably it is required to run release step to make sure release candidate can be prepared -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9017) .NET: Clear cache statistics
Denis Garus created IGNITE-9017: --- Summary: .NET: Clear cache statistics Key: IGNITE-9017 URL: https://issues.apache.org/jira/browse/IGNITE-9017 Project: Ignite Issue Type: Improvement Components: platforms Affects Versions: 2.7 Reporter: Denis Garus ICache.ClearStatistics, ICluster.ClearStatistics. See IGNITE-8705 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8992) Wrong log when LongJVMPauseDetector stops the worker thread
Denis Garus created IGNITE-8992: --- Summary: Wrong log when LongJVMPauseDetector stops the worker thread Key: IGNITE-8992 URL: https://issues.apache.org/jira/browse/IGNITE-8992 Project: Ignite Issue Type: Bug Reporter: Denis Garus When LongJVMPauseDetector stops the worker thread, a log will contain follow error: [2018-07-12 12:57:28,332][ERROR][jvm-pause-detector-worker][CacheMetricsEnableRuntimeTest1] jvm-pause-detector-worker has been interrupted java.lang.InterruptedException: sleep interrupted at java.lang.Thread.sleep(Native Method) at org.apache.ignite.internal.LongJVMPauseDetector$1.run(LongJVMPauseDetector.java:97) The error must be only if worker thread stopped unintentionally. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8614) The atomic cache in inconsistent state
Denis Garus created IGNITE-8614: --- Summary: The atomic cache in inconsistent state Key: IGNITE-8614 URL: https://issues.apache.org/jira/browse/IGNITE-8614 Project: Ignite Issue Type: Task Affects Versions: 2.4 Reporter: Denis Garus Assignee: Denis Garus Fix For: 2.6 Attachments: ReproducerAtomicCacheInconsistentStateTest.java There is a situation when the atomic cache becomes inconsistent. There are two nodes: Node_1 with primary partition and Node_2 with backup partition. 1. Node_3 is started; 2. Before a rebalance of the partition from Node_1 to Node_3 is occurred new value is put to the partition on Node_1; 3. Node_1 creates a future for a propagating new value to Node_2 and Node_3; 4. Node_3 gets new value from Node_1 in the process a rebalance; 5. Node_1 is stopped; 6. The future from step 3 is failed because of step 5. Now we have Node_3 with the new value and Node_2 with old value. We need to find out the way to fix this inconsistent state and implement one. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
