multicast fails with network interfaces instead of IP #214
Comments
|
How do you specify the |
|
I set |
|
No further reports of this in 3 years. Already fixed? Closing |
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
for multipart to work correctly you need to also include the necessary actions in the policy.
```json
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:GetBucketLocation",
"s3:ListBucketMultipartUploads",
"s3:ListBucketVersions"
],
"Resource": [
"arn:aws:s3:::yourbucket"
]
},
{
"Effect": "Allow",
"Action": [
"s3:PutObject",
"s3:GetObject",
"s3:DeleteObject",
"s3:PutObjectAcl",
"s3:AbortMultipartUpload",
"s3:ListMultipartUploadParts"
],
"Resource": [
"arn:aws:s3:::yourbucket/*"
]
}
]
}
```
Closes #214
(cherry picked from commit 62966ad)
(cherry picked from commit 25a37a5)
(cherry picked from commit e72af19)
Merged
37 tasks
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
Wit this commit we derive the race meta-data of the previous nightly and the current nightly and show a summary containing changes of all components (Elasticsearch, Rally, rally-tracks and rally-teams) with links to Github to simplify analysis of changes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment: two laptops on MacOSX 10.5 Leopard, in the same local network on Wifi (interface "en1"). The two laptops have virtual network devices (VMWare/Parallels/VirtualBox).
If don't give any configuration to elasticsearch, the two nodes do not discover each other.
If I set network.host to en1 on each host, I get these errors on the master http://pastie.org/995083
If I set network.host to the actual IPs, the two nodes go in the same cluster.
The text was updated successfully, but these errors were encountered: