[jira] [Commented] (IGNITE-5151) Add some warning when offheap eviction occurs
[ https://issues.apache.org/jira/browse/IGNITE-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449209#comment-16449209 ] Wuwei Lin commented on IGNITE-5151: --- hi [~dpavlov] i've reopened my PR > Add some warning when offheap eviction occurs > - > > Key: IGNITE-5151 > URL: https://issues.apache.org/jira/browse/IGNITE-5151 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Ksenia Rybakova >Assignee: Wuwei Lin >Priority: Major > > Currently if offheap eviction occurs we are silently losing data. It whould > be helpful to have some warning in log as it's done for onheap eviction. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5151) Add some warning when offheap eviction occurs
[ https://issues.apache.org/jira/browse/IGNITE-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449638#comment-16449638 ] Wuwei Lin commented on IGNITE-5151: --- [~ivan.glukos] fixed, please review > Add some warning when offheap eviction occurs > - > > Key: IGNITE-5151 > URL: https://issues.apache.org/jira/browse/IGNITE-5151 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Ksenia Rybakova >Assignee: Wuwei Lin >Priority: Major > > Currently if offheap eviction occurs we are silently losing data. It whould > be helpful to have some warning in log as it's done for onheap eviction. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-5011) Add validation of input params of disco command
[
https://issues.apache.org/jira/browse/IGNITE-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wuwei Lin reassigned IGNITE-5011:
-
Assignee: Wuwei Lin
> Add validation of input params of disco command
> ---
>
> Key: IGNITE-5011
> URL: https://issues.apache.org/jira/browse/IGNITE-5011
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Wuwei Lin
>Priority: Trivial
>
> {code}
> visor> disco -t=0h
> java.lang.IllegalArgumentException: Time frame size is not positive in: 0h
> at org.apache.ignite.visor.visor$.timeFilter(visor.scala:2671)
> at
> org.apache.ignite.visor.commands.disco.VisorDiscoveryCommand.disco(VisorDiscoveryCommand.scala:127)
> at
> org.apache.ignite.visor.commands.disco.VisorDiscoveryCommand$$anonfun$4.apply(VisorDiscoveryCommand.scala:282)
> at
> org.apache.ignite.visor.commands.disco.VisorDiscoveryCommand$$anonfun$4.apply(VisorDiscoveryCommand.scala:282)
> at
> org.apache.ignite.visor.commands.VisorConsole.mainLoop(VisorConsole.scala:217)
> at
> org.apache.ignite.visor.commands.VisorConsole$.delayedEndpoint$org$apache$ignite$visor$commands$VisorConsole$1(VisorConsole.scala:329)
> at
> org.apache.ignite.visor.commands.VisorConsole$delayedInit$body.apply(VisorConsole.scala:318)
> at scala.Function0$class.apply$mcV$sp(Function0.scala:34)
> at
> scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.collection.immutable.List.foreach(List.scala:381)
> at
> scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35)
> at scala.App$class.main(App.scala:76)
> at
> org.apache.ignite.visor.commands.VisorConsole$.main(VisorConsole.scala:318)
> at
> org.apache.ignite.visor.commands.VisorConsole.main(VisorConsole.scala)
> (wrn) : Invalid command name: 'disco -t=0h'
> (wrn) : Type 'help' to print commands list.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-3715) Incorrect Hibernate L2 cache statistics
[
https://issues.apache.org/jira/browse/IGNITE-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wuwei Lin reassigned IGNITE-3715:
-
Assignee: Wuwei Lin
> Incorrect Hibernate L2 cache statistics
> ---
>
> Key: IGNITE-3715
> URL: https://issues.apache.org/jira/browse/IGNITE-3715
> Project: Ignite
> Issue Type: Sub-task
> Components: Hibernate L2 cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Wuwei Lin
>Priority: Minor
>
> These methods on {{SecondLevelCacheStatistics}} return incorrect data:
> * {{getElementCountInMemory()}} - returns only local node's cache size (zero
> on client), not the global cache size.
> * {{getEntries()}} - always returns empty map, even if there is data in cache.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-3715) Incorrect Hibernate L2 cache statistics
[
https://issues.apache.org/jira/browse/IGNITE-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999696#comment-15999696
]
Wuwei Lin commented on IGNITE-3715:
---
getEntries() should return an empty set if not supported, as documented in
Hibernate.
Loading all entries from all nodes is too expensive. I think we don't need to
support this operation.
> Incorrect Hibernate L2 cache statistics
> ---
>
> Key: IGNITE-3715
> URL: https://issues.apache.org/jira/browse/IGNITE-3715
> Project: Ignite
> Issue Type: Sub-task
> Components: Hibernate L2 cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Wuwei Lin
>Priority: Minor
>
> These methods on {{SecondLevelCacheStatistics}} return incorrect data:
> * {{getElementCountInMemory()}} - returns only local node's cache size (zero
> on client), not the global cache size.
> * {{getEntries()}} - always returns empty map, even if there is data in cache.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5179) Inconsistent return type in javadoc of GridSecurityProcessor
Wuwei Lin created IGNITE-5179:
-
Summary: Inconsistent return type in javadoc of
GridSecurityProcessor
Key: IGNITE-5179
URL: https://issues.apache.org/jira/browse/IGNITE-5179
Project: Ignite
Issue Type: Bug
Components: documentation
Affects Versions: 2.0
Reporter: Wuwei Lin
Priority: Trivial
In {{GridSecurityProcessor}}, the return types of methods {{authenticate}} and
{{authenticateNode}} are {{SecurityContext}}, but documented as returning
{{boolean}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5180) Inconsistent return type in javadoc of GridSecurityProcessor
Wuwei Lin created IGNITE-5180:
-
Summary: Inconsistent return type in javadoc of
GridSecurityProcessor
Key: IGNITE-5180
URL: https://issues.apache.org/jira/browse/IGNITE-5180
Project: Ignite
Issue Type: Bug
Components: documentation
Affects Versions: 2.0
Reporter: Wuwei Lin
Priority: Trivial
In {{GridSecurityProcessor}}, the return types of methods {{authenticate}} and
{{authenticateNode}} are {{SecurityContext}}, but documented as returning
{{boolean}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-5180) Inconsistent return type in javadoc of GridSecurityProcessor
[
https://issues.apache.org/jira/browse/IGNITE-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wuwei Lin resolved IGNITE-5180.
---
Resolution: Invalid
Duplicates [IGNITE-5179]
> Inconsistent return type in javadoc of GridSecurityProcessor
>
>
> Key: IGNITE-5180
> URL: https://issues.apache.org/jira/browse/IGNITE-5180
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.0
>Reporter: Wuwei Lin
>Priority: Trivial
>
> In {{GridSecurityProcessor}}, the return types of methods {{authenticate}}
> and {{authenticateNode}} are {{SecurityContext}}, but documented as returning
> {{boolean}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-5179) Inconsistent return type in javadoc of GridSecurityProcessor
[
https://issues.apache.org/jira/browse/IGNITE-5179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wuwei Lin reassigned IGNITE-5179:
-
Assignee: Wuwei Lin
> Inconsistent return type in javadoc of GridSecurityProcessor
>
>
> Key: IGNITE-5179
> URL: https://issues.apache.org/jira/browse/IGNITE-5179
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.0
>Reporter: Wuwei Lin
>Assignee: Wuwei Lin
>Priority: Trivial
>
> In {{GridSecurityProcessor}}, the return types of methods {{authenticate}}
> and {{authenticateNode}} are {{SecurityContext}}, but documented as returning
> {{boolean}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-5151) Add some warning when offheap eviction occurs
[ https://issues.apache.org/jira/browse/IGNITE-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wuwei Lin reassigned IGNITE-5151: - Assignee: Wuwei Lin > Add some warning when offheap eviction occurs > - > > Key: IGNITE-5151 > URL: https://issues.apache.org/jira/browse/IGNITE-5151 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Ksenia Rybakova >Assignee: Wuwei Lin > > Currently if offheap eviction occurs we are silently losing data. It whould > be helpful to have some warning in log as it's done for onheap eviction. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4597) CPP: Add mechanism to reset arguments for sql queries.
[
https://issues.apache.org/jira/browse/IGNITE-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wuwei Lin reassigned IGNITE-4597:
-
Assignee: Wuwei Lin
> CPP: Add mechanism to reset arguments for sql queries.
> --
>
> Key: IGNITE-4597
> URL: https://issues.apache.org/jira/browse/IGNITE-4597
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Wuwei Lin
> Labels: cpp, newbie
>
> Currently, there is method {{AddArgument}} for {{SqlQuery}} and
> {{SqlFieldsQuery}}, but there is no way to reset arguments for query once
> they are set. This leads to inconvenience when user want to call the same
> query with different arguments as they need to re-create exactly the same
> query but set different arguments for it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-1456) CPP: Implement Cache.Rebalance()
[ https://issues.apache.org/jira/browse/IGNITE-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wuwei Lin reassigned IGNITE-1456: - Assignee: Wuwei Lin > CPP: Implement Cache.Rebalance() > > > Key: IGNITE-1456 > URL: https://issues.apache.org/jira/browse/IGNITE-1456 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Wuwei Lin > Labels: cpp > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-1456) CPP: Implement Cache.Rebalance()
[ https://issues.apache.org/jira/browse/IGNITE-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013877#comment-16013877 ] Wuwei Lin commented on IGNITE-1456: --- Ready for review. > CPP: Implement Cache.Rebalance() > > > Key: IGNITE-1456 > URL: https://issues.apache.org/jira/browse/IGNITE-1456 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Wuwei Lin > Labels: cpp > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (IGNITE-5180) Inconsistent return type in javadoc of GridSecurityProcessor
[
https://issues.apache.org/jira/browse/IGNITE-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wuwei Lin closed IGNITE-5180.
-
> Inconsistent return type in javadoc of GridSecurityProcessor
>
>
> Key: IGNITE-5180
> URL: https://issues.apache.org/jira/browse/IGNITE-5180
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.0
>Reporter: Wuwei Lin
>Priority: Trivial
>
> In {{GridSecurityProcessor}}, the return types of methods {{authenticate}}
> and {{authenticateNode}} are {{SecurityContext}}, but documented as returning
> {{boolean}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-5248) Best effort check to detect a 32-bit JVM trying to allocate too big amount of memory
[ https://issues.apache.org/jira/browse/IGNITE-5248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wuwei Lin reassigned IGNITE-5248: - Assignee: Wuwei Lin > Best effort check to detect a 32-bit JVM trying to allocate too big amount of > memory > > > Key: IGNITE-5248 > URL: https://issues.apache.org/jira/browse/IGNITE-5248 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.0 >Reporter: Alexey Goncharuk >Assignee: Wuwei Lin > Labels: newbie > Fix For: 2.1 > > > A follow-up on the user list discussion: > http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-td12840.html > We can catch the IllegalArgumentException and see if the allocated space > exceeds 2Gb. In this case, we should suggest that user check that he is > running a 64-bit JVM. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-3715) Incorrect Hibernate L2 cache statistics
[
https://issues.apache.org/jira/browse/IGNITE-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wuwei Lin reassigned IGNITE-3715:
-
Assignee: (was: Wuwei Lin)
> Incorrect Hibernate L2 cache statistics
> ---
>
> Key: IGNITE-3715
> URL: https://issues.apache.org/jira/browse/IGNITE-3715
> Project: Ignite
> Issue Type: Sub-task
> Components: hibernate
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Priority: Minor
>
> These methods on {{SecondLevelCacheStatistics}} return incorrect data:
> * {{getElementCountInMemory()}} - returns only local node's cache size (zero
> on client), not the global cache size.
> * {{getEntries()}} - always returns empty map, even if there is data in cache.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-3714) Introduce new performance hint for default store-by-value caches behavior.
[ https://issues.apache.org/jira/browse/IGNITE-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wuwei Lin reassigned IGNITE-3714: - Assignee: Wuwei Lin > Introduce new performance hint for default store-by-value caches behavior. > -- > > Key: IGNITE-3714 > URL: https://issues.apache.org/jira/browse/IGNITE-3714 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Alexei Scherbakov >Assignee: Wuwei Lin > Labels: newbie > Fix For: 2.1 > > > Default store-by-value semantics of Ignite has bad impact on performance and > rarely needed. > We must print the performance hint if some of the caches have copyOnRead > property set to true (default value). > It must work both for static and dynamic caches. > Corresponding thread on dev list: > http://apache-ignite-developers.2346864.n4.nabble.com/copyOnRead-performance-issues-td10762.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-3714) Introduce new performance hint for default store-by-value caches behavior.
[ https://issues.apache.org/jira/browse/IGNITE-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018668#comment-16018668 ] Wuwei Lin commented on IGNITE-3714: --- Any suggestions on printing performance suggestions dynamically after the grid has started? > Introduce new performance hint for default store-by-value caches behavior. > -- > > Key: IGNITE-3714 > URL: https://issues.apache.org/jira/browse/IGNITE-3714 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Alexei Scherbakov >Assignee: Wuwei Lin > Labels: newbie > Fix For: 2.1 > > > Default store-by-value semantics of Ignite has bad impact on performance and > rarely needed. > We must print the performance hint if some of the caches have copyOnRead > property set to true (default value). > It must work both for static and dynamic caches. > Corresponding thread on dev list: > http://apache-ignite-developers.2346864.n4.nabble.com/copyOnRead-performance-issues-td10762.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
