Re: transaction not timing out

[bintisepaha]

Does prepare happen as part of commit() call? 
As a user we only call commit(). so the txn should get to commit only if
prepare succeeded - right?
once in prepare mode, locks are acquired, no other txn should be able to
update these entries. then the txn goes to goes to commit() once locks are
acquired - what is holding it from updating the entries?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p6638.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Services: How to preserve value of Local variables ?

[vkulichenko]

Hi Kamal,

A. You can provide the cluster group with local node only:

ignite.services(ignite.cluster().forLocal()).deploy(...);

B. If you start the service with the same name, this should not happen. I
tried to reproduce your behavior, but everything works as expected for me.
Do you a have a test that you can share?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Services-How-to-preserve-value-of-Local-variables-tp4094p6637.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Failed to wait for initial partition map exchange

[vkulichenko]

Hi Jason,

Take a look at failure detection timeout [1]. This is a single setting that
defines the period of time after the node which loses connectivity (due to
network issues, GC, etc.) is considered failed.

Also there is a mechanism for removing slow clients [2].

[1]
https://apacheignite.readme.io/docs/cluster-config#failure-detection-timeout
[2]
https://apacheignite.readme.io/docs/clients-vs-servers#managing-slow-clients

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-tp6252p6633.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Cluster node stopped

[vkulichenko]

Hi,

Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. Here is the instruction:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1


