[jira] [Commented] (IGNITE-14702) Inconsistency of the new index when the node falls / deactivates
[ https://issues.apache.org/jira/browse/IGNITE-14702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17365239#comment-17365239 ] Kirill Tkalenko commented on IGNITE-14702: -- [~jooger] Please make code review. > Inconsistency of the new index when the node falls / deactivates > > > Key: IGNITE-14702 > URL: https://issues.apache.org/jira/browse/IGNITE-14702 > Project: Ignite > Issue Type: Bug > Components: persistence, sql >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > At the moment, if we add a new index and in the middle of its construction we > fall / deactivate a node, then it will be inconsistent and may create errors. > Need to either add a new index to DurableBackgroundTask, or add / modify a > separate mechanism that allows to resume the creation of a new index. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14702) Inconsistency of the new index when the node falls / deactivates
[ https://issues.apache.org/jira/browse/IGNITE-14702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-14702: - Reviewer: Yury Gerzhedovich (was: Stanilovsky Evgeny) > Inconsistency of the new index when the node falls / deactivates > > > Key: IGNITE-14702 > URL: https://issues.apache.org/jira/browse/IGNITE-14702 > Project: Ignite > Issue Type: Bug > Components: persistence, sql >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > At the moment, if we add a new index and in the middle of its construction we > fall / deactivate a node, then it will be inconsistent and may create errors. > Need to either add a new index to DurableBackgroundTask, or add / modify a > separate mechanism that allows to resume the creation of a new index. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14901) Document SSL metrics.
[ https://issues.apache.org/jira/browse/IGNITE-14901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17365175#comment-17365175 ] Nikita Safonov commented on IGNITE-14901: - [~igusev] would you please take a brief look at the issue? > Document SSL metrics. > - > > Key: IGNITE-14901 > URL: https://issues.apache.org/jira/browse/IGNITE-14901 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > It is needed to document SSL metrics introduced by > https://issues.apache.org/jira/browse/IGNITE-14658 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14599) Add generic way to bootstrap configuration
[
https://issues.apache.org/jira/browse/IGNITE-14599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17365172#comment-17365172
]
Vladislav Pyatkov commented on IGNITE-14599:
Only minor comments, this patch looks good.
> Add generic way to bootstrap configuration
> ---
>
> Key: IGNITE-14599
> URL: https://issues.apache.org/jira/browse/IGNITE-14599
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Assignee: Kirill Gusakov
>Priority: Major
> Labels: iep-73
>
> Currently it's possible to bootstrap configuration only with json formatted
> string.
> {code:java}
> Ignite start(@Nullable String jsonStrBootstrapCfg);
> {code}
> Instead of given temporary solution some sort of generic implementation
> should be used, for example configuration file with set of formats: json,
> hocon.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14934) Cumulative exceptions "Failed to find checkpoint record at the given WAL pointer"
RT Labaza created IGNITE-14934:
--
Summary: Cumulative exceptions "Failed to find checkpoint record
at the given WAL pointer"
Key: IGNITE-14934
URL: https://issues.apache.org/jira/browse/IGNITE-14934
Project: Ignite
Issue Type: Bug
Components: cache, persistence
Affects Versions: 2.9.1
Reporter: RT Labaza
{{Ignite is configured with setPersistence=true and WALMode=NONE and started
via an IgniteSpringBean. Each time Ignite is brought up, the following
exception is logged. This exception is cumulatively logged for (at least) the
current startup and again for each previous startup. The FileWALPointer is
always f[idx=0, fileOff=0, len=0]or all the exceptions. Ignite is set
active(true) when needed and then active(false) when done using it, but these
cumulative exceptions occur even when Ignite was not used during the app
startup/shutdown.}}
{{>>> ver. 2.9.1#20201203-sha1:adcce517}}
{{2021-06-17 13:18:37.141 <> WARN 7765 --- [main]
o.a.i.i.p.c.p.c.CheckpointHistory : Failed to process checkpoint:
CheckpointEntry [id=b490439c-991b-44e0-8389-669b4c03524f,
timestamp=1623937116800, ptr=FileWALPointer [idx=0, fileOff=0,
len=0]]}}{{org.apache.ignite.IgniteCheckedException: Failed to find checkpoint
record at the given WAL pointer: FileWALPointer [idx=0, fileOff=0, len=0]}}
{{ at
org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointEntry$GroupStateLazyStore.initIfNeeded(CheckpointEntry.java:358)
~[ignite-core-2.9.1.jar!/:2.9.1]}}
{{ at
org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointEntry$GroupStateLazyStore.access$300(CheckpointEntry.java:243)
~[ignite-core-2.9.1.jar!/:2.9.1]}}
{{ at
org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointEntry.initIfNeeded(CheckpointEntry.java:122)
~[ignite-core-2.9.1.jar!/:2.9.1]}}
{{ at
org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointEntry.groupState(CheckpointEntry.java:104)
~[ignite-core-2.9.1.jar!/:2.9.1]}}
{{ at
org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointHistory.updateEarliestCpMap(CheckpointHistory.java:187)
[ignite-core-2.9.1.jar!/:2.9.1]}}
{{ at
org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointHistory.initialize(CheckpointHistory.java:102)
[ignite-core-2.9.1.jar!/:2.9.1]}}
{{ at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:881)
[ignite-core-2.9.1.jar!/:2.9.1]}}
{{ at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:5022)
[ignite-core-2.9.1.jar!/:2.9.1]}}
{{ at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1251)
[ignite-core-2.9.1.jar!/:2.9.1]}}
{{ at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2052)
[ignite-core-2.9.1.jar!/:2.9.1]}}
{{ at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1698)
[ignite-core-2.9.1.jar!/:2.9.1]}}
{{ at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1114)
[ignite-core-2.9.1.jar!/:2.9.1]}}
{{ at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:612)
[ignite-core-2.9.1.jar!/:2.9.1]}}
{{ at org.apache.ignite.IgniteSpring.start(IgniteSpring.java:66)
[ignite-spring-2.9.1.jar!/:2.9.1]}}
{{ at
org.apache.ignite.IgniteSpringBean.afterSingletonsInstantiated(IgniteSpringBean.java:174)
[ignite-spring-2.9.1.jar!/:2.9.1]}}
{{ at
com.toshibacommerce.databridge.data.grid.IgniteDataGrid.afterSingletonsInstantiated(IgniteDataGrid.java:55)
[databridge-data-grid-1.2-SNAPSHOT.jar!/:na]}}
{{ at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:896)
[spring-beans-5.2.2.RELEASE.jar!/:5.2.2.RELEASE]}}
{{ at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:878)
[spring-context-5.2.2.RELEASE.jar!/:5.2.2.RELEASE]}}
{{ at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:550)
[spring-context-5.2.2.RELEASE.jar!/:5.2.2.RELEASE]}}
{{ at
org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141)
[spring-boot-2.2.2.RELEASE.jar!/:2.2.2.RELEASE]}}
{{ at
org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747)
[spring-boot-2.2.2.RELEASE.jar!/:2.2.2.RELEASE]}}
{{ at
org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397)
[spring-boot-2.2.2.RELEASE.jar!/:2.2.2.RELEASE]}}
{{ at
org.springframework.boot.SpringApplication.run(SpringApplication.java:315)
[jira] [Commented] (IGNITE-14702) Inconsistency of the new index when the node falls / deactivates
[
https://issues.apache.org/jira/browse/IGNITE-14702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17365050#comment-17365050
]
Ignite TC Bot commented on IGNITE-14702:
{panel:title=Branch: [pull/9150/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9150/head] Base: [master] : New Tests
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Indexing){color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=6051478]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
ResumeCreateIndexTest.testGeneralFlow - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
ResumeCreateIndexTest.testErrorFlow - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
ResumeCreateIndexTest.testConcurrentBuildNewIndexAndRebuildIndexes0 -
PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
ResumeCreateIndexTest.testConcurrentBuildNewIndexAndRebuildIndexes1 -
PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
ResumeCreateIndexTest.testNoCheckpointAfterIndexCreation - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
ResumeCreateIndexTest.testPartialCheckpointNewIndexRows - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6051320buildTypeId=IgniteTests24Java8_RunAll]
> Inconsistency of the new index when the node falls / deactivates
>
>
> Key: IGNITE-14702
> URL: https://issues.apache.org/jira/browse/IGNITE-14702
> Project: Ignite
> Issue Type: Bug
> Components: persistence, sql
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> At the moment, if we add a new index and in the middle of its construction we
> fall / deactivate a node, then it will be inconsistent and may create errors.
> Need to either add a new index to DurableBackgroundTask, or add / modify a
> separate mechanism that allows to resume the creation of a new index.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14933) Implement metrics for a snapshot restore operation
[ https://issues.apache.org/jira/browse/IGNITE-14933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-14933: -- Labels: iep-43 (was: ) > Implement metrics for a snapshot restore operation > -- > > Key: IGNITE-14933 > URL: https://issues.apache.org/jira/browse/IGNITE-14933 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Pereslegin >Priority: Major > Labels: iep-43 > > Since the automatic snapshot restore operation can take a long time, we must > be able to track its progress using metrics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14933) Implement metrics for a snapshot restore operation
[ https://issues.apache.org/jira/browse/IGNITE-14933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-14933: -- Summary: Implement metrics for a snapshot restore operation (was: Implement metrics for snapshot restore operation) > Implement metrics for a snapshot restore operation > -- > > Key: IGNITE-14933 > URL: https://issues.apache.org/jira/browse/IGNITE-14933 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Pereslegin >Priority: Major > > Since the automatic snapshot restore operation can take a long time, we must > be able to track its progress using metrics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14933) Implement metrics for snapshot restore operation
Pavel Pereslegin created IGNITE-14933: - Summary: Implement metrics for snapshot restore operation Key: IGNITE-14933 URL: https://issues.apache.org/jira/browse/IGNITE-14933 Project: Ignite Issue Type: Improvement Reporter: Pavel Pereslegin Since the automatic snapshot restore operation can take a long time, we must be able to track its progress using metrics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14932) Reference to the Ignite Storage Overview video
Nikita Safonov created IGNITE-14932: --- Summary: Reference to the Ignite Storage Overview video Key: IGNITE-14932 URL: https://issues.apache.org/jira/browse/IGNITE-14932 Project: Ignite Issue Type: Bug Components: documentation Affects Versions: 2.10 Reporter: Nikita Safonov Assignee: Nikita Safonov We need to add a callout to the Ignite Native persistence page suggesting to watch this architectural deep dive on the internals of storage engine: [https://www.youtube.com/watch?v=6Yg5QW-XFVc=PLMc7NR20hA-KF8c_hVICKpzKnWkjzfC2V=17] Page to update: [https://ignite.apache.org/docs/latest/persistence/native-persistence] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14847) Finalize metrics implementation in jraft
[ https://issues.apache.org/jira/browse/IGNITE-14847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-14847: - Description: Currently, jraft uses dropwizard metrics. We should either backport ignite2 metrics framework and move jraft to it or make dropwizard usage project-wide. > Finalize metrics implementation in jraft > > > Key: IGNITE-14847 > URL: https://issues.apache.org/jira/browse/IGNITE-14847 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > Currently, jraft uses dropwizard metrics. > We should either backport ignite2 metrics framework and move jraft to it or > make dropwizard usage project-wide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14847) Finalize metrics implementation in jraft
[ https://issues.apache.org/jira/browse/IGNITE-14847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-14847: - Ignite Flags: (was: Docs Required,Release Notes Required) > Finalize metrics implementation in jraft > > > Key: IGNITE-14847 > URL: https://issues.apache.org/jira/browse/IGNITE-14847 > Project: Ignite > Issue Type: Task > Environment: Currently jraft uses dropwizard metrics. > We should either backport ignite2 metrics framework and move jraft to it or > make dropwizard usage project wide. >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14847) Finalize metrics implementation in jraft
[ https://issues.apache.org/jira/browse/IGNITE-14847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-14847: - Environment: (was: Currently jraft uses dropwizard metrics. We should either backport ignite2 metrics framework and move jraft to it or make dropwizard usage project wide.) > Finalize metrics implementation in jraft > > > Key: IGNITE-14847 > URL: https://issues.apache.org/jira/browse/IGNITE-14847 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14931) Define common error scopes and prefix
Vyacheslav Koptilin created IGNITE-14931: Summary: Define common error scopes and prefix Key: IGNITE-14931 URL: https://issues.apache.org/jira/browse/IGNITE-14931 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14930) Need to implement marshalling/unmarshalling exceptions in order to send an exception to remote node
Vyacheslav Koptilin created IGNITE-14930: Summary: Need to implement marshalling/unmarshalling exceptions in order to send an exception to remote node Key: IGNITE-14930 URL: https://issues.apache.org/jira/browse/IGNITE-14930 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14929) Flacky test IgniteWalHistoryReservationsTest#testWalHistoryPartiallyRemoved.
Stanilovsky Evgeny created IGNITE-14929: --- Summary: Flacky test IgniteWalHistoryReservationsTest#testWalHistoryPartiallyRemoved. Key: IGNITE-14929 URL: https://issues.apache.org/jira/browse/IGNITE-14929 Project: Ignite Issue Type: Improvement Components: persistence Affects Versions: 2.10 Reporter: Stanilovsky Evgeny Assignee: Stanilovsky Evgeny We will need to finish checkpoint before node stops and only after it - clean archive directory. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14913) Add cache statistics switch to control script
[
https://issues.apache.org/jira/browse/IGNITE-14913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-14913:
---
Description:
Currently, enabling or disabling cache statistics is available only via
IgniteVisorCmd or JMX. Because it seems that IgniteVisorCmd is no longer being
developed, it would be helpful to add a cache statistics switch into the
control script.
Suggested syntax for a command:
{code:java}
--cache statistics enable|disable|status regexPattern
{code}
* regexPattern - regular expression for filtering caches (not cache groups) by
their names. Caches with names satisfying the regular expression will be
affected by the command. In case of an empty regex, the control script should
finish execution with an error. If no matching caches are found, the control
script should print a message about matching caches' absence.
* enable - enables statistics for caches satisfying the 'regexPattern'.
* disable - disables statistics for caches satisfying the 'regexPattern'.
* status - prints current statistics status (enabled/disabled) for caches
satisfying the 'regexPattern'.
was:
Currently, enabling or disabling of cache statistics is available only via
IgniteVisorCmd or JMX. Because it seems that IgniteVisorCmd is no longer being
developed, it would be helpful to add a cache statistics switch into control
script.
Suggested syntax for a command:
{code:java}
--cache statistics enable|disable|status regexPattern
{code}
* regexPattern - regular expression for filtering caches (not cache groups) by
their names. Caches with satisfying to the regular exppression names will be
affected by the command. In case of empty regexp, control script should finish
execution with an error. If no matching caches found, control script should
print message about matching caches absence.
* enable - enables statistics for all satisfying to the 'regexPattern' caches.
* disable - disables statistics for all satisfying to the 'regexPattern' caches.
* status - prints statistics status (enabled/disabled) for all satisfying to
the 'regexPattern' caches.
> Add cache statistics switch to control script
> -
>
> Key: IGNITE-14913
> URL: https://issues.apache.org/jira/browse/IGNITE-14913
> Project: Ignite
> Issue Type: New Feature
> Components: control.sh
>Reporter: Ilya Shishkov
>Priority: Minor
>
> Currently, enabling or disabling cache statistics is available only via
> IgniteVisorCmd or JMX. Because it seems that IgniteVisorCmd is no longer
> being developed, it would be helpful to add a cache statistics switch into
> the control script.
> Suggested syntax for a command:
> {code:java}
> --cache statistics enable|disable|status regexPattern
> {code}
> * regexPattern - regular expression for filtering caches (not cache groups)
> by their names. Caches with names satisfying the regular expression will be
> affected by the command. In case of an empty regex, the control script should
> finish execution with an error. If no matching caches are found, the control
> script should print a message about matching caches' absence.
> * enable - enables statistics for caches satisfying the 'regexPattern'.
> * disable - disables statistics for caches satisfying the 'regexPattern'.
> * status - prints current statistics status (enabled/disabled) for caches
> satisfying the 'regexPattern'.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14913) Add cache statistics switch to control script
[
https://issues.apache.org/jira/browse/IGNITE-14913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-14913:
---
Description:
Currently, enabling or disabling of cache statistics is available only via
IgniteVisorCmd or JMX. Because it seems that IgniteVisorCmd is no longer being
developed, it would be helpful to add a cache statistics switch into control
script.
Suggested syntax for a command:
{code:java}
--cache statistics enable|disable|status regexPattern
{code}
* regexPattern - regular expression for filtering caches (not cache groups) by
their names. Caches with satisfying to the regular exppression names will be
affected by the command. In case of empty regexp, control script should finish
execution with an error. If no matching caches found, control script should
print message about matching caches absence.
* enable - enables statistics for all satisfying to the 'regexPattern' caches.
* disable - disables statistics for all satisfying to the 'regexPattern' caches.
* status - prints statistics status (enabled/disabled) for all satisfying to
the 'regexPattern' caches.
was:
Currently, enabling or disabling of cache statistics is available only via
IgniteVisorCmd or JMX. Because it seems that IgniteVisorCmd is no longer being
developed, it would be helpful to add a cache statistics switch into control
script.
Suggested syntax for a command:
{code:java}
--cache statistics enable|disable|status regexPattern
{code}
* regexPattern - regular expression for filtering caches (not cache groups) by
their names. Caches with satisfying to the regular exppression names will be
affected by the command.
* enable - enables statistics for all satisfying to the 'regexPattern' caches.
* disable - disables statistics for all satisfying to the 'regexPattern' caches.
* status - prints statistics status (enabled/disabled) for all satisfying to
the 'regexPattern' caches.
In case of empty regexp, control script should finish execution with an error.
If no matching caches found, control script should print message about matching
caches absence.
> Add cache statistics switch to control script
> -
>
> Key: IGNITE-14913
> URL: https://issues.apache.org/jira/browse/IGNITE-14913
> Project: Ignite
> Issue Type: New Feature
> Components: control.sh
>Reporter: Ilya Shishkov
>Priority: Minor
>
> Currently, enabling or disabling of cache statistics is available only via
> IgniteVisorCmd or JMX. Because it seems that IgniteVisorCmd is no longer
> being developed, it would be helpful to add a cache statistics switch into
> control script.
> Suggested syntax for a command:
> {code:java}
> --cache statistics enable|disable|status regexPattern
> {code}
> * regexPattern - regular expression for filtering caches (not cache groups)
> by their names. Caches with satisfying to the regular exppression names will
> be affected by the command. In case of empty regexp, control script should
> finish execution with an error. If no matching caches found, control script
> should print message about matching caches absence.
> * enable - enables statistics for all satisfying to the 'regexPattern' caches.
> * disable - disables statistics for all satisfying to the 'regexPattern'
> caches.
> * status - prints statistics status (enabled/disabled) for all satisfying to
> the 'regexPattern' caches.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14913) Add cache statistics switch to control script
[
https://issues.apache.org/jira/browse/IGNITE-14913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-14913:
---
Description:
Currently, enabling or disabling of cache statistics is available only via
IgniteVisorCmd or JMX. Because it seems that IgniteVisorCmd is no longer being
developed, it would be helpful to add a cache statistics switch into control
script.
Suggested syntax for a command:
{code:java}
--cache statistics enable|disable|status regexPattern
{code}
* regexPattern - regular expression for filtering caches (not cache groups) by
their names. Caches with satisfying to the regular exppression names will be
affected by the command.
* enable - enables statistics for all satisfying to the 'regexPattern' caches.
* disable - disables statistics for all satisfying to the 'regexPattern' caches.
* status - prints statistics status (enabled/disabled) for all satisfying to
the 'regexPattern' caches.
In case of empty regexp, control script should finish execution with an error.
If no matching caches found, control script should print message about matching
caches absence.
was:
Currently, enabling or disabling of cache statistics is available only via
IgniteVisorCmd and JMX. Because it seems that IgniteVisorCmd is no longer being
developed, it would be helpful to add a cache statistics switch into control
script.
Suggested syntax for command:
{code:java}
--cache statistics enable|disable|status regexPattern
{code}
In case of empty regexp, control script should finish execution with error. If
no matching caches found, control script should print message about matching
caches absence.
> Add cache statistics switch to control script
> -
>
> Key: IGNITE-14913
> URL: https://issues.apache.org/jira/browse/IGNITE-14913
> Project: Ignite
> Issue Type: New Feature
> Components: control.sh
>Reporter: Ilya Shishkov
>Priority: Minor
>
> Currently, enabling or disabling of cache statistics is available only via
> IgniteVisorCmd or JMX. Because it seems that IgniteVisorCmd is no longer
> being developed, it would be helpful to add a cache statistics switch into
> control script.
> Suggested syntax for a command:
> {code:java}
> --cache statistics enable|disable|status regexPattern
> {code}
> * regexPattern - regular expression for filtering caches (not cache groups)
> by their names. Caches with satisfying to the regular exppression names will
> be affected by the command.
> * enable - enables statistics for all satisfying to the 'regexPattern' caches.
> * disable - disables statistics for all satisfying to the 'regexPattern'
> caches.
> * status - prints statistics status (enabled/disabled) for all satisfying to
> the 'regexPattern' caches.
> In case of empty regexp, control script should finish execution with an
> error. If no matching caches found, control script should print message about
> matching caches absence.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14745) Storage API and basic configuration module
[
https://issues.apache.org/jira/browse/IGNITE-14745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364964#comment-17364964
]
Ivan Bessonov commented on IGNITE-14745:
* Created modules {{storage-api}} and {{storage-rocksdb}}
* Created interface {{org.apache.ignite.internal.storage.Storage}} and smaller
interfaces around it
* Created default implementation
{{org.apache.ignite.internal.storage.basic.ConcurrentHashMapStorage}} in the
same module
* Created custom implementation
{{org.apache.ignite.internal.storage.rocksdb.RocksDbStorage}} with the most
basic way to instantiate it
New storage has not been integrated.
> Storage API and basic configuration module
> --
>
> Key: IGNITE-14745
> URL: https://issues.apache.org/jira/browse/IGNITE-14745
> Project: Ignite
> Issue Type: Task
>Reporter: Sergey Chugunov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: iep-74, ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Introduce basic Storage API described in
> [IEP-74|https://cwiki.apache.org/confluence/display/IGNITE/IEP-74+Data+Storage]
> in a separate module.
> For now Storage API should contain only four basic methods to read, update
> and remove keys from Storage and to iterate over available keys:
> {code:java}
> /** Interface providing methods to read, remove and update keys in storage. */
> public interface Storage {
> /** Reads a DataRow for a given Key. */
> public DataRow read(Key key);
>
> /** Removes DataRow associated with a given Key. */
> public void remove(Key key);
>
> /** Executes an update with custom logic implemented by UpdateClosure
> interface. */
> public update(Key key, UpdateClosure clo);
>
> /** Obtains Iterator over some DataRows in storage. */
> public Iterator iterator(/* parameters */).
> }
> {code}
> This simplistic API is based on IgniteCacheOffheapManager from existing code
> base of Ignite 2.x. Only essential methods were left for the initial version
> of interface but it obviously will be refined during development.
> Details about some classes like Key or UpdateClosure are not clear yet and
> can be omitted (basic stub classes may be used).
> Implement basic configuration that is expected to be common for any Storage
> implementation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14928) Introduce IndexKey and IndexValue structures
Taras Ledkov created IGNITE-14928:
-
Summary: Introduce IndexKey and IndexValue structures
Key: IGNITE-14928
URL: https://issues.apache.org/jira/browse/IGNITE-14928
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Taras Ledkov
Fix For: 3.0.0-alpha3
2.x indexed uses real data row (read by the direct link) to compare indexed
fields.
Now we have to create separate IndexKey that will be serialized to bytes.
It is required by storage engine (now it is RocksDB).
IndexKey must support all supported native data types.
{{Comparator}} must be implemented for {{IndexKey}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14927) Change the index cost model
Taras Ledkov created IGNITE-14927: - Summary: Change the index cost model Key: IGNITE-14927 URL: https://issues.apache.org/jira/browse/IGNITE-14927 Project: Ignite Issue Type: Improvement Components: sql Reporter: Taras Ledkov Fix For: 3.0.0-alpha3 Current cost model of the index is designed for 2.x indexes where IndexScan is cheaper than TableScan because index storage uses direct link to data pages. At the Ignite 3.0 index uses a primary key as the reference to the data row. So additional lookup by the PK is required. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14913) Add cache statistics switch to control script
[
https://issues.apache.org/jira/browse/IGNITE-14913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-14913:
---
Description:
Currently, enabling or disabling of cache statistics is available only via
IgniteVisorCmd and JMX. Because it seems that IgniteVisorCmd is no longer being
developed, it would be helpful to add a cache statistics switch into control
script.
Suggested syntax for command:
{code:java}
--cache statistics enable|disable|status regexPattern
{code}
In case of empty regexp, control script should finish execution with error. If
no matching caches found, control script should print message about matching
caches absence.
was:
Currently, enabling or disabling of cache statistics is available only via
IgniteVisorCmd and JMX. Because it seems that IgniteVisorCmd is no longer being
developed, it would be helpful to add a cache statistics switch into control
script.
Suggested syntax for command:
{code}
--cache statistics enable|disable|status regexPattern
{code}
or
{code}
--cache metrics enable|disable|status regexPattern
{code}
In case of empty regexp, control script should finish execution with error. If
no matching caches found, control script should print message about matching
caches absence.
> Add cache statistics switch to control script
> -
>
> Key: IGNITE-14913
> URL: https://issues.apache.org/jira/browse/IGNITE-14913
> Project: Ignite
> Issue Type: New Feature
> Components: control.sh
>Reporter: Ilya Shishkov
>Priority: Minor
>
> Currently, enabling or disabling of cache statistics is available only via
> IgniteVisorCmd and JMX. Because it seems that IgniteVisorCmd is no longer
> being developed, it would be helpful to add a cache statistics switch into
> control script.
> Suggested syntax for command:
> {code:java}
> --cache statistics enable|disable|status regexPattern
> {code}
> In case of empty regexp, control script should finish execution with error.
> If no matching caches found, control script should print message about
> matching caches absence.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14913) Add cache statistics switch to control script
[
https://issues.apache.org/jira/browse/IGNITE-14913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-14913:
---
Description:
Currently, enabling or disabling of cache statistics is available only via
IgniteVisorCmd and JMX. Because it seems that IgniteVisorCmd is no longer being
developed, it would be helpful to add a cache statistics switch into control
script.
Suggested syntax for command:
{code}
--cache statistics enable|disable|status regexPattern
{code}
or
{code}
--cache metrics enable|disable|status regexPattern
{code}
In case of empty regexp, control script should finish execution with error. If
no matching caches found, control script should print message about matching
caches absence.
was:
Currently, enabling or disabling of cache statistics is available only via
ignitevisorcmd and JMX. Because it seems that ignitevisorcmd is no longer being
developed, it would be helpful to add a cache statistics switch into control
script, moreover we already have classes for this purpose:
{code}
VisorCacheToggleStatisticsTask
VisorCacheToggleStatisticsTaskArg
{code}
Suggested syntax for command:
{code}
--cache statistics enable|disable [cacheName1,...,cacheNameN]
{code}
> Add cache statistics switch to control script
> -
>
> Key: IGNITE-14913
> URL: https://issues.apache.org/jira/browse/IGNITE-14913
> Project: Ignite
> Issue Type: New Feature
> Components: control.sh
>Reporter: Ilya Shishkov
>Priority: Minor
>
> Currently, enabling or disabling of cache statistics is available only via
> IgniteVisorCmd and JMX. Because it seems that IgniteVisorCmd is no longer
> being developed, it would be helpful to add a cache statistics switch into
> control script.
> Suggested syntax for command:
> {code}
> --cache statistics enable|disable|status regexPattern
> {code}
> or
> {code}
> --cache metrics enable|disable|status regexPattern
> {code}
> In case of empty regexp, control script should finish execution with error.
> If no matching caches found, control script should print message about
> matching caches absence.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14926) Implement DDL command CREATE / DROP INDEX for SQL parser.
Taras Ledkov created IGNITE-14926:
-
Summary: Implement DDL command CREATE / DROP INDEX for SQL parser.
Key: IGNITE-14926
URL: https://issues.apache.org/jira/browse/IGNITE-14926
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Taras Ledkov
Fix For: 3.0.0-alpha3
Implement CREATE / DROP INDEX commands for SQL parser.
See more: {{DdlCommand}}, {{CreateTableCommand}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14925) Sorted indexes engine
[ https://issues.apache.org/jira/browse/IGNITE-14925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-14925: -- Issue Type: New Feature (was: Improvement) > Sorted indexes engine > - > > Key: IGNITE-14925 > URL: https://issues.apache.org/jira/browse/IGNITE-14925 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Taras Ledkov >Priority: Major > Fix For: 3.0.0-alpha3 > > > The umbrella ticket to track improvements and issues related to design and > development sorted index engine for Ignite 3.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14925) Sorted indexes engine
Taras Ledkov created IGNITE-14925: - Summary: Sorted indexes engine Key: IGNITE-14925 URL: https://issues.apache.org/jira/browse/IGNITE-14925 Project: Ignite Issue Type: Improvement Components: sql Reporter: Taras Ledkov Fix For: 3.0.0-alpha3 The umbrella ticket to track improvements and issues related to design and development sorted index engine for Ignite 3.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14745) Storage API and basic configuration module
[
https://issues.apache.org/jira/browse/IGNITE-14745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-14745:
---
Fix Version/s: (was: 3.0)
3.0.0-alpha3
> Storage API and basic configuration module
> --
>
> Key: IGNITE-14745
> URL: https://issues.apache.org/jira/browse/IGNITE-14745
> Project: Ignite
> Issue Type: Task
>Reporter: Sergey Chugunov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: iep-74, ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Introduce basic Storage API described in
> [IEP-74|https://cwiki.apache.org/confluence/display/IGNITE/IEP-74+Data+Storage]
> in a separate module.
> For now Storage API should contain only four basic methods to read, update
> and remove keys from Storage and to iterate over available keys:
> {code:java}
> /** Interface providing methods to read, remove and update keys in storage. */
> public interface Storage {
> /** Reads a DataRow for a given Key. */
> public DataRow read(Key key);
>
> /** Removes DataRow associated with a given Key. */
> public void remove(Key key);
>
> /** Executes an update with custom logic implemented by UpdateClosure
> interface. */
> public update(Key key, UpdateClosure clo);
>
> /** Obtains Iterator over some DataRows in storage. */
> public Iterator iterator(/* parameters */).
> }
> {code}
> This simplistic API is based on IgniteCacheOffheapManager from existing code
> base of Ignite 2.x. Only essential methods were left for the initial version
> of interface but it obviously will be refined during development.
> Details about some classes like Key or UpdateClosure are not clear yet and
> can be omitted (basic stub classes may be used).
> Implement basic configuration that is expected to be common for any Storage
> implementation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14924) Implement HoconConfigurationSource
Kirill Gusakov created IGNITE-14924: --- Summary: Implement HoconConfigurationSource Key: IGNITE-14924 URL: https://issues.apache.org/jira/browse/IGNITE-14924 Project: Ignite Issue Type: Task Reporter: Kirill Gusakov According to [IEP-55|https://cwiki.apache.org/confluence/display/IGNITE/IEP-55+Unified+Configuration] we must support HOCON format as the main format for configuration files. But now we support only json configs by our configuration framework and forced to convert hocon to json before. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14856) "Failed to resolve class name" on server when cache with indexed types is defined on client
[
https://issues.apache.org/jira/browse/IGNITE-14856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14856:
Release Note: Fixed "Failed to resolve class name" on server when cache
with indexed types is defined on client
> "Failed to resolve class name" on server when cache with indexed types is
> defined on client
> ---
>
> Key: IGNITE-14856
> URL: https://issues.apache.org/jira/browse/IGNITE-14856
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.10, 2.11
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.11
>
> Attachments: IgniteMarshallerCacheSeparateDirectoryTest.java
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Please see attached reproducer test (
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest#testClientCcfgIndexedGetClosure)
> If an indexed types cache is defined on client node's configuration but not
> server, client may put values into cache but server cannot read them despite
> having class on its classpath:
> {code}
> [2021-06-09 16:00:33,611][ERROR][pub-#229%client%][GridJobWorker] Failed to
> execute job [jobId=7992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl
> [taskName=o.a.i.i.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2,
> dep=LocalDeployment [super=GridDeployment [ts=1623243633290, depMode=SHARED,
> clsLdr=sun.misc.Launcher$AppClassLoader18b4aac2,
> clsLdrId=8092cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739, userVer=0,
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false,
> undeployed=false, usage=0]],
> taskClsName=o.a.i.i.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2,
> sesId=6992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> startTime=1623243633569, endTime=9223372036854775807,
> taskNodeId=749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> clsLdr=sun.misc.Launcher$AppClassLoader18b4aac2, closed=false,
> cpSpi=null, failSpi=null, loadSpi=null, usage=1, fullSup=false,
> internal=false, topPred=null, subjId=749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> mapFut=IgniteFuture [orig=GridFutureAdapter [ignoreInterrupts=false,
> state=INIT, res=null, hash=1341412812]], execName=null],
> jobId=7992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739]]
> class org.apache.ignite.IgniteException: class
> org.apache.ignite.IgniteCheckedException: Failed to resolve class name
> [platformId=0, platform=Java, typeId=1438082999]
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1849)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:590)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7181)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:584)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:511)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Failed to resolve class name
> [platformId=0, platform=Java, typeId=1438082999]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1265)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2078)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:1105)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:637)
> at
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2.call(IgniteMarshallerCacheSeparateDirectoryTest.java:188)
> at
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2.call(IgniteMarshallerCacheSeparateDirectoryTest.java:185)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1846)
> ... 8 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve
> class name [platformId=0, platform=Java, typeId=1438082999]
> at
>
[jira] [Created] (IGNITE-14923) Replace IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE to DataStorageConfiguration#minWalArchiveSize
Kirill Tkalenko created IGNITE-14923: Summary: Replace IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE to DataStorageConfiguration#minWalArchiveSize Key: IGNITE-14923 URL: https://issues.apache.org/jira/browse/IGNITE-14923 Project: Ignite Issue Type: Improvement Components: persistence Reporter: Kirill Tkalenko Assignee: Kirill Tkalenko Replacing system property *IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE* with public property *DataStorageConfiguration#minWalArchiveSize*, with a default value of 50% of DataStorageConfiguration#maxWalArchiveSize. Subtask from [discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Exceeding-the-DataStorageConfiguration-getMaxWalArchiveSize-due-to-historical-rebalance-td52546.html]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14923) Replace IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE to DataStorageConfiguration#minWalArchiveSize
[ https://issues.apache.org/jira/browse/IGNITE-14923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-14923: - Fix Version/s: 2.12 > Replace IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE to > DataStorageConfiguration#minWalArchiveSize > -- > > Key: IGNITE-14923 > URL: https://issues.apache.org/jira/browse/IGNITE-14923 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.12 > > > Replacing system property *IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE* with > public property *DataStorageConfiguration#minWalArchiveSize*, with a default > value of 50% of DataStorageConfiguration#maxWalArchiveSize. > Subtask from > [discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Exceeding-the-DataStorageConfiguration-getMaxWalArchiveSize-due-to-historical-rebalance-td52546.html]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14922) Change protocol from HTTP to HTTPS in url: http://ignite.apache.org
[
https://issues.apache.org/jira/browse/IGNITE-14922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Victor Alen'kov updated IGNITE-14922:
-
Reviewer: Alexey Goncharuk
> Change protocol from HTTP to HTTPS in url: http://ignite.apache.org
> ---
>
> Key: IGNITE-14922
> URL: https://issues.apache.org/jira/browse/IGNITE-14922
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.11
>Reporter: Victor Alen'kov
>Priority: Trivial
> Labels: maven
> Fix For: 2.11
>
>
> Currently Maven configuration uses an insecure protocol:
>
> {code:xml}
>
> http://ignite.apache.org
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-14922) Change protocol from HTTP to HTTPS in url: http://ignite.apache.org
[
https://issues.apache.org/jira/browse/IGNITE-14922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Victor Alen'kov updated IGNITE-14922:
-
Comment: was deleted
(was: PR: https://github.com/apache/ignite/pull/9179)
> Change protocol from HTTP to HTTPS in url: http://ignite.apache.org
> ---
>
> Key: IGNITE-14922
> URL: https://issues.apache.org/jira/browse/IGNITE-14922
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.11
>Reporter: Victor Alen'kov
>Priority: Trivial
> Labels: maven
> Fix For: 2.11
>
>
> Currently Maven configuration uses an insecure protocol:
>
> {code:xml}
>
> http://ignite.apache.org
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14922) Change protocol from HTTP to HTTPS in url: http://ignite.apache.org
[
https://issues.apache.org/jira/browse/IGNITE-14922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364871#comment-17364871
]
Victor Alen'kov commented on IGNITE-14922:
--
PR: https://github.com/apache/ignite/pull/9179
> Change protocol from HTTP to HTTPS in url: http://ignite.apache.org
> ---
>
> Key: IGNITE-14922
> URL: https://issues.apache.org/jira/browse/IGNITE-14922
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.11
>Reporter: Victor Alen'kov
>Priority: Trivial
> Labels: maven
>
> Currently Maven configuration uses an insecure protocol:
>
> {code:xml}
>
> http://ignite.apache.org
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14921) NPE in ClusterImpl on node start
[
https://issues.apache.org/jira/browse/IGNITE-14921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-14921:
---
Description:
{noformat}
2021-06-17 12:54:17:578 +0300 [main] INFO ITCliServiceTest - >>>
Start test method: testChangePeers
2021-06-17 12:54:17:578 +0300 [main] INFO ITCliServiceTest - >>>
Start test method: testChangePeers2021-06-17 12:54:26:228 +0300 [main] INFO
FSMCallerImpl - Starts FSMCaller successfully.2021-06-17 12:54:26:262 +0300
[main] WARN LocalSnapshotStorage - No data for snapshot reader
D:\work\ignite-3\modules\raft\jraft_test_1455162015862\192.168.0.107_5003\snapshot.
2021-06-17 12:54:26:276 +0300 [main] INFO NodeImpl - Node
init, term=0, lastLogId=LogId [index=0,
term=0],
conf=192.168.0.107:5003,192.168.0.107:5004,192.168.0.107:5005,192.168.0.107:5103/learner,192.168.0.107:5104/learner,
oldConf=.2021-06-17 12:54:27:224 +0300
[JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl - Node
term 0 start preVote.2021-06-17
12:54:27:477 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] ERROR
RepeatedTimer - Run timer failed.
java.lang.NullPointerException at
io.scalecube.cluster.ClusterImpl.requestResponse(ClusterImpl.java:419) at
org.apache.ignite.network.scalecube.ScaleCubeMessagingService.invoke(ScaleCubeMessagingService.java:123)
at
org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcClient.send(IgniteRpcClient.java:130)
at
org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcClient.invokeAsync(IgniteRpcClient.java:124)
at
org.apache.ignite.raft.jraft.rpc.impl.AbstractClientService.invokeWithDone(AbstractClientService.java:199)
at
org.apache.ignite.raft.jraft.rpc.impl.AbstractClientService.connect(AbstractClientService.java:130)
at org.apache.ignite.raft.jraft.core.NodeImpl.preVote(NodeImpl.java:2668) at
org.apache.ignite.raft.jraft.core.NodeImpl.handleElectionTimeout(NodeImpl.java:614)
at org.apache.ignite.raft.jraft.core.NodeImpl$2.onTrigger(NodeImpl.java:910)
at org.apache.ignite.raft.jraft.util.RepeatedTimer.run(RepeatedTimer.java:80)
at
org.apache.ignite.raft.jraft.util.RepeatedTimer.lambda$schedule$0(RepeatedTimer.java:177)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:577)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:649)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$Worker.run(HashedWheelTimer.java:383)
at java.base/java.lang.Thread.run(Thread.java:834)
2021-06-17 12:54:28:348 +0300 [main] INFO Cluster - [null][doStart] Starting,
config: ClusterConfig[metadata=null, metadataTimeout=1000,
metadataCodec=io.scalecube.cluster.metadata.JdkMetadataCodec@2eee3069,
memberAlias='192.168.0.107:5003', externalHost='null', externalPort=null,
transportConfig=TransportConfig[port=0, isSecured=false, connectTimeout=1000,
messageCodec=io.scalecube.cluster.transport.api.JdkMessageCodec@2da59753,
maxFrameLength=2097152,
transportFactory=org.apache.ignite.network.scalecube.DelegatingTransportFactory@5629510],
failureDetectorConfig=FailureDetectorConfig[pingInterval=500, pingTimeout=200,
pingReqMembers=1], gossipConfig=GossipConfig[gossipFanout=3, gossipInterval=10,
gossipRepeatMult=2, gossipSegmentationThreshold=1000],
membershipConfig=MembershipConfig[seedMembers=[192.168.0.107:5003,
192.168.0.107:5004, 192.168.0.107:5005], syncInterval=1000, syncTimeout=3000,
suspicionMult=1, namespace='default', removedMembersHistorySize=42]]
2021-06-17 12:54:28:501 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] INFO
NodeImpl - Node term 0 start preVote.
{noformat}
was:
{noformat}
2021-06-17 12:54:17:578 +0300 [main] INFO ITCliServiceTest - >>>
Start test method: testChangePeers2021-06-17 12:54:17:578 +0300 [main] INFO
ITCliServiceTest - >>> Start test method: testChangePeers2021-06-17
12:54:26:228 +0300 [main] INFO FSMCallerImpl - Starts FSMCaller
successfully.2021-06-17 12:54:26:262 +0300 [main] WARN LocalSnapshotStorage -
No data for snapshot reader
D:\work\ignite-3\modules\raft\jraft_test_1455162015862\192.168.0.107_5003\snapshot.2021-06-17
12:54:26:276 +0300 [main] INFO NodeImpl - Node
init, term=0, lastLogId=LogId [index=0,
term=0],
conf=192.168.0.107:5003,192.168.0.107:5004,192.168.0.107:5005,192.168.0.107:5103/learner,192.168.0.107:5104/learner,
oldConf=.2021-06-17 12:54:27:224 +0300
[JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl - Node
term 0 start preVote.2021-06-17
12:54:27:477 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] ERROR
RepeatedTimer - Run timer failed.java.lang.NullPointerException at
io.scalecube.cluster.ClusterImpl.requestResponse(ClusterImpl.java:419) at
org.apache.ignite.network.scalecube.ScaleCubeMessagingService.invoke(ScaleCubeMessagingService.java:123)
at
[jira] [Updated] (IGNITE-14889) Investigate options for thin client marshalling in 3.0
[ https://issues.apache.org/jira/browse/IGNITE-14889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-14889: Labels: iep-75 ignite-3 (was: iep-75) > Investigate options for thin client marshalling in 3.0 > -- > > Key: IGNITE-14889 > URL: https://issues.apache.org/jira/browse/IGNITE-14889 > Project: Ignite > Issue Type: Task > Components: thin client >Affects Versions: 3.0.0-alpha1 >Reporter: Igor Sapego >Assignee: Pavel Tupitsyn >Priority: Major > Labels: iep-75, ignite-3 > > We need to investigate available options for serialisation/deserialisation > for 3.0 thin client protocol and propose those options for discussion on the > dev list. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14921) NPE in ClusterImpl on node start
[
https://issues.apache.org/jira/browse/IGNITE-14921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-14921:
---
Description:
{noformat}
2021-06-17 12:54:17:578 +0300 [main] INFO ITCliServiceTest - >>>
Start test method: testChangePeers2021-06-17 12:54:17:578 +0300 [main] INFO
ITCliServiceTest - >>> Start test method: testChangePeers2021-06-17
12:54:26:228 +0300 [main] INFO FSMCallerImpl - Starts FSMCaller
successfully.2021-06-17 12:54:26:262 +0300 [main] WARN LocalSnapshotStorage -
No data for snapshot reader
D:\work\ignite-3\modules\raft\jraft_test_1455162015862\192.168.0.107_5003\snapshot.2021-06-17
12:54:26:276 +0300 [main] INFO NodeImpl - Node
init, term=0, lastLogId=LogId [index=0,
term=0],
conf=192.168.0.107:5003,192.168.0.107:5004,192.168.0.107:5005,192.168.0.107:5103/learner,192.168.0.107:5104/learner,
oldConf=.2021-06-17 12:54:27:224 +0300
[JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl - Node
term 0 start preVote.2021-06-17
12:54:27:477 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] ERROR
RepeatedTimer - Run timer failed.java.lang.NullPointerException at
io.scalecube.cluster.ClusterImpl.requestResponse(ClusterImpl.java:419) at
org.apache.ignite.network.scalecube.ScaleCubeMessagingService.invoke(ScaleCubeMessagingService.java:123)
at
org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcClient.send(IgniteRpcClient.java:130)
at
org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcClient.invokeAsync(IgniteRpcClient.java:124)
at
org.apache.ignite.raft.jraft.rpc.impl.AbstractClientService.invokeWithDone(AbstractClientService.java:199)
at
org.apache.ignite.raft.jraft.rpc.impl.AbstractClientService.connect(AbstractClientService.java:130)
at org.apache.ignite.raft.jraft.core.NodeImpl.preVote(NodeImpl.java:2668) at
org.apache.ignite.raft.jraft.core.NodeImpl.handleElectionTimeout(NodeImpl.java:614)
at org.apache.ignite.raft.jraft.core.NodeImpl$2.onTrigger(NodeImpl.java:910)
at org.apache.ignite.raft.jraft.util.RepeatedTimer.run(RepeatedTimer.java:80)
at
org.apache.ignite.raft.jraft.util.RepeatedTimer.lambda$schedule$0(RepeatedTimer.java:177)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:577)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:649)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$Worker.run(HashedWheelTimer.java:383)
at java.base/java.lang.Thread.run(Thread.java:834)2021-06-17 12:54:28:348
+0300 [main] INFO Cluster - [null][doStart] Starting, config:
ClusterConfig[metadata=null, metadataTimeout=1000,
metadataCodec=io.scalecube.cluster.metadata.JdkMetadataCodec@2eee3069,
memberAlias='192.168.0.107:5003', externalHost='null', externalPort=null,
transportConfig=TransportConfig[port=0, isSecured=false, connectTimeout=1000,
messageCodec=io.scalecube.cluster.transport.api.JdkMessageCodec@2da59753,
maxFrameLength=2097152,
transportFactory=org.apache.ignite.network.scalecube.DelegatingTransportFactory@5629510],
failureDetectorConfig=FailureDetectorConfig[pingInterval=500, pingTimeout=200,
pingReqMembers=1], gossipConfig=GossipConfig[gossipFanout=3, gossipInterval=10,
gossipRepeatMult=2, gossipSegmentationThreshold=1000],
membershipConfig=MembershipConfig[seedMembers=[192.168.0.107:5003,
192.168.0.107:5004, 192.168.0.107:5005], syncInterval=1000, syncTimeout=3000,
suspicionMult=1, namespace='default', removedMembersHistorySize=42]]2021-06-17
12:54:28:501 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl -
Node term 0 start preVote.{noformat}
was:
{noformat}
2021-06-17 12:54:17:578 +0300 [main] INFO ITCliServiceTest - >>>
Start test method: testChangePeers2021-06-17 12:54:17:578 +0300 [main] INFO
ITCliServiceTest - >>> Start test method: testChangePeers2021-06-17
12:54:26:228 +0300 [main] INFO FSMCallerImpl - Starts FSMCaller
successfully.2021-06-17 12:54:26:262 +0300 [main] WARN LocalSnapshotStorage -
No data for snapshot reader
D:\work\ignite-3\modules\raft\jraft_test_1455162015862\192.168.0.107_5003\snapshot.2021-06-17
12:54:26:276 +0300 [main] INFO NodeImpl - Node
init, term=0, lastLogId=LogId [index=0,
term=0],
conf=192.168.0.107:5003,192.168.0.107:5004,192.168.0.107:5005,192.168.0.107:5103/learner,192.168.0.107:5104/learner,
oldConf=.2021-06-17 12:54:27:224 +0300
[JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl - Node
term 0 start preVote.2021-06-17
12:54:27:477 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] ERROR
RepeatedTimer - Run timer failed.java.lang.NullPointerException at
io.scalecube.cluster.ClusterImpl.requestResponse(ClusterImpl.java:419) at
org.apache.ignite.network.scalecube.ScaleCubeMessagingService.invoke(ScaleCubeMessagingService.java:123)
at
[jira] [Updated] (IGNITE-14921) NPE in ClusterImpl on node start
[
https://issues.apache.org/jira/browse/IGNITE-14921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-14921:
---
Description:
{noformat}
2021-06-17 12:54:17:578 +0300 [main] INFO ITCliServiceTest - >>>
Start test method: testChangePeers2021-06-17 12:54:17:578 +0300 [main] INFO
ITCliServiceTest - >>> Start test method: testChangePeers2021-06-17
12:54:26:228 +0300 [main] INFO FSMCallerImpl - Starts FSMCaller
successfully.2021-06-17 12:54:26:262 +0300 [main] WARN LocalSnapshotStorage -
No data for snapshot reader
D:\work\ignite-3\modules\raft\jraft_test_1455162015862\192.168.0.107_5003\snapshot.2021-06-17
12:54:26:276 +0300 [main] INFO NodeImpl - Node
init, term=0, lastLogId=LogId [index=0,
term=0],
conf=192.168.0.107:5003,192.168.0.107:5004,192.168.0.107:5005,192.168.0.107:5103/learner,192.168.0.107:5104/learner,
oldConf=.2021-06-17 12:54:27:224 +0300
[JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl - Node
term 0 start preVote.2021-06-17
12:54:27:477 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] ERROR
RepeatedTimer - Run timer failed.java.lang.NullPointerException at
io.scalecube.cluster.ClusterImpl.requestResponse(ClusterImpl.java:419) at
org.apache.ignite.network.scalecube.ScaleCubeMessagingService.invoke(ScaleCubeMessagingService.java:123)
at
org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcClient.send(IgniteRpcClient.java:130)
at
org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcClient.invokeAsync(IgniteRpcClient.java:124)
at
org.apache.ignite.raft.jraft.rpc.impl.AbstractClientService.invokeWithDone(AbstractClientService.java:199)
at
org.apache.ignite.raft.jraft.rpc.impl.AbstractClientService.connect(AbstractClientService.java:130)
at org.apache.ignite.raft.jraft.core.NodeImpl.preVote(NodeImpl.java:2668) at
org.apache.ignite.raft.jraft.core.NodeImpl.handleElectionTimeout(NodeImpl.java:614)
at org.apache.ignite.raft.jraft.core.NodeImpl$2.onTrigger(NodeImpl.java:910)
at org.apache.ignite.raft.jraft.util.RepeatedTimer.run(RepeatedTimer.java:80)
at
org.apache.ignite.raft.jraft.util.RepeatedTimer.lambda$schedule$0(RepeatedTimer.java:177)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:577)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:649)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$Worker.run(HashedWheelTimer.java:383)
at java.base/java.lang.Thread.run(Thread.java:834)2021-06-17 12:54:28:348
+0300 [main] INFO Cluster - [null][doStart] Starting, config:
ClusterConfig[metadata=null, metadataTimeout=1000,
metadataCodec=io.scalecube.cluster.metadata.JdkMetadataCodec@2eee3069,
memberAlias='192.168.0.107:5003', externalHost='null', externalPort=null,
transportConfig=TransportConfig[port=0, isSecured=false, connectTimeout=1000,
messageCodec=io.scalecube.cluster.transport.api.JdkMessageCodec@2da59753,
maxFrameLength=2097152,
transportFactory=org.apache.ignite.network.scalecube.DelegatingTransportFactory@5629510],
failureDetectorConfig=FailureDetectorConfig[pingInterval=500, pingTimeout=200,
pingReqMembers=1], gossipConfig=GossipConfig[gossipFanout=3, gossipInterval=10,
gossipRepeatMult=2, gossipSegmentationThreshold=1000],
membershipConfig=MembershipConfig[seedMembers=[192.168.0.107:5003,
192.168.0.107:5004, 192.168.0.107:5005], syncInterval=1000, syncTimeout=3000,
suspicionMult=1, namespace='default', removedMembersHistorySize=42]]2021-06-17
12:54:28:501 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl -
Node term 0 start preVote. {noformat}
was:2021-06-17 12:54:17:578 +0300 [main] INFO ITCliServiceTest -
>>> Start test method: testChangePeers2021-06-17 12:54:17:578 +0300
[main] INFO ITCliServiceTest - >>> Start test method:
testChangePeers2021-06-17 12:54:26:228 +0300 [main] INFO FSMCallerImpl - Starts
FSMCaller successfully.2021-06-17 12:54:26:262 +0300 [main] WARN
LocalSnapshotStorage - No data for snapshot reader
D:\work\ignite-3\modules\raft\jraft_test_1455162015862\192.168.0.107_5003\snapshot.2021-06-17
12:54:26:276 +0300 [main] INFO NodeImpl - Node
init, term=0, lastLogId=LogId [index=0,
term=0],
conf=192.168.0.107:5003,192.168.0.107:5004,192.168.0.107:5005,192.168.0.107:5103/learner,192.168.0.107:5104/learner,
oldConf=.2021-06-17 12:54:27:224 +0300
[JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl - Node
term 0 start preVote.2021-06-17
12:54:27:477 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] ERROR
RepeatedTimer - Run timer failed.java.lang.NullPointerException at
io.scalecube.cluster.ClusterImpl.requestResponse(ClusterImpl.java:419) at
org.apache.ignite.network.scalecube.ScaleCubeMessagingService.invoke(ScaleCubeMessagingService.java:123)
at
[jira] [Updated] (IGNITE-14921) NPE in ClusterImpl on node start
[
https://issues.apache.org/jira/browse/IGNITE-14921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-14921:
---
Description: 2021-06-17 12:54:17:578 +0300 [main] INFO ITCliServiceTest -
>>> Start test method: testChangePeers2021-06-17 12:54:17:578 +0300
[main] INFO ITCliServiceTest - >>> Start test method:
testChangePeers2021-06-17 12:54:26:228 +0300 [main] INFO FSMCallerImpl - Starts
FSMCaller successfully.2021-06-17 12:54:26:262 +0300 [main] WARN
LocalSnapshotStorage - No data for snapshot reader
D:\work\ignite-3\modules\raft\jraft_test_1455162015862\192.168.0.107_5003\snapshot.2021-06-17
12:54:26:276 +0300 [main] INFO NodeImpl - Node
init, term=0, lastLogId=LogId [index=0,
term=0],
conf=192.168.0.107:5003,192.168.0.107:5004,192.168.0.107:5005,192.168.0.107:5103/learner,192.168.0.107:5104/learner,
oldConf=.2021-06-17 12:54:27:224 +0300
[JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl - Node
term 0 start preVote.2021-06-17
12:54:27:477 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] ERROR
RepeatedTimer - Run timer failed.java.lang.NullPointerException at
io.scalecube.cluster.ClusterImpl.requestResponse(ClusterImpl.java:419) at
org.apache.ignite.network.scalecube.ScaleCubeMessagingService.invoke(ScaleCubeMessagingService.java:123)
at
org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcClient.send(IgniteRpcClient.java:130)
at
org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcClient.invokeAsync(IgniteRpcClient.java:124)
at
org.apache.ignite.raft.jraft.rpc.impl.AbstractClientService.invokeWithDone(AbstractClientService.java:199)
at
org.apache.ignite.raft.jraft.rpc.impl.AbstractClientService.connect(AbstractClientService.java:130)
at org.apache.ignite.raft.jraft.core.NodeImpl.preVote(NodeImpl.java:2668) at
org.apache.ignite.raft.jraft.core.NodeImpl.handleElectionTimeout(NodeImpl.java:614)
at org.apache.ignite.raft.jraft.core.NodeImpl$2.onTrigger(NodeImpl.java:910)
at org.apache.ignite.raft.jraft.util.RepeatedTimer.run(RepeatedTimer.java:80)
at
org.apache.ignite.raft.jraft.util.RepeatedTimer.lambda$schedule$0(RepeatedTimer.java:177)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:577)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:649)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$Worker.run(HashedWheelTimer.java:383)
at java.base/java.lang.Thread.run(Thread.java:834)2021-06-17 12:54:28:348
+0300 [main] INFO Cluster - [null][doStart] Starting, config:
ClusterConfig[metadata=null, metadataTimeout=1000,
metadataCodec=io.scalecube.cluster.metadata.JdkMetadataCodec@2eee3069,
memberAlias='192.168.0.107:5003', externalHost='null', externalPort=null,
transportConfig=TransportConfig[port=0, isSecured=false, connectTimeout=1000,
messageCodec=io.scalecube.cluster.transport.api.JdkMessageCodec@2da59753,
maxFrameLength=2097152,
transportFactory=org.apache.ignite.network.scalecube.DelegatingTransportFactory@5629510],
failureDetectorConfig=FailureDetectorConfig[pingInterval=500, pingTimeout=200,
pingReqMembers=1], gossipConfig=GossipConfig[gossipFanout=3, gossipInterval=10,
gossipRepeatMult=2, gossipSegmentationThreshold=1000],
membershipConfig=MembershipConfig[seedMembers=[192.168.0.107:5003,
192.168.0.107:5004, 192.168.0.107:5005], syncInterval=1000, syncTimeout=3000,
suspicionMult=1, namespace='default', removedMembersHistorySize=42]]2021-06-17
12:54:28:501 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl -
Node term 0 start preVote. (was: {noformat}
2021-06-17 12:54:17:578 +0300 [main] INFO ITCliServiceTest - >>>
Start test method: testChangePeers2021-06-17 12:54:17:578 +0300 [main] INFO
ITCliServiceTest - >>> Start test method: testChangePeers2021-06-17
12:54:26:228 +0300 [main] INFO FSMCallerImpl - Starts FSMCaller
successfully.2021-06-17 12:54:26:262 +0300 [main] WARN LocalSnapshotStorage -
No data for snapshot reader
D:\work\ignite-3\modules\raft\jraft_test_1455162015862\192.168.0.107_5003\snapshot.2021-06-17
12:54:26:276 +0300 [main] INFO NodeImpl - Node
init, term=0, lastLogId=LogId [index=0,
term=0],
conf=192.168.0.107:5003,192.168.0.107:5004,192.168.0.107:5005,192.168.0.107:5103/learner,192.168.0.107:5104/learner,
oldConf=.2021-06-17 12:54:27:224 +0300
[JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl - Node
term 0 start preVote.2021-06-17
12:54:27:477 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] ERROR
RepeatedTimer - Run timer failed.java.lang.NullPointerException at
io.scalecube.cluster.ClusterImpl.requestResponse(ClusterImpl.java:419) at
org.apache.ignite.network.scalecube.ScaleCubeMessagingService.invoke(ScaleCubeMessagingService.java:123)
at
[jira] [Updated] (IGNITE-14921) NPE in ClusterImpl on node start
[
https://issues.apache.org/jira/browse/IGNITE-14921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-14921:
---
Description:
{noformat}
2021-06-17 12:54:17:578 +0300 [main] INFO ITCliServiceTest - >>>
Start test method: testChangePeers2021-06-17 12:54:17:578 +0300 [main] INFO
ITCliServiceTest - >>> Start test method: testChangePeers2021-06-17
12:54:26:228 +0300 [main] INFO FSMCallerImpl - Starts FSMCaller
successfully.2021-06-17 12:54:26:262 +0300 [main] WARN LocalSnapshotStorage -
No data for snapshot reader
D:\work\ignite-3\modules\raft\jraft_test_1455162015862\192.168.0.107_5003\snapshot.2021-06-17
12:54:26:276 +0300 [main] INFO NodeImpl - Node
init, term=0, lastLogId=LogId [index=0,
term=0],
conf=192.168.0.107:5003,192.168.0.107:5004,192.168.0.107:5005,192.168.0.107:5103/learner,192.168.0.107:5104/learner,
oldConf=.2021-06-17 12:54:27:224 +0300
[JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl - Node
term 0 start preVote.2021-06-17
12:54:27:477 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] ERROR
RepeatedTimer - Run timer failed.java.lang.NullPointerException at
io.scalecube.cluster.ClusterImpl.requestResponse(ClusterImpl.java:419) at
org.apache.ignite.network.scalecube.ScaleCubeMessagingService.invoke(ScaleCubeMessagingService.java:123)
at
org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcClient.send(IgniteRpcClient.java:130)
at
org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcClient.invokeAsync(IgniteRpcClient.java:124)
at
org.apache.ignite.raft.jraft.rpc.impl.AbstractClientService.invokeWithDone(AbstractClientService.java:199)
at
org.apache.ignite.raft.jraft.rpc.impl.AbstractClientService.connect(AbstractClientService.java:130)
at org.apache.ignite.raft.jraft.core.NodeImpl.preVote(NodeImpl.java:2668) at
org.apache.ignite.raft.jraft.core.NodeImpl.handleElectionTimeout(NodeImpl.java:614)
at org.apache.ignite.raft.jraft.core.NodeImpl$2.onTrigger(NodeImpl.java:910)
at org.apache.ignite.raft.jraft.util.RepeatedTimer.run(RepeatedTimer.java:80)
at
org.apache.ignite.raft.jraft.util.RepeatedTimer.lambda$schedule$0(RepeatedTimer.java:177)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:577)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:649)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$Worker.run(HashedWheelTimer.java:383)
at java.base/java.lang.Thread.run(Thread.java:834)2021-06-17 12:54:28:348
+0300 [main] INFO Cluster - [null][doStart] Starting, config:
ClusterConfig[metadata=null, metadataTimeout=1000,
metadataCodec=io.scalecube.cluster.metadata.JdkMetadataCodec@2eee3069,
memberAlias='192.168.0.107:5003', externalHost='null', externalPort=null,
transportConfig=TransportConfig[port=0, isSecured=false, connectTimeout=1000,
messageCodec=io.scalecube.cluster.transport.api.JdkMessageCodec@2da59753,
maxFrameLength=2097152,
transportFactory=org.apache.ignite.network.scalecube.DelegatingTransportFactory@5629510],
failureDetectorConfig=FailureDetectorConfig[pingInterval=500, pingTimeout=200,
pingReqMembers=1], gossipConfig=GossipConfig[gossipFanout=3, gossipInterval=10,
gossipRepeatMult=2, gossipSegmentationThreshold=1000],
membershipConfig=MembershipConfig[seedMembers=[192.168.0.107:5003,
192.168.0.107:5004, 192.168.0.107:5005], syncInterval=1000, syncTimeout=3000,
suspicionMult=1, namespace='default', removedMembersHistorySize=42]]2021-06-17
12:54:28:501 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl -
Node term 0 start preVote. {noformat}
was:
{noformat}
2021-06-17 12:54:17:578 +0300 [main] INFO ITCliServiceTest - >>>
Start test method: testChangePeers2021-06-17 12:54:17:578 +0300 [main] INFO
ITCliServiceTest - >>> Start test method: testChangePeers2021-06-17
12:54:26:228 +0300 [main] INFO FSMCallerImpl - Starts FSMCaller
successfully.2021-06-17 12:54:26:262 +0300 [main] WARN LocalSnapshotStorage -
No data for snapshot reader
D:\work\ignite-3\modules\raft\jraft_test_1455162015862\192.168.0.107_5003\snapshot.2021-06-17
12:54:26:276 +0300 [main] INFO NodeImpl - Node
init, term=0, lastLogId=LogId [index=0,
term=0],
conf=192.168.0.107:5003,192.168.0.107:5004,192.168.0.107:5005,192.168.0.107:5103/learner,192.168.0.107:5104/learner,
oldConf=.2021-06-17 12:54:27:224 +0300
[JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl - Node
term 0 start preVote.2021-06-17
12:54:27:477 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] ERROR
RepeatedTimer - Run timer failed.java.lang.NullPointerException at
io.scalecube.cluster.ClusterImpl.requestResponse(ClusterImpl.java:419) at
org.apache.ignite.network.scalecube.ScaleCubeMessagingService.invoke(ScaleCubeMessagingService.java:123)
at
[jira] [Created] (IGNITE-14922) Change protocol from HTTP to HTTPS in url: http://ignite.apache.org
Victor Alen'kov created IGNITE-14922:
Summary: Change protocol from HTTP to HTTPS in url:
http://ignite.apache.org
Key: IGNITE-14922
URL: https://issues.apache.org/jira/browse/IGNITE-14922
Project: Ignite
Issue Type: Task
Affects Versions: 2.11
Reporter: Victor Alen'kov
Currently Maven configuration uses an insecure protocol:
{code:xml}
http://ignite.apache.org
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14921) NPE in ClusterImpl on node start
Alexey Scherbakov created IGNITE-14921:
--
Summary: NPE in ClusterImpl on node start
Key: IGNITE-14921
URL: https://issues.apache.org/jira/browse/IGNITE-14921
Project: Ignite
Issue Type: Task
Reporter: Alexey Scherbakov
Fix For: 3.0.0-alpha3
{noformat}
2021-06-17 12:54:17:578 +0300 [main] INFO ITCliServiceTest - >>>
Start test method: testChangePeers2021-06-17 12:54:17:578 +0300 [main] INFO
ITCliServiceTest - >>> Start test method: testChangePeers2021-06-17
12:54:26:228 +0300 [main] INFO FSMCallerImpl - Starts FSMCaller
successfully.2021-06-17 12:54:26:262 +0300 [main] WARN LocalSnapshotStorage -
No data for snapshot reader
D:\work\ignite-3\modules\raft\jraft_test_1455162015862\192.168.0.107_5003\snapshot.2021-06-17
12:54:26:276 +0300 [main] INFO NodeImpl - Node
init, term=0, lastLogId=LogId [index=0,
term=0],
conf=192.168.0.107:5003,192.168.0.107:5004,192.168.0.107:5005,192.168.0.107:5103/learner,192.168.0.107:5104/learner,
oldConf=.2021-06-17 12:54:27:224 +0300
[JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl - Node
term 0 start preVote.2021-06-17
12:54:27:477 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] ERROR
RepeatedTimer - Run timer failed.java.lang.NullPointerException at
io.scalecube.cluster.ClusterImpl.requestResponse(ClusterImpl.java:419) at
org.apache.ignite.network.scalecube.ScaleCubeMessagingService.invoke(ScaleCubeMessagingService.java:123)
at
org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcClient.send(IgniteRpcClient.java:130)
at
org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcClient.invokeAsync(IgniteRpcClient.java:124)
at
org.apache.ignite.raft.jraft.rpc.impl.AbstractClientService.invokeWithDone(AbstractClientService.java:199)
at
org.apache.ignite.raft.jraft.rpc.impl.AbstractClientService.connect(AbstractClientService.java:130)
at org.apache.ignite.raft.jraft.core.NodeImpl.preVote(NodeImpl.java:2668) at
org.apache.ignite.raft.jraft.core.NodeImpl.handleElectionTimeout(NodeImpl.java:614)
at org.apache.ignite.raft.jraft.core.NodeImpl$2.onTrigger(NodeImpl.java:910)
at org.apache.ignite.raft.jraft.util.RepeatedTimer.run(RepeatedTimer.java:80)
at
org.apache.ignite.raft.jraft.util.RepeatedTimer.lambda$schedule$0(RepeatedTimer.java:177)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:577)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:649)
at
org.apache.ignite.raft.jraft.util.timer.HashedWheelTimer$Worker.run(HashedWheelTimer.java:383)
at java.base/java.lang.Thread.run(Thread.java:834)2021-06-17 12:54:28:348
+0300 [main] INFO Cluster - [null][doStart] Starting, config:
ClusterConfig[metadata=null, metadataTimeout=1000,
metadataCodec=io.scalecube.cluster.metadata.JdkMetadataCodec@2eee3069,
memberAlias='192.168.0.107:5003', externalHost='null', externalPort=null,
transportConfig=TransportConfig[port=0, isSecured=false, connectTimeout=1000,
messageCodec=io.scalecube.cluster.transport.api.JdkMessageCodec@2da59753,
maxFrameLength=2097152,
transportFactory=org.apache.ignite.network.scalecube.DelegatingTransportFactory@5629510],
failureDetectorConfig=FailureDetectorConfig[pingInterval=500, pingTimeout=200,
pingReqMembers=1], gossipConfig=GossipConfig[gossipFanout=3, gossipInterval=10,
gossipRepeatMult=2, gossipSegmentationThreshold=1000],
membershipConfig=MembershipConfig[seedMembers=[192.168.0.107:5003,
192.168.0.107:5004, 192.168.0.107:5005], syncInterval=1000, syncTimeout=3000,
suspicionMult=1, namespace='default', removedMembersHistorySize=42]]2021-06-17
12:54:28:501 +0300 [JRaft-ElectionTimer-192.168.0.107:5003-0] INFO NodeImpl -
Node term 0 start preVote.{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14849) Calcite engine. Support '%' operator as alias for 'mod' function
[
https://issues.apache.org/jira/browse/IGNITE-14849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364809#comment-17364809
]
Aleksey Plekhanov commented on IGNITE-14849:
[~zstan] thanks for the review! Merged to sql-calcite branch.
> Calcite engine. Support '%' operator as alias for 'mod' function
>
>
> Key: IGNITE-14849
> URL: https://issues.apache.org/jira/browse/IGNITE-14849
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, the H2-based SQL engine supports both {{a % b}} and {{mod(a, b)}}
> syntax for the modulo operation. But calcite-based engine supports only
> {{mod(a, b)}} syntax. Support for {{%}} operator should be added to minimize
> compatibility issues.
> Affected tests:
> {{src/test/sql/aggregate/group/test_group_by.test}}
> And many other.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14724) Calcite engine. Create table with DATE column creates INTEGER column
[
https://issues.apache.org/jira/browse/IGNITE-14724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364805#comment-17364805
]
Aleksey Plekhanov commented on IGNITE-14724:
[~korlov] thanks for the review! Merged to sql-calcite branch.
> Calcite engine. Create table with DATE column creates INTEGER column
>
>
> Key: IGNITE-14724
> URL: https://issues.apache.org/jira/browse/IGNITE-14724
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Reproducer:
> {code:java}
> sql("CREATE TABLE t(d DATE)", true);
> sql("INSERT INTO t VALUES (date '2021-01-01')", true);
> {code}
> Fails with:
> {noformat}
> org.apache.calcite.runtime.CalciteContextException: At line 0, column 0:
> Cannot assign to target field 'D' of type INTEGER from source field 'DATE
> '2021-01-01'' of type DATE{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14702) Inconsistency of the new index when the node falls / deactivates
[ https://issues.apache.org/jira/browse/IGNITE-14702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364801#comment-17364801 ] Stanilovsky Evgeny commented on IGNITE-14702: - [~ktkale...@gridgain.com] i left some comments, overall looks good. > Inconsistency of the new index when the node falls / deactivates > > > Key: IGNITE-14702 > URL: https://issues.apache.org/jira/browse/IGNITE-14702 > Project: Ignite > Issue Type: Bug > Components: persistence, sql >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > At the moment, if we add a new index and in the middle of its construction we > fall / deactivate a node, then it will be inconsistent and may create errors. > Need to either add a new index to DurableBackgroundTask, or add / modify a > separate mechanism that allows to resume the creation of a new index. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14918) "java.util.concurrent.RejectedExecutionException: event executor terminated" in test logs
[
https://issues.apache.org/jira/browse/IGNITE-14918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev reassigned IGNITE-14918:
Assignee: Aleksandr Polovtcev
> "java.util.concurrent.RejectedExecutionException: event executor terminated"
> in test logs
> -
>
> Key: IGNITE-14918
> URL: https://issues.apache.org/jira/browse/IGNITE-14918
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Minor
> Labels: ignite-3
>
> Sometimes when running tests (particularly tests related to JRaft, e.g.
> {{ITCliServiceTest}}{color:#00})), {color}the following message can be
> seen in logs. This can probably happen due to an invalid shutdown order - we
> are closing the Netty event loop and are trying to send a message afterwards.
> {code:java}
> 2021-06-16 18:47:09:864 +0300 [main] WARN AbstractChannel - Force-closing a
> channel whose registration task was not accepted by an event loop: [id:
> 0x74fc195f]
> java.util.concurrent.RejectedExecutionException: event executor terminated
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.reject(SingleThreadEventExecutor.java:926)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.offerTask(SingleThreadEventExecutor.java:353)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.addTask(SingleThreadEventExecutor.java:346)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.execute(SingleThreadEventExecutor.java:828)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.execute(SingleThreadEventExecutor.java:818)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.register(AbstractChannel.java:471)
> at
> io.netty.channel.SingleThreadEventLoop.register(SingleThreadEventLoop.java:87)
> at
> io.netty.channel.SingleThreadEventLoop.register(SingleThreadEventLoop.java:81)
> at
> io.netty.channel.MultithreadEventLoopGroup.register(MultithreadEventLoopGroup.java:86)
> at
> io.netty.bootstrap.AbstractBootstrap.initAndRegister(AbstractBootstrap.java:323)
> at io.netty.bootstrap.Bootstrap.doResolveAndConnect(Bootstrap.java:155)
> at io.netty.bootstrap.Bootstrap.connect(Bootstrap.java:139)
> at
> org.apache.ignite.internal.network.netty.NettyClient.start(NettyClient.java:119)
> at
> org.apache.ignite.internal.network.netty.ConnectionManager.connect(ConnectionManager.java:210)
> at
> org.apache.ignite.internal.network.netty.ConnectionManager.lambda$channel$1(ConnectionManager.java:167)
> at
> java.base/java.util.concurrent.ConcurrentHashMap.compute(ConcurrentHashMap.java:1932)
> at
> org.apache.ignite.internal.network.netty.ConnectionManager.channel(ConnectionManager.java:165)
> at
> org.apache.ignite.network.scalecube.ScaleCubeDirectMarshallerTransport.lambda$send$4(ScaleCubeDirectMarshallerTransport.java:171)
> at reactor.core.publisher.Mono.lambda$fromFuture$1(Mono.java:508)
> at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:44)
> at reactor.core.publisher.Mono.subscribe(Mono.java:4219)
> at reactor.core.publisher.Mono.subscribeWith(Mono.java:4330)
> at reactor.core.publisher.Mono.subscribe(Mono.java:4190)
> at reactor.core.publisher.Mono.subscribe(Mono.java:4126)
> at reactor.core.publisher.Mono.subscribe(Mono.java:4098)
> at
> org.apache.ignite.network.scalecube.ScaleCubeDirectMarshallerTransport.lambda$requestResponse$8(ScaleCubeDirectMarshallerTransport.java:255)
> at reactor.core.publisher.MonoCreate.subscribe(MonoCreate.java:57)
> at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52)
> at reactor.core.publisher.Mono.subscribe(Mono.java:4219)
> at reactor.core.publisher.Mono.subscribeWith(Mono.java:4330)
> at reactor.core.publisher.Mono.toFuture(Mono.java:4664)
> at
> org.apache.ignite.network.scalecube.ScaleCubeMessagingService.invoke(ScaleCubeMessagingService.java:125)
> at
> org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcClient.send(IgniteRpcClient.java:165)
> at
> org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcClient.invokeAsync(IgniteRpcClient.java:161)
> at
> org.apache.ignite.raft.jraft.rpc.impl.AbstractClientService.invokeWithDone(AbstractClientService.java:182)
> at
> org.apache.ignite.raft.jraft.rpc.impl.AbstractClientService.invokeWithDone(AbstractClientService.java:156)
> at
> org.apache.ignite.raft.jraft.rpc.impl.AbstractClientService.invokeWithDone(AbstractClientService.java:150)
> at
> org.apache.ignite.raft.jraft.rpc.impl.core.DefaultRaftClientService.timeoutNow(DefaultRaftClientService.java:118)
> at
>
[jira] [Assigned] (IGNITE-14920) Implement Spring Sessions Support
[ https://issues.apache.org/jira/browse/IGNITE-14920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Atri Sharma reassigned IGNITE-14920: Assignee: Atri Sharma > Implement Spring Sessions Support > - > > Key: IGNITE-14920 > URL: https://issues.apache.org/jira/browse/IGNITE-14920 > Project: Ignite > Issue Type: Bug > Components: extensions >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > > This Jira tracks the effort to implement Spring Sessions using Ignite as the > backing data store. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14920) Implement Spring Sessions Support
Atri Sharma created IGNITE-14920: Summary: Implement Spring Sessions Support Key: IGNITE-14920 URL: https://issues.apache.org/jira/browse/IGNITE-14920 Project: Ignite Issue Type: Bug Components: extensions Reporter: Atri Sharma This Jira tracks the effort to implement Spring Sessions using Ignite as the backing data store. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13549) Calcite integration. CREATE/DROP INDEX support
[ https://issues.apache.org/jira/browse/IGNITE-13549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364708#comment-17364708 ] Stanilovsky Evgeny commented on IGNITE-13549: - looks good. > Calcite integration. CREATE/DROP INDEX support > -- > > Key: IGNITE-13549 > URL: https://issues.apache.org/jira/browse/IGNITE-13549 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Aleksey Plekhanov >Priority: Critical > Time Spent: 10m > Remaining Estimate: 0h > > We need to support DDL commands. The task about the support of CREATE/DROP > INDEX. Potentially with syntaxis as we already have in the H2 engine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
