Hello,
My name is Amit Chavan and I am just starting to use Ignite and play around
with it. I really appreciate the work this community has done for the
project. I also wanted to help contribute to the project. Is Jira board the
best place to seek any issues to work on?
Thanks,
Amit
Ok, I updated the docs saying that
"4. Add the following VM options to your Java applications. That's not
needed if you use Java thin clients or Ignite JDBC."
https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
-
Denis
On Thu, Aug 22, 2019 at 9:30 AM
Ivan, Alex Goncharuk,
The exception trace is not helpful, it's not obvious what might be a reason
and how to address it. How do we tackle these problems?
Ibrahim, please attach all the log files for a detailed look.
-
Denis
On Thu, Aug 22, 2019 at 3:08 AM ihalilaltun
wrote:
> Hi folks,
>
>
+1
-
Denis
On Thu, Aug 22, 2019 at 10:12 AM Dmitriy Pavlov wrote:
> Dear Community,
>
> I have uploaded release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/2.7.6-rc1/
> https://dist.apache.org/repos/dist/dev/ignite/packages_2.7.6-rc1/
>
> The following staging can be used for
Hi Igniters,
feel free to use this thread for all non-voting discussions or questions
related to release 2.7.6
Please cast your vote in thread after checking the release
https://www.apache.org/info/verification.html
at topic
Dear Community,
I have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.7.6-rc1/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.7.6-rc1/
The following staging can be used for any dependent project for testing:
Denis,
I didn’t find any usages of JDK internals in the implementation of the thin
clients.
It would be nice to verify in tests that thin clients can work without these
flags.
Do our Java 9/10/11 tests include thin client testing? If so, do these tests
include these flags?
Denis
On 15 Aug
Thanks, Denis! We'll take a look at those doc issues and create tickets
soon.
-g-
===
Garrett Alley
Documentation
GridGain Systems
On Thu, Aug 22, 2019 at 8:30 AM Denis Mekhanikov
wrote:
> Hi everyone!
>
> The following threads created last week address potential issues in the
> product.
>
Hello,
As I see, the community guys stepped in and ready to help with this problem
via this discussion:
http://apache-ignite-users.70518.x6.nabble.com/One-of-Ignite-pod-keeps-crashing-and-not-joining-the-cluster-td29091.html#a29105
Please check out that response that clarifies why the method you
Alexey,
Making only one node write metadata to disk synchronously is a possible and
easy to implement solution, but it still has a few drawbacks:
• Discovery will still be blocked on one node. This is better than blocking all
nodes one by one, but disk write may take indefinite time, so
Dmitriy, Thanks!
В Чт, 22/08/2019 в 15:09 +0300, Dmitriy Pavlov пишет:
> Hi Igniters,
>
> A number of updates were applied to the process description. Feedback is as
> always welcomed.
>
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
>
> I can't name it final cause I find
Hi Igniters,
A number of updates were applied to the process description. Feedback is as
always welcomed.
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
I can't name it final cause I find some issues from time to time. But it is
near to be a full description.
Sincerely,
Denis Mekhanikov,
I think at least one node (coordinator for example) still should write
metadata synchronously to protect from a scenario:
tx creating new metadata is commited <- all nodes in grid are failed
(powered off) <- async writing to disk is completed
where <- means "happens before"
Pavel Tupitsyn created IGNITE-12095:
---
Summary: .NET: Remove empty tracing-related interfaces from public
API
Key: IGNITE-12095
URL: https://issues.apache.org/jira/browse/IGNITE-12095
Project:
Dmitry Sterinzat created IGNITE-12094:
-
Summary: Scan Query scheduled to be executed on wrong node
Key: IGNITE-12094
URL: https://issues.apache.org/jira/browse/IGNITE-12094
Project: Ignite
15 matches
Mail list logo
