one last question, is there an S3 connector for Ignite which can load s3
objects in realtime to ignite cache and data updates directly back to S3? I
can use spark as one alternative but is there another approach of doing?
Let's say I want to build in-memory near real-time data lake files which
Sorry for late response , your configuration looks correct. I hope
community ami will solve the problem.
-Himanshu
On Fri, Aug 9, 2019 at 11:07 AM sri hari kali charan Tummala <
kali.tumm...@gmail.com> wrote:
> the Blog has issue's the code which is in public s3 bucket doesn't exist
> so the
Thank you.
Actually I switched from Unicast to Multicast and it seems like it's working
fine. I was able to connect to the Cluster from my Client application,
however still having issues using JDBC connection.
It's a bit frustrating since Ignite recommends to run the Nodes in the
containers but
Hello!
This looks like a bug to me. Can you file a ticket against Apache Ignite
JIRA?
Otherwise, I recommend returning data structures by their name from
compute, as a workaround.
Regards,
--
Ilya Kasnacheev
пт, 9 авг. 2019 г. в 18:20, Niels Ejrnæs :
> Hello Ilya :)
>
>
>
> Here it is. It
the Blog has issue's the code which is in public s3 bucket doesn't exist so
the ec2 instance doesn't have to ignite at all I raised a concern with AWS
Blog team, I will try community ami Ignite ec2 instance or try to install
ignite on my own manually.
On Fri, Aug 9, 2019 at 11:20 AM sri hari kali
Please update documentation on
https://apacheignite.readme.io/docs/transactions#section-handling-failed-transactions
Andrey.
От: Andrei Aleksandrov
Отправлено: 9 августа 2019 г. в 18:35
Кому: user@ignite.apache.org
Тема: Re: TimeoutException not wrapped in CacheException
Hi,
Sorry, it's my
Hi,
Sorry, it's my fault.
I thought that you get TransactionTimeoutExceptionfrom from some
IgniteCache method. So it's not expected there.
From commit method you can't get the CacheException of course.
So I guess that you should handle only exceptions that mentioned in Java
Doc.
BR,
Hello
We're testing out Ignite and are running them in Docker as well. It's a bit
tricky to get to work.
Keep in mind that referencing localhost inside a docker container is pointing
them against their internal address. Not the host address of your machine. So
that's why they aren't
As I see In javadocs for org.apache.ignite.transactions.Transaction
/**
* Commits this transaction by initiating {@code two-phase-commit}
process.
*
* @throws IgniteException If commit failed.
* @throws TransactionTimeoutException If transaction is timed out.
*
Hello Ilya :)
Here it is. It contains two projects server-node and client-node. I'm gonna
have to rephrase what works and what doesn't. Now I can't even return the
AtomicLong/Reference objects through the compute task. I have to unpack them
first.
Run the main for ServerNode to start the
Sorry fo misprint, test does not check that there are no any way to get
TimeoutException
On Fri, Aug 9, 2019 at 5:55 PM Andrey Davydov
wrote:
> It is a little bit difficult to reproduce. We got unhadled exception on
> pre prod performance test of our system. I will try to reproduce it on
>
give me couple of minutes I think I opened 0 to 65000 ports for inbound
thats it , if I have to open all these ports separately I have to give a
try.
On Fri, Aug 9, 2019 at 10:55 AM Himanshu Gupta
wrote:
> Can you share screenshot of your inbound traffic setting, I think it need
> to be
It is a little bit difficult to reproduce. We got unhadled exception on pre
prod performance test of our system. I will try to reproduce it on weekend.
You test just check that if you get CacheException then TimeoutException is
inside it, but doesn't check that there are no any way to get
Can you share screenshot of your inbound traffic setting, I think it need
to be something like this
Example:
Inbound:
Custom TCP Rule TCP 10800 - 10900 0.0.0.0/0 client
Custom TCP Rule TCP 47500 - 47600 0.0.0.0/0 discovery
Custom TCP Rule TCP 47100 - 47200 0.0.0.0/0 communication
Outbound:
All
yes, all traffic inbound and outbound (TCP), I am able to do ssh also I am
able to ping public ip address from my laptop and the Ec2 instance is able
to ping the www.amazon.com.
On Fri, Aug 9, 2019 at 10:46 AM Himanshu Gupta
wrote:
> Did you open the ports on EC2 at which your ignite cluster
Did you open the ports on EC2 at which your ignite cluster is running?
On Fri, Aug 9, 2019 at 8:50 AM sri hari kali charan Tummala <
kali.tumm...@gmail.com> wrote:
> Hi,
>
> thanks for replying I am following the below blog as per some expert
> suggestion he asked me to use my laptop ip address
Hi,
It looks strange because even Ignite tests expect that
TransactionTimeoutException will be wrapped in CacheException. For
example IgniteTxConfigCacheSelfTest:
try (final Transaction tx = ignite.transactions().txStart()) {
assert tx != null;
On ignite 2.7.5 I got TransactionTimeoutException not wrapped
in CacheException. If it is normal behaviour and I should catch
TransactionTimeoutException too. My current logic is to
catch CacheException and check CacheException.getCause() if it
was TransactionTimeoutException.
Thanks.
Full
Hi,
thanks for replying I am following the below blog as per some expert
suggestion he asked me to use my laptop ip address and elastic ip address
of Ec2 instance (
Hello!
In my experience, on EC2 nodes usually use internal network to talk to each
other. They will advertise these to any nodes trying to connect, which will
cause issues.
Is it an option for you to use some flavor of Thin Client to talk to your
cluster? We do not recommend having heterogenous,
Hi,
Spark contains several *SaveModes *that will be applied if the table
that you are going to use exists:
* *Overwrite *- with this option you *will try to re-create* existed
table or create new and load data there using IgniteDataStreamer
implementation
* *Append *- with this option you
21 matches
Mail list logo
