[jira] [Commented] (IGNITE-17734) CorruptedFreeListException after upgrade to 2.13.0 and JDK17
[ https://issues.apache.org/jira/browse/IGNITE-17734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622956#comment-17622956 ] YuJue Li commented on IGNITE-17734: --- [~Lopata] What version of JDK do you use? OpenJDK or others? What JVM parameters are configured? > CorruptedFreeListException after upgrade to 2.13.0 and JDK17 > > > Key: IGNITE-17734 > URL: https://issues.apache.org/jira/browse/IGNITE-17734 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.13 > Environment: JDK17, IGNITE 2.13.0 >Reporter: Lopata >Priority: Blocker > Attachments: stacktrace.txt > > > After migration to Ignite version 2.13.0 from 2.12.0 we are getting following > error: > org.apache.ignite.internal.processors.cache.persistence.freelist.CorruptedFreeListException: > Failed to insert data row > caused by: > Caused by: java.lang.IllegalStateException: Tail not found: 0 > > Full stack trace is in attachment. Along with the Ignite version upgrade, we > are updating Java from 11 to 17. There have been no other changes in our code > or IGNITE configurations. The error occurs after a few hours of running and > then occurs for every store. > Can you help us to to solve this problem. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17754) Display useful information for the user on node start
[ https://issues.apache.org/jira/browse/IGNITE-17754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr reassigned IGNITE-17754: -- Assignee: Aleksandr > Display useful information for the user on node start > - > > Key: IGNITE-17754 > URL: https://issues.apache.org/jira/browse/IGNITE-17754 > Project: Ignite > Issue Type: Task > Components: cli, rest >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: ignite-3 > > There should be a clear way for the user how to connect to the node from cli > after it is started. Now there is nothing displayed after the node started. > I would like to recommend displaying something like: "Ignite 3 node started. > Use ignite3-cli command to connect to the node. 'ignite connect > http://localhost:10300;. > Note that there is no easy way to understand what port REST server is running > on. So, this is part of this ticket to develop the mechanism of propagating > the REST port. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17773) Remove node start/stop/list commands
[ https://issues.apache.org/jira/browse/IGNITE-17773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622886#comment-17622886 ] Stanislav Lukyanov commented on IGNITE-17773: - Sure, that's what I meant - since this is already in the main, we should include it. > Remove node start/stop/list commands > > > Key: IGNITE-17773 > URL: https://issues.apache.org/jira/browse/IGNITE-17773 > Project: Ignite > Issue Type: Task > Components: cli >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta1 > > Time Spent: 20m > Remaining Estimate: 0h > > Now, ignite3 node start/stop/restart managements are done through a special > script that is provided by the distribution. CLI commands: node start, node > stop, node list, and bootstrap now do not make any sense. We have to remove > them because they do not work if a user has started a node with a startup > script. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17954) Store checkstyle and codestyle configuration in idea configuration files
[ https://issues.apache.org/jira/browse/IGNITE-17954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semyon Danilov updated IGNITE-17954: Description: ATM, checkstyle in IntelliJ IDEA must be configured manually (which can lead to different counterintuitive errors if selected checkstyle version is too old or too new). Also, the code style is stored under the VCS but is not imported by default. We can leverage IDEA's configuration files to make checkstyle and codestyle settings load by default > Store checkstyle and codestyle configuration in idea configuration files > > > Key: IGNITE-17954 > URL: https://issues.apache.org/jira/browse/IGNITE-17954 > Project: Ignite > Issue Type: Improvement >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > > ATM, checkstyle in IntelliJ IDEA must be configured manually (which can lead > to different counterintuitive errors if selected checkstyle version is too > old or too new). Also, the code style is stored under the VCS but is not > imported by default. We can leverage IDEA's configuration files to make > checkstyle and codestyle settings load by default -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17954) Store checkstyle and codestyle configuration in idea configuration files
Semyon Danilov created IGNITE-17954: --- Summary: Store checkstyle and codestyle configuration in idea configuration files Key: IGNITE-17954 URL: https://issues.apache.org/jira/browse/IGNITE-17954 Project: Ignite Issue Type: Improvement Reporter: Semyon Danilov Assignee: Semyon Danilov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-17773) Remove node start/stop/list commands
[ https://issues.apache.org/jira/browse/IGNITE-17773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622764#comment-17622764 ] Vyacheslav Koptilin edited comment on IGNITE-17773 at 10/23/22 9:19 AM: Hello [~slukyanov], I took a look at this patch. I agree that this task is not a blocker for beta1. On the other hand, it can be merged right now without any issues. I would propose to include this ticket in the release. was (Author: slava.koptilin): Hello [~slukyanov], I took a look at this patch. I agree that this task is a blocker for beta1. On the other hand, it can be merged right now without any issues. I would propose to include this ticket in the release. > Remove node start/stop/list commands > > > Key: IGNITE-17773 > URL: https://issues.apache.org/jira/browse/IGNITE-17773 > Project: Ignite > Issue Type: Task > Components: cli >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta1 > > Time Spent: 20m > Remaining Estimate: 0h > > Now, ignite3 node start/stop/restart managements are done through a special > script that is provided by the distribution. CLI commands: node start, node > stop, node list, and bootstrap now do not make any sense. We have to remove > them because they do not work if a user has started a node with a startup > script. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17773) Remove node start/stop/list commands
[ https://issues.apache.org/jira/browse/IGNITE-17773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622764#comment-17622764 ] Vyacheslav Koptilin commented on IGNITE-17773: -- Hello [~slukyanov], I took a look at this patch. I agree that this task is a blocker for beta1. On the other hand, it can be merged right now without any issues. I would propose to include this ticket in the release. > Remove node start/stop/list commands > > > Key: IGNITE-17773 > URL: https://issues.apache.org/jira/browse/IGNITE-17773 > Project: Ignite > Issue Type: Task > Components: cli >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta1 > > Time Spent: 20m > Remaining Estimate: 0h > > Now, ignite3 node start/stop/restart managements are done through a special > script that is provided by the distribution. CLI commands: node start, node > stop, node list, and bootstrap now do not make any sense. We have to remove > them because they do not work if a user has started a node with a startup > script. -- This message was sent by Atlassian Jira (v8.20.10#820010)
