-
-
Notifications
You must be signed in to change notification settings - Fork 420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only a warning com.hazelcast.spi.impl.operationservice.impl.Invocation. Minor #503
Comments
wow, that is evil Allright most peolple nowadays may not react that alarmed, but I don't care. We cannot use phoning-home software in YaCy. Hazelcast was interesting for the possible purpose to interconnect local YaCy instances, but this is not acceptable. |
I would not now where to start to remove it but I will have a look. |
I tried removing from the lib but yacy wont start. |
Thats a good tool, if you encounter any other phone-home please let me know. |
add metadata.google.internal to the list. I will block these with a regex herokuapp.com see what happens. Google maybe? |
removed hazelcast, see also #504 I don't know what is calling metadata.google.internal, please open another issue if you found out what it calls |
W 2022/09/28 16:41:42 com.hazelcast.spi.impl.operationservice.impl.Invocation [192.168.1.20]:5701 [YaCyP2P] [4.2] Retrying invocation: Invocation{op=com.hazelcast.cp.internal.operation.RaftQueryOp{serviceName='hz:core:raft', identityHash=202548218, partitionId=0, replicaIndex=0, callId=6789, invocationTime=1664354504244 (2022-09-28 16:41:44.244), waitTimeout=-1, callTimeout=60000, tenantControl=com.hazelcast.spi.impl.tenantcontrol.NoopTenantControl@0, op=com.hazelcast.cp.internal.raftop.metadata.GetRaftGroupOp{serviceName='hz:core:raft', targetGroupId=CPGroupId{name='METADATA', seed=0, groupId=0}}, groupId=CPGroupId{name='METADATA', seed=0, groupId=0}, policy=LEADER_LOCAL}, tryCount=250, tryPauseMillis=500, invokeCount=220, callTimeoutMillis=60000, firstInvocationTimeMs=1664354423832, firstInvocationTime='2022-09-28 16:40:23.832', lastHeartbeatMillis=0, lastHeartbeatTime='1970-01-01 08:00:00.000', target=null, pendingResponse={VOID}, backupsAcksExpected=-1, backupsAcksReceived=0, connection=null}, Reason: com.hazelcast.spi.exception.WrongTargetException: WrongTarget! local: Member [192.168.1.20]:5701 - 75f3d9c5-8368-4c29-8fe2-26e36dd00091 this, expected-target: null, partitionId: 0, replicaIndex: 0, operation: com.hazelcast.cp.internal.operation.RaftQueryOp, service: hz:core:raft
Windows 11
Java 19
old I7 laptop 16 GB
YaCy 1.925/9749
Pihole Pi-hole v5.12.2 FTL v5.18.1 Web Interface v5.15.1
There is DNS Requests to Domain phonehome.hazelcast.com being answered.
I tried blocking it but this still happened.
W 2022/09/28 16:53:11 com.hazelcast.spi.impl.operationservice.impl.Invocation [192.168.1.20]:5701 [YaCyP2P] [4.2] Retrying invocation: Invocation{op=com.hazelcast.cp.internal.operation.RaftQueryOp{serviceName='hz:core:raft', identityHash=2060613243, partitionId=0, replicaIndex=0, callId=75713, invocationTime=1664355193392 (2022-09-28 16:53:13.392), waitTimeout=-1, callTimeout=60000, tenantControl=com.hazelcast.spi.impl.tenantcontrol.NoopTenantControl@0, op=com.hazelcast.cp.internal.raftop.metadata.GetRaftGroupOp{serviceName='hz:core:raft', targetGroupId=CPGroupId{name='METADATA', seed=0, groupId=0}}, groupId=CPGroupId{name='METADATA', seed=0, groupId=0}, policy=LEADER_LOCAL}, tryCount=250, tryPauseMillis=500, invokeCount=230, callTimeoutMillis=60000, firstInvocationTimeMs=1664355109089, firstInvocationTime='2022-09-28 16:51:49.089', lastHeartbeatMillis=0, lastHeartbeatTime='1970-01-01 08:00:00.000', target=null, pendingResponse={VOID}, backupsAcksExpected=-1, backupsAcksReceived=0, connection=null}, Reason: com.hazelcast.spi.exception.WrongTargetException: WrongTarget! local: Member [192.168.1.20]:5701 - 75f3d9c5-8368-4c29-8fe2-26e36dd00091 this, expected-target: null, partitionId: 0, replicaIndex: 0, operation: com.hazelcast.cp.internal.operation.RaftQueryOp, service: hz:core:raft
Thanks.
The text was updated successfully, but these errors were encountered: