Re: Zookeeper Discovery SPI & external IP address in AWS

Igor, You need to investigate deeper then. It's not obvious what's going on and why there is an issue. -Val On Mon, Jun 26, 2017 at 3:36 PM, Igor Rudyak wrote: > I am 100% sure, cause "*telnet11211*" works just perfect. > > Igor > > On Mon, Jun 26, 2017 at 3:32 PM,

Re: Zookeeper Discovery SPI & external IP address in AWS

I am 100% sure, cause "*telnet11211*" works just perfect. Igor On Mon, Jun 26, 2017 at 3:32 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Igor, > > Are you sure these connections are not blocked by firewall? If you provide > addresses explicitly in static IP finder,

Re: Zookeeper Discovery SPI & external IP address in AWS

Igor, Are you sure these connections are not blocked by firewall? If you provide addresses explicitly in static IP finder, then it doesn't matter what is published in shared IP finder. Is it possible that public addresses are actually published and connectivity issue is caused by something else?

Re: Zookeeper Discovery SPI & external IP address in AWS

Igor, It depends on how address resolver works. But I agree, in general case it's possible that a node can only resolve public address for itself. In such scenario we must publish public addresses in IP finder. -Val On Mon, Jun 26, 2017 at 1:02 PM, Igor Rudyak wrote: >

Re: Zookeeper Discovery SPI & external IP address in AWS

Option 2 also will not work for IaaS environments, where node can dynamically join or leave cluster. Igor On Jun 26, 2017 12:12 PM, "Valentin Kulichenko" < valentin.kuliche...@gmail.com> wrote: > Yakov, > > Nodes that join outside of the network (usually these are clients) need to > know public

Re: IgniteCache#localEvict method

Created ticket: https://issues.apache.org/jira/browse/IGNITE-5592 -Val On Sun, Jun 25, 2017 at 7:49 AM, Ivan Rakov wrote: > Agree as well. > > Best Regards, > Ivan Rakov > > On 22.06.2017 1:23, Valentin Kulichenko wrote: > > I agree. Ivan, do you have objections? > >

[jira] [Created] (IGNITE-5592) Remove IgniteCache#localEvict method

Valentin Kulichenko created IGNITE-5592: --- Summary: Remove IgniteCache#localEvict method Key: IGNITE-5592 URL: https://issues.apache.org/jira/browse/IGNITE-5592 Project: Ignite Issue

Re: Zookeeper Discovery SPI & external IP address in AWS

Yakov, Nodes that join outside of the network (usually these are clients) need to know public addresses to connect. To make it work either of these must happen: 1. Server nodes publish their public addresses in IP finder so that clients can use them to connect. 2. Client nodes use address

New Member

Hello guys, I'm a computer engineer and recently joined the ignite dev community. My Jira user is "caio.nishibe" and I need some help with the permissions. Thank you! Best regards, Caio -- View this message in context:

[GitHub] ignite pull request #2198: Ignite 5591: WAL QueueFlusher replaced with sched...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/2198 Ignite 5591: WAL QueueFlusher replaced with schedule() method You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2191: Ignite-1.8.8-b1

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/2191 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[jira] [Created] (IGNITE-5591) WAL queue flusher for background mode can be replaced with Timeout processor

Dmitriy Pavlov created IGNITE-5591: -- Summary: WAL queue flusher for background mode can be replaced with Timeout processor Key: IGNITE-5591 URL: https://issues.apache.org/jira/browse/IGNITE-5591

[GitHub] ignite pull request #2197: IGNITE-GG-12330 Fixed cache & group destroying

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/2197 IGNITE-GG-12330 Fixed cache & group destroying You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12330

Re: I am a new Ignite Development Community member

Hi, Alexey! I added you to Ignite JIRA. Looking forward for your contributions! On Fri, Jun 23, 2017 at 6:58 PM, Alexey Kukushkin < alexeykukush...@yahoo.com.invalid> wrote: > Dear Ignite Development Community, > I am a software engineer and joined the community to contribute to the > product.

Re: GridCacheAdapter#size() has O(n) complexity

On Mon, Jun 26, 2017 at 2:31 AM, Yakov Zhdanov wrote: > Guys, I see little inconsistency. Imagine user does 1000 puts with near > cache enabled. Then user does some gets() and size() returns 1000 + N, more > gets() and size() is 1000 + M. This is a bit weird. Can we have

[GitHub] ignite pull request #2196: Ignite 5587: Generate File WAL Segment Archive Co...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/2196 Ignite 5587: Generate File WAL Segment Archive Completed Event Don't merge, this PR is in progresss You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2195: Add unit-test for https://issues.apache.org/jira/...

GitHub user onishkov opened a pull request: https://github.com/apache/ignite/pull/2195 Add unit-test for https://issues.apache.org/jira/browse/IGNITE-3935 Added unit-test corresponding to the problem https://issues.apache.org/jira/browse/IGNITE-3935 (ClassLoaders are not switched

[jira] [Created] (IGNITE-5590) Physical and logical caches wtih the same amount of data have different storage size

Ksenia Rybakova created IGNITE-5590: --- Summary: Physical and logical caches wtih the same amount of data have different storage size Key: IGNITE-5590 URL: https://issues.apache.org/jira/browse/IGNITE-5590

[GitHub] ignite pull request #2194: Ignite 5076 1

GitHub user sk0x50 opened a pull request: https://github.com/apache/ignite/pull/2194 Ignite 5076 1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/sk0x50/ignite ignite-5076-1 Alternatively you can review and apply these changes

