Skip to main content
Version: 5.7

Filtering members with attributes

You can define various member attributes on your Hazelcast members. You can use these member attributes to tag your members as your business logic requires.

To define a member attribute on a member, provide MemberAttributeConfig to your Config object. You cannot change member attributes after the member starts.

For example, you can tag your members with their CPU characteristics, and route CPU-intensive tasks to those CPU-rich members:

java
public class ExampleMemberAttributes {

public static void main(String[] args) {
MemberAttributeConfig fourCore = new MemberAttributeConfig();
fourCore.setAttribute( "CPU_CORE_COUNT", "4" );
MemberAttributeConfig twelveCore = new MemberAttributeConfig();
twelveCore.setAttribute( "CPU_CORE_COUNT", "12" );
MemberAttributeConfig twentyFourCore = new MemberAttributeConfig();
twentyFourCore.setAttribute( "CPU_CORE_COUNT", "24" );

Config member1Config = new Config();
member1Config.setMemberAttributeConfig( fourCore );
Config member2Config = new Config();
member2Config.setMemberAttributeConfig( twelveCore );
Config member3Config = new Config();
member3Config.setMemberAttributeConfig( twentyFourCore );

HazelcastInstance member1 = Hazelcast.newHazelcastInstance( member1Config );
HazelcastInstance member2 = Hazelcast.newHazelcastInstance( member2Config );
HazelcastInstance member3 = Hazelcast.newHazelcastInstance( member3Config );

IExecutorService executorService = member1.getExecutorService( "processor" );

executorService.execute( new CPUIntensiveTask(), new MemberSelector() {
@Override
public boolean select(Member member) {
int coreCount = Integer.parseInt(member.getAttribute( "CPU_CORE_COUNT" ));
// Task will be executed at either member2 or member3
if ( coreCount > 8 ) {
return true;
}
return false;
}
} );
}
}

For another example, you can tag some members with a filter so that a member in the cluster can load classes from those tagged members. See the User Code Deployment section for more information.

Declarative configuration​

You can also define member attributes through declarative configuration, and start your member afterward:

xml
<hazelcast>
...
<member-attributes>
<attribute name="CPU_CORE_COUNT">4</attribute>
</member-attributes>
...
</hazelcast>