[jira] [Updated] (IGNITE-14908) Remove non-inclusive terms in Ignite
[
https://issues.apache.org/jira/browse/IGNITE-14908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishwas updated IGNITE-14908:
-
Description:
Ignite has non inclusive words like blacklist/whitelist.
{code:java}
public static final String IGNITE_MARSHALLER_WHITELIST =
"IGNITE_MARSHALLER_WHITELIST";
public static final String IGNITE_MARSHALLER_BLACKLIST =
"IGNITE_MARSHALLER_BLACKLIST";
{code}
All these references needs to be removed from ignite and needs to be replaced
with more inclusive terms.
was:
Ignite has non inclusive words like blacklist/whitelist.
{code:java}
public static final String IGNITE_MARSHALLER_WHITELIST =
"IGNITE_MARSHALLER_WHITELIST";
public static final String IGNITE_MARSHALLER_BLACKLIST =
"IGNITE_MARSHALLER_BLACKLIST";
{code}
All these references needs to be removed from ignite and needs to be replaced
with more inclusive terms.
> Remove non-inclusive terms in Ignite
>
>
> Key: IGNITE-14908
> URL: https://issues.apache.org/jira/browse/IGNITE-14908
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.10
>Reporter: Vishwas
>Priority: Major
>
> Ignite has non inclusive words like blacklist/whitelist.
> {code:java}
> public static final String IGNITE_MARSHALLER_WHITELIST =
> "IGNITE_MARSHALLER_WHITELIST";
> public static final String IGNITE_MARSHALLER_BLACKLIST =
> "IGNITE_MARSHALLER_BLACKLIST";
> {code}
> All these references needs to be removed from ignite and needs to be replaced
> with more inclusive terms.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14908) Remove non-inclusive terms in Ignite
Vishwas created IGNITE-14908:
Summary: Remove non-inclusive terms in Ignite
Key: IGNITE-14908
URL: https://issues.apache.org/jira/browse/IGNITE-14908
Project: Ignite
Issue Type: Improvement
Affects Versions: 2.10
Reporter: Vishwas
Ignite has non inclusive words like blacklist/whitelist.
{code:java}
public static final String IGNITE_MARSHALLER_WHITELIST =
"IGNITE_MARSHALLER_WHITELIST";
public static final String IGNITE_MARSHALLER_BLACKLIST =
"IGNITE_MARSHALLER_BLACKLIST";
{code}
All these references needs to be removed from ignite and needs to be replaced
with more inclusive terms.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13912) Incorrect calculation of WAL segments that should be deleted from WAL archive
[ https://issues.apache.org/jira/browse/IGNITE-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17266723#comment-17266723 ] Vishwas commented on IGNITE-13912: -- Hi [~ktkale...@gridgain.com]/ [~akalashnikov] , In our testing with [2.10 branch|https://github.com/apache/ignite/tree/ignite-2.10], we have hit the same issue in our k8s environment. I see the fix for this is marked for 2.11, can this be included in 2.10 branch ? > Incorrect calculation of WAL segments that should be deleted from WAL archive > - > > Key: IGNITE-13912 > URL: https://issues.apache.org/jira/browse/IGNITE-13912 > Project: Ignite > Issue Type: Bug > Components: persistence >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Critical > Fix For: 2.11 > > Attachments: wal_usage_dec12.PNG, wal_usage_dec22nd_binary.PNG > > Time Spent: 10m > Remaining Estimate: 0h > > Now there is an incorrect calculation of WAL segments that should be deleted > from WAL archive. Since we delete only those segments whose total size should > not exceed *DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*, but should be up to > DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*. Therefore, an excess of > *DataStorageConfiguration#maxWalArchiveSize* occurs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13974) onDisconnected() method does not get called for thinClient on "kubectl delete pod"
Vishwas created IGNITE-13974:
Summary: onDisconnected() method does not get called for
thinClient on "kubectl delete pod"
Key: IGNITE-13974
URL: https://issues.apache.org/jira/browse/IGNITE-13974
Project: Ignite
Issue Type: Bug
Components: jdbc, thin client
Affects Versions: 2.9
Environment: k8s
Reporter: Vishwas
Below is the test I am performing:
1) Bring up ignite on k8s cluster 2 pods of Ignite server are running.
2) Connect via sqlline to the Ignite Cluster (connect via k8s service):
{code:java}
./sqlline.sh --verbose=true -u
"jdbc:ignite:thin://ignite-service.ignite.svc.cluster.local:10800" -n test_user
-p test_user
{code}
3) Restart the pod on which sqlline connection is made
{code:java}
kubectl delete pod
{code}
4) *Observation ClientListenerAbstractConnectionContext.onDisconnected() is not
getting called.*
*This causes leak of the authenticationContext as onSessionExpired method does
not get called.*
+Note:+
When I tried the same scenario on a windows machine, I did not hit the issue
and the onDisconnected() method is getting called.
For step 3 above, I connected to ignite visor and ran the kill -k command on
windows.
When I ran the same kill -k command on k8s cluster from visor, I do not see
this issue.
What should be the behaviour when "kubectl delete pod" is triggered ? I think
onDisconnected() should get called.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13974) onDisconnected() method does not get called for thinClient on "kubectl delete pod"
[
https://issues.apache.org/jira/browse/IGNITE-13974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishwas updated IGNITE-13974:
-
Affects Version/s: 2.9.1
> onDisconnected() method does not get called for thinClient on "kubectl delete
> pod"
> --
>
> Key: IGNITE-13974
> URL: https://issues.apache.org/jira/browse/IGNITE-13974
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, thin client
>Affects Versions: 2.9, 2.9.1
> Environment: k8s
>Reporter: Vishwas
>Priority: Major
>
> Below is the test I am performing:
> 1) Bring up ignite on k8s cluster 2 pods of Ignite server are running.
> 2) Connect via sqlline to the Ignite Cluster (connect via k8s service):
> {code:java}
> ./sqlline.sh --verbose=true -u
> "jdbc:ignite:thin://ignite-service.ignite.svc.cluster.local:10800" -n
> test_user -p test_user
> {code}
> 3) Restart the pod on which sqlline connection is made
> {code:java}
> kubectl delete pod
> {code}
> 4) *Observation ClientListenerAbstractConnectionContext.onDisconnected() is
> not getting called.*
> *This causes leak of the authenticationContext as onSessionExpired method
> does not get called.*
>
> +Note:+
> When I tried the same scenario on a windows machine, I did not hit the issue
> and the onDisconnected() method is getting called.
> For step 3 above, I connected to ignite visor and ran the kill -k command on
> windows.
> When I ran the same kill -k command on k8s cluster from visor, I do not see
> this issue.
>
> What should be the behaviour when "kubectl delete pod" is triggered ? I think
> onDisconnected() should get called.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13112) The current security context should be obtained using the IgniteSecurity interface only.
[ https://issues.apache.org/jira/browse/IGNITE-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244513#comment-17244513 ] Vishwas commented on IGNITE-13112: -- Hi [~garus.d.g] I see this ticket is labeled with iep-41 and related to IGNITE-12781 Does it mean all the securityCtx propogation needed for iep-41 will be present in 2.10 release ? > The current security context should be obtained using the IgniteSecurity > interface only. > > > Key: IGNITE-13112 > URL: https://issues.apache.org/jira/browse/IGNITE-13112 > Project: Ignite > Issue Type: Bug > Components: cache, security >Affects Versions: 2.8.1 >Reporter: Denis Garus >Assignee: Denis Garus >Priority: Major > Labels: iep-41 > Fix For: 2.10 > > Time Spent: 4h 40m > Remaining Estimate: 0h > > For getting the current security context, we have to use the IgniteSecurity > interface only. > We need to get rid of all other ways to transfer a security subject id. -- This message was sent by Atlassian Jira (v8.3.4#803005)