[GitHub] ignite pull request #2193: IGNITE-5468

GitHub user BiryukovVA opened a pull request: https://github.com/apache/ignite/pull/2193 IGNITE-5468 IGNITE-5468: Added the ability to set IGNITE_SQL_MERGE_TABLE_MAX_SIZE and IGNITE_SQL_MERGE_TABLE_PREFETCH_SIZE via cache configuration You can merge this pull request into a Git

[jira] [Created] (IGNITE-5589) Archive WAL segment after significiant period of grid inactivity

Dmitriy Pavlov created IGNITE-5589: -- Summary: Archive WAL segment after significiant period of grid inactivity Key: IGNITE-5589 URL: https://issues.apache.org/jira/browse/IGNITE-5589 Project: Ignite

[jira] [Created] (IGNITE-5588) .NET: InstanceResourceAttribute does not work in scan queries

Pavel Tupitsyn created IGNITE-5588: -- Summary: .NET: InstanceResourceAttribute does not work in scan queries Key: IGNITE-5588 URL: https://issues.apache.org/jira/browse/IGNITE-5588 Project: Ignite

Re: Transparent Data Encryption (TDE) in Apache Ignite

No, we don't have plans for it. Sergi 2017-06-26 14:20 GMT+03:00 Vyacheslav Daradur : > Sergi, thanks for the answer. > > >> see TDE is just an option for PCI DSS compliancy but not a requirement. > Requirement: "Protect stored cardholder data" > Encryption is required. >

Re: Transparent Data Encryption (TDE) in Apache Ignite

Sergi, thanks for the answer. >> see TDE is just an option for PCI DSS compliancy but not a requirement. Requirement: "Protect stored cardholder data" Encryption is required. TDE - is one of ways to implement it at the database level. Sure, an implementation at the application level solve it. I

Re: Transparent Data Encryption (TDE) in Apache Ignite

I think no one is interested in this stuff right now. Also as far as I see TDE is just an option for PCI DSS compliancy but not a requirement. Your system should pass PCI DSS if you will do the required encryption at the application level and will properly manage encryption keys. Sergi

Re: Transaction Boundary - Data Streamer

Done. Revision hash ec9d47b197738459b7721d5b393f5be223cd76e0 --Yakov

[jira] [Created] (IGNITE-5587) Generate File WAL Segment Archive Completed Event

Dmitriy Pavlov created IGNITE-5587: -- Summary: Generate File WAL Segment Archive Completed Event Key: IGNITE-5587 URL: https://issues.apache.org/jira/browse/IGNITE-5587 Project: Ignite Issue

Re: Zookeeper Discovery SPI & external IP address in AWS

Guys, I don't get the point. 1. Why addresses processed by address resolver should appear in shared finder? In my understanding finders contain only internal IPs which should be processed by a resolver. 2. This one is very critical. Nikolay and Anton, how can I review the changes?! Please update

Re: Ignite JDBC and "Runnable tasks outlived thread pool executor service"

Igor, can you please share the reproducer? This message is printed only when Ignite node or internal client stops with active tasks in internal pools. Stop may occur due to GC pause. Please give more details. --Yakov

Re: place for printing info about partition distribution

Vadim, we don't have FairAffinity any more. Can you please provide brief and descriptive format for this message. I think we should print the message on exchange finish before rebalancing procedure start. --Yakov

Re: Replace Cron4J with Quartz for ignite-schedule module.

Guys, I remember we discussed this some time ago. http://apache-ignite-developers.2346864.n4.nabble.com/Tasks-Scheduling-and-Chaining-td14293.html Denis, do you have any ticket or SoW? --Yakov

[GitHub] ignite pull request #2192: fix metadata update

GitHub user sboikov opened a pull request: https://github.com/apache/ignite/pull/2192 fix metadata update You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite gg-12133 Alternatively you can review and apply

Re: GridCacheAdapter#size() has O(n) complexity

Guys, I see little inconsistency. Imagine user does 1000 puts with near cache enabled. Then user does some gets() and size() returns 1000 + N, more gets() and size() is 1000 + M. This is a bit weird. Can we have nearSize() on public API? Any thoughts here? As far as the original issue I would not

[jira] [Created] (IGNITE-5586) Visor CMD: Add possibility to activate/deactivate grid

Vasiliy Sisko created IGNITE-5586: - Summary: Visor CMD: Add possibility to activate/deactivate grid Key: IGNITE-5586 URL: https://issues.apache.org/jira/browse/IGNITE-5586 Project: Ignite

[jira] [Created] (IGNITE-5585) NPE at CacheContinuousQueryManager.skipUpdateEvent during load test

Ksenia Rybakova created IGNITE-5585: --- Summary: NPE at CacheContinuousQueryManager.skipUpdateEvent during load test Key: IGNITE-5585 URL: https://issues.apache.org/jira/browse/IGNITE-5585 Project:

Re: Transparent Data Encryption (TDE) in Apache Ignite

Guys, any thoughts? 2017-06-20 11:02 GMT+03:00 Vyacheslav Daradur : > Hi Igniters. > > I have some user cases where I need fast storage with TDE support. > It is requered for PCI DSS certification. > > As far as I know AI doesn't support it. > > I looked at other storages. >

[jira] [Created] (IGNITE-5584) Exception on grid activation on daemon node

Vasiliy Sisko created IGNITE-5584: - Summary: Exception on grid activation on daemon node Key: IGNITE-5584 URL: https://issues.apache.org/jira/browse/IGNITE-5584 Project: Ignite Issue Type: