[jira] [Created] (IGNITE-1506) visorcmd: inconsistent result of 'disco' command
Pavel Konstantinov created IGNITE-1506: -- Summary: visorcmd: inconsistent result of 'disco' command Key: IGNITE-1506 URL: https://issues.apache.org/jira/browse/IGNITE-1506 Project: Ignite Issue Type: Bug Components: UI Affects Versions: ignite-1.4 Reporter: Pavel Konstantinov Assignee: Vasiliy Sisko Priority: Minor Fix For: ignite-1.5 Currently 'disco' command shows at least on event (from node which executes the task) in result even if discovery events are not configured - this is a bit confuses. I think would be better to print out something like 'discovery events are not configured'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1506) visorcmd: inconsistent result of 'disco' command
[ https://issues.apache.org/jira/browse/IGNITE-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1506: --- Description: Currently 'disco' command shows at least one event (from node which executes the task) in result even if discovery events are not configured - this is a bit confuses. I think would be better to print out something like 'discovery events are not configured'. was: Currently 'disco' command shows at least on event (from node which executes the task) in result even if discovery events are not configured - this is a bit confuses. I think would be better to print out something like 'discovery events are not configured'. > visorcmd: inconsistent result of 'disco' command > > > Key: IGNITE-1506 > URL: https://issues.apache.org/jira/browse/IGNITE-1506 > Project: Ignite > Issue Type: Bug > Components: UI >Affects Versions: ignite-1.4 >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko >Priority: Minor > Fix For: ignite-1.5 > > > Currently 'disco' command shows at least one event (from node which executes > the task) in result even if discovery events are not configured - this is a > bit confuses. > I think would be better to print out something like 'discovery events are not > configured'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1507) visorcmd: need to correct help text for 'tasks' command
[
https://issues.apache.org/jira/browse/IGNITE-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-1507:
---
Description:
currently we printing out
{code}
By default - all events are *enabled* and Ignite stores last 10,000 local
events on each node. Both of these defaults can be changed in configuration.
{code}
But now all events are disabled by default.
was:
currently we printing out
{code}
By default - all events are enabled and Ignite stores last 10,000 local
events on each node. Both of these defaults can be changed in configuration.
{code}
But now all events are disabled by default.
> visorcmd: need to correct help text for 'tasks' command
> ---
>
> Key: IGNITE-1507
> URL: https://issues.apache.org/jira/browse/IGNITE-1507
> Project: Ignite
> Issue Type: Task
> Components: UI
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Minor
> Fix For: ignite-1.5
>
>
> currently we printing out
> {code}
>
>
>
> By default - all events are *enabled* and Ignite stores last 10,000 local
> events on each node. Both of these defaults can be changed in configuration.
> {code}
> But now all events are disabled by default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1507) visorcmd: need to correct help text for 'tasks' command
Pavel Konstantinov created IGNITE-1507:
--
Summary: visorcmd: need to correct help text for 'tasks' command
Key: IGNITE-1507
URL: https://issues.apache.org/jira/browse/IGNITE-1507
Project: Ignite
Issue Type: Task
Components: UI
Affects Versions: ignite-1.4
Reporter: Pavel Konstantinov
Assignee: Vasiliy Sisko
Priority: Minor
Fix For: ignite-1.5
currently we printing out
{code}
By default - all events are enabled and Ignite stores last 10,000 local
events on each node. Both of these defaults can be changed in configuration.
{code}
But now all events are disabled by default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-1218) Show how configuration changes as the user updates the fields.
[ https://issues.apache.org/jira/browse/IGNITE-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-1218. > Show how configuration changes as the user updates the fields. > -- > > Key: IGNITE-1218 > URL: https://issues.apache.org/jira/browse/IGNITE-1218 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Dmitriy Setrakyan >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > > It would be nice if we allocated some area to show the current configuration > tabs (just like on summary screen) as the user keeps entering new data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-850) Implement clusters screen
[ https://issues.apache.org/jira/browse/IGNITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-850. --- Assignee: (was: Pavel Konstantinov) > Implement clusters screen > - > > Key: IGNITE-850 > URL: https://issues.apache.org/jira/browse/IGNITE-850 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk > Fix For: ignite-1.5 > > Attachments: cluster page.png, clusters-page-2.png, > clusters-page-3.png, clusters.pdf, ig-850-zones.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1363) Add animations for angular strap elements.
[ https://issues.apache.org/jira/browse/IGNITE-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-1363: Assignee: (was: Andrey Novikov) > Add animations for angular strap elements. > -- > > Key: IGNITE-1363 > URL: https://issues.apache.org/jira/browse/IGNITE-1363 > Project: Ignite > Issue Type: Sub-task > Components: UI >Affects Versions: ignite-1.4 >Reporter: Vasiliy Sisko >Priority: Minor > Fix For: ignite-1.4 > > > Tooltip, popover, popup, modal. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1489) Usability issues
[ https://issues.apache.org/jira/browse/IGNITE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14805197#comment-14805197 ] Alexey Kuznetsov commented on IGNITE-1489: -- Implemented. > Usability issues > > > Key: IGNITE-1489 > URL: https://issues.apache.org/jira/browse/IGNITE-1489 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: ignite-1.5 > > > Sub-ticket for collecting usability issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1489) Usability issues
[ https://issues.apache.org/jira/browse/IGNITE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14805198#comment-14805198 ] Alexey Kuznetsov commented on IGNITE-1489: -- What about to generate cache definition in XML (cache bean) and Java-preview (CacheConfiguration cache = new CacheConfiguration() to have a completed code for each section? > Usability issues > > > Key: IGNITE-1489 > URL: https://issues.apache.org/jira/browse/IGNITE-1489 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: ignite-1.5 > > > Sub-ticket for collecting usability issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1485) Improve loading metadata from DB
[ https://issues.apache.org/jira/browse/IGNITE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-1485. Assignee: (was: Alexey Kuznetsov) > Improve loading metadata from DB > > > Key: IGNITE-1485 > URL: https://issues.apache.org/jira/browse/IGNITE-1485 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov > Fix For: ignite-1.5 > > > I think will be useful to generate separate cache for each metadata loaded > from DB. > In this case web console will generate a cache + metadata linked to it. > User could point already created cache as a template for generation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1485) Improve loading metadata from DB
[ https://issues.apache.org/jira/browse/IGNITE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-1485. -- Resolution: Duplicate Moved text to IGNITE-1489. > Improve loading metadata from DB > > > Key: IGNITE-1485 > URL: https://issues.apache.org/jira/browse/IGNITE-1485 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > > I think will be useful to generate separate cache for each metadata loaded > from DB. > In this case web console will generate a cache + metadata linked to it. > User could point already created cache as a template for generation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1489) Usability issues
[ https://issues.apache.org/jira/browse/IGNITE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14805201#comment-14805201 ] Alexey Kuznetsov commented on IGNITE-1489: -- It think will be useful to generate separate cache for each metadata loaded from DB. In this case web console will generate a cache + metadata linked to it. User could point already created cache as a template for generation. We could have some checkbox for it. > Usability issues > > > Key: IGNITE-1489 > URL: https://issues.apache.org/jira/browse/IGNITE-1489 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: ignite-1.5 > > > Sub-ticket for collecting usability issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1147) Implement profile page for user.
[ https://issues.apache.org/jira/browse/IGNITE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-1147. Assignee: (was: Alexey Kuznetsov) > Implement profile page for user. > > > Key: IGNITE-1147 > URL: https://issues.apache.org/jira/browse/IGNITE-1147 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov > Fix For: ignite-1.5 > > Attachments: profile.png > > > Need add possibility to change email, password, username. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1147) Implement profile page for user.
[ https://issues.apache.org/jira/browse/IGNITE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-1147. -- Resolution: Fixed > Implement profile page for user. > > > Key: IGNITE-1147 > URL: https://issues.apache.org/jira/browse/IGNITE-1147 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: profile.png > > > Need add possibility to change email, password, username. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1214) Implement validation instead of blocking "Save" button
[ https://issues.apache.org/jira/browse/IGNITE-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-1214. > Implement validation instead of blocking "Save" button > -- > > Key: IGNITE-1214 > URL: https://issues.apache.org/jira/browse/IGNITE-1214 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: ignite-1.4 >Reporter: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: > #_IGNITE-1214_Validation_of_cluster,_common_validation.patch, > #_IGNITE-1214_Validation_of_cluster_discovery.patch > > > We should not block "Save" button, but instead set focus to field with error > and show error message near it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1148) Implement sql query to ignite node.
[ https://issues.apache.org/jira/browse/IGNITE-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-1148. -- Resolution: Fixed Assignee: Pavel Konstantinov (was: Andrey Novikov) Pavel, please test SQL functionality. > Implement sql query to ignite node. > --- > > Key: IGNITE-1148 > URL: https://issues.apache.org/jira/browse/IGNITE-1148 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > Attachments: metadata mockup.png, sql - notebooks.png > > > Need create page for display sql query result: > * Add optional select cache. > * Scan query > * Explain query > * Query > * Show metadata. > Connect with agent through websocket. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1201) Create tests for Web Console Agent
[ https://issues.apache.org/jira/browse/IGNITE-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-1201: - Summary: Create tests for Web Console Agent (was: Create tests for Web Control Center Agent) > Create tests for Web Console Agent > -- > > Key: IGNITE-1201 > URL: https://issues.apache.org/jira/browse/IGNITE-1201 > Project: Ignite > Issue Type: Sub-task >Reporter: Sergey Evdokimov >Assignee: Alexey Kuznetsov > Attachments: ignite-843_4abc9f1_ignite-1201.patch > > > Need tests for Web Control Center Agent. > Tests should simulate Web Control Center requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-586) [Test] GridGgfsAbstractSelfTest.testFormat() fails on TC.
[ https://issues.apache.org/jira/browse/IGNITE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-586: --- Fix Version/s: (was: ignite-1.4) ignite-1.5 > [Test] GridGgfsAbstractSelfTest.testFormat() fails on TC. > - > > Key: IGNITE-586 > URL: https://issues.apache.org/jira/browse/IGNITE-586 > Project: Ignite > Issue Type: Bug > Components: hadoop >Reporter: Artem Shutak >Assignee: Ivan Veselovsky > Labels: failedtest > Fix For: ignite-1.5 > > > The problem is that format() doesn't clean all previously written data. > See GG-8578 (the issue was closed, but stay reproducible) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-586) [Test] GridGgfsAbstractSelfTest.testFormat() fails on TC.
[ https://issues.apache.org/jira/browse/IGNITE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14805258#comment-14805258 ] Vladimir Ozerov commented on IGNITE-586: Moving back to ignite-1.5 again because the problem appears to be bigger than expected. > [Test] GridGgfsAbstractSelfTest.testFormat() fails on TC. > - > > Key: IGNITE-586 > URL: https://issues.apache.org/jira/browse/IGNITE-586 > Project: Ignite > Issue Type: Bug > Components: hadoop >Reporter: Artem Shutak >Assignee: Ivan Veselovsky > Labels: failedtest > Fix For: ignite-1.5 > > > The problem is that format() doesn't clean all previously written data. > See GG-8578 (the issue was closed, but stay reproducible) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1508) .Net: Create common ToString() method.
Vladimir Ozerov created IGNITE-1508: --- Summary: .Net: Create common ToString() method. Key: IGNITE-1508 URL: https://issues.apache.org/jira/browse/IGNITE-1508 Project: Ignite Issue Type: Improvement Components: interop Affects Versions: 1.1.4 Reporter: Vladimir Ozerov Fix For: ignite-1.5 We have lots of places with the same code pattern in ToString() method: culture info + String.Format(). Let's move it to utilities and re-use just like it is done in Java. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1509) .Net: User must operate on IEnumerable in events API rather than on arrays.
Vladimir Ozerov created IGNITE-1509: --- Summary: .Net: User must operate on IEnumerable in events API rather than on arrays. Key: IGNITE-1509 URL: https://issues.apache.org/jira/browse/IGNITE-1509 Project: Ignite Issue Type: Task Components: interop Affects Versions: 1.1.4 Reporter: Vladimir Ozerov Priority: Blocker Fix For: ignite-1.5 Currently we expose arrays for event groups. As they are mutable, we have to copy them every time user use them. To avoid this we should switch to IEnumerables and leave shortcut methods with "params[]" for convenience. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1494) Get return nulls for some cache configurations
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-1494:
--
Attachment: (was: grid_config_01.xml)
> Get return nulls for some cache configurations
> --
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Critical
> Fix For: ignite-1.4
>
>
> 1. Copy grid_config_01.xml and grid_config_01.client.xml in examples/config
> directory (it contains 25 FULL_SYNCed cache configurations)
> 2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
> 3. Start two nodes by bin/ignite.sh examples/config/grid_config_01.xml
> 4. Build and run CacheTestExample (it makes put/get/remove operations for 100
> keys)
> 5. The normal output should be following:
> {noformat}
> [12:12:02] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [12:12:02]
> [12:12:02] Ignite node started OK (id=3f1ea113)
> [12:12:02] Topology snapshot [ver=5, servers=2, clients=1, CPUs=8, heap=3.8GB]
> >>>cache_0001
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> >>>cache_0002
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> >>>cache_0003
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> ...
> {noformat}
> But for some caches I got:
> {noformat}
> >>>cache_0011
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Wrong value found [key=1, val=null]
> Wrong value found [key=2, val=null]
> Wrong value found [key=3, val=null]
> Wrong value found [key=4, val=null]
> Get 21..100
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1494) Get return nulls for some cache configurations
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-1494:
--
Attachment: (was: CacheTestExample.java)
> Get return nulls for some cache configurations
> --
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Critical
> Fix For: ignite-1.4
>
>
> 1. Copy grid_config_01.xml and grid_config_01.client.xml in examples/config
> directory (it contains 25 FULL_SYNCed cache configurations)
> 2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
> 3. Start two nodes by bin/ignite.sh examples/config/grid_config_01.xml
> 4. Build and run CacheTestExample (it makes put/get/remove operations for 100
> keys)
> 5. The normal output should be following:
> {noformat}
> [12:12:02] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [12:12:02]
> [12:12:02] Ignite node started OK (id=3f1ea113)
> [12:12:02] Topology snapshot [ver=5, servers=2, clients=1, CPUs=8, heap=3.8GB]
> >>>cache_0001
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> >>>cache_0002
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> >>>cache_0003
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> ...
> {noformat}
> But for some caches I got:
> {noformat}
> >>>cache_0011
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Wrong value found [key=1, val=null]
> Wrong value found [key=2, val=null]
> Wrong value found [key=3, val=null]
> Wrong value found [key=4, val=null]
> Get 21..100
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1494) Get return nulls for some cache configurations
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-1494:
--
Description:
1. Copy grid_config_01.xml and grid_config_01.client.xml in examples/config
directory (it contains 25 FULL_SYNCed cache configurations)
2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
3. Start two nodes by bin/ignite.sh examples/config/grid_config_01.xml
4. Build and run CacheTestExample (it makes put/get/remove operations for 100
keys)
5. The normal output should be following:
{noformat}
[12:12:02] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[12:12:02]
[12:12:02] Ignite node started OK (id=3f1ea113)
[12:12:02] Topology snapshot [ver=5, servers=2, clients=1, CPUs=8, heap=3.8GB]
>>>cache_0001
Put 100 -> put1_
Get 100
RemoveAll 100
Put 1..50 -> put2_
Remove 30.40
RemoveAll 21..50
PutAll 21..100 -> putall_
Get 1..20
Get 21..100
>>>cache_0002
Put 100 -> put1_
Get 100
RemoveAll 100
Put 1..50 -> put2_
Remove 30.40
RemoveAll 21..50
PutAll 21..100 -> putall_
Get 1..20
Get 21..100
>>>cache_0003
Put 100 -> put1_
Get 100
RemoveAll 100
Put 1..50 -> put2_
Remove 30.40
RemoveAll 21..50
PutAll 21..100 -> putall_
Get 1..20
Get 21..100
...
{noformat}
But for some caches I got:
{noformat}
>>>cache_0011
Put 100 -> put1_
Get 100
RemoveAll 100
Put 1..50 -> put2_
Remove 30.40
RemoveAll 21..50
PutAll 21..100 -> putall_
Get 1..20
Wrong value found [key=1, val=null]
Wrong value found [key=2, val=null]
Wrong value found [key=3, val=null]
Wrong value found [key=4, val=null]
Get 21..100
...
{noformat}
was:
1. Copy grid_config_01.xml in examples/config directory (it contains 25
FULL_SYNCed cache configurations)
2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
3. Start two nodes by bin/ignite.sh examples/config/grid_config_01.xml
4. Build and run CacheTestExample (it makes 1000 single key-value puts and then
1000 gets)
5. The normal output should be following:
{noformat}
[22:55:58]__
[22:55:58] / _/ ___/ |/ / _/_ __/ __/
[22:55:58] _/ // (7 7// / / / / _/
[22:55:58] /___/\___/_/|_/___/ /_/ /___/
[22:55:58]
[22:55:58] ver. 1.4.0-QASVK150901#20150915-sha1:3e762e25
[22:55:58] 2015 Copyright(C) Apache Software Foundation
[22:55:58]
[22:55:58] Ignite documentation: http://ignite.apache.org
[22:55:58]
[22:55:58] Quiet mode.
[22:55:58] ^-- Logging to file
'D:\1.4.0\gridgain-community-fabric-1.4.0-QASVK150901\work\log\ignite-faa18f29.log'
[22:55:58] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
"-v" to ignite.{sh|bat}
[22:55:58]
[22:55:58] Initial heap size is 256MB (should be no less than 512MB, use
-Xms512m -Xmx512m).
[22:56:00] Configured plugins:
[22:56:00] ^-- None
[22:56:00]
[22:56:01] Security status [authentication=off, communication encryption=off]
[22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
(entries will not be moved to off-heap store): cache_4
[22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
(entries will not be moved to off-heap store): cache_1
[22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
(entries will not be moved to off-heap store): cache_10
[22:56:04] Performance suggestions for grid (fix if possible)
[22:56:04] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[22:56:04] ^-- Disable fully synchronous writes (set
'writeSynchronizationMode' to PRIMARY_SYNC or FULL_ASYNC)
[22:56:04] ^-- Decrease number of backups (set 'keyBackups' to 0)
[22:56:04]
[22:56:04] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[22:56:04]
[22:56:04] Ignite node started OK (id=faa18f29)
[22:56:04] Topology snapshot [ver=3, servers=3, clients=0, CPUs=4, heap=5.5GB]
>>>cache_1
Put for 1000
Get for 1000
>>>cache_2
Put for 1000
[23:03:21] New version is available at
http://www.gridgain.com/download/editions: 1.3.3
Get for 1000
>>>cache_3
Put for 1000
Get for 1000
>>>cache_4
Put for 1000
Get for 1000
...
{noformat}
But for some caches I got:
{noformat}
>>>cache_18
Put for 1000
Get for 1000
Wrong value found [key=0, val=null]
Wrong value found [key=1, val=null]
Wrong value found [key=2, val=null]
Wrong value found [key=3, val=null]
Wrong value found [key=4, val=null]
Wrong value found [key=5, val=null]
Wrong value found [key=6, val=null]
Wrong value found [key=7, val=null]
Wrong value found [key=8, val=null]
Wrong value found [key=9, val=null]
...
{noformat}
> Get return nulls for some cache configurations
> --
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
[jira] [Assigned] (IGNITE-1494) Get return nulls for some cache configurations
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov reassigned IGNITE-1494:
Assignee: Semen Boikov (was: Sergey Kozlov)
> Get return nulls for some cache configurations
> --
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: ignite-1.4
>
> Attachments: CacheTestExample.java, grid_config_01.client.xml,
> grid_config_01.xml
>
>
> 1. Copy grid_config_01.xml and grid_config_01.client.xml in examples/config
> directory (it contains 25 FULL_SYNCed cache configurations)
> 2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
> 3. Start two nodes by bin/ignite.sh examples/config/grid_config_01.xml
> 4. Build and run CacheTestExample (it makes put/get/remove operations for 100
> keys)
> 5. The normal output should be following:
> {noformat}
> [12:12:02] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [12:12:02]
> [12:12:02] Ignite node started OK (id=3f1ea113)
> [12:12:02] Topology snapshot [ver=5, servers=2, clients=1, CPUs=8, heap=3.8GB]
> >>>cache_0001
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> >>>cache_0002
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> >>>cache_0003
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> ...
> {noformat}
> But for some caches I got:
> {noformat}
> >>>cache_0011
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Wrong value found [key=1, val=null]
> Wrong value found [key=2, val=null]
> Wrong value found [key=3, val=null]
> Wrong value found [key=4, val=null]
> Get 21..100
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1494) Get return nulls for some cache configurations
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-1494:
--
Attachment: CacheTestExample.java
grid_config_01.xml
grid_config_01.client.xml
> Get return nulls for some cache configurations
> --
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Critical
> Fix For: ignite-1.4
>
> Attachments: CacheTestExample.java, grid_config_01.client.xml,
> grid_config_01.xml
>
>
> 1. Copy grid_config_01.xml and grid_config_01.client.xml in examples/config
> directory (it contains 25 FULL_SYNCed cache configurations)
> 2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
> 3. Start two nodes by bin/ignite.sh examples/config/grid_config_01.xml
> 4. Build and run CacheTestExample (it makes put/get/remove operations for 100
> keys)
> 5. The normal output should be following:
> {noformat}
> [12:12:02] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [12:12:02]
> [12:12:02] Ignite node started OK (id=3f1ea113)
> [12:12:02] Topology snapshot [ver=5, servers=2, clients=1, CPUs=8, heap=3.8GB]
> >>>cache_0001
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> >>>cache_0002
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> >>>cache_0003
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> ...
> {noformat}
> But for some caches I got:
> {noformat}
> >>>cache_0011
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Wrong value found [key=1, val=null]
> Wrong value found [key=2, val=null]
> Wrong value found [key=3, val=null]
> Wrong value found [key=4, val=null]
> Get 21..100
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1510) Weird format() and remove() semantics.
Vladimir Ozerov created IGNITE-1510: --- Summary: Weird format() and remove() semantics. Key: IGNITE-1510 URL: https://issues.apache.org/jira/browse/IGNITE-1510 Project: Ignite Issue Type: Task Components: hadoop Affects Versions: 1.1.4 Reporter: Vladimir Ozerov Priority: Critical Fix For: ignite-1.5 Currently we have two methods to remove something from IGFS: 1) remove - performs soft delete for PRIMARY mode and hard delete for others 2) format - delete of all IGFS data without touching seocndary file system, which can be either soft or hard depending on some very coutner-intuitive conditions. I think we should do the following: 1) remove operation stays as is. 2) format method is deprecated and just falls-back to a new method "clear(ROOT)". 3) "clear" operation is semantically identical to cache clear: remove in-memory data, do not touch persistence layer. Essentially it just moves a tree into the trash just like remove does. But also this operation will offer sync and async modes. In sync mode operation exits when all data in-memory data is really removed even from trash. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1511) Revisit IGFS delete worker.
Vladimir Ozerov created IGNITE-1511: --- Summary: Revisit IGFS delete worker. Key: IGNITE-1511 URL: https://issues.apache.org/jira/browse/IGNITE-1511 Project: Ignite Issue Type: Task Components: hadoop Affects Versions: 1.1.4 Reporter: Vladimir Ozerov Priority: Critical Fix For: ignite-1.5 Looks like our IGFS delete worker is broken: 1) It doesn't account of locked files 2) It first removes data and then removes meta. Looks like we should do that in the opposite order to prevent orphaned data blocks in case very close concurrent write. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1494) Get return nulls for some cache configurations
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-1494:
--
Description:
1. Copy grid_config_01.xml and grid_config_01.client.xml in examples/config
directory (it contains 25 FULL_SYNCed cache configurations)
2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
3. Start two nodes by bin/ignite.sh examples/config/grid_config_01.xml
4. Build and run CacheTestExample (it makes put/get/remove operations for 100
keys) a few times (w/o stopping server nodes)
5. The normal output should be following:
{noformat}
[12:12:02] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[12:12:02]
[12:12:02] Ignite node started OK (id=3f1ea113)
[12:12:02] Topology snapshot [ver=5, servers=2, clients=1, CPUs=8, heap=3.8GB]
>>>cache_0001
Put 100 -> put1_
Get 100
RemoveAll 100
Put 1..50 -> put2_
Remove 30.40
RemoveAll 21..50
PutAll 21..100 -> putall_
Get 1..20
Get 21..100
>>>cache_0002
Put 100 -> put1_
Get 100
RemoveAll 100
Put 1..50 -> put2_
Remove 30.40
RemoveAll 21..50
PutAll 21..100 -> putall_
Get 1..20
Get 21..100
>>>cache_0003
Put 100 -> put1_
Get 100
RemoveAll 100
Put 1..50 -> put2_
Remove 30.40
RemoveAll 21..50
PutAll 21..100 -> putall_
Get 1..20
Get 21..100
...
{noformat}
But for some caches I got:
{noformat}
>>>cache_0011
Put 100 -> put1_
Get 100
RemoveAll 100
Put 1..50 -> put2_
Remove 30.40
RemoveAll 21..50
PutAll 21..100 -> putall_
Get 1..20
Wrong value found [key=1, val=null]
Wrong value found [key=2, val=null]
Wrong value found [key=3, val=null]
Wrong value found [key=4, val=null]
Get 21..100
...
{noformat}
was:
1. Copy grid_config_01.xml and grid_config_01.client.xml in examples/config
directory (it contains 25 FULL_SYNCed cache configurations)
2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
3. Start two nodes by bin/ignite.sh examples/config/grid_config_01.xml
4. Build and run CacheTestExample (it makes put/get/remove operations for 100
keys)
5. The normal output should be following:
{noformat}
[12:12:02] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[12:12:02]
[12:12:02] Ignite node started OK (id=3f1ea113)
[12:12:02] Topology snapshot [ver=5, servers=2, clients=1, CPUs=8, heap=3.8GB]
>>>cache_0001
Put 100 -> put1_
Get 100
RemoveAll 100
Put 1..50 -> put2_
Remove 30.40
RemoveAll 21..50
PutAll 21..100 -> putall_
Get 1..20
Get 21..100
>>>cache_0002
Put 100 -> put1_
Get 100
RemoveAll 100
Put 1..50 -> put2_
Remove 30.40
RemoveAll 21..50
PutAll 21..100 -> putall_
Get 1..20
Get 21..100
>>>cache_0003
Put 100 -> put1_
Get 100
RemoveAll 100
Put 1..50 -> put2_
Remove 30.40
RemoveAll 21..50
PutAll 21..100 -> putall_
Get 1..20
Get 21..100
...
{noformat}
But for some caches I got:
{noformat}
>>>cache_0011
Put 100 -> put1_
Get 100
RemoveAll 100
Put 1..50 -> put2_
Remove 30.40
RemoveAll 21..50
PutAll 21..100 -> putall_
Get 1..20
Wrong value found [key=1, val=null]
Wrong value found [key=2, val=null]
Wrong value found [key=3, val=null]
Wrong value found [key=4, val=null]
Get 21..100
...
{noformat}
> Get return nulls for some cache configurations
> --
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: ignite-1.4
>
> Attachments: CacheTestExample.java, grid_config_01.client.xml,
> grid_config_01.xml
>
>
> 1. Copy grid_config_01.xml and grid_config_01.client.xml in examples/config
> directory (it contains 25 FULL_SYNCed cache configurations)
> 2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
> 3. Start two nodes by bin/ignite.sh examples/config/grid_config_01.xml
> 4. Build and run CacheTestExample (it makes put/get/remove operations for 100
> keys) a few times (w/o stopping server nodes)
> 5. The normal output should be following:
> {noformat}
> [12:12:02] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [12:12:02]
> [12:12:02] Ignite node started OK (id=3f1ea113)
> [12:12:02] Topology snapshot [ver=5, servers=2, clients=1, CPUs=8, heap=3.8GB]
> >>>cache_0001
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> >>>cache_0002
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> >>>cache_0003
> Put 100 -> put1_
> Get 100
> RemoveAll 100
> Put 1..50 -> put2_
> Remove 30.40
> RemoveAll 21..50
> PutAll 21..100 -> putall_
> Get 1..20
> Get 21..100
> ...
> {noformat}
> But for some c
[jira] [Created] (IGNITE-1512) Rework IGFS remove operation.
Vladimir Ozerov created IGNITE-1512: --- Summary: Rework IGFS remove operation. Key: IGNITE-1512 URL: https://issues.apache.org/jira/browse/IGNITE-1512 Project: Ignite Issue Type: Task Components: hadoop Affects Versions: 1.1.4 Reporter: Vladimir Ozerov Priority: Critical Fix For: ignite-1.5 Currently it goes through "move" on it's final stage. This causes redundant code dependencies and unnecessary check. Let's implement it as a separate method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1492) Platform .Net: Set up FxCop project, fix/suppress warnings
[ https://issues.apache.org/jira/browse/IGNITE-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14805283#comment-14805283 ] Pavel Tupitsyn commented on IGNITE-1492: - 1,2) fixed 3) It does not: https://msdn.microsoft.com/en-us/library/ms229012(v=vs.110).aspx. Actually, "protected instance fields are not allowed by the member design guidelines.", but other than that, non-private fields should be PascalCase. Anyway, I made it private, we have accessor methods. > Platform .Net: Set up FxCop project, fix/suppress warnings > -- > > Key: IGNITE-1492 > URL: https://issues.apache.org/jira/browse/IGNITE-1492 > Project: Ignite > Issue Type: Sub-task >Affects Versions: ignite-1.5 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: ignite-1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1513) Implement build procedure for platforms.
Vladimir Ozerov created IGNITE-1513: --- Summary: Implement build procedure for platforms. Key: IGNITE-1513 URL: https://issues.apache.org/jira/browse/IGNITE-1513 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: 1.1.4 Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Priority: Blocker Fix For: ignite-1.5 1) To simplify things all CPP and .Net stuff must be moved to a two folders: dotnet and cpp. 2) Both .Net and CPP will be redistributed as source with VS/autotools projects exposed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1423) Zero expiry policy does not work sometimes
[
https://issues.apache.org/jira/browse/IGNITE-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14805372#comment-14805372
]
Roman Shtykh commented on IGNITE-1423:
--
I might be wrong, but shouldn't
{code}
cache0.put(key0, key0);
cache0.put(key1, key1);
cache.get(key0);
cache.get(key1);
assert !cache0.containsKey(key0);
assert !cache0.containsKey(key1);
{code}
be
{code}
cache0.put(key0, key0);
cache0.put(key1, key1);
cache.get(key0);
cache.get(key1);
assert cache0.containsKey(key0);
assert cache0.containsKey(key1);
{code}
as in the previous code chunk?
> Zero expiry policy does not work sometimes
> --
>
> Key: IGNITE-1423
> URL: https://issues.apache.org/jira/browse/IGNITE-1423
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: ignite-1.5
>
>
> Paste the following test to GridCacheReplicatedMultiNodeFullApiSelfTest.java
> and run.
> Last assertion fails. Cycle is necessary because it does not always fail.
> {code:title=GridCacheReplicatedMultiNodeFullApiSelfTest.java}
> public void testExpiredBug() throws Exception {
> final ExpiryPolicy plc = new ExpiryPolicy() {
> @Override public Duration getExpiryForCreation() {
> return Duration.ZERO;
> }
> @Override public Duration getExpiryForAccess() {
> return Duration.ZERO;
> }
> @Override public Duration getExpiryForUpdate() {
> return Duration.ZERO;
> }
> };
> IgniteCache c1 = ignite(0).cache(null);
> IgniteCache c2 = ignite(1).cache(null);
> String key0 = primaryKeysForCache(c1, 1).get(0);
> String key1 = primaryKeysForCache(c2, 1).get(0);
> IgniteCache cache0 = c1;
> IgniteCache cache = c1.withExpiryPolicy(plc);
> for (int i = 0; i < 3000; i++) {
> cache.put(key0, key0);
> cache.put(key1, key1);
> assert !cache0.containsKey(key0);
> assert !cache0.containsKey(key1);
> cache0.put(key0, key0);
> cache0.put(key1, key1);
> assert cache0.containsKey(key0);
> assert cache0.containsKey(key1);
> cache.put(key0, key0 + 1);
> cache.put(key1, key1 + 1);
> assert !cache0.containsKey(key0);
> assert !cache0.containsKey(key1);
> cache0.put(key0, key0);
> cache0.put(key1, key1);
> cache.get(key0);
> cache.get(key1);
> assert !cache0.containsKey(key0);
> assert !cache0.containsKey(key1);
> }
> }}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1423) Zero expiry policy does not work sometimes
[
https://issues.apache.org/jira/browse/IGNITE-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14819650#comment-14819650
]
Pavel Tupitsyn commented on IGNITE-1423:
-
Roman, why do you think so? See javax.cache.expiry.ExpiryPolicy javadoc: "If a
{@link Duration#ZERO} is returned the new Cache.Entry is considered to be
already expired and will not be added to the Cache.". So containsKey should
return false.
> Zero expiry policy does not work sometimes
> --
>
> Key: IGNITE-1423
> URL: https://issues.apache.org/jira/browse/IGNITE-1423
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: ignite-1.5
>
>
> Paste the following test to GridCacheReplicatedMultiNodeFullApiSelfTest.java
> and run.
> Last assertion fails. Cycle is necessary because it does not always fail.
> {code:title=GridCacheReplicatedMultiNodeFullApiSelfTest.java}
> public void testExpiredBug() throws Exception {
> final ExpiryPolicy plc = new ExpiryPolicy() {
> @Override public Duration getExpiryForCreation() {
> return Duration.ZERO;
> }
> @Override public Duration getExpiryForAccess() {
> return Duration.ZERO;
> }
> @Override public Duration getExpiryForUpdate() {
> return Duration.ZERO;
> }
> };
> IgniteCache c1 = ignite(0).cache(null);
> IgniteCache c2 = ignite(1).cache(null);
> String key0 = primaryKeysForCache(c1, 1).get(0);
> String key1 = primaryKeysForCache(c2, 1).get(0);
> IgniteCache cache0 = c1;
> IgniteCache cache = c1.withExpiryPolicy(plc);
> for (int i = 0; i < 3000; i++) {
> cache.put(key0, key0);
> cache.put(key1, key1);
> assert !cache0.containsKey(key0);
> assert !cache0.containsKey(key1);
> cache0.put(key0, key0);
> cache0.put(key1, key1);
> assert cache0.containsKey(key0);
> assert cache0.containsKey(key1);
> cache.put(key0, key0 + 1);
> cache.put(key1, key1 + 1);
> assert !cache0.containsKey(key0);
> assert !cache0.containsKey(key1);
> cache0.put(key0, key0);
> cache0.put(key1, key1);
> cache.get(key0);
> cache.get(key1);
> assert !cache0.containsKey(key0);
> assert !cache0.containsKey(key1);
> }
> }}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-851) Implement caches screen
[ https://issues.apache.org/jira/browse/IGNITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-851. - Resolution: Fixed > Implement caches screen > --- > > Key: IGNITE-851 > URL: https://issues.apache.org/jira/browse/IGNITE-851 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: Caches.pdf, caches-page-advanced-2.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-851) Implement caches screen
[ https://issues.apache.org/jira/browse/IGNITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-851. --- Assignee: (was: Alexey Kuznetsov) > Implement caches screen > --- > > Key: IGNITE-851 > URL: https://issues.apache.org/jira/browse/IGNITE-851 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk > Fix For: ignite-1.5 > > Attachments: Caches.pdf, caches-page-advanced-2.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-1177. -- Resolution: Fixed Assignee: Pavel Konstantinov (was: Alexey Kuznetsov) Fixed issue with package name and selection of items in tables with filtration. > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1423) Zero expiry policy does not work sometimes
[
https://issues.apache.org/jira/browse/IGNITE-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14842454#comment-14842454
]
Roman Shtykh commented on IGNITE-1423:
--
I apologize, I forgot about getExpiryForAccess
> Zero expiry policy does not work sometimes
> --
>
> Key: IGNITE-1423
> URL: https://issues.apache.org/jira/browse/IGNITE-1423
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: ignite-1.5
>
>
> Paste the following test to GridCacheReplicatedMultiNodeFullApiSelfTest.java
> and run.
> Last assertion fails. Cycle is necessary because it does not always fail.
> {code:title=GridCacheReplicatedMultiNodeFullApiSelfTest.java}
> public void testExpiredBug() throws Exception {
> final ExpiryPolicy plc = new ExpiryPolicy() {
> @Override public Duration getExpiryForCreation() {
> return Duration.ZERO;
> }
> @Override public Duration getExpiryForAccess() {
> return Duration.ZERO;
> }
> @Override public Duration getExpiryForUpdate() {
> return Duration.ZERO;
> }
> };
> IgniteCache c1 = ignite(0).cache(null);
> IgniteCache c2 = ignite(1).cache(null);
> String key0 = primaryKeysForCache(c1, 1).get(0);
> String key1 = primaryKeysForCache(c2, 1).get(0);
> IgniteCache cache0 = c1;
> IgniteCache cache = c1.withExpiryPolicy(plc);
> for (int i = 0; i < 3000; i++) {
> cache.put(key0, key0);
> cache.put(key1, key1);
> assert !cache0.containsKey(key0);
> assert !cache0.containsKey(key1);
> cache0.put(key0, key0);
> cache0.put(key1, key1);
> assert cache0.containsKey(key0);
> assert cache0.containsKey(key1);
> cache.put(key0, key0 + 1);
> cache.put(key1, key1 + 1);
> assert !cache0.containsKey(key0);
> assert !cache0.containsKey(key1);
> cache0.put(key0, key0);
> cache0.put(key1, key1);
> cache.get(key0);
> cache.get(key1);
> assert !cache0.containsKey(key0);
> assert !cache0.containsKey(key1);
> }
> }}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (IGNITE-1423) Zero expiry policy does not work sometimes
[
https://issues.apache.org/jira/browse/IGNITE-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shtykh updated IGNITE-1423:
-
Comment: was deleted
(was: I apologize, I forgot about getExpiryForAccess)
> Zero expiry policy does not work sometimes
> --
>
> Key: IGNITE-1423
> URL: https://issues.apache.org/jira/browse/IGNITE-1423
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: ignite-1.5
>
>
> Paste the following test to GridCacheReplicatedMultiNodeFullApiSelfTest.java
> and run.
> Last assertion fails. Cycle is necessary because it does not always fail.
> {code:title=GridCacheReplicatedMultiNodeFullApiSelfTest.java}
> public void testExpiredBug() throws Exception {
> final ExpiryPolicy plc = new ExpiryPolicy() {
> @Override public Duration getExpiryForCreation() {
> return Duration.ZERO;
> }
> @Override public Duration getExpiryForAccess() {
> return Duration.ZERO;
> }
> @Override public Duration getExpiryForUpdate() {
> return Duration.ZERO;
> }
> };
> IgniteCache c1 = ignite(0).cache(null);
> IgniteCache c2 = ignite(1).cache(null);
> String key0 = primaryKeysForCache(c1, 1).get(0);
> String key1 = primaryKeysForCache(c2, 1).get(0);
> IgniteCache cache0 = c1;
> IgniteCache cache = c1.withExpiryPolicy(plc);
> for (int i = 0; i < 3000; i++) {
> cache.put(key0, key0);
> cache.put(key1, key1);
> assert !cache0.containsKey(key0);
> assert !cache0.containsKey(key1);
> cache0.put(key0, key0);
> cache0.put(key1, key1);
> assert cache0.containsKey(key0);
> assert cache0.containsKey(key1);
> cache.put(key0, key0 + 1);
> cache.put(key1, key1 + 1);
> assert !cache0.containsKey(key0);
> assert !cache0.containsKey(key1);
> cache0.put(key0, key0);
> cache0.put(key1, key1);
> cache.get(key0);
> cache.get(key1);
> assert !cache0.containsKey(key0);
> assert !cache0.containsKey(key1);
> }
> }}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1423) Zero expiry policy does not work sometimes
[
https://issues.apache.org/jira/browse/IGNITE-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14847277#comment-14847277
]
Roman Shtykh commented on IGNITE-1423:
--
I apologize, I forgot about getExpiryForAccess
> Zero expiry policy does not work sometimes
> --
>
> Key: IGNITE-1423
> URL: https://issues.apache.org/jira/browse/IGNITE-1423
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: ignite-1.5
>
>
> Paste the following test to GridCacheReplicatedMultiNodeFullApiSelfTest.java
> and run.
> Last assertion fails. Cycle is necessary because it does not always fail.
> {code:title=GridCacheReplicatedMultiNodeFullApiSelfTest.java}
> public void testExpiredBug() throws Exception {
> final ExpiryPolicy plc = new ExpiryPolicy() {
> @Override public Duration getExpiryForCreation() {
> return Duration.ZERO;
> }
> @Override public Duration getExpiryForAccess() {
> return Duration.ZERO;
> }
> @Override public Duration getExpiryForUpdate() {
> return Duration.ZERO;
> }
> };
> IgniteCache c1 = ignite(0).cache(null);
> IgniteCache c2 = ignite(1).cache(null);
> String key0 = primaryKeysForCache(c1, 1).get(0);
> String key1 = primaryKeysForCache(c2, 1).get(0);
> IgniteCache cache0 = c1;
> IgniteCache cache = c1.withExpiryPolicy(plc);
> for (int i = 0; i < 3000; i++) {
> cache.put(key0, key0);
> cache.put(key1, key1);
> assert !cache0.containsKey(key0);
> assert !cache0.containsKey(key1);
> cache0.put(key0, key0);
> cache0.put(key1, key1);
> assert cache0.containsKey(key0);
> assert cache0.containsKey(key1);
> cache.put(key0, key0 + 1);
> cache.put(key1, key1 + 1);
> assert !cache0.containsKey(key0);
> assert !cache0.containsKey(key1);
> cache0.put(key0, key0);
> cache0.put(key1, key1);
> cache.get(key0);
> cache.get(key1);
> assert !cache0.containsKey(key0);
> assert !cache0.containsKey(key1);
> }
> }}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1135) GridPartitionedGetFuture assertion error
[
https://issues.apache.org/jira/browse/IGNITE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14847318#comment-14847318
]
Andrey Gura commented on IGNITE-1135:
-
Alexey,
I found the following places in code that potentially can lead to
{{AssertionError}} with {{skipVals == true}}:
# {{GridPartitionedGetFuture#createResultMap:590}} (it's our case)
# {{GridNearGetFuture#loadEntries:706}}
# {{IgniteTxLocalAdapter#getAllAsync:1978}}
But I can't find any invokes of {{getAllAsync}} with {{skipVals == true}}
except {{containsKey}} and {{containsKeys}}. {{getAllAsync0}} method alwyas
invokes with {{skipVals}} parameter that passed from {{getAllAsync}} method.
> GridPartitionedGetFuture assertion error
>
>
> Key: IGNITE-1135
> URL: https://issues.apache.org/jira/browse/IGNITE-1135
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: ignite-1.4
>
>
> During working on IGNITE-1079 ticket the following problem was found:
> {noformat}
> Failed processing message [senderId=7a07cc81-11e5-42f2-8ffc-184c6c377fc5,
> msg=GridNearGetResponse
> [futId=575ef41be41-1a1482a7-e1b9-48c8-9cb7-382fe83792df,
> miniId=675ef41be41-1a1482a7-e1b9-48c8-9cb7-382fe83792df, ver=GridCacheVersion
> [topVer=48973890, nodeOrderDrId=3, globalTime=1437493884602,
> order=1437493880034], entries=[GridCacheEntryInfo [key=KeyCacheObjectImpl
> [val=7a07cc81-11e5-42f2-8ffc-184c6c377fc5, hasValBytes=true],
> cacheId=414885281, val=null, ttl=0, expireTime=0, ver=GridCacheVersion
> [topVer=48973890, nodeOrderDrId=7, globalTime=1437493884824,
> order=1437493880064], isNew=false, deleted=false]], invalidParts=[],
> topVer=AffinityTopologyVersion [topVer=7, minorTopVer=0], err=null]]
> java.lang.AssertionError
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1811)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.createResultMap(GridPartitionedGetFuture.java:535)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.access$200(GridPartitionedGetFuture.java:45)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture$MiniFuture.onResult(GridPartitionedGetFuture.java:715)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.onResult(GridPartitionedGetFuture.java:234)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearGetResponse(GridDhtAtomicCache.java:2345)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1000(GridDhtAtomicCache.java:64)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$9.apply(GridDhtAtomicCache.java:218)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$9.apply(GridDhtAtomicCache.java:216)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:534)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:240)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:158)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:48)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:761)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:59)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:724)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> In order to reproduce this need to start IgniteComplexHATest (see
> https://github.com/agura/vertx-ignite) and run tests several times. Test
> hangs. Thread dump contains thread that hangs on waiting for future
> completion:
> {noformat}
> "vert.x-worker-thread-3" #4236 prio=5 os_prio=0 tid=0x7f47f43c3800
> nid=0xc2f waiting on condition [0x7f475ebe6000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0xcee89bc8> (a
> org.apache.ignite.internal.util.future.GridFutureAd
[jira] [Assigned] (IGNITE-1500) Invalid docs in distributed data structures classes.
[
https://issues.apache.org/jira/browse/IGNITE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura reassigned IGNITE-1500:
---
Assignee: Andrey Gura
> Invalid docs in distributed data structures classes.
>
>
> Key: IGNITE-1500
> URL: https://issues.apache.org/jira/browse/IGNITE-1500
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Andrey Gura
> Fix For: ignite-1.5
>
>
> Problem: it is mentioned that async operations are supported, while they are
> not:
> {code}All previously described methods have asynchronous analogs.{code}
> Affected classes:
> - IgniteAtomicLong
> - IgniteAtomicReference
> - IgniteAtomicSequence
> - IgniteAtomicStamped
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (IGNITE-1500) Invalid docs in distributed data structures classes.
[
https://issues.apache.org/jira/browse/IGNITE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura reopened IGNITE-1500:
-
> Invalid docs in distributed data structures classes.
>
>
> Key: IGNITE-1500
> URL: https://issues.apache.org/jira/browse/IGNITE-1500
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Andrey Gura
> Fix For: ignite-1.5
>
>
> Problem: it is mentioned that async operations are supported, while they are
> not:
> {code}All previously described methods have asynchronous analogs.{code}
> Affected classes:
> - IgniteAtomicLong
> - IgniteAtomicReference
> - IgniteAtomicSequence
> - IgniteAtomicStamped
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-1500) Invalid docs in distributed data structures classes.
[
https://issues.apache.org/jira/browse/IGNITE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura resolved IGNITE-1500.
-
Resolution: Fixed
Pull request: https://github.com/apache/ignite/pull/100
> Invalid docs in distributed data structures classes.
>
>
> Key: IGNITE-1500
> URL: https://issues.apache.org/jira/browse/IGNITE-1500
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Andrey Gura
> Fix For: ignite-1.5
>
>
> Problem: it is mentioned that async operations are supported, while they are
> not:
> {code}All previously described methods have asynchronous analogs.{code}
> Affected classes:
> - IgniteAtomicLong
> - IgniteAtomicReference
> - IgniteAtomicSequence
> - IgniteAtomicStamped
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1416) .Net: Implement "atomic" data structures.
[ https://issues.apache.org/jira/browse/IGNITE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14862445#comment-14862445 ] Pavel Tupitsyn commented on IGNITE-1416: - Platform semantics should be as close to native as possible. See Interlocked class. > .Net: Implement "atomic" data structures. > - > > Key: IGNITE-1416 > URL: https://issues.apache.org/jira/browse/IGNITE-1416 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn >Priority: Critical > Fix For: ignite-1.5 > > > This includes: > - atomicLong; > - atomicSequence; > - atomicStamped; > - atomicReference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-530) Implement IgniteTwitterStreamer to stream data from Twitter feeds
[
https://issues.apache.org/jira/browse/IGNITE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14803196#comment-14803196
]
Lalit Kumar Jha edited comment on IGNITE-530 at 9/18/15 1:51 PM:
-
I want to work on this. Can anyone assignt this to me.
As per my underatanding this is to integrate Twitter Streaming API (public
streams) from https://dev.twitter.com/streaming/overview
was (Author: lalitj):
I want to work on this. Can anyone assignt his to me.
As per my underatanding this is to integrate Twitter Streaming API (public
streams) from https://dev.twitter.com/streaming/overview
> Implement IgniteTwitterStreamer to stream data from Twitter feeds
> -
>
> Key: IGNITE-530
> URL: https://issues.apache.org/jira/browse/IGNITE-530
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> We should create {{IgniteTwitterStreamer}} which will consume messages from
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Twitter data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1514) Platform .Net: Implement IIgnite.DestroyCache
Pavel Tupitsyn created IGNITE-1514: --- Summary: Platform .Net: Implement IIgnite.DestroyCache Key: IGNITE-1514 URL: https://issues.apache.org/jira/browse/IGNITE-1514 Project: Ignite Issue Type: Task Components: interop Affects Versions: ignite-1.5 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: ignite-1.5 Add and implement IIgnite.DestroyCache. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-825) [Test] HadoopIgfs20FileSystemAbstractSelfTest # testRenameDirectoryIfDstPathExists was disabled.
[ https://issues.apache.org/jira/browse/IGNITE-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Veselovsky reassigned IGNITE-825: -- Assignee: Ivan Veselovsky > [Test] HadoopIgfs20FileSystemAbstractSelfTest # > testRenameDirectoryIfDstPathExists was disabled. > > > Key: IGNITE-825 > URL: https://issues.apache.org/jira/browse/IGNITE-825 > Project: Ignite > Issue Type: Bug > Components: hadoop >Reporter: Artem Shutak >Assignee: Ivan Veselovsky > Labels: failedtest > Fix For: ignite-1.5 > > > HadoopIgfs20FileSystemAbstractSelfTest # testRenameDirectoryIfDstPathExists > was disabled. It has to be fixed or removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-586) [Test] GridGgfsAbstractSelfTest.testFormat() fails on TC.
[ https://issues.apache.org/jira/browse/IGNITE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14875976#comment-14875976 ] ASF GitHub Bot commented on IGNITE-586: --- GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/101 IGNITE-586: version for "master" branch You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-586-master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/101.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 #101 commit bbb4952c1453eb5d0b2fd48b700a342e2252b006 Author: iveselovskiy Date: 2015-09-18T16:57:33Z IGNITE-586: moved from ignite-586 branch (version for ignite-1.4). > [Test] GridGgfsAbstractSelfTest.testFormat() fails on TC. > - > > Key: IGNITE-586 > URL: https://issues.apache.org/jira/browse/IGNITE-586 > Project: Ignite > Issue Type: Bug > Components: hadoop >Reporter: Artem Shutak >Assignee: Ivan Veselovsky > Labels: failedtest > Fix For: ignite-1.5 > > > The problem is that format() doesn't clean all previously written data. > See GG-8578 (the issue was closed, but stay reproducible) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1515) IGFS: delete operations should be truly thread-safe
Ivan Veselovsky created IGNITE-1515: --- Summary: IGFS: delete operations should be truly thread-safe Key: IGNITE-1515 URL: https://issues.apache.org/jira/browse/IGNITE-1515 Project: Ignite Issue Type: Bug Reporter: Ivan Veselovsky Assignee: Ivan Veselovsky In IGNITE-586 we fixed concurrency problem in rename/move operations. Since delete is actually also remove, we should fix deletion operations also accordingly using similar logic. IgfsMetaManager#move0(2) method is to be used partially in delete operation -- need to refactor code accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-586) [Test] GridGgfsAbstractSelfTest.testFormat() fails on TC.
[ https://issues.apache.org/jira/browse/IGNITE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Veselovsky updated IGNITE-586: --- Assignee: Vladimir Ozerov (was: Ivan Veselovsky) > [Test] GridGgfsAbstractSelfTest.testFormat() fails on TC. > - > > Key: IGNITE-586 > URL: https://issues.apache.org/jira/browse/IGNITE-586 > Project: Ignite > Issue Type: Bug > Components: hadoop >Reporter: Artem Shutak >Assignee: Vladimir Ozerov > Labels: failedtest > Fix For: ignite-1.5 > > > The problem is that format() doesn't clean all previously written data. > See GG-8578 (the issue was closed, but stay reproducible) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1397) Load/consistency test framework
[ https://issues.apache.org/jira/browse/IGNITE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14876046#comment-14876046 ] Artem Shutak commented on IGNITE-1397: -- I've finished the framework implementation and implemented the tests. My changes affects yardstick [1] and ignite [2]. Yardstick changes (to have ability implement the tests): - implement memberId functionality - now all benchmark nodes and server nodes have IDs - log file names improvements - improve current restart functionality - improve BenchmarkConfiguration: implements Serializable and pass new properties at config. Ignite changes - RestartUtils with startServer and kill9Server methods - allow to start and to kill server on remote host by host configuration. - create IgniteFailoverAbstractBenchmark - abstract class which runs restarter thread on firs benchmark node. It allows implement any logic of restarting. - new tests implementations. Will run benchmarks (and play with Ignite configuration) for proper testing. [1] https://github.com/gridgain/yardstick/tree/member-id-dev [2] https://github.com/ashutakGG/incubator-ignite/tree/yardstick-dev > Load/consistency test framework > --- > > Key: IGNITE-1397 > URL: https://issues.apache.org/jira/browse/IGNITE-1397 > Project: Ignite > Issue Type: Task >Reporter: Artem Shutak >Assignee: Artem Shutak >Priority: Critical > Fix For: ignite-1.5 > > > Need to create "Load/consistency test framework". See: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316109. > As POC it should be implemented test cases described on the wiki. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1079) Implement Ignite-based cluster manager for Vert.x framework.
[
https://issues.apache.org/jira/browse/IGNITE-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14876111#comment-14876111
]
Andrey Gura commented on IGNITE-1079:
-
Using workarounds for IGNITE-1171 and IGNITE-1135 {{ComplexHATest}} fails with
JUnit assertion. I'll debug this problem.
> Implement Ignite-based cluster manager for Vert.x framework.
>
>
> Key: IGNITE-1079
> URL: https://issues.apache.org/jira/browse/IGNITE-1079
> Project: Ignite
> Issue Type: New Feature
> Components: cache
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Gura
>Priority: Trivial
> Labels: newbie
> Fix For: ignite-1.4
>
>
> Implement Ignite-based cluster manager for Vert.x framework: http://vertx.io/
> vertx-hazelcast could be used as start point:
> https://github.com/vert-x3/vertx-hazelcast
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1079) Implement Ignite-based cluster manager for Vert.x framework.
[
https://issues.apache.org/jira/browse/IGNITE-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14876111#comment-14876111
]
Andrey Gura edited comment on IGNITE-1079 at 9/18/15 6:48 PM:
--
Using workarounds for IGNITE-1171 and IGNITE-1135 {{ComplexHATest}}
periodically fails with JUnit assertion. I'll debug this problem.
was (Author: agura):
Using workarounds for IGNITE-1171 and IGNITE-1135 {{ComplexHATest}} fails with
JUnit assertion. I'll debug this problem.
> Implement Ignite-based cluster manager for Vert.x framework.
>
>
> Key: IGNITE-1079
> URL: https://issues.apache.org/jira/browse/IGNITE-1079
> Project: Ignite
> Issue Type: New Feature
> Components: cache
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Gura
>Priority: Trivial
> Labels: newbie
> Fix For: ignite-1.4
>
>
> Implement Ignite-based cluster manager for Vert.x framework: http://vertx.io/
> vertx-hazelcast could be used as start point:
> https://github.com/vert-x3/vertx-hazelcast
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1516) Need to investigate performance drop for sql-query-offheap benchmark
Yakov Zhdanov created IGNITE-1516: - Summary: Need to investigate performance drop for sql-query-offheap benchmark Key: IGNITE-1516 URL: https://issues.apache.org/jira/browse/IGNITE-1516 Project: Ignite Issue Type: Bug Reporter: Yakov Zhdanov Assignee: Semen Boikov Priority: Blocker Fix For: ignite-1.4 Latest benchmark run showed performance drop for sql-query-offheap. Possible reason of drop - it is fix for race in indexing (change in GridH2AbstractKeyValueRow, commit a7490a6, added one more call 'getOffheapValue'). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1517) CacheInterceptor is not called on 'put' operations
Denis Magda created IGNITE-1517:
---
Summary: CacheInterceptor is not called on 'put' operations
Key: IGNITE-1517
URL: https://issues.apache.org/jira/browse/IGNITE-1517
Project: Ignite
Issue Type: Bug
Affects Versions: ignite-1.4
Reporter: Denis Magda
Assignee: Yakov Zhdanov
Priority: Blocker
Fix For: ignite-1.5
According to {{CacheInterceptor}} API {{onBeforePut}} and {{onAfterPut}}
methods are called when a value is being put or updated in cache.
However, these methods are not called when {{Cache.put}} is being executed, so
'puts' are not intercepted.
Steps to reproduce:
- create cacheconfiguration with cache interceptor;
- populate a cache and you will see that the cache interceptor is not called.
Attached is a simple source code that considered that the interceptor would be
executed for 'company' cache but that didn't happen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1517) CacheInterceptor is not called on 'put' operations
[
https://issues.apache.org/jira/browse/IGNITE-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-1517:
Attachment: CacheInterceptorTest.java
> CacheInterceptor is not called on 'put' operations
> --
>
> Key: IGNITE-1517
> URL: https://issues.apache.org/jira/browse/IGNITE-1517
> Project: Ignite
> Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Yakov Zhdanov
>Priority: Blocker
> Fix For: ignite-1.5
>
> Attachments: CacheInterceptorTest.java
>
>
> According to {{CacheInterceptor}} API {{onBeforePut}} and {{onAfterPut}}
> methods are called when a value is being put or updated in cache.
> However, these methods are not called when {{Cache.put}} is being executed,
> so 'puts' are not intercepted.
> Steps to reproduce:
> - create cacheconfiguration with cache interceptor;
> - populate a cache and you will see that the cache interceptor is not called.
> Attached is a simple source code that considered that the interceptor would
> be executed for 'company' cache but that didn't happen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-1517) CacheInterceptor is not called on 'put' operations
[
https://issues.apache.org/jira/browse/IGNITE-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda resolved IGNITE-1517.
-
Resolution: Not A Problem
Well, these methods are called on a sever node that will hold a cache entry.
Not a bug, closing
> CacheInterceptor is not called on 'put' operations
> --
>
> Key: IGNITE-1517
> URL: https://issues.apache.org/jira/browse/IGNITE-1517
> Project: Ignite
> Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Yakov Zhdanov
>Priority: Blocker
> Fix For: ignite-1.5
>
> Attachments: CacheInterceptorTest.java
>
>
> According to {{CacheInterceptor}} API {{onBeforePut}} and {{onAfterPut}}
> methods are called when a value is being put or updated in cache.
> However, these methods are not called when {{Cache.put}} is being executed,
> so 'puts' are not intercepted.
> Steps to reproduce:
> - create cacheconfiguration with cache interceptor;
> - populate a cache and you will see that the cache interceptor is not called.
> Attached is a simple source code that considered that the interceptor would
> be executed for 'company' cache but that didn't happen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-1517) CacheInterceptor is not called on 'put' operations
[
https://issues.apache.org/jira/browse/IGNITE-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda closed IGNITE-1517.
---
Assignee: Denis Magda (was: Yakov Zhdanov)
> CacheInterceptor is not called on 'put' operations
> --
>
> Key: IGNITE-1517
> URL: https://issues.apache.org/jira/browse/IGNITE-1517
> Project: Ignite
> Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: ignite-1.5
>
> Attachments: CacheInterceptorTest.java
>
>
> According to {{CacheInterceptor}} API {{onBeforePut}} and {{onAfterPut}}
> methods are called when a value is being put or updated in cache.
> However, these methods are not called when {{Cache.put}} is being executed,
> so 'puts' are not intercepted.
> Steps to reproduce:
> - create cacheconfiguration with cache interceptor;
> - populate a cache and you will see that the cache interceptor is not called.
> Attached is a simple source code that considered that the interceptor would
> be executed for 'company' cache but that didn't happen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
