Lukas, would you be so kind as to suggest edits for the mentioned
documentation page. Your suggesions will be reviewed and incorporated.
Thanks!
--Yakov
We've changed our code to use IgniteConfiguration#setLocalEventListeners
instead and it works fine, so at this point we don't need to get the pull
request accepted. However, if you think it will be useful, I don't mind
finishing the work.
Yakov, should I create a bug for the documentation update?
I think there should be a link on the page - Suggest edits
--Yakov
Well, yes, this looks like a simplest solution. Let's implement it for the
beginning and set this feature to "false" by default, as this feature looks
complex, probably error-prone, and should be considered in a "beta"
state for the first release.
Best Regards,
Igor
On Mon, Mar 11, 2019 at 8:04
For the "false" I mean "disable" here.
BTW, I believe we should name this parameter in a positive way:
EnableAffinityAwareness, not disable.
Best Regards,
Igor
On Wed, Mar 13, 2019 at 12:50 PM Igor Sapego wrote:
> Well, yes, this looks like a simplest solution. Let's implement it for the
> be
Sergey Antonov created IGNITE-11536:
---
Summary: Add information about possible long GC pause to
checkpoint started message.
Key: IGNITE-11536
URL: https://issues.apache.org/jira/browse/IGNITE-11536
P
Taras Ledkov created IGNITE-11537:
-
Summary: SQL: enchanced log mode for SQL queries
Key: IGNITE-11537
URL: https://issues.apache.org/jira/browse/IGNITE-11537
Project: Ignite
Issue Type: Task
Pavel Kuznetsov created IGNITE-11538:
Summary: SQL: Support new features (precision, scale, etc) in JDBC
drivers
Key: IGNITE-11538
URL: https://issues.apache.org/jira/browse/IGNITE-11538
Project:
Vyacheslav Daradur created IGNITE-11539:
---
Summary: Document services hot redeployment via DeploymentSpi
Key: IGNITE-11539
URL: https://issues.apache.org/jira/browse/IGNITE-11539
Project: Ignite
Default value for boolean is false, and I though we'll have the feature
enabled by default.
But I agree with you. Let's disable by default and name the config property
EnableAffinityAwareness.
On Wed, Mar 13, 2019 at 12:52 PM Igor Sapego wrote:
> For the "false" I mean "disable" here.
>
> BTW, I
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to finalize
Hi Team,
I was using ignite as dependecy in our application and was able to trace end to
end trace microservice calls.
Then, to let ignite handle our services in compute task, we removed all
spring-boot dependencies and created task for each service we had in our
microservice.
The issue we ar
Hi,
As far as I remember zipkin defines tracing units in a current thread
of execution. I cannot say for sure what goes wrong in your case. But
it might be that traced execution on ser3 side switches from one
thread to another and you see 2 units as a result.
чт, 14 мар. 2019 г. в 02:09, Aditya K
13 matches
Mail list logo