suhuadong wrote
>   I build ignite Cluster with 9 nodes.But,one node stoped.
> 
>   log:
> [22:03:38,100][WARNING][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi]
> Node is out of topology (probably, due to short-time network problems).
> [22:03:38,103][WARNING][disco-event-worker-#144%null%][GridDiscoveryManager]
> Local node SEGMENTED: TcpDiscoveryNode
> [id=424ef276-c1b6-48b0-9ded-c6fca0997502, addrs=[124.250.36.149,
> 127.0.0.1, 172.21.0.183], sockAddrs=[/172.21.0.183:58600,
> /124.250.36.149:58600, /124.250.36.149:58600, /127.0.0.1:58600,
> /172.21.0.183:58600], discPort=58600, order=485, intOrder=255,
> lastExchangeTime=1469714618102, loc=true,
> ver=1.6.0#20160518-sha1:0b22c45b, isClient=false]

The first thing to check is memory. Do you have enough heap? Are there nodes
in topology that run out of memory and/or experience GC pauses?

-Val



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

Re: Issue with querying from cache

[vkulichenko]

Are you using the correct cache when executing the query? You can also try to
explicitly specify the cache name:

select * from "testCache".TableB ...

BTW, it seems weird to me that the cache type is Payroll, but the indexed
type is TableB. How are they related to each other?

-Val



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

Re: question about ignite key field mapping

[vkulichenko]

Hi Kevin,

If there is no mapping for a field, it will be null when he object is loaded
from the DB and the field will be ignored when writing to the DB. This is an
absolutely valid case and should work without issues.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/question-about-ignite-key-field-mapping-tp6614p6629.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Rest-api: Returning no reply from server

[vkulichenko]

'host' and 'port' properties are for binary protocol. In case of Jetty,
everything is defined by the XML file.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Rest-api-Returning-no-reply-from-server-tp6561p6628.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: If firewall, how many ports are necessary to be opened for in-bound for Ignite nodes?

[vkulichenko]

Hi Jason,

Please take a look at this thread:
http://apache-ignite-users.70518.x6.nabble.com/list-of-ports-used-td737.html

Only discovery and communication ports are required.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/If-firewall-how-many-ports-are-necessary-to-be-opened-for-in-bound-for-Ignite-nodes-tp6623p6627.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

How is memory used for the Ignite server node?

[Jason]

hi Ignite team,

I've a 21 server nodes Ignite cluster and found that their memory usage has
a very big difference:
the min is ~28G, and the max is ~45G.

our total data capacity is ~90G (key is tens of bytes and value is ~2-3k),
with 2 backups and few columns for sql query and based on the capacity
planning formula in your doc:

memory for each node: 90G * 3 * 1.3 / 21 ~= 17G

And now, we've set the JVM max memory to 10G and use off_heap with max size
30G.

Checked the JMX for the min memory and max memory nodes, found that:

for max memory node (45G),
total entries: ~6.2M, allocated off-heap size: ~17.3G, heap: 9G 
for min memory node (28G),
total entries: ~5.5M, allocated off-heap size: ~14.5G, heap: 7G

So I wonder where other memory is used (max memory node: 45G - 17.3G - 9G ~=
17G, even for min memory node: 28G - 14.5G - 7G ~= 6.5G) ?

BTW, we use off-heap, why does it still need so many heap (9G versus 17.3G,
7G versus 14.5G)? If I reduce the max JVM memory, will it throw OOM
exception? If not, any impact to the latency?

would you like to share some experience data during production?

Thanks,
-Jason





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/How-is-memory-used-for-the-Ignite-server-node-tp6626.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: QuerySqlFunction methods with variable arguments do not seem to work

[edwardkblk]

https://issues.apache.org/jira/browse/IGNITE-3608



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/QuerySqlFunction-methods-with-variable-arguments-do-not-seem-to-work-tp6524p6625.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Failed to wait for initial partition map exchange

[Jason]

Thanks Val.

If there's assertion, OOM error in one node, client or server, cannot it be
identified as a failed node and be isolated? Or there's some policy or
parameter that can be tuned? 

If not, the whole cluster should be very vulnerable to failures in the
distributed environment, right?
E.g. one client node runs on a very busy machine and runs out of memory and
fails, then the whole cluster will be hang?

Thanks,
-Jason







--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-tp6252p6624.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

If firewall, how many ports are necessary to be opened for in-bound for Ignite nodes?

[Jason]

hi Ignite team,

per my understanding, the below ports are necessary to be opened:

for server node:
1. TCP discovery: 47500
2. TCP communication: 47100
3. UDP discovery: 47400 (this can be closed if not use UDP? how?)
4. TCP rest: 11211 (this can be closed if not use http rest ? how?)
5. Share memory: 48100 (this can be closed if don't want to use shared
memory in the machine?)

for client node:
1. TCP communication: 47100

BTW, would you like to help give some description about the process of
failure detection of one node? or any guide link?

Thanks,
-Jason



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/If-firewall-how-many-ports-are-necessary-to-be-opened-for-in-bound-for-Ignite-nodes-tp6623.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Deadlock during Client Continuous Query deserialization

[ross.anderson]

Could you not use a hash of the remote filter predicates that the update
'passed' on the server to identify which local listeners to propagate to?

I appreciate the speedy response anyway guys. Have a good weekend.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Deadlock-during-Client-Continuous-Query-deserialization-tp6565p6622.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Deadlock during Client Continuous Query deserialization

[Alexey Goncharuk]

Ross,

The optimization you suggested does not work in the case when remote filter
is present, but it indeed works for your case. I created a ticket for this
optimization: https://issues.apache.org/jira/browse/IGNITE-3607



2016-07-29 17:51 GMT+03:00 ross.anderson :

> Glad to be of assistance
> I can confirm that setting the queue limit does resolve the initial problem
> of updates getting through, but one `put` is taking between 6 and 50
> seconds.
>
> Out of curiosity, shouldn't one of these cache update notifications be sent
> across the wire just once - and then multicast to the query listeners
> locally within the client process?
> Currently it seems to generate a lot of load - perhaps I need to rethink
> our
> use of continuous queries?
>
> Best,
> Ross
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Deadlock-during-Client-Continuous-Query-deserialization-tp6565p6620.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Deadlock during Client Continuous Query deserialization

[ross.anderson]

Glad to be of assistance
I can confirm that setting the queue limit does resolve the initial problem
of updates getting through, but one `put` is taking between 6 and 50
seconds.

Out of curiosity, shouldn't one of these cache update notifications be sent
across the wire just once - and then multicast to the query listeners
locally within the client process?
Currently it seems to generate a lot of load - perhaps I need to rethink our
use of continuous queries?

Best,
Ross



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Deadlock-during-Client-Continuous-Query-deserialization-tp6565p6620.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Error when trying to configure web session clustering

[mthompson]

Regarding environment, I am trying to run it on a Glassfish server, as that
is what we currently use. I'm willing to try another server if it is known
that ignite does not work with Glassfish.

*Web.xml*

http://java.sun.com/xml/ns/javaee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http:$
distributable/>


SecureIt
/*
PUT
OPTIONS
DELETE
TRACE


NoOne



IgniteWebSessionsFilter
   
org.apache.ignite.cache.websession.WebSessionFilter


ResponseOverrideFilter
   
org.displaytag.filter.ResponseOverrideFilter

   
IgniteWebSessionsFilter
/*
   

   IgniteConfigurationFilePath
   config/default-config.xml


   IgniteWebSessionsCacheName
   session-cache

   
ResponseOverrideFilter
*.do


ResponseOverrideFilter
*.jsp



   
org.apache.ignite.startup.servlet.ServletContextListenerStartup


AxisServlet

org.apache.axis.transport.http.AxisServlet



AdminServlet

org.apache.axis.transport.http.AdminServlet

100


SOAPMonitorService

org.apache.axis.monitor.SOAPMonitorService


SOAPMonitorPort
5001

100



action
   
org.apache.struts.action.ActionServlet

config
/WEB-INF/struts-config.xml
  


debug
0


detail
0


null
false

2




action
*.do


wsdl
text/xml


xsd
text/xml



index.jsp



Log can be found  here   



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Error-when-trying-to-configure-web-session-clustering-tp6596p6617.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Deadlock during Client Continuous Query deserialization

[ross.anderson]

Hi, has anyone had a chance to take a look at this? 
I'd imagine it's a critical issue if a client can cause a cluster to freeze
indefinitely based solely on a smallish number of queries running?
If there's anything else I can provide to assist please do let me know, as
this is a blocker for us using Ignite.
Thanks, Ross



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Deadlock-during-Client-Continuous-Query-deserialization-tp6565p6616.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

question about ignite key field mapping

[Zhengqingzheng]

Hi there,
I am confused with the key type mapping between java and jdbc.
Suppose I have a key defined with three elements/fields
Class AKey {
 Private  String  name;
Private  BigDecimal id;
Private  Object obj;
}
When I create cache, there are keytype mapping configurations like this:
   jdbcTypeFields[0] = (new JdbcTypeField(Types.VARCHAR, "NAME",
String.class, "name"));
Which will be used in CacheJdbcPojoStoreFactory.
But there is no Object mapping. So I did not create Object Mapping during set 
up key type mappings.

It is still okay to put and get data.

What kind of bugs it might be if I leave the key type mapping blank for my 
object field?

Best regards,
Kevin

Re: How to monitor the cache info?

[Jason]

Got it, thanks Alexey.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/How-to-monitor-the-cache-info-tp6515p6613.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How to monitor the cache info?

[Alexey Kuznetsov]

Jason,

>> so far, the Web console can only be hosted on GridGain servers, right? is
>> there any plan to open source it in the near future?

Configuration and SQL functionality of Web Console is open source since
ignite-1.6.

See ignite-web-console module:

https://github.com/gridgain/apache-ignite/blob/master/modules/web-console/README.txt

https://github.com/gridgain/apache-ignite/blob/master/modules/web-console/DEVNOTES.txt

Monitoring is developed as enterprise plugin. And available only via GridGain
servers for now.

>> BTW, it also uses JMX to get all the information of cluster and cache,
right?
No, Web Console uses Visor tasks that I mentioned in previous e-mail.

Thanks.

-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com