[jira] [Created] (IGNITE-5612) JdbcResultSet#next is fetching all the data into memory and fetch size is used only to data-column mapping
Anil Dasari created IGNITE-5612: --- Summary: JdbcResultSet#next is fetching all the data into memory and fetch size is used only to data-column mapping Key: IGNITE-5612 URL: https://issues.apache.org/jira/browse/IGNITE-5612 Project: Ignite Issue Type: Bug Affects Versions: 1.9 Reporter: Anil Dasari GridReduceQueryExecutor is fetching all the records and then returns the results as per fetch results. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-5611: Assignee: Dmitriy Shabalin (was: Alexey Kuznetsov) Looks good for me. Dima, please also review. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Dmitriy Shabalin >Priority: Minor > Attachments: new-select-look.PNG, old select look.PNG > > > Update all selects that look [like this|^new-select-look.PNG] to look [like > that|^old select look.PNG]. > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. > During testing, please make sure that *all* places that use bs-select > directive don't have regressions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-5611: Assignee: Alexey Kuznetsov (was: Ilya Borisov) Please review. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Attachments: new-select-look.PNG, old select look.PNG > > > Update all selects that look [like this|^new-select-look.PNG] to look [like > that|^old select look.PNG]. > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. > During testing, please make sure that *all* places that use bs-select > directive don't have regressions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look [like this|^new-select-look.PNG] to look [like that|^old select look.PNG]. Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. During testing, please make sure that *all* places that use bs-select directive don't have regressions. was: Update all selects that look [like this|^new-select-look.PNG] to look [like that|^old select look.PNG]. Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new-select-look.PNG, old select look.PNG > > > Update all selects that look [like this|^new-select-look.PNG] to look [like > that|^old select look.PNG]. > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. > During testing, please make sure that *all* places that use bs-select > directive don't have regressions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look [like this|^new-select-look.PNG] to look [like that|^old select look.PNG]. Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look [like this|^new-select-look.PNG] to look [^old select look.PNG]. Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new-select-look.PNG, old select look.PNG > > > Update all selects that look [like this|^new-select-look.PNG] to look [like > that|^old select look.PNG]. > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look [^new-select-look.PNG|like this] to look [^old select look.PNG]. Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look [^new-select-look.PNG] to look [^old select look.PNG]. Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new-select-look.PNG, old select look.PNG > > > Update all selects that look [^new-select-look.PNG|like this] to look [^old > select look.PNG]. > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look [like this|^new-select-look.PNG] to look [^old select look.PNG]. Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look [^new-select-look.PNG|like this] to look [^old select look.PNG]. Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new-select-look.PNG, old select look.PNG > > > Update all selects that look [like this|^new-select-look.PNG] to look [^old > select look.PNG]. > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look [^new-select-look.PNG] To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: !new-select-look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new-select-look.PNG, old select look.PNG > > > Update all selects that look [^new-select-look.PNG] > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look [^new-select-look.PNG] to look [^old select look.PNG]. Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look [^new-select-look.PNG] To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new-select-look.PNG, old select look.PNG > > > Update all selects that look [^new-select-look.PNG] to look [^old select > look.PNG]. > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: !new-select-look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: !new select look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new-select-look.PNG, old select look.PNG > > > Update all selects that look like this: > !new-select-look.PNG|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Attachment: new-select-look.PNG > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new-select-look.PNG, old select look.PNG > > > Update all selects that look like this: > !new select look.PNG|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Attachment: (was: new select look.PNG) > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: old select look.PNG > > > Update all selects that look like this: > !new select look.PNG|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: !new select look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: !^new select look.png|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > > Update all selects that look like this: > !new select look.PNG|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: !^new select look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: [^new select look.PNG] To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > > Update all selects that look like this: > !^new select look.PNG|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: !^new select look.png|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: !^new select look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > > Update all selects that look like this: > !^new select look.png|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: [^new select look.PNG] To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: !old select look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > > Update all selects that look like this: > [^new select look.PNG] > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: !old select look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: !old%20select%20look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > > Update all selects that look like this: > !old select look.PNG|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: !old%20select%20look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: !old select look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > > Update all selects that look like this: > !old%20select%20look.PNG|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: !old select look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: !12874997|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > > Update all selects that look like this: > !old select look.PNG|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: !https://issues.apache.org/jira/secure/attachment/12874997/old%20select%20look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > > Update all selects that look like this: > !https://issues.apache.org/jira/secure/attachment/12874997/old%20select%20look.PNG|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: !12874997|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: !old%20select%20look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > > Update all selects that look like this: > !12874997|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: !old%20select%20look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: !https://issues.apache.org/jira/secure/attachment/12874997/old%20select%20look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > > Update all selects that look like this: > !old%20select%20look.PNG|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: !old%20select%20look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > > Update all selects that look like this: > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: !old%20select%20look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: !old-select-look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > > Update all selects that look like this: > !old%20select%20look.PNG|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: !old-select-look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: !old select look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > > Update all selects that look like this: > !old-select-look.PNG|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: !old select look.PNG|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. was: Update all selects that look like this: !attachment-name.jpg|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > > Update all selects that look like this: > !old select look.PNG|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Description: Update all selects that look like this: !attachment-name.jpg|thumbnail! To look like that: [] Notable changes: 1. Add "All" default option to top of the menu. It should be unchecked when no items are selected. It should be checked when all items are selected. When all items are selected, click on "all" should unselect all items. When some items are selected, "all" click should select all items. 2. Selected checkbox icon should be of brand blue color. Unselected icons are grey. Checkmark icon might look slightly different from new design, we will sync checkbox implementations/design in a separate task anyway. > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > > Update all selects that look like this: > !attachment-name.jpg|thumbnail! > To look like that: > [] > Notable changes: > 1. Add "All" default option to top of the menu. It should be unchecked when > no items are selected. It should be checked when all items are selected. When > all items are selected, click on "all" should unselect all items. When some > items are selected, "all" click should select all items. > 2. Selected checkbox icon should be of brand blue color. Unselected icons are > grey. Checkmark icon might look slightly different from new design, we will > sync checkbox implementations/design in a separate task anyway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5611) Web Console: update some of selects to new design
Ilya Borisov created IGNITE-5611: Summary: Web Console: update some of selects to new design Key: IGNITE-5611 URL: https://issues.apache.org/jira/browse/IGNITE-5611 Project: Ignite Issue Type: Sub-task Components: UI, wizards Reporter: Ilya Borisov Assignee: Ilya Borisov Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5611) Web Console: update some of selects to new design
[ https://issues.apache.org/jira/browse/IGNITE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-5611: - Attachment: new select look.PNG old select look.PNG > Web Console: update some of selects to new design > - > > Key: IGNITE-5611 > URL: https://issues.apache.org/jira/browse/IGNITE-5611 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: new select look.PNG, old select look.PNG > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (IGNITE-5601) WriteBehind mode hide SQLExceptions
[ https://issues.apache.org/jira/browse/IGNITE-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shtykh closed IGNITE-5601. > WriteBehind mode hide SQLExceptions > --- > > Key: IGNITE-5601 > URL: https://issues.apache.org/jira/browse/IGNITE-5601 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Affects Versions: 2.0 > Environment: Ignite 2.0.0 > Oracle JDK 1.8.0_121 > Derby 10.13.1.1 >Reporter: Benjamin Garaude >Assignee: Roman Shtykh > Fix For: 2.0 > > > If an exception, e.g. SQLException occurs during a wite-behind operation, the > exception is lost and appears nowhere in the logs. > The logs basically say: > [2017-06-28 10:48:52] SEVERE: Unable to update underlying store: > CacheJdbcPojoStore [] > [2017-06-28 10:48:52] WARNING: Failed to update store (value will be lost as > current buffer size is greater than 'cacheCriticalSize' or node has been > stopped before store was repaired) [key=test.WriteBehindIssue$FooKey > [idHash=524852907, hash=-1388553726, id=1], val=test.WriteBehindIssue$Foo > [idHash=323347362, hash=574522785, value1=abcd, value2=1234], op=PUT] > If we do the same with write-through mode, it fails by throwing an exception > with the SQLException as cause, deep in the trace. > Would it be possible the write-behind operation logs the SQLException, and > other exception? > You can find a test case showing that here: > https://github.com/bgaraude/IgniteTest -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5601) WriteBehind mode hide SQLExceptions
[ https://issues.apache.org/jira/browse/IGNITE-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shtykh reassigned IGNITE-5601: Assignee: Roman Shtykh > WriteBehind mode hide SQLExceptions > --- > > Key: IGNITE-5601 > URL: https://issues.apache.org/jira/browse/IGNITE-5601 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Affects Versions: 2.0 > Environment: Ignite 2.0.0 > Oracle JDK 1.8.0_121 > Derby 10.13.1.1 >Reporter: Benjamin Garaude >Assignee: Roman Shtykh > Fix For: 2.0 > > > If an exception, e.g. SQLException occurs during a wite-behind operation, the > exception is lost and appears nowhere in the logs. > The logs basically say: > [2017-06-28 10:48:52] SEVERE: Unable to update underlying store: > CacheJdbcPojoStore [] > [2017-06-28 10:48:52] WARNING: Failed to update store (value will be lost as > current buffer size is greater than 'cacheCriticalSize' or node has been > stopped before store was repaired) [key=test.WriteBehindIssue$FooKey > [idHash=524852907, hash=-1388553726, id=1], val=test.WriteBehindIssue$Foo > [idHash=323347362, hash=574522785, value1=abcd, value2=1234], op=PUT] > If we do the same with write-through mode, it fails by throwing an exception > with the SQLException as cause, deep in the trace. > Would it be possible the write-behind operation logs the SQLException, and > other exception? > You can find a test case showing that here: > https://github.com/bgaraude/IgniteTest -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5610) MySQL Time Machine and Ignite Integration
Denis Magda created IGNITE-5610: --- Summary: MySQL Time Machine and Ignite Integration Key: IGNITE-5610 URL: https://issues.apache.org/jira/browse/IGNITE-5610 Project: Ignite Issue Type: Task Reporter: Denis Magda There are scenarios when a relational database like MySQL is used as a persistent store by Ignite and, at the same time, the database is being updated directly by some other application. This happens when a company migrates from a pure RDBMS based architecture to Ignite as a primary in-memory storage. During the migration, some of the applications might already work with Ignite (which will keep MySQL in sync) while the others can still interact with MySQL directly. If this is the case, then there has to be a way to propagate all the updates happened at MySQL level and caused by direct application calls to Ignite. As one of the solution, Ignite can be integrated with MySQL Time Machine that can send all such updates to the cluster. https://mysql-time-machine.github.io Read more in this discussion on the dev list: http://apache-ignite-developers.2346864.n4.nabble.com/Re-External-Re-Triggering-cache-updates-in-Ignite-td19193.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5609) Geo-spatial indexes implementation for off-heap memory architecture
Denis Magda created IGNITE-5609: --- Summary: Geo-spatial indexes implementation for off-heap memory architecture Key: IGNITE-5609 URL: https://issues.apache.org/jira/browse/IGNITE-5609 Project: Ignite Issue Type: Task Reporter: Denis Magda Geo-spatial indexes have to be stored in off-heap region of the new memory architecture. Both RAM and disk have to be supported. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5608) SQL scripts execution capability
Denis Magda created IGNITE-5608: --- Summary: SQL scripts execution capability Key: IGNITE-5608 URL: https://issues.apache.org/jira/browse/IGNITE-5608 Project: Ignite Issue Type: Task Reporter: Denis Magda There should be a way to feed an SQL script to Ignite and execute it right away. A script can consist of DDL command that will define cluster and SQL configuration as well as of DML commands that, for instance, preload data into Ignite. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5607) HttpSessionBindingListener is not supported for clustered web session
Valentin Kulichenko created IGNITE-5607:
---
Summary: HttpSessionBindingListener is not supported for clustered
web session
Key: IGNITE-5607
URL: https://issues.apache.org/jira/browse/IGNITE-5607
Project: Ignite
Issue Type: Bug
Components: websession
Affects Versions: 2.0
Reporter: Valentin Kulichenko
Fix For: 2.1
Ignite's implementation of {{HttpSession}} ignores values implementing
{{HttpSessionBindingListener}}.
{{WebSession#setAttribute}} and {{WebSession#removeAttribute}} should be
modified accordingly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5114) Parallel plus/multiply matrix algorithms.
[ https://issues.apache.org/jira/browse/IGNITE-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Ignatenko updated IGNITE-5114: --- Summary: Parallel plus/multiply matrix algorithms. (was: Parallalel plus/multiply matrix algorithms.) > Parallel plus/multiply matrix algorithms. > - > > Key: IGNITE-5114 > URL: https://issues.apache.org/jira/browse/IGNITE-5114 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Yury Babak >Assignee: Yury Babak > Labels: important > Fix For: 2.2 > > > We need design and implement parallel(distributed?) versions of matrix > plus/multiply algorithms because current implementation is implemented by > definition. Those implementations is really slow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-4991) Do not print out system properties when IGNITE_TO_STRING_INCLUDE_SENSITIVE is set
[
https://issues.apache.org/jira/browse/IGNITE-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16067020#comment-16067020
]
Konstantin Boudnik commented on IGNITE-4991:
Shouldn't this be closed after the PR has been fixed?
> Do not print out system properties when IGNITE_TO_STRING_INCLUDE_SENSITIVE is
> set
> -
>
> Key: IGNITE-4991
> URL: https://issues.apache.org/jira/browse/IGNITE-4991
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 1.9
>Reporter: Valentin Kulichenko
>Assignee: Alexei Kaigorodov
> Labels: newbie
> Fix For: 2.1
>
>
> {{IgniteKernal#ackSystemProperties}} and {{IgniteKernal#ackVmArguments}}
> print out system properties that can contain sensitive data. This print outs
> should be disabled when {{IGNITE_TO_STRING_INCLUDE_SENSITIVE}} system
> property is set to {{true}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-5535) BLAS support for offheap vector/matrix
[ https://issues.apache.org/jira/browse/IGNITE-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064995#comment-16064995 ] Oleg Ignatenko edited comment on IGNITE-5535 at 6/28/17 5:27 PM: - briefly discussed this JIRA with Yury: looks like we've got two options to consider - either we do it all at Ignite side or additionally make some modifications in [BLAS|https://en.wikipedia.org/wiki/Basic_Linear_Algebra_Subprograms] ([netlib-java|https://github.com/fommil/netlib-java]). The open question for the latter is whether it's feasible licensing wise (BLAS is probably LGPL(?)). Also Yury suspects that [CacheUtils|https://github.com/apache/ignite/blob/master/modules/ml/src/main/java/org/apache/ignite/ml/math/impls/CacheUtils.java] may need to be rather heavily reworked along the way was (Author: oignatenko): briefly discussed this JIRA with Yury: looks like we've got two options to consider - either we do it all at Ignite side or additionally make some modifications in [BLAS|https://en.wikipedia.org/wiki/Basic_Linear_Algebra_Subprograms]. The open question for the latter is whether it's feasible licensing wise (BLAS is LGPL). Also Yury suspects that [CacheUtils|https://github.com/apache/ignite/blob/master/modules/ml/src/main/java/org/apache/ignite/ml/math/impls/CacheUtils.java] may need to be rather heavily reworked along the way > BLAS support for offheap vector/matrix > -- > > Key: IGNITE-5535 > URL: https://issues.apache.org/jira/browse/IGNITE-5535 > Project: Ignite > Issue Type: Task > Components: ml >Reporter: Yury Babak >Assignee: Oleg Ignatenko > > We want to add BLAS support for offheap stuctures. Current we implement only > onheap version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5498) Failures in GridNioSslSelfTest
[
https://issues.apache.org/jira/browse/IGNITE-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin reassigned IGNITE-5498:
---
Assignee: Semen Boikov (was: Vyacheslav Koptilin)
> Failures in GridNioSslSelfTest
> --
>
> Key: IGNITE-5498
> URL: https://issues.apache.org/jira/browse/IGNITE-5498
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Vladimir Ozerov
>Assignee: Semen Boikov
> Labels: test-fail
> Fix For: 2.1
>
>
> Affected tests:
> {{GridNioSslSelfTest.testConcurrentConnects}}
> {{GridNioSslSelfTest.testSimpleMessages}}
> {code}
> junit.framework.AssertionFailedError: Unexpected exception occurred while
> handling connection: class
> org.apache.ignite.internal.util.nio.GridNioException: An established
> connection was aborted by the software in your host machine
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> org.apache.ignite.internal.util.nio.GridNioSelfTest$EchoListener.onDisconnected(GridNioSelfTest.java:1361)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onExceptionCaught(GridNioFilterChain.java:261)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedExceptionCaught(GridNioFilterAdapter.java:102)
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onExceptionCaught(GridNioCodecFilter.java:80)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedExceptionCaught(GridNioFilterAdapter.java:102)
> at
> org.apache.ignite.internal.util.nio.ssl.GridNioSslFilter.onExceptionCaught(GridNioSslFilter.java:241)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedExceptionCaught(GridNioFilterAdapter.java:102)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onExceptionCaught(GridNioServer.java:3188)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onExceptionCaught(GridNioFilterChain.java:160)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.close(GridNioServer.java:2437)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2199)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1968)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1669)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5498) Failures in GridNioSslSelfTest
[
https://issues.apache.org/jira/browse/IGNITE-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066873#comment-16066873
]
Vyacheslav Koptilin commented on IGNITE-5498:
-
This issue is reproduced on Windows 10 (Oracle jdk 1.8.0_131)
TC build is available here:
http://ci.ignite.apache.org/viewLog.html?buildId=692891&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteBasic
On the other hand, I cannot reproduce the failure on Linux.
> Failures in GridNioSslSelfTest
> --
>
> Key: IGNITE-5498
> URL: https://issues.apache.org/jira/browse/IGNITE-5498
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Koptilin
> Labels: test-fail
> Fix For: 2.1
>
>
> Affected tests:
> {{GridNioSslSelfTest.testConcurrentConnects}}
> {{GridNioSslSelfTest.testSimpleMessages}}
> {code}
> junit.framework.AssertionFailedError: Unexpected exception occurred while
> handling connection: class
> org.apache.ignite.internal.util.nio.GridNioException: An established
> connection was aborted by the software in your host machine
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> org.apache.ignite.internal.util.nio.GridNioSelfTest$EchoListener.onDisconnected(GridNioSelfTest.java:1361)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onExceptionCaught(GridNioFilterChain.java:261)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedExceptionCaught(GridNioFilterAdapter.java:102)
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onExceptionCaught(GridNioCodecFilter.java:80)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedExceptionCaught(GridNioFilterAdapter.java:102)
> at
> org.apache.ignite.internal.util.nio.ssl.GridNioSslFilter.onExceptionCaught(GridNioSslFilter.java:241)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedExceptionCaught(GridNioFilterAdapter.java:102)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onExceptionCaught(GridNioServer.java:3188)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onExceptionCaught(GridNioFilterChain.java:160)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.close(GridNioServer.java:2437)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2199)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1968)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1669)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-5452) Tx with timeout can make node can hang on stop.
[ https://issues.apache.org/jira/browse/IGNITE-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Biryukov Vitaliy reassigned IGNITE-5452: Assignee: Biryukov Vitaliy > Tx with timeout can make node can hang on stop. > --- > > Key: IGNITE-5452 > URL: https://issues.apache.org/jira/browse/IGNITE-5452 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.0 >Reporter: Andrew Mashenkov >Assignee: Biryukov Vitaliy > Fix For: 2.1 > > Attachments: LockTimeoutFailedOnStop.java > > > PFA repro attached. > Actually, there are 2 issue. > 1. GridTimeoutProcessor can't be stopped if TimeoutObject eats > InterruptedException. We should handle this correctly. > 2. TX use TimeoutObjects to be rolled back by timeout. However, TXs doesn't > remove their TimeoutObjects on node stop. > Possible, TimeoutObject doesn't removed on TX rollback and this should be > investigated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5030) Support Spring @Cacheable(sync=true) annotation
[ https://issues.apache.org/jira/browse/IGNITE-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066776#comment-16066776 ] ASF GitHub Bot commented on IGNITE-5030: Github user mcherkasov closed the pull request at: https://github.com/apache/ignite/pull/2030 > Support Spring @Cacheable(sync=true) annotation > --- > > Key: IGNITE-5030 > URL: https://issues.apache.org/jira/browse/IGNITE-5030 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Mikhail Cherkasov > Fix For: 2.1 > > > @Cacheable(sync=true) guarantee that only one thread (across the cluster) > will fetch value for a key on get, even in case of some simultaneous gets. > So, > org.apache.ignite.cache.spring.SpringCache#get(java.lang.Object, > java.util.concurrent.Callable) > should be implemented to provide such guarantee. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5364) Remove contention on DataStructure creation or removing
[ https://issues.apache.org/jira/browse/IGNITE-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066775#comment-16066775 ] ASF GitHub Bot commented on IGNITE-5364: Github user mcherkasov closed the pull request at: https://github.com/apache/ignite/pull/2053 > Remove contention on DataStructure creation or removing > --- > > Key: IGNITE-5364 > URL: https://issues.apache.org/jira/browse/IGNITE-5364 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Mikhail Cherkasov >Assignee: Mikhail Cherkasov > Labels: important > Fix For: 2.1 > > > All DSs are stored in one Map which itself is stored in utilityCache, this > makes high contention on DS creation or removing, it requires lock on the key > and manipulation with the Map under the lock. So all threads in cluster > should wait for this lock to create or remove DS. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5558) Add ability to read WAL outside of an Ignite node
[ https://issues.apache.org/jira/browse/IGNITE-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5558: --- Component/s: (was: cache) persistence > Add ability to read WAL outside of an Ignite node > - > > Key: IGNITE-5558 > URL: https://issues.apache.org/jira/browse/IGNITE-5558 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.1 >Reporter: Alexey Goncharuk >Assignee: Dmitriy Pavlov > Fix For: 2.1 > > > Currently, the WAL iterator can be obtained from the WAL manager when an > Ignite node is up and running. > However, it may be extremely useful to read WAL in an 'offline' mode, when a > node is not started up. This may be required for crash analysis or to export > committed data to some external systems. > In the future we can make this even a public interface, however as a starting > point, I would like to keep it in private package because moving to the > public package will require Iterator and records to be public too. > So, as a starting point, we need: > * An object that will allow us to get WALIterator instances (probably, > should be closeable) > * A method on this object which will create an iterator by a file name or > file names > Using this object should not require an active Ignite instance running. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5587) Generate File WAL Segment Archive Completed Event
[ https://issues.apache.org/jira/browse/IGNITE-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5587: --- Component/s: persistence > Generate File WAL Segment Archive Completed Event > - > > Key: IGNITE-5587 > URL: https://issues.apache.org/jira/browse/IGNITE-5587 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov > Fix For: 2.1 > > > Now segment archive complete event is based internally on wait-notifyAll > It is impossible to subscribe to this event outside archiver module. > It is required to create SEGMENT_ARCHIVED event type and fire this event each > time segment archiving was completed -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5076) Optimization of multi-threaded start nodes in tests
[ https://issues.apache.org/jira/browse/IGNITE-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066563#comment-16066563 ] Vyacheslav Koptilin commented on IGNITE-5076: - TC looks good. Please review the PR. > Optimization of multi-threaded start nodes in tests > --- > > Key: IGNITE-5076 > URL: https://issues.apache.org/jira/browse/IGNITE-5076 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Dmitriy Govorukhin >Assignee: Vyacheslav Koptilin > Fix For: 2.1 > > > Concurrent start,will more effective if we have coordinator before, > multi-threaded start nodes. If start all nodes concurrent, they will be > compete for coordinator role, it is not effective way. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5606) .NET: Enums do not work as a messaging topic or message
[
https://issues.apache.org/jira/browse/IGNITE-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-5606:
---
Description: Trying to use .NET enum in {{IMessaging}} causes "unknown
pair" exception in Java. May be we are missing binary mode somewhere.
> .NET: Enums do not work as a messaging topic or message
> ---
>
> Key: IGNITE-5606
> URL: https://issues.apache.org/jira/browse/IGNITE-5606
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.1
>
>
> Trying to use .NET enum in {{IMessaging}} causes "unknown pair" exception in
> Java. May be we are missing binary mode somewhere.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5606) .NET: Enums do not work as a messaging topic or message
Pavel Tupitsyn created IGNITE-5606: -- Summary: .NET: Enums do not work as a messaging topic or message Key: IGNITE-5606 URL: https://issues.apache.org/jira/browse/IGNITE-5606 Project: Ignite Issue Type: Bug Affects Versions: 2.0 Reporter: Pavel Tupitsyn Fix For: 2.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5606) .NET: Enums do not work as a messaging topic or message
[ https://issues.apache.org/jira/browse/IGNITE-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-5606: --- Labels: .NET (was: ) > .NET: Enums do not work as a messaging topic or message > --- > > Key: IGNITE-5606 > URL: https://issues.apache.org/jira/browse/IGNITE-5606 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.0 >Reporter: Pavel Tupitsyn > Labels: .NET > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5606) .NET: Enums do not work as a messaging topic or message
[ https://issues.apache.org/jira/browse/IGNITE-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-5606: --- Component/s: platforms > .NET: Enums do not work as a messaging topic or message > --- > > Key: IGNITE-5606 > URL: https://issues.apache.org/jira/browse/IGNITE-5606 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.0 >Reporter: Pavel Tupitsyn > Labels: .NET > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5591) WAL queue flusher for background mode can be replaced with Timeout processor
[
https://issues.apache.org/jira/browse/IGNITE-5591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5591:
---
Description:
Use
cctx.time().schedule(new Runnable() {});
intead of propriatery API and separate thread for WAL background mode
This change saves us 1 thread creation.
was:
Use
cctx.time().schedule(new Runnable() {});
intead of propriatery API and separate thread for WAL background mode
> WAL queue flusher for background mode can be replaced with Timeout processor
>
>
> Key: IGNITE-5591
> URL: https://issues.apache.org/jira/browse/IGNITE-5591
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Minor
> Fix For: 2.1
>
>
> Use
> cctx.time().schedule(new Runnable() {});
> intead of propriatery API and separate thread for WAL background mode
> This change saves us 1 thread creation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5589) Archive WAL segment after significant period of grid inactivity
[ https://issues.apache.org/jira/browse/IGNITE-5589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5589: --- Component/s: persistence > Archive WAL segment after significant period of grid inactivity > --- > > Key: IGNITE-5589 > URL: https://issues.apache.org/jira/browse/IGNITE-5589 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov > Fix For: 2.1 > > > Placing WAL records into files in work directory (preallocated size; files > with same name) was intitially done for perfomance reasons. > But for case there is no activity in the system there is no need to keep open > segment in work directory. > It is possible move data of this incomplete segment into archive. > Proposed change: wait some configurable time, e.g N minutes and move WAL > segment to archive. > This operation should be done with appropriate lock held to avoid writting > record to WAL segment which is being archived. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5598) WAL Iteration stopped with exception after writting log with background mode
[ https://issues.apache.org/jira/browse/IGNITE-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066487#comment-16066487 ] ASF GitHub Bot commented on IGNITE-5598: GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/2212 IGNITE-5598: Fixed switch segment record, WAL read and rollover are now OK for background mode https://issues.apache.org/jira/browse/IGNITE-5598 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5598 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2212.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2212 commit 468033cc060cff8bdb7c74054eb47500d25732af Author: dpavlov Date: 2017-06-21T14:10:04Z IGNITE-5558: mock based test iterator created: Add ability to read WAL outside of an Ignite node commit 3c1e28e46c3d5095ce00638e225768a10163a307 Author: dpavlov Date: 2017-06-21T15:00:25Z IGNITE-5558: change to run on TC commit defda5b4003bf990e6ca10ffef20ea0d35ee546b Author: dpavlov Date: 2017-06-22T11:42:50Z IGNITE-5558: first non-mockito based iterator implementation commit 55fdb9ba2ecd46c4f701c11deb0cc2fea7ab5ff4 Author: dpavlov Date: 2017-06-22T12:10:46Z IGNITE-5558: update for running on teamcity commit 8e61faeb1a4eaa541c7ae7257721c302b966fbf5 Author: dpavlov Date: 2017-06-22T13:20:56Z IGNITE-5558: WAL iterator creation moved to standalone class commit b7024715585735a7011defafade5d267fe3f86e3 Author: dpavlov Date: 2017-06-22T14:24:41Z IGNITE-5558: Mock factory extracted as standalone class commit fed81a079b82d3445793fef37c61ef16a40c9446 Author: dpavlov Date: 2017-06-22T15:00:42Z IGNITE-5558: compile fix commit 9a844a8e7b80d6cde2247780500878a5ab70128a Author: dpavlov Date: 2017-06-22T16:47:32Z IGNITE-5558: WAL reader was moved to core, main() method was created commit c6cbb4b910a29135e73298a7f64a63dbb354dfa0 Author: dpavlov Date: 2017-06-22T17:49:26Z IGNITE-5558: WAL reader: correct close, record exception printing, file headers, javadoc commit 1be55120fd9d56f9ef28fd691a526a3482ceef48 Author: dpavlov Date: 2017-06-22T18:35:03Z IGNITE-5558: WAL reader: 2 modes were created: directory and files commit 9df9b12297fd103a8f5564f600a90814961d94c1 Author: dpavlov Date: 2017-06-23T10:38:22Z IGNITE-5558: WAL reader NPE fix and javadocs commit 79d934d36e768430376655c05517f83386028cae Author: dpavlov Date: 2017-06-23T12:36:52Z IGNITE-5558: cosmetic & javadocs commit 7b00272edf9dbcd35c9f2a6697253c61bbb7f80c Author: dpavlov Date: 2017-06-26T14:16:46Z IGNITE-5587: Generate File WAL Segment Archive Completed Event commit 13a3b1a52cfb561011df96dda32eb41c2551ce26 Author: dpavlov Date: 2017-06-26T15:07:34Z IGNITE-5587: Javadoc and cosmetic: Generate File WAL Segment Archive Completed Event commit dce18c0581f9e3caff39c13cf0b681daa43934fc Author: dpavlov Date: 2017-06-26T16:42:55Z IGNITE-5587: Generate File WAL Segment Archive Completed Event commit 69bbd6e7eedb90382128023a0ed478dd9cc42492 Author: dpavlov Date: 2017-06-26T16:57:56Z IGNITE-5591: WAL queue flusher for background mode was replaced with Timeout processor commit 91eb1e926500c0eb9d4c87f0686372dfa4ad0cef Author: dpavlov Date: 2017-06-26T17:22:09Z IGNITE-5591: serial version ID added commit 552e379b5238cdbedbb818f3d56ea04207deb984 Author: dpavlov Date: 2017-06-27T13:54:00Z IGNITE-5589: Archive WAL segment after significant period of grid inactivity commit c60bc89e89bdc538f44fe8877e3137cc3f4339cc Author: dpavlov Date: 2017-06-27T15:47:49Z IGNITE-5589: Archive WAL segment after significant period of grid inactivity commit 1f9c2869d489b32908d5df2dd66be21151c5fbd6 Author: dpavlov Date: 2017-06-28T10:23:48Z IGNITE-5589: Minimise visibility of fields, javadoc IGNITE-5598: exception propagation for reproducing commit 16c28db3d6a289c9c0006406f283b37e14e86433 Author: dpavlov Date: 2017-06-28T13:30:56Z IGNITE-5598: Fixed switch segment record, WAL read and rollover are now OK for background mode > WAL Iteration stopped with exception after writting log with background mode > > > Key: IGNITE-5598 > URL: https://issues.apache.org/jira/browse/IGNITE-5598 > Project: Ignite > Issue Type: Bug > Components: persistence >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov > Fix For: 2.1 > > > Need to research if it is problem of IGNITE-5558 implementation or standalone > issue > Exception is logged into stderr:
[jira] [Commented] (IGNITE-4887) Support for starting transaction in another thread
[
https://issues.apache.org/jira/browse/IGNITE-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066484#comment-16066484
]
Alexey Kuznetsov commented on IGNITE-4887:
--
[~yzhdanov] TransactionsInMultipleThreadsClientTest test contains tests for
client and server node. Where client node is initiator.
> Support for starting transaction in another thread
> --
>
> Key: IGNITE-4887
> URL: https://issues.apache.org/jira/browse/IGNITE-4887
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 1.9
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>
> Consider the following pseudo-code:
> {code:xml}
> IgniteTransactions transactions = ignite1.transactions();
> Transaction tx = startTransaction(transactions);
> cache.put("key1", 1);
> tx.stop();
> {code}
> And in another thread:
> {code:xml}
> transactions.txStart(tx);
> cache.put("key3", 3);
> cache.remove("key2");
> tx.commit();
> {code}
> The Api should be implemented , that let you continue transaction in another
> thread.
> method stop() should mark the transaction as unavailable for further commit.
> method txStart() should resume the transaction.
> reason behind the proposal :
> Consider the next scenario:
> we begin transaction, doing some changes and start async future that will be
> able to introduce futher changes into transaction and commit it in the end.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5322) Improve WAL record/iterator structure
[ https://issues.apache.org/jira/browse/IGNITE-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066476#comment-16066476 ] Dmitriy Pavlov commented on IGNITE-5322: Additionally Swich Segment record (and its WAL pointer) writting was fixed in IGNITE-5598. > Improve WAL record/iterator structure > - > > Key: IGNITE-5322 > URL: https://issues.apache.org/jira/browse/IGNITE-5322 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.1 >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk > Labels: important > Fix For: 2.1 > > > Currently, we rely on the WAL files layout and zero-ing to make a decision > when to stop the iteration. > Instead, we should write a WAL Pointer to each record with it's position in > the file. This will allow us to verify that we are reading a consistent > records sequence and should also remove a requirement for zero-clean WAL > segment. > When iterating over the WAL, we should calculate expected next WAL pointer > and check that read pointer is equal to the read. If we found a difference, > this means that we encountered a stale segment and can stop the iteration. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5598) WAL Iteration stopped with exception after writting log with background mode
[
https://issues.apache.org/jira/browse/IGNITE-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5598:
---
Component/s: persistence
> WAL Iteration stopped with exception after writting log with background mode
>
>
> Key: IGNITE-5598
> URL: https://issues.apache.org/jira/browse/IGNITE-5598
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
> Fix For: 2.1
>
>
> Need to research if it is problem of IGNITE-5558 implementation or standalone
> issue
> Exception is logged into stderr:
> {noformat}
> java.lang.RuntimeException: java.io.EOFException
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.handleRecordException(StandaloneWalRecordsIterator.java:168)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:166)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:121)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:106)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:42)
> at
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.wal.reader.IgniteWalReaderTest.testFillWalAndReadRecords(IgniteWalReaderTest.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1994)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1909)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.io.EOFException
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput.ensure(FileInput.java:104)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.ensure(FileInput.java:288)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readByte(FileInput.java:361)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readUnsignedByte(FileInput.java:370)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:677)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:657)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:156)
> ... 14 more
> Suppressed: class
> org.apache.ignite.internal.processors.cache.persistence.wal.crc.IgniteDataIntegrityViolationException:
> val: 771559538 writtenCrc: 0
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.close(FileInput.java:305)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:664)
> ... 15 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5598) WAL Iteration stopped with exception after writting log with background mode
[
https://issues.apache.org/jira/browse/IGNITE-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5598:
---
Issue Type: Bug (was: Task)
> WAL Iteration stopped with exception after writting log with background mode
>
>
> Key: IGNITE-5598
> URL: https://issues.apache.org/jira/browse/IGNITE-5598
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
> Fix For: 2.1
>
>
> Need to research if it is problem of IGNITE-5558 implementation or standalone
> issue
> Exception is logged into stderr:
> {noformat}
> java.lang.RuntimeException: java.io.EOFException
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.handleRecordException(StandaloneWalRecordsIterator.java:168)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:166)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:121)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:106)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:42)
> at
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.wal.reader.IgniteWalReaderTest.testFillWalAndReadRecords(IgniteWalReaderTest.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1994)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1909)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.io.EOFException
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput.ensure(FileInput.java:104)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.ensure(FileInput.java:288)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readByte(FileInput.java:361)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readUnsignedByte(FileInput.java:370)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:677)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:657)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:156)
> ... 14 more
> Suppressed: class
> org.apache.ignite.internal.processors.cache.persistence.wal.crc.IgniteDataIntegrityViolationException:
> val: 771559538 writtenCrc: 0
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.close(FileInput.java:305)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:664)
> ... 15 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5598) WAL Iteration stopped with exception after writting log with background mode
[
https://issues.apache.org/jira/browse/IGNITE-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5598:
---
Fix Version/s: (was: 1.9)
2.1
> WAL Iteration stopped with exception after writting log with background mode
>
>
> Key: IGNITE-5598
> URL: https://issues.apache.org/jira/browse/IGNITE-5598
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
> Fix For: 2.1
>
>
> Need to research if it is problem of IGNITE-5558 implementation or standalone
> issue
> Exception is logged into stderr:
> {noformat}
> java.lang.RuntimeException: java.io.EOFException
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.handleRecordException(StandaloneWalRecordsIterator.java:168)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:166)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:121)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:106)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:42)
> at
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.wal.reader.IgniteWalReaderTest.testFillWalAndReadRecords(IgniteWalReaderTest.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1994)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1909)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.io.EOFException
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput.ensure(FileInput.java:104)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.ensure(FileInput.java:288)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readByte(FileInput.java:361)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readUnsignedByte(FileInput.java:370)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:677)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:657)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:156)
> ... 14 more
> Suppressed: class
> org.apache.ignite.internal.processors.cache.persistence.wal.crc.IgniteDataIntegrityViolationException:
> val: 771559538 writtenCrc: 0
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.close(FileInput.java:305)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:664)
> ... 15 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5598) WAL Iteration stopped with exception after writting log with background mode
[
https://issues.apache.org/jira/browse/IGNITE-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5598:
---
Fix Version/s: 1.9
> WAL Iteration stopped with exception after writting log with background mode
>
>
> Key: IGNITE-5598
> URL: https://issues.apache.org/jira/browse/IGNITE-5598
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
> Fix For: 2.1
>
>
> Need to research if it is problem of IGNITE-5558 implementation or standalone
> issue
> Exception is logged into stderr:
> {noformat}
> java.lang.RuntimeException: java.io.EOFException
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.handleRecordException(StandaloneWalRecordsIterator.java:168)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:166)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:121)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:106)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:42)
> at
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.wal.reader.IgniteWalReaderTest.testFillWalAndReadRecords(IgniteWalReaderTest.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1994)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1909)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.io.EOFException
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput.ensure(FileInput.java:104)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.ensure(FileInput.java:288)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readByte(FileInput.java:361)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readUnsignedByte(FileInput.java:370)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:677)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:657)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:156)
> ... 14 more
> Suppressed: class
> org.apache.ignite.internal.processors.cache.persistence.wal.crc.IgniteDataIntegrityViolationException:
> val: 771559538 writtenCrc: 0
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.close(FileInput.java:305)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:664)
> ... 15 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5604) Activate fails in case node was stopped with cancel=true and big objects in cache
[
https://issues.apache.org/jira/browse/IGNITE-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-5604:
-
Summary: Activate fails in case node was stopped with cancel=true and big
objects in cache (was: Activate fails node was stopped with cancel=true and
big objects in cache)
> Activate fails in case node was stopped with cancel=true and big objects in
> cache
> -
>
> Key: IGNITE-5604
> URL: https://issues.apache.org/jira/browse/IGNITE-5604
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>
> Please take a look at the test
> {{IgniteWalRecoveryTest#testWalBigObjectNodeCancel}}.
> The test is available at the [pull
> request|https://github.com/apache/ignite/pull/2211].
> The error is:
> {code}
> [2017-06-28 15:50:46,020][ERROR][main][root] Test failed.
> class org.apache.ignite.IgniteException: Fail activate
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)
> at
> org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3408)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteWalRecoveryTest.testWalBigObjectNodeCancel(IgniteWalRecoveryTest.java:249)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1995)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1910)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: Fail activate
> Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to
> restore memory state (checkpoint marker is present on disk, but checkpoint
> record is missed in WAL) [cpStatus=CheckpointStatus [cpStartTs=1498654243491,
> cpStartId=7f873e0b-b1ee-4bd6-8605-b139b82898c9, startPtr=FileWALPointer
> [idx=0, fileOffset=8657376, len=2425, forceFlush=false],
> cpEndId=----, endPtr=FileWALPointer [idx=0,
> fileOffset=0, len=0, forceFlush=false]], lastRead=FileWALPointer [idx=0,
> fileOffset=4340447, len=39, forceFlush=false]]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreMemory(GridCacheDatabaseSharedManager.java:1471)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readCheckpointAndRestoreMemory(GridCacheDatabaseSharedManager.java:578)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.initCachesAndRestoreMemory(GridCacheDatabaseSharedManager.java:492)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.onActivate(GridCacheDatabaseSharedManager.java:508)
> at
> org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onActivate(GridClusterStateProcessor.java:747)
> at
> org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onChangeGlobalState(GridClusterStateProcessor.java:655)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:719)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:563)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1872)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5605) .NET: Inject resources into event listeners and filters
Pavel Tupitsyn created IGNITE-5605:
--
Summary: .NET: Inject resources into event listeners and filters
Key: IGNITE-5605
URL: https://issues.apache.org/jira/browse/IGNITE-5605
Project: Ignite
Issue Type: Bug
Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: 2.1
{{IEventListener}} and {{IEventFilter}} must support {{[InstanceResource]}}
attribute.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5604) Activate fails node was stopped with cancel=true and big objects in cache
[
https://issues.apache.org/jira/browse/IGNITE-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066448#comment-16066448
]
Taras Ledkov commented on IGNITE-5604:
--
[~DmitriyGovorukhin], [~agoncharuk] please take a look.
> Activate fails node was stopped with cancel=true and big objects in cache
> -
>
> Key: IGNITE-5604
> URL: https://issues.apache.org/jira/browse/IGNITE-5604
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>
> Please take a look at the test
> {{IgniteWalRecoveryTest#testWalBigObjectNodeCancel}}.
> The test is available at the [pull
> request|https://github.com/apache/ignite/pull/2211].
> The error is:
> {code}
> [2017-06-28 15:50:46,020][ERROR][main][root] Test failed.
> class org.apache.ignite.IgniteException: Fail activate
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)
> at
> org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3408)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteWalRecoveryTest.testWalBigObjectNodeCancel(IgniteWalRecoveryTest.java:249)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1995)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1910)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: Fail activate
> Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to
> restore memory state (checkpoint marker is present on disk, but checkpoint
> record is missed in WAL) [cpStatus=CheckpointStatus [cpStartTs=1498654243491,
> cpStartId=7f873e0b-b1ee-4bd6-8605-b139b82898c9, startPtr=FileWALPointer
> [idx=0, fileOffset=8657376, len=2425, forceFlush=false],
> cpEndId=----, endPtr=FileWALPointer [idx=0,
> fileOffset=0, len=0, forceFlush=false]], lastRead=FileWALPointer [idx=0,
> fileOffset=4340447, len=39, forceFlush=false]]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreMemory(GridCacheDatabaseSharedManager.java:1471)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readCheckpointAndRestoreMemory(GridCacheDatabaseSharedManager.java:578)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.initCachesAndRestoreMemory(GridCacheDatabaseSharedManager.java:492)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.onActivate(GridCacheDatabaseSharedManager.java:508)
> at
> org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onActivate(GridClusterStateProcessor.java:747)
> at
> org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onChangeGlobalState(GridClusterStateProcessor.java:655)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:719)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:563)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1872)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5604) Activate fails node was stopped with cancel=true and big objects in cache
[
https://issues.apache.org/jira/browse/IGNITE-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-5604:
-
Description:
Please take a look at the test
{{IgniteWalRecoveryTest#testWalBigObjectNodeCancel}}.
The test is available at the [pull
request|https://github.com/apache/ignite/pull/2211].
The error is:
{code}
[2017-06-28 15:50:46,020][ERROR][main][root] Test failed.
class org.apache.ignite.IgniteException: Fail activate
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)
at
org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3408)
at
org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteWalRecoveryTest.testWalBigObjectNodeCancel(IgniteWalRecoveryTest.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1995)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1910)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteCheckedException: Fail activate
Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to
restore memory state (checkpoint marker is present on disk, but checkpoint
record is missed in WAL) [cpStatus=CheckpointStatus [cpStartTs=1498654243491,
cpStartId=7f873e0b-b1ee-4bd6-8605-b139b82898c9, startPtr=FileWALPointer [idx=0,
fileOffset=8657376, len=2425, forceFlush=false],
cpEndId=----, endPtr=FileWALPointer [idx=0,
fileOffset=0, len=0, forceFlush=false]], lastRead=FileWALPointer [idx=0,
fileOffset=4340447, len=39, forceFlush=false]]
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreMemory(GridCacheDatabaseSharedManager.java:1471)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readCheckpointAndRestoreMemory(GridCacheDatabaseSharedManager.java:578)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.initCachesAndRestoreMemory(GridCacheDatabaseSharedManager.java:492)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.onActivate(GridCacheDatabaseSharedManager.java:508)
at
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onActivate(GridClusterStateProcessor.java:747)
at
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onChangeGlobalState(GridClusterStateProcessor.java:655)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:719)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:563)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1872)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
{code}
was:
Please take a look at the test
{{IgniteWalRecoveryTest#testWalBigObjectNodeCancel}}.
The test is available at the [pull
request|https://github.com/apache/ignite/pull/2211].
> Activate fails node was stopped with cancel=true and big objects in cache
> -
>
> Key: IGNITE-5604
> URL: https://issues.apache.org/jira/browse/IGNITE-5604
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>
> Please take a look at the test
> {{IgniteWalRecoveryTest#testWalBigObjectNodeCancel}}.
> The test is available at the [pull
> request|https://github.com/apache/ignite/pull/2211].
> The error is:
> {code}
> [2017-06-28 15:50:46,020][ERROR][main][root] Test failed.
> class org.apache.ignite.IgniteException: Fail activate
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)
> at
> org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3408)
>
[jira] [Updated] (IGNITE-5604) Activate fails node was stopped with cancel=true and big objects in cache
[
https://issues.apache.org/jira/browse/IGNITE-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-5604:
-
Description:
Please take a look at the test
{{IgniteWalRecoveryTest#testWalBigObjectNodeCancel}}.
The test is available at the [pull
request|https://github.com/apache/ignite/pull/2211].
was:Please take a look at the test
{{IgniteWalRecoveryTest#testWalBigObjectNodeCancel}}.
> Activate fails node was stopped with cancel=true and big objects in cache
> -
>
> Key: IGNITE-5604
> URL: https://issues.apache.org/jira/browse/IGNITE-5604
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>
> Please take a look at the test
> {{IgniteWalRecoveryTest#testWalBigObjectNodeCancel}}.
> The test is available at the [pull
> request|https://github.com/apache/ignite/pull/2211].
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5604) Activate fails node was stopped with cancel=true and big objects in cache
[ https://issues.apache.org/jira/browse/IGNITE-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066441#comment-16066441 ] ASF GitHub Bot commented on IGNITE-5604: GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2211 IGNITE-5604 Activate fails node was stopped with cancel=true and big objects in cache You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5604 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2211.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2211 commit b52a84e885b0f88971290200942e0bbe01252ff6 Author: sboikov Date: 2017-06-13T15:09:41Z Merge remote-tracking branch 'remotes/origin/master' into ignite-2.1.1 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/IgniteDiagnosticAware.java # modules/core/src/main/java/org/apache/ignite/internal/IgniteDiagnosticMessage.java # modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCacheIoManager.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCachePartitionExchangeManager.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridDhtTxPrepareFuture.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridPartitionedSingleGetFuture.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridDhtAtomicCache.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/colocated/GridDhtColocatedLockFuture.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/preloader/GridDhtPartitionsExchangeFuture.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/transactions/IgniteTxImplicitSingleStateImpl.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/transactions/IgniteTxStateImpl.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cluster/ClusterProcessor.java # modules/core/src/main/java/org/apache/ignite/internal/util/nio/GridNioServer.java # modules/core/src/main/java/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.java # modules/core/src/test/java/org/apache/ignite/internal/managers/IgniteDiagnosticMessagesTest.java # modules/web-console/web-agent/src/main/java/org/apache/ignite/console/agent/handlers/ClusterListener.java commit fb2e6d4ab00e3e443bdd896918e812d6fa6119ba Author: sboikov Date: 2017-06-13T15:10:18Z Merge remote-tracking branch 'remotes/origin/master' into ignite-2.1.1 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/IgniteDiagnosticAware.java # modules/core/src/main/java/org/apache/ignite/internal/IgniteDiagnosticMessage.java # modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCacheIoManager.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCachePartitionExchangeManager.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridDhtTxPrepareFuture.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridPartitionedSingleGetFuture.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridDhtAtomicCache.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/colocated/GridDhtColocatedLockFuture.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/preloader/GridDhtPartitionsExchangeFuture.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/transactions/IgniteTxImplicitSingleStateImpl.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/transactions/IgniteTxStateImpl.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cluster/ClusterProcessor.java # modules/core/src/main/java/org/apache/ignite/internal/util/nio/GridNioServer.java # modules/core/src/main/java/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.java # modules/core/src/test/java/org/apache/ignite/internal/managers/IgniteDiagnosticMessagesTest.java # modules/web-console
[jira] [Created] (IGNITE-5604) Activate fails node was stopped with cancel=true and big objects in cache
Taras Ledkov created IGNITE-5604:
Summary: Activate fails node was stopped with cancel=true and big
objects in cache
Key: IGNITE-5604
URL: https://issues.apache.org/jira/browse/IGNITE-5604
Project: Ignite
Issue Type: Bug
Components: persistence
Affects Versions: 2.1
Reporter: Taras Ledkov
Please take a look at the test
{{IgniteWalRecoveryTest#testWalBigObjectNodeCancel}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5087) Enum comparison fails after marshal-unmarshal with BinaryMarshaller.
[ https://issues.apache.org/jira/browse/IGNITE-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066399#comment-16066399 ] Amelchev Nikita commented on IGNITE-5087: - [~amashenkov] I add a test in BinaryMarshallerSelfTest. I left only binary marshaller enum test so as change applied only the BinaryMarshaller. In addition I add test to BinaryEnumsSelfTest. Please, review. > Enum comparison fails after marshal-unmarshal with BinaryMarshaller. > > > Key: IGNITE-5087 > URL: https://issues.apache.org/jira/browse/IGNITE-5087 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.9 >Reporter: Andrew Mashenkov >Assignee: Amelchev Nikita > Fix For: 2.1 > > Attachments: EnumBinaryMarshallerBug.java > > > PFA repro. > It fails on 1.9 and on 2.0-snapshot as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5603) All daemon node, can be only client daemon, server daemon is not allow.
Dmitriy Govorukhin created IGNITE-5603: -- Summary: All daemon node, can be only client daemon, server daemon is not allow. Key: IGNITE-5603 URL: https://issues.apache.org/jira/browse/IGNITE-5603 Project: Ignite Issue Type: Improvement Components: general Reporter: Dmitriy Govorukhin Priority: Critical Fix For: 2.1 No reason for daemon server right now. Rework current functionality, prevent the server node from being a daemon. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5601) WriteBehind mode hide SQLExceptions
[ https://issues.apache.org/jira/browse/IGNITE-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066359#comment-16066359 ] Benjamin Garaude commented on IGNITE-5601: -- Hi, Indeed, i actually have the issue in 1.6. When i pushed my test case it inherited the 2.0 dependency from the parent module So it means the issue is solved in 2.0. Sorry. I'l close the issue, > WriteBehind mode hide SQLExceptions > --- > > Key: IGNITE-5601 > URL: https://issues.apache.org/jira/browse/IGNITE-5601 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Affects Versions: 2.0 > Environment: Ignite 2.0.0 > Oracle JDK 1.8.0_121 > Derby 10.13.1.1 >Reporter: Benjamin Garaude > Fix For: 2.0 > > > If an exception, e.g. SQLException occurs during a wite-behind operation, the > exception is lost and appears nowhere in the logs. > The logs basically say: > [2017-06-28 10:48:52] SEVERE: Unable to update underlying store: > CacheJdbcPojoStore [] > [2017-06-28 10:48:52] WARNING: Failed to update store (value will be lost as > current buffer size is greater than 'cacheCriticalSize' or node has been > stopped before store was repaired) [key=test.WriteBehindIssue$FooKey > [idHash=524852907, hash=-1388553726, id=1], val=test.WriteBehindIssue$Foo > [idHash=323347362, hash=574522785, value1=abcd, value2=1234], op=PUT] > If we do the same with write-through mode, it fails by throwing an exception > with the SQLException as cause, deep in the trace. > Would it be possible the write-behind operation logs the SQLException, and > other exception? > You can find a test case showing that here: > https://github.com/bgaraude/IgniteTest -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (IGNITE-5601) WriteBehind mode hide SQLExceptions
[ https://issues.apache.org/jira/browse/IGNITE-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Garaude resolved IGNITE-5601. -- Resolution: Fixed Fix Version/s: 2.0 > WriteBehind mode hide SQLExceptions > --- > > Key: IGNITE-5601 > URL: https://issues.apache.org/jira/browse/IGNITE-5601 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Affects Versions: 2.0 > Environment: Ignite 2.0.0 > Oracle JDK 1.8.0_121 > Derby 10.13.1.1 >Reporter: Benjamin Garaude > Fix For: 2.0 > > > If an exception, e.g. SQLException occurs during a wite-behind operation, the > exception is lost and appears nowhere in the logs. > The logs basically say: > [2017-06-28 10:48:52] SEVERE: Unable to update underlying store: > CacheJdbcPojoStore [] > [2017-06-28 10:48:52] WARNING: Failed to update store (value will be lost as > current buffer size is greater than 'cacheCriticalSize' or node has been > stopped before store was repaired) [key=test.WriteBehindIssue$FooKey > [idHash=524852907, hash=-1388553726, id=1], val=test.WriteBehindIssue$Foo > [idHash=323347362, hash=574522785, value1=abcd, value2=1234], op=PUT] > If we do the same with write-through mode, it fails by throwing an exception > with the SQLException as cause, deep in the trace. > Would it be possible the write-behind operation logs the SQLException, and > other exception? > You can find a test case showing that here: > https://github.com/bgaraude/IgniteTest -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-4887) Support for starting transaction in another thread
[
https://issues.apache.org/jira/browse/IGNITE-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066320#comment-16066320
]
Alexey Kuznetsov edited comment on IGNITE-4887 at 6/28/17 10:43 AM:
[~yzhdanov] Your test has succesfully passed for OPTIMISTIC transactions. For
PESSIMISTIC transactions it has hanged
was (Author: alexey kuznetsov):
[~yzhdanov] Your test has succesfully passed for OPTIMISTIC transaction. For
PESSIMISTIC transaction it has hanged
> Support for starting transaction in another thread
> --
>
> Key: IGNITE-4887
> URL: https://issues.apache.org/jira/browse/IGNITE-4887
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 1.9
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>
> Consider the following pseudo-code:
> {code:xml}
> IgniteTransactions transactions = ignite1.transactions();
> Transaction tx = startTransaction(transactions);
> cache.put("key1", 1);
> tx.stop();
> {code}
> And in another thread:
> {code:xml}
> transactions.txStart(tx);
> cache.put("key3", 3);
> cache.remove("key2");
> tx.commit();
> {code}
> The Api should be implemented , that let you continue transaction in another
> thread.
> method stop() should mark the transaction as unavailable for further commit.
> method txStart() should resume the transaction.
> reason behind the proposal :
> Consider the next scenario:
> we begin transaction, doing some changes and start async future that will be
> able to introduce futher changes into transaction and commit it in the end.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-4887) Support for starting transaction in another thread
[
https://issues.apache.org/jira/browse/IGNITE-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066320#comment-16066320
]
Alexey Kuznetsov edited comment on IGNITE-4887 at 6/28/17 10:43 AM:
[~yzhdanov] Your test has succesfully passed for OPTIMISTIC transaction. For
PESSIMISTIC transaction it has hanged
was (Author: alexey kuznetsov):
[~yzhdanov] Your test has succesfully passed.
> Support for starting transaction in another thread
> --
>
> Key: IGNITE-4887
> URL: https://issues.apache.org/jira/browse/IGNITE-4887
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 1.9
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>
> Consider the following pseudo-code:
> {code:xml}
> IgniteTransactions transactions = ignite1.transactions();
> Transaction tx = startTransaction(transactions);
> cache.put("key1", 1);
> tx.stop();
> {code}
> And in another thread:
> {code:xml}
> transactions.txStart(tx);
> cache.put("key3", 3);
> cache.remove("key2");
> tx.commit();
> {code}
> The Api should be implemented , that let you continue transaction in another
> thread.
> method stop() should mark the transaction as unavailable for further commit.
> method txStart() should resume the transaction.
> reason behind the proposal :
> Consider the next scenario:
> we begin transaction, doing some changes and start async future that will be
> able to introduce futher changes into transaction and commit it in the end.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-4887) Support for starting transaction in another thread
[
https://issues.apache.org/jira/browse/IGNITE-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066320#comment-16066320
]
Alexey Kuznetsov commented on IGNITE-4887:
--
[~yzhdanov] Your test has succesfully passed.
> Support for starting transaction in another thread
> --
>
> Key: IGNITE-4887
> URL: https://issues.apache.org/jira/browse/IGNITE-4887
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 1.9
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>
> Consider the following pseudo-code:
> {code:xml}
> IgniteTransactions transactions = ignite1.transactions();
> Transaction tx = startTransaction(transactions);
> cache.put("key1", 1);
> tx.stop();
> {code}
> And in another thread:
> {code:xml}
> transactions.txStart(tx);
> cache.put("key3", 3);
> cache.remove("key2");
> tx.commit();
> {code}
> The Api should be implemented , that let you continue transaction in another
> thread.
> method stop() should mark the transaction as unavailable for further commit.
> method txStart() should resume the transaction.
> reason behind the proposal :
> Consider the next scenario:
> we begin transaction, doing some changes and start async future that will be
> able to introduce futher changes into transaction and commit it in the end.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-5601) WriteBehind mode hide SQLExceptions
[
https://issues.apache.org/jira/browse/IGNITE-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066313#comment-16066313
]
Roman Shtykh edited comment on IGNITE-5601 at 6/28/17 10:37 AM:
Running your tests produces the following output for me
{noformat}
重大: Unable to update underlying store: CacheJdbcPojoStore []
javax.cache.integration.CacheWriterException: Failed to write entries in
database
at
org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore.writeAll(CacheAbstractJdbcStore.java:1151)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore.updateStore(GridCacheWriteBehindStore.java:804)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore.applyBatch(GridCacheWriteBehindStore.java:720)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore.access$2400(GridCacheWriteBehindStore.java:75)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore$Flusher.flushCacheCoalescing(GridCacheWriteBehindStore.java:1135)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore$Flusher.body(GridCacheWriteBehindStore.java:1006)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.sql.SQLSyntaxErrorException: 'UNEXISTING_COLUMN' is not a
column in table or VTI 'DERBY.FOO'.
at
org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement42.(Unknown
Source)
at org.apache.derby.jdbc.Driver42.newEmbedPreparedStatement(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown
Source)
at
org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore.writeAll(CacheAbstractJdbcStore.java:1131)
... 7 more
Caused by: ERROR 42X14: 'UNEXISTING_COLUMN' is not a column in table or VTI
'DERBY.FOO'.
at org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
at org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
at
org.apache.derby.impl.sql.compile.ResultColumn.bindResultColumnByName(Unknown
Source)
at
org.apache.derby.impl.sql.compile.ResultColumnList.bindResultColumnsByName(Unknown
Source)
at org.apache.derby.impl.sql.compile.InsertNode.bindStatement(Unknown
Source)
at org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown Source)
at org.apache.derby.impl.sql.GenericStatement.prepare(Unknown Source)
at
org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(Unknown
Source)
... 13 more
6 28, 2017 7:34:32 午後 org.apache.ignite.logger.java.JavaLogger warning
警告: Failed to update store (value will be lost as current buffer size is
greater than 'cacheCriticalSize' or node has been stopped before store was
repaired) [key=test.WriteBehindIssueTest$FooKey [idHash=1079871273,
hash=-1388553726, id=1], val=test.WriteBehindIssueTest$Foo [idHash=1996018097,
hash=574522785, value1=abcd, value2=1234], op=PUT]
{noformat}
was (Author: roman_s):
Running your tests I get
{noformat}
重大: Unable to update underlying store: CacheJdbcPojoStore []
javax.cache.integration.CacheWriterException: Failed to write entries in
database
at
org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore.writeAll(CacheAbstractJdbcStore.java:1151)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore.updateStore(GridCacheWriteBehindStore.java:804)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore.applyBatch(GridCacheWriteBehindStore.java:720)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore.access$2400(GridCacheWriteBehindStore.java:75)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore$Flusher.flushCacheCoalescing(GridCacheWriteBehindStore.java:1135)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore$Flusher.body(GridCacheWriteBehindStore.java:1006)
at
org.apache.ignit
[jira] [Commented] (IGNITE-5601) WriteBehind mode hide SQLExceptions
[
https://issues.apache.org/jira/browse/IGNITE-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066313#comment-16066313
]
Roman Shtykh commented on IGNITE-5601:
--
Running your tests I get
{noformat}
重大: Unable to update underlying store: CacheJdbcPojoStore []
javax.cache.integration.CacheWriterException: Failed to write entries in
database
at
org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore.writeAll(CacheAbstractJdbcStore.java:1151)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore.updateStore(GridCacheWriteBehindStore.java:804)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore.applyBatch(GridCacheWriteBehindStore.java:720)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore.access$2400(GridCacheWriteBehindStore.java:75)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore$Flusher.flushCacheCoalescing(GridCacheWriteBehindStore.java:1135)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore$Flusher.body(GridCacheWriteBehindStore.java:1006)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.sql.SQLSyntaxErrorException: 'UNEXISTING_COLUMN' is not a
column in table or VTI 'DERBY.FOO'.
at
org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement42.(Unknown
Source)
at org.apache.derby.jdbc.Driver42.newEmbedPreparedStatement(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown
Source)
at
org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore.writeAll(CacheAbstractJdbcStore.java:1131)
... 7 more
Caused by: ERROR 42X14: 'UNEXISTING_COLUMN' is not a column in table or VTI
'DERBY.FOO'.
at org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
at org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
at
org.apache.derby.impl.sql.compile.ResultColumn.bindResultColumnByName(Unknown
Source)
at
org.apache.derby.impl.sql.compile.ResultColumnList.bindResultColumnsByName(Unknown
Source)
at org.apache.derby.impl.sql.compile.InsertNode.bindStatement(Unknown
Source)
at org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown Source)
at org.apache.derby.impl.sql.GenericStatement.prepare(Unknown Source)
at
org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(Unknown
Source)
... 13 more
6 28, 2017 7:34:32 午後 org.apache.ignite.logger.java.JavaLogger warning
警告: Failed to update store (value will be lost as current buffer size is
greater than 'cacheCriticalSize' or node has been stopped before store was
repaired) [key=test.WriteBehindIssueTest$FooKey [idHash=1079871273,
hash=-1388553726, id=1], val=test.WriteBehindIssueTest$Foo [idHash=1996018097,
hash=574522785, value1=abcd, value2=1234], op=PUT]
{noformat}
> WriteBehind mode hide SQLExceptions
> ---
>
> Key: IGNITE-5601
> URL: https://issues.apache.org/jira/browse/IGNITE-5601
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
>Affects Versions: 2.0
> Environment: Ignite 2.0.0
> Oracle JDK 1.8.0_121
> Derby 10.13.1.1
>Reporter: Benjamin Garaude
>
> If an exception, e.g. SQLException occurs during a wite-behind operation, the
> exception is lost and appears nowhere in the logs.
> The logs basically say:
> [2017-06-28 10:48:52] SEVERE: Unable to update underlying store:
> CacheJdbcPojoStore []
> [2017-06-28 10:48:52] WARNING: Failed to update store (value will be lost as
> current buffer size is greater than 'cacheCriticalSize' or node has been
> stopped before store was repaired) [key=test.WriteBehindIssue$FooKey
> [idHash=524852907, hash=-1388553726, id=1], val=test.WriteBehindIssue$Foo
> [idHash=323347362, hash=574522785, value1=abcd, value2=1234], op=PUT]
> If we do the same with write-through mode, it fails by throwing an ex
[jira] [Commented] (IGNITE-5087) Enum comparison fails after marshal-unmarshal with BinaryMarshaller.
[ https://issues.apache.org/jira/browse/IGNITE-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066269#comment-16066269 ] Andrew Mashenkov commented on IGNITE-5087: -- Looks fine. We should add a test in BinaryMarshallerSelfTest as well (as it done in attached repro with marshal-unmarshal approach) before merge to master. > Enum comparison fails after marshal-unmarshal with BinaryMarshaller. > > > Key: IGNITE-5087 > URL: https://issues.apache.org/jira/browse/IGNITE-5087 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.9 >Reporter: Andrew Mashenkov >Assignee: Amelchev Nikita > Fix For: 2.1 > > Attachments: EnumBinaryMarshallerBug.java > > > PFA repro. > It fails on 1.9 and on 2.0-snapshot as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5602) By bytes access to binary format
Vladislav Pyatkov created IGNITE-5602:
-
Summary: By bytes access to binary format
Key: IGNITE-5602
URL: https://issues.apache.org/jira/browse/IGNITE-5602
Project: Ignite
Issue Type: New Feature
Affects Versions: 2.0
Reporter: Vladislav Pyatkov
Need to avoid memory additional allocation when pass bytes to stream.
Now we are doing only
{code}
BinaryObject get = (BinaryObject) cache.get(key);
byte[] dataFromCache = get.field("data");
System.out.write(dataFromCache, 0, dataFromCache.length);
{code}
But we want to write bytes to stream directly, without allocation additional
{{byte[]}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5601) WriteBehind mode hide SQLExceptions
[ https://issues.apache.org/jira/browse/IGNITE-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Garaude updated IGNITE-5601: - Environment: Ignite 2.0.0 Oracle JDK 1.8.0_121 Derby 10.13.1.1 was: +Ignite 2.0.0 Oracle JDK 1.8.0_121 Derby 10.13.1.1+ > WriteBehind mode hide SQLExceptions > --- > > Key: IGNITE-5601 > URL: https://issues.apache.org/jira/browse/IGNITE-5601 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Affects Versions: 2.0 > Environment: Ignite 2.0.0 > Oracle JDK 1.8.0_121 > Derby 10.13.1.1 >Reporter: Benjamin Garaude > > If an exception, e.g. SQLException occurs during a wite-behind operation, the > exception is lost and appears nowhere in the logs. > The logs basically say: > [2017-06-28 10:48:52] SEVERE: Unable to update underlying store: > CacheJdbcPojoStore [] > [2017-06-28 10:48:52] WARNING: Failed to update store (value will be lost as > current buffer size is greater than 'cacheCriticalSize' or node has been > stopped before store was repaired) [key=test.WriteBehindIssue$FooKey > [idHash=524852907, hash=-1388553726, id=1], val=test.WriteBehindIssue$Foo > [idHash=323347362, hash=574522785, value1=abcd, value2=1234], op=PUT] > If we do the same with write-through mode, it fails by throwing an exception > with the SQLException as cause, deep in the trace. > Would it be possible the write-behind operation logs the SQLException, and > other exception? > You can find a test case showing that here: > https://github.com/bgaraude/IgniteTest -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5601) WriteBehind mode hide SQLExceptions
[ https://issues.apache.org/jira/browse/IGNITE-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Garaude updated IGNITE-5601: - Environment: +Ignite 2.0.0 Oracle JDK 1.8.0_121 Derby 10.13.1.1+ was: Ignite 2.0.0 Oracle JDK 1.8.0_121 > WriteBehind mode hide SQLExceptions > --- > > Key: IGNITE-5601 > URL: https://issues.apache.org/jira/browse/IGNITE-5601 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Affects Versions: 2.0 > Environment: +Ignite 2.0.0 > Oracle JDK 1.8.0_121 > Derby 10.13.1.1+ >Reporter: Benjamin Garaude > > If an exception, e.g. SQLException occurs during a wite-behind operation, the > exception is lost and appears nowhere in the logs. > The logs basically say: > [2017-06-28 10:48:52] SEVERE: Unable to update underlying store: > CacheJdbcPojoStore [] > [2017-06-28 10:48:52] WARNING: Failed to update store (value will be lost as > current buffer size is greater than 'cacheCriticalSize' or node has been > stopped before store was repaired) [key=test.WriteBehindIssue$FooKey > [idHash=524852907, hash=-1388553726, id=1], val=test.WriteBehindIssue$Foo > [idHash=323347362, hash=574522785, value1=abcd, value2=1234], op=PUT] > If we do the same with write-through mode, it fails by throwing an exception > with the SQLException as cause, deep in the trace. > Would it be possible the write-behind operation logs the SQLException, and > other exception? > You can find a test case showing that here: > https://github.com/bgaraude/IgniteTest -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5601) WriteBehind mode hide SQLExceptions
[ https://issues.apache.org/jira/browse/IGNITE-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Garaude updated IGNITE-5601: - Description: If an exception, e.g. SQLException occurs during a wite-behind operation, the exception is lost and appears nowhere in the logs. The logs basically say: [2017-06-28 10:48:52] SEVERE: Unable to update underlying store: CacheJdbcPojoStore [] [2017-06-28 10:48:52] WARNING: Failed to update store (value will be lost as current buffer size is greater than 'cacheCriticalSize' or node has been stopped before store was repaired) [key=test.WriteBehindIssue$FooKey [idHash=524852907, hash=-1388553726, id=1], val=test.WriteBehindIssue$Foo [idHash=323347362, hash=574522785, value1=abcd, value2=1234], op=PUT] If we do the same with write-through mode, it fails by throwing an exception with the SQLException as cause, deep in the trace. Would it be possible the write-behind operation logs the SQLException, and other exception? You can find a test case showing that here: https://github.com/bgaraude/IgniteTest was: If an exception, e.g. SQLException occurs during a wite-behind operation, the exception is lost and appears nowhere in the logs. The logs basically say: [2017-06-28 10:48:52] SEVERE: Unable to update underlying store: CacheJdbcPojoStore [] [2017-06-28 10:48:52] WARNING: Failed to update store (value will be lost as current buffer size is greater than 'cacheCriticalSize' or node has been stopped before store was repaired) [key=test.WriteBehindIssue$FooKey [idHash=524852907, hash=-1388553726, id=1], val=test.WriteBehindIssue$Foo [idHash=323347362, hash=574522785, value1=abcd, value2=1234], op=PUT] If we do the same with write-through mode, it fails by throwing an exception with the SQLException as cause, deep in the trace. Would it be possible the write-behind operation logs the SQLException, and other exception? You can find a test case showing that here: https://github.com/bgaraude/IgniteTest > WriteBehind mode hide SQLExceptions > --- > > Key: IGNITE-5601 > URL: https://issues.apache.org/jira/browse/IGNITE-5601 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Affects Versions: 2.0 > Environment: Ignite 2.0.0 > Oracle JDK 1.8.0_121 >Reporter: Benjamin Garaude > > If an exception, e.g. SQLException occurs during a wite-behind operation, the > exception is lost and appears nowhere in the logs. > The logs basically say: > [2017-06-28 10:48:52] SEVERE: Unable to update underlying store: > CacheJdbcPojoStore [] > [2017-06-28 10:48:52] WARNING: Failed to update store (value will be lost as > current buffer size is greater than 'cacheCriticalSize' or node has been > stopped before store was repaired) [key=test.WriteBehindIssue$FooKey > [idHash=524852907, hash=-1388553726, id=1], val=test.WriteBehindIssue$Foo > [idHash=323347362, hash=574522785, value1=abcd, value2=1234], op=PUT] > If we do the same with write-through mode, it fails by throwing an exception > with the SQLException as cause, deep in the trace. > Would it be possible the write-behind operation logs the SQLException, and > other exception? > You can find a test case showing that here: > https://github.com/bgaraude/IgniteTest -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5601) WriteBehind mode hide SQLExceptions
Benjamin Garaude created IGNITE-5601: Summary: WriteBehind mode hide SQLExceptions Key: IGNITE-5601 URL: https://issues.apache.org/jira/browse/IGNITE-5601 Project: Ignite Issue Type: Improvement Components: jdbc Affects Versions: 2.0 Environment: Ignite 2.0.0 Oracle JDK 1.8.0_121 Reporter: Benjamin Garaude If an exception, e.g. SQLException occurs during a wite-behind operation, the exception is lost and appears nowhere in the logs. The logs basically say: [2017-06-28 10:48:52] SEVERE: Unable to update underlying store: CacheJdbcPojoStore [] [2017-06-28 10:48:52] WARNING: Failed to update store (value will be lost as current buffer size is greater than 'cacheCriticalSize' or node has been stopped before store was repaired) [key=test.WriteBehindIssue$FooKey [idHash=524852907, hash=-1388553726, id=1], val=test.WriteBehindIssue$Foo [idHash=323347362, hash=574522785, value1=abcd, value2=1234], op=PUT] If we do the same with write-through mode, it fails by throwing an exception with the SQLException as cause, deep in the trace. Would it be possible the write-behind operation logs the SQLException, and other exception? You can find a test case showing that here: https://github.com/bgaraude/IgniteTest -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5600) Compute hang if send broadcast runnable on daemon cluster group
[ https://issues.apache.org/jira/browse/IGNITE-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-5600: --- Description: Step to reproduce. 1. Start server node 2. Start daemon client and daemon server 3. Try to send compute on daemon nodes was: Step to reproduce. 1. Start server node 2. Start daemon client and daemon server 3. Try to compute on daemon nodes > Compute hang if send broadcast runnable on daemon cluster group > --- > > Key: IGNITE-5600 > URL: https://issues.apache.org/jira/browse/IGNITE-5600 > Project: Ignite > Issue Type: Bug > Components: compute >Reporter: Dmitriy Govorukhin > Fix For: 2.1 > > Attachments: repdoducer.java > > > Step to reproduce. > 1. Start server node > 2. Start daemon client and daemon server > 3. Try to send compute on daemon nodes -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5087) Enum comparison fails after marshal-unmarshal with BinaryMarshaller.
[ https://issues.apache.org/jira/browse/IGNITE-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066133#comment-16066133 ] Amelchev Nikita commented on IGNITE-5087: - [~amashenkov] I fixed it, please review > Enum comparison fails after marshal-unmarshal with BinaryMarshaller. > > > Key: IGNITE-5087 > URL: https://issues.apache.org/jira/browse/IGNITE-5087 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.9 >Reporter: Andrew Mashenkov >Assignee: Amelchev Nikita > Fix For: 2.1 > > Attachments: EnumBinaryMarshallerBug.java > > > PFA repro. > It fails on 1.9 and on 2.0-snapshot as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5593) Affinity change message leak on massive topology updates
[ https://issues.apache.org/jira/browse/IGNITE-5593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066127#comment-16066127 ] ASF GitHub Bot commented on IGNITE-5593: GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2210 IGNITE-5593: Affinity change message leak on massive topology updates You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5593 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2210.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2210 commit 52a5d4f7725609050fd64335369da7d123598d35 Author: Andrey V. Mashenkov Date: 2017-06-27T17:43:07Z Fixed. commit a69488397cbd3d2209f17fc9778237cd7d8d6b79 Author: Andrey V. Mashenkov Date: 2017-06-28T08:02:48Z Minor. > Affinity change message leak on massive topology updates > > > Key: IGNITE-5593 > URL: https://issues.apache.org/jira/browse/IGNITE-5593 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.7 >Reporter: Alexey Goncharuk >Assignee: Andrew Mashenkov >Priority: Critical > Fix For: 2.1 > > > When late affinity assignment is enabled, we complete the exchange future > with custom discovery event. Since discovery topology events usually are much > faster than exchange futures completion, it is possible that a newly joined > node can 'see' the affinity change messages that are related to previous > topology versions when this node even was not present in the topology. > When this message is received, an exchange future is created and this message > is added to discoEvts list. However, this future never completes on this node > because init() is never called. This means that this exchange future sits in > the exchange set with the affinity change message. > Since the number of topology changes (and, thus, messages) can be quite > large, this leads to excessive memory consumption on the starting node. I've > observed ~3Gb of heap wasted on one of the nodes when > 200 nodes were > restarted. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5600) Compute hang if send broadcast runnable on daemon cluster group
[ https://issues.apache.org/jira/browse/IGNITE-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-5600: --- Component/s: compute > Compute hang if send broadcast runnable on daemon cluster group > --- > > Key: IGNITE-5600 > URL: https://issues.apache.org/jira/browse/IGNITE-5600 > Project: Ignite > Issue Type: Bug > Components: compute >Reporter: Dmitriy Govorukhin > Fix For: 2.1 > > Attachments: repdoducer.java > > > Step to reproduce. > 1. Start server node > 2. Start daemon client and daemon server > 3. Try to compute on daemon nodes -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5600) Compute hang if send broadcast runnable on daemon cluster group
[ https://issues.apache.org/jira/browse/IGNITE-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-5600: --- Attachment: repdoducer.java > Compute hang if send broadcast runnable on daemon cluster group > --- > > Key: IGNITE-5600 > URL: https://issues.apache.org/jira/browse/IGNITE-5600 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin > Fix For: 2.1 > > Attachments: repdoducer.java > > > Step to reproduce. > 1. Start server node > 2. Start daemon client and daemon server > 3. Try to compute on daemon nodes -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5600) Compute hang if send broadcast runnable on daemon cluster group
Dmitriy Govorukhin created IGNITE-5600: -- Summary: Compute hang if send broadcast runnable on daemon cluster group Key: IGNITE-5600 URL: https://issues.apache.org/jira/browse/IGNITE-5600 Project: Ignite Issue Type: Bug Reporter: Dmitriy Govorukhin Fix For: 2.1 Step to reproduce. 1. Start server node 2. Start daemon client and daemon server 3. Try to compute on daemon nodes -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura reassigned IGNITE-3495:
---
Assignee: Vyacheslav Koptilin (was: Vladislav Pyatkov)
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Vyacheslav Koptilin
> Fix For: 2.1
>
> Attachments: example-default.xml, ExampleNodeStartupClient.java,
> IGNITE_3495.patch
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-5536) Web console: Invalid configuration file variable in generated docker file.
[ https://issues.apache.org/jira/browse/IGNITE-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-5536: Assignee: Alexey Kuznetsov (was: Andrey Novikov) > Web console: Invalid configuration file variable in generated docker file. > -- > > Key: IGNITE-5536 > URL: https://issues.apache.org/jira/browse/IGNITE-5536 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Vasiliy Sisko >Assignee: Alexey Kuznetsov > Fix For: 2.1 > > > # Fix generation of docker file. > # Check creation and work of docker image. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (IGNITE-5536) Web console: Invalid configuration file variable in generated docker file.
[ https://issues.apache.org/jira/browse/IGNITE-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-5536. > Web console: Invalid configuration file variable in generated docker file. > -- > > Key: IGNITE-5536 > URL: https://issues.apache.org/jira/browse/IGNITE-5536 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Vasiliy Sisko >Assignee: Alexey Kuznetsov > Fix For: 2.1 > > > # Fix generation of docker file. > # Check creation and work of docker image. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5536) Web console: Invalid configuration file variable in generated docker file.
[ https://issues.apache.org/jira/browse/IGNITE-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-5536: - Summary: Web console: Invalid configuration file variable in generated docker file. (was: Web console: Invalid configu file varialbe in generated docker file.) > Web console: Invalid configuration file variable in generated docker file. > -- > > Key: IGNITE-5536 > URL: https://issues.apache.org/jira/browse/IGNITE-5536 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Vasiliy Sisko >Assignee: Andrey Novikov > Fix For: 2.1 > > > # Fix generation of docker file. > # Check creation and work of docker image. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5593) Affinity change message leak on massive topology updates
[ https://issues.apache.org/jira/browse/IGNITE-5593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov reassigned IGNITE-5593: Assignee: Andrew Mashenkov > Affinity change message leak on massive topology updates > > > Key: IGNITE-5593 > URL: https://issues.apache.org/jira/browse/IGNITE-5593 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.7 >Reporter: Alexey Goncharuk >Assignee: Andrew Mashenkov >Priority: Critical > Fix For: 2.1 > > > When late affinity assignment is enabled, we complete the exchange future > with custom discovery event. Since discovery topology events usually are much > faster than exchange futures completion, it is possible that a newly joined > node can 'see' the affinity change messages that are related to previous > topology versions when this node even was not present in the topology. > When this message is received, an exchange future is created and this message > is added to discoEvts list. However, this future never completes on this node > because init() is never called. This means that this exchange future sits in > the exchange set with the affinity change message. > Since the number of topology changes (and, thus, messages) can be quite > large, this leads to excessive memory consumption on the starting node. I've > observed ~3Gb of heap wasted on one of the nodes when > 200 nodes were > restarted. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (IGNITE-5461) Visor shows wrong statistics for off heap memory
[
https://issues.apache.org/jira/browse/IGNITE-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov closed IGNITE-5461.
> Visor shows wrong statistics for off heap memory
>
>
> Key: IGNITE-5461
> URL: https://issues.apache.org/jira/browse/IGNITE-5461
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.0
>Reporter: Mikhail Cherkasov
>Assignee: Alexey Kuznetsov
> Labels: important
> Fix For: 2.1
>
> Attachments: CreateCache.java, visor-config.xml
>
>
> Visor show that data is stored in Heap, while the data is in off heap:
> Total: 1
> Heap: 1
> Off-Heap: 0
> Off-Heap Memory: 0
> while:
> cache.localPeek("Key1", ONHEAP) == null
> cache.localPeek("Key1", OFFHEAP) == Value
> reproducer is attached.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (IGNITE-5599) Web console: Agent should check that node URL is valid
[ https://issues.apache.org/jira/browse/IGNITE-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-5599. > Web console: Agent should check that node URL is valid > -- > > Key: IGNITE-5599 > URL: https://issues.apache.org/jira/browse/IGNITE-5599 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.1 >Reporter: Vasiliy Sisko >Assignee: Alexey Kuznetsov > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (IGNITE-5599) Web console: Agent should check that node URL is valid
[ https://issues.apache.org/jira/browse/IGNITE-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-5599. -- Resolution: Fixed > Web console: Agent should check that node URL is valid > -- > > Key: IGNITE-5599 > URL: https://issues.apache.org/jira/browse/IGNITE-5599 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.1 >Reporter: Vasiliy Sisko >Assignee: Alexey Kuznetsov > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
