[jira] [Updated] (IGNITE-20016) Introduce bulk operation to catalog
[ https://issues.apache.org/jira/browse/IGNITE-20016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-20016: -- Fix Version/s: 3.0.0-beta2 > Introduce bulk operation to catalog > --- > > Key: IGNITE-20016 > URL: https://issues.apache.org/jira/browse/IGNITE-20016 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > To optimize registration of system views to catalog, the latter should > support bulk update. > Let's extend API of catalogManager with method, accepting list of parameters, > and applying all changes as a single update to the catalog -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20097) WAL writes to an archived segment after node restart
[
https://issues.apache.org/jira/browse/IGNITE-20097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761073#comment-17761073
]
Ignite TC Bot commented on IGNITE-20097:
{panel:title=Branch: [pull/10887/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10887/head] Base: [master] : New Tests
(12)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 2{color} [[tests
6|https://ci2.ignite.apache.org/viewLog.html?buildId=7323512]]
* {color:#013220}IgnitePdsTestSuite2:
RestartWithWalForceArchiveTimeoutTest.testRestartAfterArchive[walMode=FSYNC] -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
RestartWithWalForceArchiveTimeoutTest.testRestartAfterArchive[walMode=LOG_ONLY]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
RestartWithWalForceArchiveTimeoutTest.testRestartAfterArchive[walMode=BACKGROUND]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
WalRolloverOnStopTest.testWallRollover[walMode=BACKGROUND] - PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
WalRolloverOnStopTest.testWallRollover[walMode=LOG_ONLY] - PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
WalRolloverOnStopTest.testWallRollover[walMode=FSYNC] - PASSED{color}
{color:#8b}Disk Page Compressions 2{color} [[tests
6|https://ci2.ignite.apache.org/viewLog.html?buildId=7323556]]
* {color:#013220}IgnitePdsCompressionTestSuite2:
RestartWithWalForceArchiveTimeoutTest.testRestartAfterArchive[walMode=FSYNC] -
PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite2:
RestartWithWalForceArchiveTimeoutTest.testRestartAfterArchive[walMode=LOG_ONLY]
- PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite2:
RestartWithWalForceArchiveTimeoutTest.testRestartAfterArchive[walMode=BACKGROUND]
- PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite2:
WalRolloverOnStopTest.testWallRollover[walMode=LOG_ONLY] - PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite2:
WalRolloverOnStopTest.testWallRollover[walMode=FSYNC] - PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite2:
WalRolloverOnStopTest.testWallRollover[walMode=BACKGROUND] - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7323558&buildTypeId=IgniteTests24Java8_RunAll]
> WAL writes to an archived segment after node restart
>
>
> Key: IGNITE-20097
> URL: https://issues.apache.org/jira/browse/IGNITE-20097
> Project: Ignite
> Issue Type: Bug
>Reporter: Nikita Amelchev
>Assignee: Nikita Amelchev
>Priority: Critical
> Labels: ise
> Fix For: 2.16
>
> Attachments: NodeRestartTest.java
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> WAL writes to an archived segment after node restart if segment was archiver
> right before node stop (no records were written to the next segment). User
> data may be lost. Reproducer attached.
> {noformat}
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.StorageException:
> Failed to read checkpoint record from WAL, persistence consistency cannot be
> guaranteed. Make sure configuration points to correct WAL folders and WAL
> folder is properly mounted [ptr=WALPointer [idx=0, fileOff=259442,
> len=21409], walPath=db/wal, walArchive=db/wal/archive]]]
> org.apache.ignite.internal.processors.cache.persistence.StorageException:
> Failed to read checkpoint record from WAL, persistence consistency cannot be
> guaranteed. Make sure configuration points to correct WAL folders and WAL
> folder is properly mounted [ptr=WALPointer [idx=0, fileOff=259442,
> len=21409], walPath=db/wal, walArchive=db/wal/archive]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.performBinaryMemoryRestore(GridCacheDatabaseSharedManager.java:2134)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:855)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:3062)
> [classes/:?]
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1125)
> [classes/:?]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1725)
> [classes/:?]
[jira] [Updated] (IGNITE-20097) WAL writes to an archived segment after node restart
[
https://issues.apache.org/jira/browse/IGNITE-20097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikita Amelchev updated IGNITE-20097:
-
Release Note: Fixed WAL logging to an archived segment after node restart
> WAL writes to an archived segment after node restart
>
>
> Key: IGNITE-20097
> URL: https://issues.apache.org/jira/browse/IGNITE-20097
> Project: Ignite
> Issue Type: Bug
>Reporter: Nikita Amelchev
>Assignee: Nikita Amelchev
>Priority: Critical
> Labels: ise
> Fix For: 2.16
>
> Attachments: NodeRestartTest.java
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> WAL writes to an archived segment after node restart if segment was archiver
> right before node stop (no records were written to the next segment). User
> data may be lost. Reproducer attached.
> {noformat}
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.StorageException:
> Failed to read checkpoint record from WAL, persistence consistency cannot be
> guaranteed. Make sure configuration points to correct WAL folders and WAL
> folder is properly mounted [ptr=WALPointer [idx=0, fileOff=259442,
> len=21409], walPath=db/wal, walArchive=db/wal/archive]]]
> org.apache.ignite.internal.processors.cache.persistence.StorageException:
> Failed to read checkpoint record from WAL, persistence consistency cannot be
> guaranteed. Make sure configuration points to correct WAL folders and WAL
> folder is properly mounted [ptr=WALPointer [idx=0, fileOff=259442,
> len=21409], walPath=db/wal, walArchive=db/wal/archive]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.performBinaryMemoryRestore(GridCacheDatabaseSharedManager.java:2134)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:855)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:3062)
> [classes/:?]
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1125)
> [classes/:?]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1725)
> [classes/:?]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
> [classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1089)
> [classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:599)
> [classes/:?]
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:1321)
> [test-classes/:?]
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:1238)
> [test-classes/:?]
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:1214)
> [test-classes/:?]
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:1045)
> [test-classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.NodeRestartTest.test(NodeRestartTest.java:75)
> [test-classes/:?]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.8.0_352]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_352]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_352]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_352]
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> [junit-4.12.jar:4.12]
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> [junit-4.12.jar:4.12]
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> [junit-4.12.jar:4.12]
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> [junit-4.12.jar:4.12]
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2504)
> [test-classes/:?]
> at java.lang.Thread.run(Thread.java:750) [?:1.8.0_352]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20323) SQL hint for join type.
[ https://issues.apache.org/jira/browse/IGNITE-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-20323: -- Labels: ise (was: ) > SQL hint for join type. > --- > > Key: IGNITE-20323 > URL: https://issues.apache.org/jira/browse/IGNITE-20323 > Project: Ignite > Issue Type: Task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > Labels: ise > > Additionally to the hint for locked join order, we might have a hint for > choosing join type. Like 'USE_NL' or 'USE_MERGE' OracleDB hint. To implement, > we might base all join rules on the same abstract join rule aware of known > join types and join type hints. There, we could process join type hints > enabling or disabling current join type converter rule. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20323) SQL hint for join type.
Vladimir Steshin created IGNITE-20323: - Summary: SQL hint for join type. Key: IGNITE-20323 URL: https://issues.apache.org/jira/browse/IGNITE-20323 Project: Ignite Issue Type: Task Reporter: Vladimir Steshin Assignee: Vladimir Steshin Additionally to the hint for locked join order, we might have a hint for choosing join type. Like 'USE_NL' or 'USE_MERGE' OracleDB hint. To implement, we might base all join rules on the same abstract join rule aware of known join types and join type hints. There, we could process join type hints enabling or disabling current join type converter rule. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20322) Ability to pass an observable time stamp to an implicit transaction
Vladislav Pyatkov created IGNITE-20322: -- Summary: Ability to pass an observable time stamp to an implicit transaction Key: IGNITE-20322 URL: https://issues.apache.org/jira/browse/IGNITE-20322 Project: Ignite Issue Type: Improvement Reporter: Vladislav Pyatkov *Motivation* An implicit transaction is a transaction that is started by the table API when a single operation is executed and committed when the operation is finished. Currently, internal transactions use the only observable timestamp. The timestamp is reserved for embedded transactions only. That leads to incorrect calculations of the observable timestamp (the timestamp is updated more frequently than required). *Definition of done* Implicit transactions should start with a specific observable timestamp (for the embedded server or for each client). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20158) CLI: cluster/node config update is not user friendly
[
https://issues.apache.org/jira/browse/IGNITE-20158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin reassigned IGNITE-20158:
--
Assignee: Mikhail Pochatkin
> CLI: cluster/node config update is not user friendly
>
>
> Key: IGNITE-20158
> URL: https://issues.apache.org/jira/browse/IGNITE-20158
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Assignee: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
>
> The configuration update process can be painful because of the way CLI parses
> the command line. For example,
> {code:java}
> [defaultNode]> cluster config update -u http://localhost:10300
> "{aipersist.regions: [{name: persistent_region,size: 2560
> 0}],aimem.regions: [{name: btree_volatile_region,maxSize: 25600}]}"
> IGN-CMN-65535 Trace ID: 5430a4a7-b24d-4861-89aa-fdb84a17b199
> com.typesafe.config.ConfigException$Parse: String: 1: Key
> '"{aipersist.regions: [{name: persistent_region,size:
> 25600}],aimem.regions: [{name: btree_volatile_region,maxSize:
> 25600}]}"' may not be followed by token: end of file
> {code}
> There is no way to understand what is going wrong.
> I suggest improving the error text and showing the correct command example.
> And we have to investigate the root cause of the issue and create a follow-up
> ticket to fix the way CLI parses the command line. I expect the example
> command to be valid.
> We have to provide user-friendly response in any case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-18784) Repair disable test on Windows with reason IGNITE-17601
[ https://issues.apache.org/jira/browse/IGNITE-18784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-18784: -- Assignee: Mikhail Pochatkin > Repair disable test on Windows with reason IGNITE-17601 > --- > > Key: IGNITE-18784 > URL: https://issues.apache.org/jira/browse/IGNITE-18784 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > These tests are disable with reason IGNITE-17601: > * org.apache.ignite.raft.jraft.core.ItNodeTest#testSetPeer2 > * > org.apache.ignite.internal.cluster.management.raft.RocksDbClusterStateStorageManagerTest > * org.apache.ignite.internal.sql.engine.exec.rel.ExecutionTest > * org.apache.ignite.internal.sql.engine.planner.PlannerTest > Need to repair it and enable on Windows -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-19889) Implement observable timestamp on server
[ https://issues.apache.org/jira/browse/IGNITE-19889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760941#comment-17760941 ] Vladislav Pyatkov commented on IGNITE-19889: Merged d2c56b072a54eca7608c49ddbb14a85c0cacdaec > Implement observable timestamp on server > > > Key: IGNITE-19889 > URL: https://issues.apache.org/jira/browse/IGNITE-19889 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > Time Spent: 1h 20m > Remaining Estimate: 0h > > *Motivation* > Client timestamp is used to determine a read timestamp for RO transaction on > client-side (IGNITE-19888). For consistency behavior, need to implement a > similar timestamp on server. > *Implementation note* > The last server observable timestamp should update at least when the > transaction commuted. > Any RO transaction should use the timestamp: for SQL (IGNITE-19898) and > through key-value API (IGNITE-19887) > *Definition of done* > All serve-side created RO transactions should execute in past with timestamp > has been determining by last observation time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-19889) Implement observable timestamp on server
[ https://issues.apache.org/jira/browse/IGNITE-19889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760940#comment-17760940 ] Denis Chudov commented on IGNITE-19889: --- [~v.pyatkov] LGTM. > Implement observable timestamp on server > > > Key: IGNITE-19889 > URL: https://issues.apache.org/jira/browse/IGNITE-19889 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > Time Spent: 1h 10m > Remaining Estimate: 0h > > *Motivation* > Client timestamp is used to determine a read timestamp for RO transaction on > client-side (IGNITE-19888). For consistency behavior, need to implement a > similar timestamp on server. > *Implementation note* > The last server observable timestamp should update at least when the > transaction commuted. > Any RO transaction should use the timestamp: for SQL (IGNITE-19898) and > through key-value API (IGNITE-19887) > *Definition of done* > All serve-side created RO transactions should execute in past with timestamp > has been determining by last observation time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20307) Move handler of DropTable command from CatalogManager to command itself
[ https://issues.apache.org/jira/browse/IGNITE-20307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-20307: -- Fix Version/s: 3.0.0-beta2 > Move handler of DropTable command from CatalogManager to command itself > --- > > Key: IGNITE-20307 > URL: https://issues.apache.org/jira/browse/IGNITE-20307 > Project: Ignite > Issue Type: Improvement >Reporter: Konstantin Orlov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > As described in IGNITE-20284, we need to restructure code to improve code > locality and avoid conflict when introducing new commands in future. > Under this ticket let's address drop table command. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20288) .NET: Thin 3.0: TestDroppedConnectionsAreRestoredInBackground is flaky
[
https://issues.apache.org/jira/browse/IGNITE-20288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-20288:
Summary: .NET: Thin 3.0: TestDroppedConnectionsAreRestoredInBackground is
flaky (was: TestDroppedConnectionsAreRestoredInBackground is flaky)
> .NET: Thin 3.0: TestDroppedConnectionsAreRestoredInBackground is flaky
> --
>
> Key: IGNITE-20288
> URL: https://issues.apache.org/jira/browse/IGNITE-20288
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> 3 of 1000 failed
> https://ci.ignite.apache.org/test/3972078589555679559?currentProjectId=ApacheIgnite3xGradle_Test&expandTestHistoryChartSection=true&branch=
> {code}
> Condition not reached after 00:00:04.5004651
>at Apache.Ignite.Tests.TestUtils.WaitForConditionAsync(Func`1 condition,
> Int32 timeoutMs, Func`1 messageFactory) in
> /opt/buildagent/work/b8d4df1365f1f1e5/modules/platforms/dotnet/Apache.Ignite.Tests/TestUtils.cs:line
> 68
>at Apache.Ignite.Tests.TestUtils.WaitForCondition(Func`1 condition, Int32
> timeoutMs, Func`1 messageFactory) in
> /opt/buildagent/work/b8d4df1365f1f1e5/modules/platforms/dotnet/Apache.Ignite.Tests/TestUtils.cs:line
> 37
>at
> Apache.Ignite.Tests.ReconnectTests.TestDroppedConnectionsAreRestoredInBackground()
> in
> /opt/buildagent/work/b8d4df1365f1f1e5/modules/platforms/dotnet/Apache.Ignite.Tests/ReconnectTests.cs:line
> 95
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20288) .NET: Thin 3.0: TestDroppedConnectionsAreRestoredInBackground is flaky
[
https://issues.apache.org/jira/browse/IGNITE-20288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-20288:
Ignite Flags: (was: Docs Required,Release Notes Required)
> .NET: Thin 3.0: TestDroppedConnectionsAreRestoredInBackground is flaky
> --
>
> Key: IGNITE-20288
> URL: https://issues.apache.org/jira/browse/IGNITE-20288
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> 3 of 1000 failed
> https://ci.ignite.apache.org/test/3972078589555679559?currentProjectId=ApacheIgnite3xGradle_Test&expandTestHistoryChartSection=true&branch=
> {code}
> Condition not reached after 00:00:04.5004651
>at Apache.Ignite.Tests.TestUtils.WaitForConditionAsync(Func`1 condition,
> Int32 timeoutMs, Func`1 messageFactory) in
> /opt/buildagent/work/b8d4df1365f1f1e5/modules/platforms/dotnet/Apache.Ignite.Tests/TestUtils.cs:line
> 68
>at Apache.Ignite.Tests.TestUtils.WaitForCondition(Func`1 condition, Int32
> timeoutMs, Func`1 messageFactory) in
> /opt/buildagent/work/b8d4df1365f1f1e5/modules/platforms/dotnet/Apache.Ignite.Tests/TestUtils.cs:line
> 37
>at
> Apache.Ignite.Tests.ReconnectTests.TestDroppedConnectionsAreRestoredInBackground()
> in
> /opt/buildagent/work/b8d4df1365f1f1e5/modules/platforms/dotnet/Apache.Ignite.Tests/ReconnectTests.cs:line
> 95
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20275) AssertionError in ClientInboundMessageHandler ctor - race condition
[
https://issues.apache.org/jira/browse/IGNITE-20275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760895#comment-17760895
]
Pavel Tupitsyn commented on IGNITE-20275:
-
Merged to main: f7b464cef7c6df2c97f5557ea32dd07fe5abf869
> AssertionError in ClientInboundMessageHandler ctor - race condition
> ---
>
> Key: IGNITE-20275
> URL: https://issues.apache.org/jira/browse/IGNITE-20275
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code}
> [2023-08-24T06:52:18,812][WARN
> ][TestServer--srv-worker-1][ChannelInitializer] Failed to initialize a
> channel. Closing: [id: 0x252ff875, L:/127.0.0.1:10903 - R:/127.0.0.1:52514]
> java.lang.AssertionError: null
> at
> org.apache.ignite.client.handler.ClientInboundMessageHandler.(ClientInboundMessageHandler.java:215)
> ~[ignite-client-handler-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.client.handler.ClientHandlerModule.createInboundMessageHandler(ClientHandlerModule.java:291)
> ~[ignite-client-handler-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.client.handler.ClientHandlerModule$1.initChannel(ClientHandlerModule.java:254)
> ~[ignite-client-handler-3.0.0-SNAPSHOT.jar:?]
> at
> io.netty.channel.ChannelInitializer.initChannel(ChannelInitializer.java:129)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.ChannelInitializer.handlerAdded(ChannelInitializer.java:112)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.callHandlerAdded(AbstractChannelHandlerContext.java:1114)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.DefaultChannelPipeline.callHandlerAdded0(DefaultChannelPipeline.java:609)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.DefaultChannelPipeline.access$100(DefaultChannelPipeline.java:46)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.DefaultChannelPipeline$PendingHandlerAddedTask.execute(DefaultChannelPipeline.java:1463)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.DefaultChannelPipeline.callHandlerAddedForAllHandlers(DefaultChannelPipeline.java:1115)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.DefaultChannelPipeline.invokeHandlerAddedIfNeeded(DefaultChannelPipeline.java:650)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.register0(AbstractChannel.java:514)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.access$200(AbstractChannel.java:429)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe$1.run(AbstractChannel.java:486)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174)
> ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167)
> ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
> ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
> ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
> at java.lang.Thread.run(Thread.java:834) ~[?:?]
> {code}
> Looks like a race condition in *ClientHandlerModule* between:
> * clusterId = clusterIdSupplier.get().join();
> * createInboundMessageHandler (which passes clusterId to
> ClientInboundMessageHandler)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20275) AssertionError in ClientInboundMessageHandler ctor - race condition
[
https://issues.apache.org/jira/browse/IGNITE-20275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760894#comment-17760894
]
Igor Sapego commented on IGNITE-20275:
--
Looks good to me
> AssertionError in ClientInboundMessageHandler ctor - race condition
> ---
>
> Key: IGNITE-20275
> URL: https://issues.apache.org/jira/browse/IGNITE-20275
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> [2023-08-24T06:52:18,812][WARN
> ][TestServer--srv-worker-1][ChannelInitializer] Failed to initialize a
> channel. Closing: [id: 0x252ff875, L:/127.0.0.1:10903 - R:/127.0.0.1:52514]
> java.lang.AssertionError: null
> at
> org.apache.ignite.client.handler.ClientInboundMessageHandler.(ClientInboundMessageHandler.java:215)
> ~[ignite-client-handler-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.client.handler.ClientHandlerModule.createInboundMessageHandler(ClientHandlerModule.java:291)
> ~[ignite-client-handler-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.client.handler.ClientHandlerModule$1.initChannel(ClientHandlerModule.java:254)
> ~[ignite-client-handler-3.0.0-SNAPSHOT.jar:?]
> at
> io.netty.channel.ChannelInitializer.initChannel(ChannelInitializer.java:129)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.ChannelInitializer.handlerAdded(ChannelInitializer.java:112)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.callHandlerAdded(AbstractChannelHandlerContext.java:1114)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.DefaultChannelPipeline.callHandlerAdded0(DefaultChannelPipeline.java:609)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.DefaultChannelPipeline.access$100(DefaultChannelPipeline.java:46)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.DefaultChannelPipeline$PendingHandlerAddedTask.execute(DefaultChannelPipeline.java:1463)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.DefaultChannelPipeline.callHandlerAddedForAllHandlers(DefaultChannelPipeline.java:1115)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.DefaultChannelPipeline.invokeHandlerAddedIfNeeded(DefaultChannelPipeline.java:650)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.register0(AbstractChannel.java:514)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.access$200(AbstractChannel.java:429)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe$1.run(AbstractChannel.java:486)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174)
> ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167)
> ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
> ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
> ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
> ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
> at java.lang.Thread.run(Thread.java:834) ~[?:?]
> {code}
> Looks like a race condition in *ClientHandlerModule* between:
> * clusterId = clusterIdSupplier.get().join();
> * createInboundMessageHandler (which passes clusterId to
> ClientInboundMessageHandler)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19806) Port new log storage from jraft
[ https://issues.apache.org/jira/browse/IGNITE-19806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-19806: --- Labels: ignite-3 ignite3_performance (was: ignite-3) > Port new log storage from jraft > --- > > Key: IGNITE-19806 > URL: https://issues.apache.org/jira/browse/IGNITE-19806 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3, ignite3_performance > Time Spent: 0.5h > Remaining Estimate: 0h > > [https://github.com/sofastack/sofa-jraft/commit/30499b948ed60211a508199a220be173e7ef2be5] > First of all, we need to port it and run benchmarks. After that we should > adapt it to our multi-group approach and benchmark it once again. > Another possibility is "enabling" batch log writes first, to be more fair. > UPDATE > There's no point in migrating hybrid storage. Ignite is not yet released, and > if we need it in the future, we will port it separately. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20321) Fix compilation error in ErrorGroups.
[ https://issues.apache.org/jira/browse/IGNITE-20321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-20321: Ignite Flags: (was: Docs Required,Release Notes Required) > Fix compilation error in ErrorGroups. > - > > Key: IGNITE-20321 > URL: https://issues.apache.org/jira/browse/IGNITE-20321 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Maksim Zhuravkov >Assignee: Maksim Zhuravkov >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20321) Fix compilation error in ErrorGroups.
[ https://issues.apache.org/jira/browse/IGNITE-20321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky reassigned IGNITE-20321: --- Assignee: Maksim Zhuravkov > Fix compilation error in ErrorGroups. > - > > Key: IGNITE-20321 > URL: https://issues.apache.org/jira/browse/IGNITE-20321 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Maksim Zhuravkov >Assignee: Maksim Zhuravkov >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20303) "Raft group on the node is already started" exception when pending and planned assignment changed faster then rebalance
[
https://issues.apache.org/jira/browse/IGNITE-20303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Uttsel updated IGNITE-20303:
---
Reviewer: Kirill Gusakov
> "Raft group on the node is already started" exception when pending and
> planned assignment changed faster then rebalance
> ---
>
> Key: IGNITE-20303
> URL: https://issues.apache.org/jira/browse/IGNITE-20303
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Uttsel
>Assignee: Sergey Uttsel
>Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If many changes of assignment are happened quickly then rebalance does not
> have time to be completed for each change. In this case exception is thrown:
> {code:java}
> 2023-08-24T16:58:51,328][ERROR][%irdt_ttqr_2%tableManager-io-10][WatchProcessor]
> Error occurred when processing a watch event
> org.apache.ignite.lang.IgniteInternalException: Raft group on the node is
> already started [nodeId=RaftNodeId [groupId=1_part_0, peer=Peer
> [consistentId=irdt_ttqr_2, idx=0]]]
> at
> org.apache.ignite.internal.raft.Loza.startRaftGroupNodeInternal(Loza.java:342)
> ~[main/:?]
> at
> org.apache.ignite.internal.raft.Loza.startRaftGroupNode(Loza.java:230)
> ~[main/:?]
> at
> org.apache.ignite.internal.raft.Loza.startRaftGroupNode(Loza.java:203)
> ~[main/:?]
> at
> org.apache.ignite.internal.table.distributed.TableManager.startPartitionRaftGroupNode(TableManager.java:2361)
> ~[main/:?]
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$handleChangePendingAssignmentEvent$98(TableManager.java:2261)
> ~[main/:?]
> at
> org.apache.ignite.internal.util.IgniteUtils.inBusyLock(IgniteUtils.java:922)
> ~[main/:?]
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$handleChangePendingAssignmentEvent$99(TableManager.java:2259)
> ~[main/:?]
> at
> java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736)
> ~[?:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> ~[?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> ~[?:?]
> at java.lang.Thread.run(Thread.java:834) ~[?:?]
> {code}
> The reproducer based on ItRebalanceDistributedTest#testThreeQueuedRebalances.
> See exception in the test log:
> {code:java}
> @Test
> void testThreeQueuedRebalances() throws Exception {
> Node node = getNode(0);
> createZone(node, ZONE_NAME, 1, 1);
> createTable(node, ZONE_NAME, TABLE_NAME);
> assertTrue(waitForCondition(() -> getPartitionClusterNodes(node,
> 0).size() == 1, AWAIT_TIMEOUT_MILLIS));
> alterZone(node, ZONE_NAME, 2);
> alterZone(node, ZONE_NAME, 3);
> alterZone(node, ZONE_NAME, 2);
> alterZone(node, ZONE_NAME, 3);
> alterZone(node, ZONE_NAME, 2);
> alterZone(node, ZONE_NAME, 3);
> alterZone(node, ZONE_NAME, 2);
> alterZone(node, ZONE_NAME, 3);
> alterZone(node, ZONE_NAME, 2);
> alterZone(node, ZONE_NAME, 3);
> alterZone(node, ZONE_NAME, 2);
> waitPartitionAssignmentsSyncedToExpected(0, 2);
> checkPartitionNodes(0, 2);
> }
> {code}
> We can fix it by a check if the raft node and the Replica are created before
> startPartitionRaftGroupNode and startReplicaWithNewListener in
> TableManager#handleChangePendingAssignmentEvent.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20321) Fix compilation error in ErrorGroups.
Maksim Zhuravkov created IGNITE-20321: - Summary: Fix compilation error in ErrorGroups. Key: IGNITE-20321 URL: https://issues.apache.org/jira/browse/IGNITE-20321 Project: Ignite Issue Type: Task Components: sql Reporter: Maksim Zhuravkov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20070) Ignite Docs: Remove docs related to DataRegionMetrics and so on.
[ https://issues.apache.org/jira/browse/IGNITE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760853#comment-17760853 ] Igor Gusev commented on IGNITE-20070: - Looks good, thanks! > Ignite Docs: Remove docs related to DataRegionMetrics and so on. > > > Key: IGNITE-20070 > URL: https://issues.apache.org/jira/browse/IGNITE-20070 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.15 >Reporter: YuJue Li >Assignee: YuJue Li >Priority: Trivial > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-19568) Ignite Docs: change {nodeId} to {consistentId} in the snapshot docs
[
https://issues.apache.org/jira/browse/IGNITE-19568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760851#comment-17760851
]
Igor Gusev commented on IGNITE-19568:
-
Looks good, thanks!
> Ignite Docs: change {nodeId} to {consistentId} in the snapshot docs
> ---
>
> Key: IGNITE-19568
> URL: https://issues.apache.org/jira/browse/IGNITE-19568
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.15
>Reporter: YuJue Li
>Assignee: YuJue Li
>Priority: Minor
> Fix For: 2.16
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Ignite Docs: change \{nodeId} to \{consistentId} in the snapshot docs
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20320) Avoid sharing HybridClock between nodes in tests
Andrey Mashenkov created IGNITE-20320: - Summary: Avoid sharing HybridClock between nodes in tests Key: IGNITE-20320 URL: https://issues.apache.org/jira/browse/IGNITE-20320 Project: Ignite Issue Type: Test Reporter: Andrey Mashenkov As for now, 1. There are tests, where a HybridClock instance is shared among cluster nodes. This looks like a bug. Let's avoid clock sharing among nodes, or, otherwise, add a comprehensive comment, why HybridClock instance is reused. Example: ActiveActorTest, MultiActiveActorTest, PlacementDriverManagerTest... 2. In some tests, different HybridClock instance are passed to different components. However, there may be no nodes, but it is assumed the components belong to the same one though. This also looks like a bug. Exampple: ItRebalanceDistributedTest... Let's revisit all the tests, where HybridClock is created and fix these issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20018) Introduce system view definition API
[
https://issues.apache.org/jira/browse/IGNITE-20018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760845#comment-17760845
]
Evgeny Stanilovsky commented on IGNITE-20018:
-
[~mzhuravkov] thanks ! merged into main.
> Introduce system view definition API
>
>
> Key: IGNITE-20018
> URL: https://issues.apache.org/jira/browse/IGNITE-20018
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Maksim Zhuravkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Let's introduce API to define a system view. Below is a few examples of how
> it may look like:
> {code:java}
> SystemView.clusterViewBuilder()
> .name("USERS")
> .addColumn("ID", Integer.class, Table::id)
> .addColumn("SCHEMA_ID", Integer.class, Table::schemaId)
> .addColumn("NAME", String.class, Table::name)
> .addColumn("COLUMN_NAMES", String.class, Table::columnNames)
> .dataProvider(() -> toAsyncCursor(tableManager.allTables()))
> .build();
> SystemView.nodeViewBuilder()
> .name("CONNECTIONS")
> .addColumn("USER", String.class, Connection::user)
> .addColumn("ADDRESS", String.class, Connection::address)
> .addColumn("ATTRS", String.class, Connection::attrs)
> .localNodeColumnAlias("NODE_ID")
> .dataProvider(() -> toAsyncCursor(connManager.connections()))
> .build();
> {code}
> Explanation of the code snippet above:
> * We need to distinguish between views exposing data with cluster-wide
> semantic and views exposing data with node-specific semantic. Such
> segregation is required to properly map queries' fragments to nodes owning
> data.
> * *name* attribute – is a name of the view under which it will be available
> in sql
> * *addColumn* attribute – appends a column to the view definition. View
> definition should have columns in the order of invocation of addColumn
> method. This method accepts three parameters: name, column type represented
> by class, and property reader. Name is a name of the column, under which the
> column under which it will be available in sql. Class is required to properly
> build the view's description. Property reader is a function which accepts
> objects of type specified in generic of builder, and returns value for the
> column of interest.
> * *dataProvider* attribute – provides an access to data this view is supposed
> to expose. Data provider accepts the supplier of AsyncCursor (see
> org.apache.ignite.internal.sql.engine.AsyncCursor; should be moved to core).
> AsyncCursor is required, because some of the data may be not stored locally,
> thus remote call will be required. To avoid blocking of query engine threads,
> it's better to integrate with async primitives, rather than force every
> module to store required state in local collections.
> * *localNodeColumnAlias* attribute – alias for the column exposing node id.
> This attribute is available only for nodeView’s, since node id will be
> injected automatically only for this type of view.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20319) MultiActorPlacementDriverTest and PlacementDriverManagerTest incorrectly share hybridClock
[ https://issues.apache.org/jira/browse/IGNITE-20319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-20319: - Labels: ignite-3 (was: ) > MultiActorPlacementDriverTest and PlacementDriverManagerTest incorrectly > share hybridClock > -- > > Key: IGNITE-20319 > URL: https://issues.apache.org/jira/browse/IGNITE-20319 > Project: Ignite > Issue Type: Bug >Reporter: Alexander Lapin >Priority: Major > Labels: ignite-3 > > Within aforementioned tests placement drivers share same clock instance > whether nodes have node specific ones. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20319) MultiActorPlacementDriverTest and PlacementDriverManagerTest incorrectly share hybridClock
[ https://issues.apache.org/jira/browse/IGNITE-20319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-20319: - Ignite Flags: (was: Docs Required,Release Notes Required) > MultiActorPlacementDriverTest and PlacementDriverManagerTest incorrectly > share hybridClock > -- > > Key: IGNITE-20319 > URL: https://issues.apache.org/jira/browse/IGNITE-20319 > Project: Ignite > Issue Type: Bug >Reporter: Alexander Lapin >Priority: Major > > Within aforementioned tests placement drivers share same clock instance > whether nodes have node specific ones. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20319) MultiActorPlacementDriverTest and PlacementDriverManagerTest incorrectly share hybridClock
[ https://issues.apache.org/jira/browse/IGNITE-20319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-20319: - Description: Within aforementioned tests placement drivers share same clock instance whether nodes have node specific ones. > MultiActorPlacementDriverTest and PlacementDriverManagerTest incorrectly > share hybridClock > -- > > Key: IGNITE-20319 > URL: https://issues.apache.org/jira/browse/IGNITE-20319 > Project: Ignite > Issue Type: Bug >Reporter: Alexander Lapin >Priority: Major > > Within aforementioned tests placement drivers share same clock instance > whether nodes have node specific ones. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20319) MultiActorPlacementDriverTest and PlacementDriverManagerTest incorretly share hybridClock
Alexander Lapin created IGNITE-20319: Summary: MultiActorPlacementDriverTest and PlacementDriverManagerTest incorretly share hybridClock Key: IGNITE-20319 URL: https://issues.apache.org/jira/browse/IGNITE-20319 Project: Ignite Issue Type: Bug Reporter: Alexander Lapin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20319) MultiActorPlacementDriverTest and PlacementDriverManagerTest incorrectly share hybridClock
[ https://issues.apache.org/jira/browse/IGNITE-20319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-20319: - Summary: MultiActorPlacementDriverTest and PlacementDriverManagerTest incorrectly share hybridClock (was: MultiActorPlacementDriverTest and PlacementDriverManagerTest incorretly share hybridClock) > MultiActorPlacementDriverTest and PlacementDriverManagerTest incorrectly > share hybridClock > -- > > Key: IGNITE-20319 > URL: https://issues.apache.org/jira/browse/IGNITE-20319 > Project: Ignite > Issue Type: Bug >Reporter: Alexander Lapin >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-14697) Implement node restart mechanism
[
https://issues.apache.org/jira/browse/IGNITE-14697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin resolved IGNITE-14697.
--
Fix Version/s: 3.0.0-beta2
Resolution: Fixed
> Implement node restart mechanism
>
>
> Key: IGNITE-14697
> URL: https://issues.apache.org/jira/browse/IGNITE-14697
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Mirza Aliev
>Assignee: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> While we were implementing 3.0.0-alpha2 release, we didn't properly develop a
> cluster restart scenario, so several places in the code were patched with
> TODO:
> * Both Local and Distributed Configuration Storage's {{storage version}}
> should be [persisted|https://issues.apache.org/jira/browse/IGNITE-14408] and
> set after a restart
> * {{ConfigurationStorage#notifyApplied}} mechanism should be revised
> according to restart mechanism
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-14410) Node components startup
[ https://issues.apache.org/jira/browse/IGNITE-14410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14410. -- Fix Version/s: 3.0.0-beta2 Resolution: Fixed > Node components startup > --- > > Key: IGNITE-14410 > URL: https://issues.apache.org/jira/browse/IGNITE-14410 > Project: Ignite > Issue Type: New Feature >Reporter: Vyacheslav Koptilin >Assignee: Alexander Lapin >Priority: Major > Labels: iep-73, ignite-3 > Fix For: 3.0.0-beta2 > > > Need to define requirements/rules that should define components lifecycle and > theirs mutual interaction. > For testability purposes, we require that component dependencies are defined > upfront and provided at the construction time. This additionaly requires that > component dependencies form no cycles. Therefore, components form an acyclic > directed graph that is constructed in topological sort order wrt root. > Components created and initialized also in an order consistent with a > topological sort of the components graph. This enforces serveral rules > related to the components interaction: > - Since metastorage watches can only be added during the component startup, > the watch notification order is consistent with the component initialization > order. I.e. if a component B depdends on a component A, then A receives watch > notification prior to B. > - Dependent component can directly call an API method on a dependee > component (because it can obtain the dependee reference during construction). > Direct inverse calls are prohibited (this is enforced by only acquiring > component references during the components construction). Nevertheless, > inverse call can be implemented by means of listeners or callbacks: the > dependent component installs a listener to a dependeee, which can be later > invoked. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-16001) Raft nodes shouldn't process network messages before Ignite node started
[
https://issues.apache.org/jira/browse/IGNITE-16001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin resolved IGNITE-16001.
--
Resolution: Won't Fix
Is not actual anymore.
> Raft nodes shouldn't process network messages before Ignite node started
> -
>
> Key: IGNITE-16001
> URL: https://issues.apache.org/jira/browse/IGNITE-16001
> Project: Ignite
> Issue Type: Task
>Reporter: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
>
> At the components start (Metastorage manager, Table manager) they are start
> several RAFT groups and these groups process all RAFT messages don't wait all
> components started. But until component start the Ignite node is not ready to
> data load, it is not joined to a cluster topology and can be not authorized.
> For solve these issues, recommend listening network events by RAFT node only
> when the node fully started.
> Here, message handler subscribed:
> {code}
> service.messagingService().addMessageHandler(RaftMessageGroup.class,
> messageHandler);
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-14887) Need a way to protect public API from stopping node
[ https://issues.apache.org/jira/browse/IGNITE-14887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-14887: - Parent: (was: IGNITE-14410) Issue Type: Improvement (was: Sub-task) > Need a way to protect public API from stopping node > --- > > Key: IGNITE-14887 > URL: https://issues.apache.org/jira/browse/IGNITE-14887 > Project: Ignite > Issue Type: Improvement >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-14604) Implement redeploy for DMS manager aggregated watch
[ https://issues.apache.org/jira/browse/IGNITE-14604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14604. -- Resolution: Won't Fix Is not actual anymore. > Implement redeploy for DMS manager aggregated watch > --- > > Key: IGNITE-14604 > URL: https://issues.apache.org/jira/browse/IGNITE-14604 > Project: Ignite > Issue Type: Sub-task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > > DMS manager must support redeploying of aggregated container watch if any > watches returns onUpdate=false. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20262) Refuse accepting partition Raft commands when not enough schemas are available
[ https://issues.apache.org/jira/browse/IGNITE-20262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760795#comment-17760795 ] Kirill Tkalenko commented on IGNITE-20262: -- Looks good. > Refuse accepting partition Raft commands when not enough schemas are available > -- > > Key: IGNITE-20262 > URL: https://issues.apache.org/jira/browse/IGNITE-20262 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: iep-98, ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > This is a left-over from IGNITE-19227. Analogous to processing incoming > AppendEntriesRequests, we should not accept Raft commands when we don't have > enough metadata. This could happen if a Primary replica turns out to be not > colocated with a partition Raft group leader and the leader lags wrt > MetaStorage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20318) Improve logging of log truncation
[ https://issues.apache.org/jira/browse/IGNITE-20318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-20318: - Fix Version/s: 3.0.0-beta2 > Improve logging of log truncation > - > > Key: IGNITE-20318 > URL: https://issues.apache.org/jira/browse/IGNITE-20318 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > There's no info log for RAFT log truncation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20318) Improve logging of log truncation
[ https://issues.apache.org/jira/browse/IGNITE-20318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-20318: - Reviewer: Kirill Tkalenko Looks good. > Improve logging of log truncation > - > > Key: IGNITE-20318 > URL: https://issues.apache.org/jira/browse/IGNITE-20318 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > There's no info log for RAFT log truncation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20312) Change default logger settings
[
https://issues.apache.org/jira/browse/IGNITE-20312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760785#comment-17760785
]
Vyacheslav Koptilin commented on IGNITE-20312:
--
LGTM, considering the fact that this config can be used for testing purposes
> Change default logger settings
> --
>
> Key: IGNITE-20312
> URL: https://issues.apache.org/jira/browse/IGNITE-20312
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> What we have now is:
>
> {noformat}
> java.util.logging.FileHandler.limit = 10485760
> java.util.logging.FileHandler.count = 10
> {noformat}
>
> That's not enough for good testing, especially considering that each restart
> will start with next file, instead of appending to the previous file. I
> suggest greatly increasing the number of files in rotation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20316) WatchListenerInhibitor might cause lost updates
[ https://issues.apache.org/jira/browse/IGNITE-20316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-20316: --- Summary: WatchListenerInhibitor might cause lost updates (was: MetastorageInhibitor might cause lost updates) > WatchListenerInhibitor might cause lost updates > --- > > Key: IGNITE-20316 > URL: https://issues.apache.org/jira/browse/IGNITE-20316 > Project: Ignite > Issue Type: Bug >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3, tech-debt > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > WatchListenerInhibitor installs its future to the chain of > notificationFutures inside a WatchProcessor. This requires to read > notificationFuture, build a new future on top of it and then put it to the > same field. There is no synchrinization in place, so either production code's > or WatchListenerInhibitor's update might be lost in the case of a concurrent > update. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20316) MetastorageInhibitor might cause lost updates
[ https://issues.apache.org/jira/browse/IGNITE-20316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-20316: --- Description: WatchListenerInhibitor installs its future to the chain of notificationFutures inside a WatchProcessor. This requires to read notificationFuture, build a new future on top of it and then put it to the same field. There is no synchrinization in place, so either production code's or WatchListenerInhibitor's update might be lost in the case of a concurrent update. (was: TBD) > MetastorageInhibitor might cause lost updates > - > > Key: IGNITE-20316 > URL: https://issues.apache.org/jira/browse/IGNITE-20316 > Project: Ignite > Issue Type: Bug >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3, tech-debt > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > WatchListenerInhibitor installs its future to the chain of > notificationFutures inside a WatchProcessor. This requires to read > notificationFuture, build a new future on top of it and then put it to the > same field. There is no synchrinization in place, so either production code's > or WatchListenerInhibitor's update might be lost in the case of a concurrent > update. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20318) Improve logging of log truncation
Ivan Bessonov created IGNITE-20318: -- Summary: Improve logging of log truncation Key: IGNITE-20318 URL: https://issues.apache.org/jira/browse/IGNITE-20318 Project: Ignite Issue Type: Improvement Reporter: Ivan Bessonov Assignee: Ivan Bessonov There's no info log for RAFT log truncation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (IGNITE-18272) Update contributing process on the Community page
[ https://issues.apache.org/jira/browse/IGNITE-18272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev closed IGNITE-18272. -- > Update contributing process on the Community page > - > > Key: IGNITE-18272 > URL: https://issues.apache.org/jira/browse/IGNITE-18272 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Erlan Aytpaev >Priority: Major > > Due to changes in ASF Jira process of creating accounts, we need to change > steps 1-2 for the new contributors we have on the page > [https://ignite.apache.org/our-community.html#contributing] > # Join the dev mailing list and introduce yourself (see the example > message). > # If you don’t have an ASF JIRA account, mention this in the introduction > email along with preferable username and one of the PMC members will create > the account for you and provide permissions. > further steps are still relevant > The exmaple message many people asked us to share: > Example: First email to the dev mailing list > Subject: I want to contribute to Apache ignite. > Hello, Everyone! > My name is [ Name ]. I want to contribute to Ignite. I would like to start > from [ identification of particular ticket or module, if you have one in mind > ]. Please, help me to start contributing. > My ASF JIRA username is [ username ]. > OR > I don’t have an ASF JIRA account. My preferred username is [username, no > hyphens allowed ] . > Regards, > [ Name ] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (IGNITE-17873) [Ignite Website] Ignite Summit 2022 Europe_Update website banners
[ https://issues.apache.org/jira/browse/IGNITE-17873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev closed IGNITE-17873. -- Ignite Flags: (was: Docs Required,Release Notes Required) > [Ignite Website] Ignite Summit 2022 Europe_Update website banners > - > > Key: IGNITE-17873 > URL: https://issues.apache.org/jira/browse/IGNITE-17873 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Evgenia >Assignee: Erlan Aytpaev >Priority: Major > Attachments: Event page.jpg, docs.jpg, ignite-Summit.jpg > > > Please add a new Ignite Summit and update event banners. > > All the links should lead to [Ignite Summit November 9, 2022 > |https://ignite-summit.org/2022-november/] > Places to update banners: > 1) Featured events > [Distributed Database - Apache Ignite|https://ignite.apache.org/] > 2) Doc's banner > [https://ignite.apache.org/docs/latest/] > 3) Text banner at the top (doc's page) > Ignite Summit Europe — November 9 — Join virtually! > 4) Update event page with a new image > [Apache Ignite Events - Meetups, Summit, > Conference|https://ignite.apache.org/events.html#summit] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (IGNITE-18124) [Ignite Website] Ignite Summit Europe_Update website banners_Recordings Now Available
[ https://issues.apache.org/jira/browse/IGNITE-18124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev closed IGNITE-18124. -- Ignite Flags: (was: Docs Required,Release Notes Required) > [Ignite Website] Ignite Summit Europe_Update website banners_Recordings Now > Available > - > > Key: IGNITE-18124 > URL: https://issues.apache.org/jira/browse/IGNITE-18124 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Evgenia >Assignee: Erlan Aytpaev >Priority: Major > Attachments: Events.jpg, docs.jpg, ignite-Summit.jpg > > > Please update Ignite Summit event banners. > > All the links should lead to [Ignite Summit November 9, 2022 - Join > virtually! (ignite-summit.org)|https://ignite-summit.org/2022-november/] > Places to update banners: > 1) Featured events > [Distributed Database - Apache Ignite|https://ignite.apache.org/] > 2) Doc's banner > [https://ignite.apache.org/docs/latest/] > 3) Text banner at the top (doc's page) > Ignite Summit Europe — Recordings Available — Watch Now > 4) Update the event page with a new image > [Apache Ignite Events - Meetups, Summit, > Conference|https://ignite.apache.org/events.html#summit] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (IGNITE-18886) Training section updates
[ https://issues.apache.org/jira/browse/IGNITE-18886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev closed IGNITE-18886. -- > Training section updates > > > Key: IGNITE-18886 > URL: https://issues.apache.org/jira/browse/IGNITE-18886 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Erlan Aytpaev >Assignee: Erlan Aytpaev >Priority: Major > > Update the training section on [https://ignite.apache.org/resources.html] > page: > 1) remove training "Apache Ignite Management and Monotoring" > 2) the first one now will be "Essentials", next - Apache Ignite and > Kubernetes: Deployment and Orchestration Strategies with the new picture. > Text below the picture: Learn how to deploy and orchestrate Apache Ignite in > a Kubernetes environment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (IGNITE-19382) [Ignite Website] Ignite Summit 2023_Update website banners
[ https://issues.apache.org/jira/browse/IGNITE-19382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev closed IGNITE-19382. -- Ignite Flags: (was: Docs Required,Release Notes Required) > [Ignite Website] Ignite Summit 2023_Update website banners > -- > > Key: IGNITE-19382 > URL: https://issues.apache.org/jira/browse/IGNITE-19382 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Evgenia >Assignee: Erlan Aytpaev >Priority: Major > Attachments: FB.jpg, docs.jpg, ignite-Summit.jpg > > > Update summit banners please. Places to update banners: > 1) Featured events > [Distributed Database - Apache Ignite|https://ignite.apache.org/] > 2) Doc's banner > [https://ignite.apache.org/docs/latest/] > 3) Update event page with a new image > [Apache Ignite Events - Meetups, Summit, > Conference|https://ignite.apache.org/events.html#summit] > > Also lets talk about how to move the banner on the main page upper(jn the > first screen) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (IGNITE-18898) Cases Section Update
[ https://issues.apache.org/jira/browse/IGNITE-18898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev closed IGNITE-18898. -- > Cases Section Update > > > Key: IGNITE-18898 > URL: https://issues.apache.org/jira/browse/IGNITE-18898 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Erlan Aytpaev >Assignee: Erlan Aytpaev >Priority: Major > > 1)Change 3 cases on the main page + create new "cards" for them > 2)On the page with cases add, remove and change places some cases + create > new cards (marked with the *): > IBM + Bloomberg* > Trimble + CERN* > Cardano*+ Yahoo Japan > Ameriacan Airlines +INDG > Banco do Brasil + 24 hours fitness > iFood* + nference > JPMC + JPMC > Expedia* + Sentienz > Komodo Health* + Hypi > Transition Technologies PSC* + Kubo* > Dutch Railways + Teradata -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (IGNITE-19695) [Ignite Website] Ignite Summit 2023_Update website banners_On demand
[ https://issues.apache.org/jira/browse/IGNITE-19695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev closed IGNITE-19695. -- Ignite Flags: (was: Docs Required,Release Notes Required) > [Ignite Website] Ignite Summit 2023_Update website banners_On demand > > > Key: IGNITE-19695 > URL: https://issues.apache.org/jira/browse/IGNITE-19695 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Evgenia >Assignee: Erlan Aytpaev >Priority: Major > Attachments: docs (5).png, ignite-Summit (3).png, past events.png > > > Update featured the event banner (image attached) and put it down on the main > page (where it was before) > Update the TEXT banner on the main page: Ignite Summit 2023 — Watch on demand > — Register now --> > Update past event banner (image attached) > Update the banner on the DOCS page (image attached) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19797) [Website] Add analytics tag GA4
[ https://issues.apache.org/jira/browse/IGNITE-19797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev reassigned IGNITE-19797: -- Assignee: Erlan Aytpaev > [Website] Add analytics tag GA4 > --- > > Key: IGNITE-19797 > URL: https://issues.apache.org/jira/browse/IGNITE-19797 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Erlan Aytpaev >Priority: Major > > On July 1st GA will stop supporting UA tag. Please add GA4 to the Ignite > Website Analytics before that deadline. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (IGNITE-20282) Add new committers to the website
[ https://issues.apache.org/jira/browse/IGNITE-20282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev closed IGNITE-20282. -- > Add new committers to the website > - > > Key: IGNITE-20282 > URL: https://issues.apache.org/jira/browse/IGNITE-20282 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Erlan Aytpaev >Priority: Trivial > > Please add to the community page[1] two new committers: > > Aleksandr Polovtsev [https://github.com/sashapolo > http://people.apache.org/phonebook.html?uid=apolovtsev > |https://github.com/sashapolo] > Stephen Darlington [https://github.com/sdarlington > http://people.apache.org/phonebook.html?uid=sdarlington|https://github.com/sdarlington] > > [1] https://ignite.apache.org/our-community.html#community -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (IGNITE-19797) [Website] Add analytics tag GA4
[ https://issues.apache.org/jira/browse/IGNITE-19797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev closed IGNITE-19797. -- > [Website] Add analytics tag GA4 > --- > > Key: IGNITE-19797 > URL: https://issues.apache.org/jira/browse/IGNITE-19797 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Erlan Aytpaev >Priority: Major > > On July 1st GA will stop supporting UA tag. Please add GA4 to the Ignite > Website Analytics before that deadline. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (IGNITE-19959) Grammar error on Ignite main page
[ https://issues.apache.org/jira/browse/IGNITE-19959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev closed IGNITE-19959. -- > Grammar error on Ignite main page > - > > Key: IGNITE-19959 > URL: https://issues.apache.org/jira/browse/IGNITE-19959 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Erlan Aytpaev >Assignee: Erlan Aytpaev >Priority: Major > > The short preview of the Apache Ignite website, Google shows “… *a* best > distributed database…”. That would be a minor typo but this is literally the > first thing you see when you google Ignite, so we should fix it. > Let's say, "a leading distributed database management system..." > !https://mail.google.com/mail/u/0?ui=2&ik=881562c0d8&attid=0.1.1&permmsgid=msg-f:1771140881722414345&th=18945b3f7e3c9509&view=fimg&fur=ip&sz=s0-l75-ft&attbid=ANGjdJ-L7daOwYz1jj3pwRotkAm1CxPXDHYIxl1Bu2TBuCLy52cjOF_uk_gyvAT58ANJQpbXFs6YRzi1TgqZq4NaDtrkmuXkMKIErhb8ns42PeHkAFRH7XlKRqrAL94&disp=emb! -- This message was sent by Atlassian Jira (v8.20.10#820010)
