Re: Offheap memory consumption + enabled persistence

[Dmitriy Govorukhin]

Mikle,

A pure data is a size of(keyByte+ValueBytes), as I can see you have Key=int
and Value=String(1024)
4+1024 bytes this is your pure data size which will be stored in the cache
(of course Ignite has overhead for save data ~45 bytes ) 

In internal Ignite has a structure named "FreeList" for tracking free space,
the in-memory region has only one FreeList for the region, the persistence
region has FreeList per partition in the cache, this means persistence case
have move overhead for internal structure. This structure has 256 buckets in
each bucket we have a page, so this means we may have 256*pageSize(4kb) -
1mb overhead. As default value cache has 1024 partition, therefore we may
have 1GB  overhead if we putting data in each partition repeatedly.
in custody, persistence mode may have more overhead for work with data, it
related to the internal structure. 
As a check, you can persistence create a cache with 1 partition and the
result will be the same as in-memory.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Offheap memory consumption + enabled persistence

[Dmitriy Govorukhin]

Hi Mikle,

Could you please check what happening with files, they too grow as a metric?
You need to check the size of files in
{IGNITE_HOME}/work/db/cache-{cacheName}/* during random key upload and clean
up. Also, calculate data size on each iteration and print to log.
My assumption in that we have some leak in tracing free space in partition
and each iteration tries to allocate new pages.
In the end, please provide the case with random keys.
- Pure data size on each iteration
- Folder cache size for each iteration
- Chart for DataRegionMetrics.getOffheapUsedSize



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: NegativeArraySizeException on cluster rebalance

[Dmitriy Govorukhin]

Hi Ibrahim,

Looks like Btree corrupted problem, I guess it was fixed in
https://issues.apache.org/jira/browse/IGNITE-11953
The fix you can find in 9c323149db1cee0ff6586389def059a85428b116
org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:1631

Thank you!

On Wed, Jul 17, 2019 at 1:55 PM ihalilaltun 
wrote:

> Hi Igniters,
>
> We are getting negativearraysizeexception on one of our cacheGroups
> rebalancing period. I am adding the details that I could get from logs;
>
> *Ignite version*: 2.7.5
> *Cluster size*: 16
> *Client size*: 22
> *Cluster OS version*: Centos 7
> *Cluster Kernel version*: 4.4.185-1.el7.elrepo.x86_64
> *Java version* :
> java version "1.8.0_201"
> Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
> Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
>
>
> Pojo we use;
> UserPriceDropRecord.txt
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t2515/UserPriceDropRecord.txt>
>
>
> Error we got;
>
> [2019-07-17T10:23:13,162][ERROR][sys-#241][GridDhtPartitionSupplier] Failed
> to continue supplying [grp=userPriceDropDataCacheGroup,
> demander=12d8bad8-62a9-465d-aca4-4afa203d6778,
> topVer=AffinityTopologyVersion [topVer=238, minorTopVer=0], topic=1]
> java.lang.NegativeArraySizeException: null
> at
> org.apache.ignite.internal.pagemem.PageUtils.getBytes(PageUtils.java:63)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.readFullRow(CacheDataRowAdapter.java:330)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:167)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:108)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.tree.DataRow.(DataRow.java:55)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.tree.CacheDataRowStore.dataRow(CacheDataRowStore.java:92)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.tree.CacheDataTree.getRow(CacheDataTree.java:200)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.tree.CacheDataTree.getRow(CacheDataTree.java:49)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.fillFromBuffer0(BPlusTree.java:5512)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.fillFromBuffer(BPlusTree.java:5280)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.nextPage(BPlusTree.java:5332)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.next(BPlusTree.java:5566)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$9.onHasNext(IgniteCacheOffheapManagerImpl.java:1185)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.advance(IgniteRebalanceIteratorImpl.java:79)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.nextX(IgniteRebalanceIteratorImpl.java:139)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:185)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:37)
> ~[ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:333)
> [ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleDemandMessage(GridDhtPreloader.java:404)
> [ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:424)
> [ignite-core-2.7.5.jar:2.7.5]
> at
>
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:409)
> 

Re: ignite git repo

[Dmitriy Govorukhin]

This link work for me, https://gitbox.apache.org/repos/asf/ignite

чт, 17 янв. 2019 г., 20:03 Scott Cote sc...@etcc.com:

> Petr,
>
>
>
> Thank you for your quick reply.
>
>
>
> git clone https://gitbox.apache.org/repos/ignite.git
>
>
>
> 404 on that one ….
>
>
>
> “[image: git] projects
>  /
>
>
>
> 404 - No projects found
>
> OPML  TXT
> 
>
> “
>
>
>
> I just realized that this is a security outcome ….   Looking at
> gitbox.apache.com, I need an account there.   Can I just clone (for now)
> from a github repo?
>
>
>
> Issuing the command:
>
>
>
> git clone https://github.com/apache/ignite
>
>
>
> yielded what seems like what I want ….
>
>
>
> If I want to give back ….  How do I go about getting (gitting  ) an
> apache id?   I might already have one from some work with Apache Metron
> (not sure). …
>
>
>
> For Apache Metron - was investigating the use of ignite to replace the
> lucene decendents of hot data repos …
>
>
>
> For now – I’m building off of the mirror apache github site ….
>
>
>
> Cheers
>
>
>
> SCott
>
>
>
> *From:* Petr Ivanov 
> *Sent:* Thursday, January 17, 2019 10:18 AM
> *To:* user@ignite.apache.org
> *Subject:* Re: ignite git repo
>
>
>
> Repository is move to GitBox
>
> Clone command: git clone http://gitbox.apache.org/repos/ignite.git
>
>
>
>
>
>
>
> On 17 Jan 2019, at 19:17, Scott Cote  wrote:
>
>
>
> Hello Igniters:
>
>
>
> I’m having trouble cloning the git repo.  Want to build from source and
> maybe make an add on ….
>
>
>
> Went to the link:  https://ignite.apache.org/download.cgi#git-repository
> to get the “git” url/command
>
> Am issuing the command:   git clone
> https://git-wip-us.apache.org/repos/asf/ignite
>
>
>
> But am getting (gitting???):
>
>
>
> $ git clone https://git-wip-us.apache.org/repos/asf/ignite
>
> Cloning into 'ignite'...
>
> fatal: repository 'https://git-wip-us.apache.org/repos/asf/ignite/' not
> found
>
>
>
> Investigating the url and I’m redirected to
>
>
>
> https://gitbox.apache.org/repos/asf?p=ignite.git
>
>
>
> So how do I clone?  The instructions are off ….
>
>
>
> Thanks in advance.
>
>
>
> SCott
>
>
>

Re: Delete/remove cache does not free the memory in PCF server

[Dmitriy Govorukhin]

In the current implementation, Ignite does not support deallocate memory.
Maybe you can try to use ignite with persistence and reduce in-memory
region size?
Please explain your use case in more details and provide Ignite and cache
configurations.

On Mon, Jul 30, 2018 at 8:29 PM okiesong  wrote:

> Hi, first of all, thank you very much for your quick response!
>
> My case is that on the PCF server, once I execute the ignite against the
> 1.0
> million records, my memory usage displayed by the PCF server increase by
> 200MB. After I execute the destroy cache function (just like I posted in my
> above post), the memory displayed in PCF server was never decreased, and we
> need some way to reduce the memory in used on PCF by 200 MB to avoid a lack
> of memory. Thanks again.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Distributed closure and cache.

[Dmitriy Govorukhin]

HI,

Yes, you can. Try to do something like this

ignite.compute().call(() -> {
// Get local ignite instance (local in compute task).
Ignite remoteIg = Ignition.localIgnite();

IgniteCache cache = remoteIg.cache("cacheName");

Object val = cache.get("someKey");

return "result";
});

or use @IgniteInstanceResource.

ignite.compute().call(new MyComputeTask());

class MyComputeTask implements IgniteCallable {
@IgniteInstanceResource
private Ignite ignite;

@Override public Object call() throws IgniteCheckedException {

IgniteCache cache = remoteIg.cache("cacheName");

Object val = cache.get("someKey");

return "result";
   }
 }



On Tue, Jul 31, 2018 at 4:50 PM F.D.  wrote:

> Hi,
>
> First, I want sat thank you for your job, and for the help you gave me.
> I've a new question for you. I need to get a cache value inside the method
> Call of my closure. Is it possibile?  I need to start a new node?!? (ignite
> = Ignition::Start(cfg)) Can I use an already initialized variable?!?
>
> Thanks,
>F.D.
>

Re: Delete/remove cache does not free the memory in PCF server

[Dmitriy Govorukhin]

Ignite does not deallocate memory in a region after all caches are stopped.
It is the default behavior.
In future, you may create new caches in this regions without
necessary allocate memory.
Could you please explain your case in more details?

On Fri, Jul 27, 2018 at 4:10 PM okiesong  wrote:

> Hi my ignite version is 2.6. And yes, I am using in-memory options. thanks
> in
> advance!
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: IgniteMessaging, What am I doing wrong?

[Dmitriy Govorukhin]

No, a new client will not receive these messages because they were sent on
previous topology version. (topology version changing after join/left any
node)
The messages will be sent only to current client nodes.

On Fri, Jul 27, 2018 at 2:07 PM monstereo  wrote:

> thanks,
> When I want to send messages from server to client, it works
> probably, there were a problem as you stated.
>
> May I ask :
> Let's say server send a messages to client ("hello")
> When I create another client after  seconds, minutes vs.. , this new client
> will see this messages?
> Same question for events?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Delete/remove cache does not free the memory in PCF server

[Dmitriy Govorukhin]

Hi,
Do you use the in-memory region for these caches or region with persistence?
What is your ignite version?

On Fri, Jul 27, 2018 at 12:17 AM okiesong  wrote:

> Hi, this is basically the command that I am using to clear and destroy the
> cache from the server that is deployed on the PCF server.
>
> But memory does not free, even after I do this.
>
> private clearCacheByName(String item) {
> if (ignite.cacheNames().contains(item)) {
>  ignite.cache(item).clear();
>  ignite.cache(item).destroy();
>  ignite.destroyCache(item);
> }
> }
>
> When I call ignite.cacheNames(), that specified cache is gone, but memory
> is
> not freed from the PCF server that runs Ignite.
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: IgniteMessaging, What am I doing wrong?

[Dmitriy Govorukhin]

Hi,

Are you sure that server sends a message only after a client is joined to
topology?
Please, check that ClusterGroup clientNodes is not empty before sending a
message to the topic.

On Fri, Jul 27, 2018 at 8:27 AM monstereo  wrote:

> I want to send message to client nodes from server nodes, and client nodes
> will take this message and print it.
>
> Here is the server nodes
>
> public static void main {
>   Ignite server = //start ignite with default config path
> ClusterGroup clientNodes = server.cluster().forClients();
>  IgniteMessaging messaging = server.message(clientNodes);
> messaging.send("ServerTopic", "hello");
> }
>
> Here is the client node
> public static void main ...{
> Ignite client = //start ignite client with default config
> ClusterGroup clientNodes = client.cluster().forClients();
> IgniteMessaging serverTopic = client.message(clientNodes);
> consumerTopic.remoteListen("ServerTopic", (nodeId, message) ->{
> System.out.println("Severr with id:" + nodeId +"\nsend this
> message : " + message);
> return true;
> });
> }
>
> But I can not see the message on client nodes.
> (I run client first, then run the server node(s))
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Node stopped automatically

[Dmitriy Govorukhin]

Hi, kvenkatramtreddy!

Could you please provide a full log, not only stack trace with an exception?


On Sat, Jun 30, 2018 at 3:24 PM kvenkatramtreddy 
wrote:

> Hi,
>
> Node stopped automatically after 48 hours uptime. Please find the logs
> below.
>
> I got 2 hosts and 3 Ignite nodes
>
>
> Host 1, Node 1
>
>
>
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=5582ed60, uptime=48:00:04.981]
> ^-- H/N/C [hosts=2, nodes=3, CPUs=4]
> ^-- CPU [cur=15.67%, avg=15.01%, GC=0.43%]
> ^-- PageMemory [pages=390178]
> ^-- Heap [used=1387MB, free=11.75%, comm=1572MB]
> ^-- Non heap [used=369MB, free=-1%, comm=409MB]
> ^-- Outbound messages queue [size=0]
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=6, qSize=0]
>
>
>
> [6/27/18 8:28:43:098 UTC] 00c5
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi  I TCP
> discovery
> accepted incoming connection [rmtAddr=/57.20.44.84, rmtPort=47056]
> [6/27/18 8:28:43:098 UTC] 00c5
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi  I TCP
> discovery
> spawning a new thread for connection [rmtAddr=/57.20.44.84, rmtPort=4
> 7056]
>
> [6/27/18 8:28:43:117 UTC] 000d83ee
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi  I Started
> serving remote node connection [rmtAddr=/57.20.44.84:47056, rmtPort=47056]
> [6/27/18 8:28:43:128 UTC] 00c4
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi  W Node is out
> of topology (probably, due to short-time network problems).
> [6/27/18 8:28:43:129 UTC] 00cb
> ache.ignite.internal.managers.discovery.GridDiscoveryManager W Local node
> SEGMENTED: TcpDiscoveryNode [id=5582ed60-76f5-42b1-bd19-ed3af12b12f7, ad
> drs=[57.20.44.85], sockAddrs=[myhost1.org/57.20.44.85:48500],
> discPort=48500, order=2, intOrder=2, lastExchangeTime=1530088123126,
> loc=true, ver=2.4.0#201803
> 05-sha1:aa342270, isClient=false]
> [6/27/18 8:28:43:135 UTC] 00c5
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi  I TCP
> discovery
> accepted incoming connection [rmtAddr=/57.20.44.84, rmtPort=58172]
> [6/27/18 8:28:43:137 UTC] 000d83ee
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi  I Finished
> serving remote node connection [rmtAddr=/57.20.44.84:47056, rmtPort=47056
> [6/27/18 8:28:43:140 UTC] 00c5
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi  I TCP
> discovery
> spawning a new thread for connection [rmtAddr=/57.20.44.84, rmtPort=5
> 8172]
> [6/27/18 8:28:43:140 UTC] 000d83f0
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi  I Started
> serving remote node connection [rmtAddr=/57.20.44.84:58172, rmtPort=58172]
> [6/27/18 8:28:43:162 UTC] 000d83f0
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi  I Finished
> serving remote node connection [rmtAddr=/57.20.44.84:58172, rmtPort=58172
> [6/27/18 8:28:43:184 UTC] 00cb
> ache.ignite.internal.managers.discovery.GridDiscoveryManager W Stopping
> local node according to configured segmentation policy.
>
>
>
>
> Host 2(have 2 ignite nodes) Node1
>
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=58a3d911, uptime=48:00:05.572]
> ^-- H/N/C [hosts=2, nodes=3, CPUs=4]
> ^-- CPU [cur=8.17%, avg=8.27%, GC=0.5%]
> ^-- PageMemory [pages=70]
> ^-- Heap [used=1306MB, free=16.92%, comm=1572MB]
> ^-- Non heap [used=355MB, free=-1%, comm=392MB]
> ^-- Outbound messages queue [size=0]
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=6, qSize=0]
>
>
>
> [6/27/18 8:28:34:381 UTC] 0095
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi  W Timed out
> waiting for message delivery receipt (most probably, the reason is in lon
> g GC pauses on remote node; consider tuning GC and increasing 'ackTimeout'
> configuration property). Will retry to send message with increased timeout
> [currentTimeout=1, rmtAddr=
> myhost2.org/57.20.44.85:48500, rmtPort=48500]
> [6/27/18 8:28:34:382 UTC] 0095
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi  W Failed to
> send message to next node [msg=TcpDiscoveryMetricsUpdateMessage [super=Tc
> pDiscoveryAbstractMessage [sndNodeId=null,
> id=27b0fa80461-58a3d911-aa4c-453d-ae5a-0fc3d450a09f,
> verifierNodeId=58a3d911-aa4c-453d-ae5a-0fc3d450a09f, topVer=0,
> pendingIdx=0,
> failedNo
> des=null, isClient=false]], next=TcpDiscoveryNode
> [id=5582ed60-76f5-42b1-bd19-ed3af12b12f7, addrs=[57.20.44.85],
> sockAddrs=[myhost2.org/57.20.44.85:48500], d
> iscPort=48500, order=2, intOrder=2, lastExchangeTime=1529051134737,
> loc=false, ver=2.4.0#20180305-sha1:aa342270, isClient=false], errMsg=Failed
> to send message to next node [msg=Tcp
> DiscoveryMetricsUpdateMessage [super=TcpDiscoveryAbstractMessage
> [sndNodeId=null, id=27b0fa80461-58a3d911-aa4c-453d-ae5a-0fc3d450a09f,
> verifierNodeId=58a3d911-aa4c-453d-ae5a-0fc3d45
> 0a09f, 

Re: put vs putAll

[Dmitriy Govorukhin]

Prasad,

PutAll more effective in many cases, because transaction obtains locks for
keysSet in the batch.
Each put will be produced a call for obtain lock for the appropriate key,
in general, it more slowly.

On Mon, May 14, 2018 at 4:47 PM, Prasad Bhalerao <
prasadbhalerao1...@gmail.com> wrote:

> Hi,
>
> Does putAll perform better than put method if the data being pushed to the
> cache is going to land up on same node from where it is being pushed?
>
> 1)   try (Transaction transaction = transactions.txStart()) {
>   for (Data data : datas) {
> ipv4DataCache.put(data.getKey(), data);
>   }
>   transaction.commit();
> }
>
>
>
> 2)  try (Transaction transaction = transactions.txStart()) {
> ipv4DataCache.putAll(map);
> transaction.commit();
> }
>
> Does code 2 performs better than code 1?
>
>
> Thanks,
> Prasad
>

Re: Scheduler throwing NullPointerException for Ignite 2.0.0

[Dmitriy Govorukhin]

Hi ronly2008,

I applied your stacktrace on ignite-2.0.0, but code lines is does not
matched. Are you sure that you use ignite-2.0.0 (it is tag)? Can you provide
small reproducer? It can help solve problem more quickly.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Scheduler-throwing-NullPointerException-for-Ignite-2-0-0-tp13420p15843.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite with cassandra

[Dmitriy Govorukhin]

Hi, i think it problem related to cassandra configuration or network, check
you firewall. You can try change cassandra configuration and enable port
9160 for using. Also check which version cassandra-jdbc driver using,
different version use different ports.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-with-cassandra-tp8777p8881.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Very high memory consumption in apache ignite

[Dmitriy Govorukhin]

Hi, could you please provide your final jvm options  and cache configuration?  



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Very-high-memory-consumption-in-apache-ignite-tp8822p8879.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: rest-http can't get data if key is Integer or others

[Dmitriy Govorukhin]

Hi, 

Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
the reply. 

Could you please provide test for reproduce issue? And i think that need to
move Cross-origin and your fix to separate pull request, also need add
tests.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/rest-http-can-t-get-data-if-key-is-Integer-or-others-tp8762p8876.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Question about cron-based scheduler

[Dmitriy Govorukhin]

Hi,

Do you want use exactly cron scheduler?

Unfortunately cron supported the minimum unit time 1 min.

 # ┌─ min (0 - 59)
 # │ ┌── hour (0 - 23)
 # │ │ ┌─── day of month (1 - 31)
 # │ │ │ ┌ month (1 - 12)
 # │ │ │ │ ┌─ day of week (0 - 6) (0 to 6 are Sunday to
 # │ │ │ │ │  Saturday, or use names; 7 is also Sunday)
 # │ │ │ │ │
 # │ │ │ │ │

# * * * * * command to execute

Ignite just only add prefix specifying the number of iteration and delay
beetwen invoke method "scheduleLocal" and  first execution. {n1, n2} n1
-delay before first execution, n2- number of iteration.

if there is no need cron, you can try any other scheduler which support
delay less 1 min. For example ScheduledExecutorService.


On Thu, Sep 29, 2016 at 4:42 AM, Level D <724172...@qq.com> wrote:

> Hi all,
>
> I find the minimal scheduling time unit this scheduler supported is 1
> minute.
>
> But I need a scheduling time unit less than 1 minute .
> Is there a way to make it happen?
>
> Regards,
>
> Zhou.
>
>>
>